IR.L2-3.6.3 Incident Response Testing
Test the organizational incident response capability to confirm it works.
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
- Incident response test or exercise records · Document repository
governing documentDocuments that govern the control
- Defined test frequency and scenario scope · Policy repository / GRC workspace
- Lessons learned and resulting plan updates · 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
- Testing never performed or long lapsed
- Exercises run without capturing findings
- Findings identified but the plan never updated
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 sheetIR.L2-3.6.2 Incident Reporting · MA.L2-3.7.1 Perform Maintenance