Delete WAFv2 WebACL
Can delete a WAF WebACL, dropping request filtering in front of the app.
Grants escalation on its own.
wafv2:DeleteWebACLOn its own, wafv2:DeleteWebACL can delete a WAF WebACL, dropping request filtering in front of the app. On a wide resource scope that alone reaches blinded detection or removed guardrails.
Why it is dangerous
A principal can call wafv2:DeleteWebACL to remove a WAF WebACL, dropping request filtering in front of the protected app.
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 DeleteWebACL. The call shows up in CloudTrail but blends into normal administration, so it needs a rule to stand out.
Detection
DeleteWebACLPrerequisites
wafv2:DeleteWebACL on the WebACL (disassociated, with a current LockToken).
Tactic
Defense Evasion
A control that would remove it: Restrict wafv2:DeleteWebACL to a break-glass role. UpdateWebACL to default-Allow or DeleteLoggingConfiguration are variants.
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 wafv2:DeleteWebACL allow?
Can delete a WAF WebACL, dropping request filtering in front of the app.
Can wafv2:DeleteWebACL 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 delete WAFv2 WebACL detected?
Watch for DeleteWebACL 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 wafv2:DeleteWebACL to a break-glass role. UpdateWebACL to default-Allow or DeleteLoggingConfiguration are variants. 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.