12.10.1 Incident response plan
An incident response plan exists and is ready to be activated in the event of a suspected or confirmed security incident, covering roles, responsibilities, communication, containment, and recovery.
5
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Annual review records · Document repository
governing documentDocuments that govern the control
- Incident response plan with named roles · Policy repository / GRC workspace
- Communication trees including legal, comms, law enforcement · Policy repository / GRC workspace
- Containment and recovery procedures · Policy repository / GRC workspace
- Approval and version control · 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
- IRP stale
- Roles unassigned
- No communication tree
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 sheet12.9.2 TPSP supports customer requests for compliance info (SP) · 12.10.2 IRP reviewed and tested annually