SEC10-BP07 Run simulations
Conduct regular game days and tabletop exercises for credential compromise, ransomware and data breach scenarios to test plans, tools and team readiness.
Source: AWS Well-Architected Security Pillar, SEC10-BP07. 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
- Tabletop minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Game day schedule and scenarios · Document repository
- Lessons learned register · Policy repository / GRC workspace
- Remediation actions tracked · Document repository
First move
Common gaps auditors find
- no exercises run
- lessons learned never implemented
- same scenario repeated
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-BP06 Pre-deploy tools · SEC10-BP08 Establish a framework for learning from incidents