SEC03 EGI-CSIRT Critical Vulnerability Handling
|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|
|Title||EGI-CSIRT Critical Vulnerability Handling|
|Policy Group Acronym||EGI-CSIRT|
|Policy Group Name||EGI-CSIRT|
|Procedure Statement||The scope of this procedure is to maintain a properly patched infrastructure and make sure that CRITICAL Vulnerabilities are handled adequately by all involved entities.|
|Owner||Owner of procedure|
After a problem has been assessed as critical, and a solution or a mitigation is available then sites are required to take action. This document primarily defines the procedure from this time, when sites are asked to take action, and what steps are taken if they do not respond or do not take action. If a site fails to take action, this may lead to site suspension.
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
- SVG: svg-rat at mailman.egi.eu
- EGI-CSIRT: csirt at mailman.egi.eu
- NGI-Security-Officer: ngi-security-contacts at mailman.egi.eu
- Resource Center Security Contact: as defined in goc-db
- VM-Endorsers: Contact list does not yet exist
This procedure applies to Vulnerabilities assessed as CRITICAL by SVG. The assessment process and the resulting required steps to handle vulnerablities is described in: described in the Vulnerability issue handling process.
Vulnerability affecting Resource Center services or resources
|Step#||Responsible||Action||Prerequisites, if any||Time to comply|
|1||EGI-CSIRT / SVG||Send advisory as per Vulnerability issue handling process||SVG and/or EGI-CSIRT assessed the vulnerability as CRITICAL.||*|
|2||Resource Center||Upgrade the affected software to a non vulnerable version or apply mitigations||Non-vulnerable version available or mitigation described in the advisory||7 Calendar days after Step 1|
|3||EGI-CSIRT / Security Monitoring||Update Security Monitoring to check for vulnerable software versions/configurations||Vulnerability detectable via Pakiti or other external probles||7 Calendar days after Step 1|
|4||EGI-CSIRT/Security Officer on Duty||For each RC who failed to comply to step 2 within 7 calendar days, the Security Officer on Duty sends a notification to the RC and the NGI Security Officer when applicable||Failure to comply to step 2 within 7 calendar days or vulnerability detected by EGI's Security Monitoring after 7 working days||*|
|5||Resource Center||Any notified RC has to comply to the actions required by the Security Officer on Duty to resolve the vulnerability, in particular, when applicable, manually running the Pakiti client on the vulnerable system after fixing it.||Vulnerable site notified during step 4||3 working days|
|6||EGI-CSIRT Security Officer||For each the RC who failed to comply to step 5 within 3 working days, the EGI-CSIRT Security Officer temporarily suspends it from the infrastructure by setting the Certification Status of this RC to Suspended in GOC-DB. The EGI-CSIRT Security Officer will inform the NGI and EGI Operations of this action||Resource center failing to comply to step 5 within 3 working days||*|
|7||Resource Center||Suspended RCs might request recertification as per PROC09||RC suspended in step 6||*|
A diagram representing this procedure is available as an pdf.
|8||Sveng||16. Jul. 2015|
|8||Vincent Brillault||27. Jul. 2015||Split in two|