SEC10-BP03 Prepare forensic capabilities
Pre-provision a forensic account, isolated VPC, tooling AMIs, IAM roles and EBS snapshot procedures so responders can acquire and analyse evidence quickly.
4
artefacts
0
held by a system
1
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
- Evidence acquisition runbook · Document repository
governing documentDocuments that govern the control
- Forensic account design · Policy repository / GRC workspace
- Forensic AMI inventory · Policy repository / GRC workspace
- Chain of custody template · 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 dedicated forensic account
- evidence collection ad hoc
- no chain of custody process
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-BP02 Develop incident management plans · SEC10-BP04 Develop and test security incident response playbooks