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.
Source: AWS Well-Architected Security Pillar, SEC10-BP08. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open AWS Well-Architected Security Pillar in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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