SEC10-BP02 Develop incident management plans
Document IR plans covering detection, triage, containment, eradication, recovery and lessons learned, mapped to specific AWS scenarios such as credential compromise.
3
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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
- Incident response plan document · Policy repository / GRC workspace
- Scenario-specific runbooks (key compromise, data exfil, ransomware) · Policy repository / GRC workspace
- RACI matrix · Policy repository / GRC workspace
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
- generic IR plan with no AWS specifics
- no runbooks for cloud scenarios
- plan untested
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-BP01 Identify key personnel and external resources · SEC10-BP03 Prepare forensic capabilities