Difference between revisions of "WI07 Security Vulnerability handling"
Jump to navigation
Jump to search
m (Add some links, rewording.) |
m (Fix link to sec dashaboard) |
||
Line 15: | Line 15: | ||
| 1 | | 1 | ||
| [[IRTF]] is responsible for: | | [[IRTF]] is responsible for: | ||
* looking at [https://pakiti.egi.eu/ Pakiti] | * looking at [https://pakiti.egi.eu/ Pakiti] and [https://operations-portal.egi.eu/csiDashboard Security dashboard]. | ||
* looking for false positives | * looking for false positives | ||
* creating new [https://rt.egi.eu/ RT] tickets in the Vulnerability Handling queue with a due date of 3 days. | * creating new [https://rt.egi.eu/ RT] tickets in the Vulnerability Handling queue with a due date of 3 days. |
Revision as of 10:28, 4 May 2018
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 handle new Security Vulnerability handling GGUS tickets
The purpose of this page is to provide instructions to the EGI Operations team members 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.
Step | Action |
---|---|
1 | IRTF is responsible for:
|
2a | If there is no acknowledgement or answer from the site:
|
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:
|