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.
4
artefacts
0
held by a system
1
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
- 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
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 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