|
|
| (16 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| {{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}} | | {{Template:Op menubar}} {{Template:GO menubar}} |
|
| |
|
| = Work instruction to handle new Security Vulnerability handling GGUS tickets =
| | [[Category:Infrastructure_Oversight|*]] |
|
| |
|
| The purpose of this page is to provide instructions to the EGI Operations team members on how to handle Security Vulnerability identified by [[IRTF]].
| | {{DeprecatedAndMovedTo|new_location=https://confluence.egi.eu/display/EGIPP/WI07+Security+Vulnerability+handling}} |
| | |
| The main idea behind this handling is to make sure that sites are aware of the issue and working on it.
| |
| Usualy sites that are showing good intention are not penalized even if the progress is not within the procedure: [[SEC03_EGI-CSIRT_Critical_Vulnerability_Handling|SEC03]] put deadlines on site to do few things but does not put a deadline on the [[Csirt|CSIRT]] to enforce them, allowing to adapt the answer.
| |
| | |
| {| align="center" cellspacing="0" cellpadding="5" border="1" | |
| |-
| |
| ! Step
| |
| ! Action
| |
| |-
| |
| | 1
| |
| | [[IRTF]] is responsible for:
| |
| * looking at Pakiti/the security dashboard
| |
| * looking for false positives
| |
| * creating new tickets with a due date of 3 days.
| |
| |-
| |
| | 2a
| |
| | If there is no acknowledgement or answer from the site:
| |
| * 1 working day before the due date, send another reminder via [[https://rt.egi.eu/|RT]] (in the Vulnerability Handling queue)
| |
| * .5 working day before the due date, send a last reminder, potentially including operational contacts in addition of security contacts. In such case, in case of an answer, make sure to verify that the security contact is still valid
| |
| * After the due date, suspend the site
| |
| |-
| |
| | 2b
| |
| | If there is an acknowledgement, but no solution announced:
| |
| * 1 working day before the due date, check Pakiti:
| |
| ** If there is no change, ask for progress/for an update, insisting
| |
| ** If the vulnerability disappeared from [[https://pakiti.egi.eu/|Pakiti]], ask for a confirmation that the vulnerability was fixed and that it's not simply the affected node not being reached by the Nagios probe (which usually reach different nodes every day)
| |
| |-
| |
| | 3
| |
| | After the due date, if there is still no answer/solution announced, suspend the site
| |
| |-
| |
| | 4
| |
| | If a solution is said to be deployed:
| |
| * If it's a mitigation:
| |
| ** If different from any mentioned in the advisory escalate to [[IRTF]]
| |
| ** If it's the same, wait for up to a day and check the security dashboard
| |
| * If it's a simple package/kernel update, check [[https://pakiti.egi.eu/|Pakiti]]:
| |
| ** If there is a report for the affected node(s) without any vulnerability, thanks and close the ticket
| |
| ** If the last report for the affect node(s) is still from before the update, ask to run the pakiti client by following [[EGI_CSIRT:Pakiti_client]].
| |
| *** If the vulnerability then disappear from Pakiti, with or without any other message, close the ticket
| |
| |-
| |
| | 5
| |
| | If a solution is announced but for after the deadline, it can be tolerated if justified (e.g. special kernel update requiring different vendor update). In case of doubt don't hesitate to escalate to [[IRTF]].
| |
| |}
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.