| Info |
|---|
This is a draft document for comments. |
This document sets out the scope for eduGAIN Incident Response Coordination, which will be piloted from 1 July 2018 - 31 July 2019. eduGAIN Incident Response coordination will be supported by edugain-support and a dedicated team of incident response experts.
A. Put in place team
| Requirements |
|
|---|
| A1. | Define support team |
|
B. Put in place service parameters
| Requirements |
|
|---|
| B1. | Scope |
|
| B2. | Hours |
|
| B3. | Supported users |
|
C. Define workflow for team response.
| Requirements |
|
|---|
| C1. | global identifier for each incident |
|
| C2. | incident type classification |
|
| C3. | recognizing and escalating a security ticket |
|
| C4. | ensuring the right people are added to communication chain |
|
| C5. | supporting move to a secure channel |
|
| C6. | supporting post incident communications and reporting |
|
D. Select and implement support tools.
E. Ensure eduGAIN policy and supporting templates are in place.
...
F. Implement support for testing.
