|Main page||Software Security Checklist||Issue Handling||Advisories||Notes On Risk||Advisory Template||More|
The EGI Software Vulnerability Group (SVG)
The purpose of the EGI Software Vulnerability Group is to eliminate existing vulnerabilities from the deployed infrastructure, primarily from the grid middleware, prevent the introduction of new ones and prevent security incidents
- Terms of Reference (draft)
Main Tasks of the EGI Software Vulnerability Group
- Provide an efficient process to report, handle, and resolve software vulnerabilities found in middleware.
This is expected to be the largest activity of the EGI SVG.
- Provide consultation on software vulnerabilities to the CSIRT team and other EGI groups.
- Collaborate with other partners to assess software provided in the EGI Unified Middleware Distribution and to look for vulnerabilities.
- Encourage developers to write secure code, thus reducing the likelihood of future problems, by education and awareness.
If a vulnerability has been exploited, it is an incident. You should then follow the EGI CSIRT incident Handling procedure EGI CSIRT incident Handling procedure. Also see the [EGI_CSIRT:Incident_reporting | EGI CSIRT Incident Reporting Wiki ]
What to do if you find a Software Vulnerability in the EGI infrastructure
You should follow the EGI Software Vulnerability Handling Issue process EGI Software Vulnerability Handling Issue process pdf-file
DO NOT discuss on a mailing list - especially one with an open subsription policy or public archive
DO NOT post information on a web page
DO NOT publicise in any way - e.g. to the media
IMMEDIATELY Report it to report-vulnerability (at) egi.eu
The Software Vulnerability Issue Handling process
The EGI Software Vulnerability issue handling summary contains a brief summary of the issue handling process, and links to further information.
The Issue handling process document which as been approved by the project executive board as part of the EGI milestone MS405 is also available at
Vulnerability Assessment is the proactive examination of software in order to find vulnerabilities that may exist.
The SVG also encourages developers to write Secure Code Secure Coding