SEC10-BP04 Develop and test security incident response playbooks
Develop incident response playbooks giving prescriptive steps for anticipated incident scenarios, and test them so responders follow a known structure rather than improvising.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Playbooks for known finding and alert types · SIEM / log platform
periodic reviewEvidence produced at each review
- Records of playbook tests or exercises with dates and participants · Document repository
governing documentDocuments that govern the control
- Playbook set covering anticipated scenarios such as denial of service, ransomware and credential compromise · Policy repository / GRC workspace
- Playbook revision history after incidents or tests · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- a single generic plan with no scenario-specific steps
- playbooks written once and never exercised
- no playbook for the alert types the detection tooling actually raises
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 sheetSEC10-BP03 Prepare forensic capabilities · SEC10-BP05 Pre-provision access