English
Español
Français
Deutsch
日本語
한국어
العربيةLeave the organization
Can remove the account from the org, escaping every SCP at once.
Grants escalation on its own.
organizations:LeaveOrganizationOn its own, organizations:LeaveOrganization can remove the account from the org, escaping every SCP at once. On a wide resource scope that alone reaches blinded detection or removed guardrails.
Why it is dangerous
A principal can call organizations:LeaveOrganization to remove the account from the org, escaping every SCP that constrained it in one call.
In MITRE ATT&CK terms this maps to T1562.001, Impair Defenses: Disable or Modify Tools, under the defense evasion tactic. AWS records it in CloudTrail as LeaveOrganization. The call is loud in CloudTrail and stands out from normal activity.
Detection
LeaveOrganizationPrerequisites
organizations:LeaveOrganization on the member account.
Tactic
Defense Evasion
A control that would remove it: Restrict organizations:LeaveOrganization to a break-glass role; deny for member accounts via SCP.
Whether to apply it depends on how the permission is used in your environment, so it is a business decision rather than an automatic fix. The same permission can be load-bearing in one account and pure risk in another.
Pathbreak confirms whether this path resolves in your account, ranks it against the others by how much it opens up, and uses your threat model and business context to show which paths are worth cutting.
Questions
What does organizations:LeaveOrganization allow?
Can remove the account from the org, escaping every SCP at once.
Can organizations:LeaveOrganization escalate privileges on its own?
Yes. Held on a broad enough resource it reaches blinded detection or removed guardrails with no other permission.
How is leave the organization detected?
Watch for LeaveOrganization in CloudTrail. The call is loud in CloudTrail and stands out from normal activity.
How do you break this path?
A control that would remove it is: Restrict organizations:LeaveOrganization to a break-glass role; deny for member accounts via SCP. Whether to apply it depends on how the permission is used in your account, so it is a business decision rather than an automatic fix.
Which MITRE ATT&CK technique is this?
T1562.001, Impair Defenses: Disable or Modify Tools, under the defense evasion tactic.
Related paths
References
Find this in your own account
We run a read-only scan of one AWS account and show you which of these paths exist, ranked by blast radius, with the change that breaks each one. First validated paths within the hour.