AWS Well-Architected Security Pillar 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.
What else in your programme already covers this
This control maps to 65 controls across 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST800-SC-3 Security Function Isolation. Isolate security functions from nonsecurity functions
NIST800-SC-32 System Partitioning. Partition the system into [organization-defined] residing in separate [organization-defined] domains or environments based on [organization-defined]
2.2.3 Primary functions isolated or secured to highest level
6.5.3 Pre-production environments are separated from production environments and the separation is enforced with access controls
6.5.4 Roles and functions are separated between production and pre-production environments to provide accountability such that only reviewed and approved changes are deployed
You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?
AWS Well-Architected Security Pillar SEC01-BP01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.