IR.L2-3.6.1 Incident Handling
Operate an incident handling capability covering preparation, detection, analysis, containment, recovery and user response.
3
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
- Records of handled incidents showing the lifecycle applied · Document repository
governing documentDocuments that govern the control
- Incident response plan covering all named lifecycle activities · Policy repository / GRC workspace
- Assigned incident response roles and contact details · Policy repository / GRC workspace
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
- Plan covers detection and containment but omits recovery or user response
- Capability documented with no assigned or trained personnel
- No records demonstrating the plan is actually used
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 sheetIA.L2-3.5.11 Obscure Feedback · IR.L2-3.6.2 Incident Reporting