Prevent Member Accounts from Leaving the Organization
Specification & Description
Attach a Service Control Policy (SCP) at the AWS Organization Root that denies organizations:LeaveOrganization so member accounts cannot detach from central governance.
Technical Specifications
If a member account calls organizations:LeaveOrganization, it immediately drops all inherited SCPs, Resource Control Policies (RCPs), Tag Policies, and delegated security integrations. Attaching a Root-level Deny SCP stops every member account principal, including the member account root user, from detaching the account. Because AWS Organizations never evaluates SCPs against the Management account (and the Management account cannot leave its own organization), no Management account exclusion is required in the policy.
Security Rationale
A detached member account becomes an unmonitored standalone account outside your landing zone guardrails, centralized logging, and billing controls. Preventing LeaveOrganization preserves the integrity of the entire policy hierarchy.
Business & Security Impact
Without this SCP, an administrator or compromised root credential in a member account can remove the account from the organization, bypassing preventative SCPs and central security monitoring.
Policy Exceptions (1)
Intentional account offboarding or divestiture requires removing the account from the organization using RemoveAccountFromOrganization from the Management account or temporarily moving the account to a dedicated offboarding OU exempt from this SCP under change-control approval.
Operational & Implementation Notes
Attaching this SCP at the Organization Root guarantees automatic inheritance for every newly created or invited member account without waiting for OU placement.
Related Controls & Guardrails (2)
Official References
Compliance Framework Mappings (5)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | AC-2AC-3CM-2 | 3 |
ISO 27001:2022ISO 27001 | A.5.15A.8.2A.8.9 | 3 |
PCI DSS v4.0PCI DSS | 2.2.17.2.1 | 2 |
SOC 2SOC 2 | CC6.1CC6.3 | 2 |
AWS Foundational Security Best PracticesAWS FSBP | Account.2 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Resolve the Organization Root ID, list custom SCPs attached to Root, and inspect each policy document via describe-policy to confirm an explicit Deny statement covers organizations:LeaveOrganization. Required IAM permissions: organizations:ListRoots, organizations:ListPoliciesForTarget, and organizations:DescribePolicy.
Remediation Guide & Automation
From the Management account, create an SCP denying organizations:LeaveOrganization on all resources and attach it directly to the Organization Root so all current and future member accounts inherit it. Required IAM permissions: organizations:ListRoots, organizations:EnablePolicyType, organizations:CreatePolicy, and organizations:AttachPolicy.
Step-by-Step Instructions
- Sign in to the AWS Organizations Management account with an administrative role.
- Confirm SERVICE_CONTROL_POLICY is enabled on the Organization Root.
- Create an SCP named PreventLeaveOrganization that denies organizations:LeaveOrganization on Resource '*'.
- Attach the SCP to the Organization Root so all current and future OUs and member accounts inherit it.