SEC10-BP08 Establish a framework for learning from incidents
Run blameless post-incident reviews, capture root causes and contributing factors, and feed improvements back into controls, runbooks and training.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Post incident review template · Document repository
- Completed PIRs · Document repository
- Improvement backlog and closure · Document repository
- Control changes from PIRs · 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
- no formal PIR process
- PIRs blame individuals
- actions never closed
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-BP07 Run simulations · SEC11-BP01 Train for application security