SEC01-BP01 Separate workloads using accounts
Use AWS Organizations and multiple AWS accounts to separate workloads, environments and data classifications, enforcing isolation boundaries that contain blast radius and simplify governance.
Source: AWS Well-Architected Security Pillar, SEC01-BP01. 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
- Account inventory with purpose and owner · Identity provider / directory
- SCP policy set · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- AWS Organizations OU diagram · Policy repository / GRC workspace
- Landing zone design document (Control Tower or custom) · Policy repository / GRC workspace
- Account vending process · Policy repository / GRC workspace
First move
Common gaps auditors find
- single monolithic account
- no SCP guardrails
- production and non-prod sharing accounts
- ad hoc account creation without baseline
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 sheet