IR-2 Incident Response Training
Requires incident response training for system users consistent with their assigned roles, within a defined period of assuming the role and periodically thereafter.
5
artefacts
0
held by a system
0
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Control implementation statement for IR-2 citing the system mission and inheritance from common controls · Document repository
- Forensic toolkit readiness checklist and chain of custody templates · Document repository
- Regulatory notification procedure with jurisdiction specific timelines · Policy repository / GRC workspace
- Incident response plan with severity definitions and escalation paths · Policy repository / GRC workspace
- Incident response team roster with on call rotation · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Third party incident responder retainer expired
- Detection coverage gaps allow incidents to be discovered externally
- Severity criteria inconsistent across teams leading to under reporting
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet