IR-3 Incident response testing
Requires the incident response capability serving the system to be tested for effectiveness at an organization-defined frequency using the test types the organization has defined, so readiness is demonstrated rather than
4
artefacts
0
held by a system
2
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
- Exercise scenario documents and participant lists · Document repository
- Test reports with observations and identified weaknesses · Document repository
governing documentDocuments that govern the control
- Defined test types and frequency for incident response testing · Document repository
- Corrective actions tracked to closure after each test · 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
- Only tabletop exercises run, so technical containment steps are never proven
- Test scope excludes third party providers who hold part of the response
- Findings from exercises are not fed back into plans or training
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