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.
5
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
- AWS Organizations OU diagram · Policy repository / GRC workspace
- Account inventory with purpose and owner · Policy repository / GRC workspace
- SCP policy set · 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
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
- 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