|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|Documentation menu:||Home •||Manuals •||Procedures •||Training •||Other •||Contact ►||For:||VO managers •||Administrators|
|This page is under construction.|
|Policy Group Acronym||OMB|
|Policy Group Name||Operations Management Board|
|Contact Group||operations at mailman.egi.eu|
|Owner||Owner of procedure|
The EGI Software Vulnerability issue handling procedure is described in EGI Software Vulnerability Issue Handling Process the current version was approved by the EGI OMB in November 2017.
At present (8th December 2017) this document has not been translated to this wiki.
A summary of the procedure is available on the EGI SVG wiki at issue handling summary
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Entities involved in the procedure
- XX: person who...
The following table describes
|Step#||Responsible||Action||Prerequisites, if any|