SEC02
Jump to navigation
Jump to search
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. |
Title | ' |
Document link | |
Last modified | |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations at mailman.egi.eu |
Document Status | |
Approved Date | |
Procedure Statement | |
Owner | Owner of procedure |
Overview
The EGI Software Vulnerability issue handling procedure is described in EGI Software Vulnerability Issue Handling Process which is approved by the EGI OMB.
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
Definitions
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...
- XXX:
Requirements
Steps
The following table describes
Step# | Responsible | Action | Prerequisites, if any | |
---|---|---|---|---|
Revision History
Version | Authors | Date | Comments |
---|---|---|---|