English
Español
Français
Deutsch
日本語
한국어
العربيةDetach SCP guardrail
Can detach an SCP guardrail from an account or OU.
Grants escalation on its own.
organizations:DetachPolicyOn its own, organizations:DetachPolicy can detach an SCP guardrail from an account or OU. On a wide resource scope that alone reaches blinded detection or removed guardrails.
Why it is dangerous
A principal can call organizations:DetachPolicy to detach an SCP guardrail from an account or OU, removing an org-wide Deny the rest of the model relies on.
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 DetachPolicy. The call shows up in CloudTrail but blends into normal administration, so it needs a rule to stand out.
Detection
DetachPolicyPrerequisites
organizations:DetachPolicy from the management or a delegated-admin account.
Tactic
Defense Evasion
A control that would remove it: Restrict organizations:DetachPolicy to a break-glass management-account role; alarm on SCP detachment.
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:DetachPolicy allow?
Can detach an SCP guardrail from an account or OU.
Can organizations:DetachPolicy 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 detach SCP guardrail detected?
Watch for DetachPolicy in CloudTrail. The call shows up in CloudTrail but blends into normal administration, so it needs a rule to stand out.
How do you break this path?
A control that would remove it is: Restrict organizations:DetachPolicy to a break-glass management-account role; alarm on SCP detachment. 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.