WI07 Security Vulnerability handling
|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|EGI Infrastructure Operations Oversight menu:||Home •||EGI.eu Operations Team •||Regional Operators (ROD)|
Work instruction to follow Security Vulnerability handling RT tickets
The purpose of this page is to provide instructions to the EGI Operations team members part of the operations-vulnerability-handling SSO group on how to handle Security Vulnerability identified by IRTF.
The main idea behind this handling is to make sure that sites are aware of the issue and working on it. Usually, sites that are showing good intention are not penalized even if the progress is not strictly within the procedure: SEC03.
|1||IRTF is responsible for:|
|2a||If there is no acknowledgement or answer from the site:
Dear security contact for XX-XX-XXX, This is a friendly reminder that we didn't receive any update about this ticket! Thanks,
|2b||If there is an acknowledgement, but no solution announced:
|3||After the due date, if there is still no answer/solution announced, EGI Operations suspend the site|
|4||If a solution is said to be deployed: