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.
Source: AWS Well-Architected Security Pillar, SEC10-BP03. 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
- Forensic account design · Policy repository / GRC workspace
- Evidence acquisition runbook · Document repository
- Forensic AMI inventory · Policy repository / GRC workspace
- Chain of custody template · Document repository
First move
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