English
Español
Français
Deutsch
日本語
한국어
العربيةDisable Security Hub
Can disable Security Hub in this region, ending aggregated findings.
Grants escalation on its own.
securityhub:DisableSecurityHubOn its own, securityhub:DisableSecurityHub can disable Security Hub in this region, ending aggregated findings. On a wide resource scope that alone reaches blinded detection or removed guardrails.
Why it is dangerous
A principal can call securityhub:DisableSecurityHub to turn off Security Hub in the region, ending aggregated findings and compliance scoring.
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 DisableSecurityHub. The call shows up in CloudTrail but blends into normal administration, so it needs a rule to stand out.
Detection
DisableSecurityHubPrerequisites
securityhub:DisableSecurityHub in the region.
Tactic
Defense Evasion
A control that would remove it: Restrict securityhub:DisableSecurityHub to a break-glass role; deny 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 securityhub:DisableSecurityHub allow?
Can disable Security Hub in this region, ending aggregated findings.
Can securityhub:DisableSecurityHub 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 disable Security Hub detected?
Watch for DisableSecurityHub 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 securityhub:DisableSecurityHub to a break-glass role; deny 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.