SEF-04 Incident Response Testing
Test incident response plans at planned intervals and after significant organisational or environmental change, and update them on what the test shows.
4
artefacts
0
held by a system
3
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
- Test records with date, scenario and participants · Document repository
- The planned interval and evidence it was met · Document repository
- Evidence of a test triggered by significant change · Document repository
governing documentDocuments that govern the control
- Findings from each test and their closure · 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
- Tests run as tabletop discussion only, never exercising the actual mechanics
- Findings raised and carried forward untouched
- No test after a major platform or supplier change
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 sheetSEF-03 Incident Response Plans · SEF-05 Incident Response Metrics