English
Español
Français
Deutsch
日本語
한국어
العربيةDegrade CloudTrail configuration
Can repoint or degrade a trail (dead bucket, drop multi-region).
Grants escalation on its own.
cloudtrail:UpdateTrailOn its own, cloudtrail:UpdateTrail can repoint or degrade a trail (dead bucket, drop multi-region). On a wide resource scope that alone reaches blinded detection or removed guardrails.
Why it is dangerous
A principal can call cloudtrail:UpdateTrail on the trail to send delivery to an attacker-controlled or non-existent S3 bucket, or to turn off multi-region and global-service events. The trail is still 'logging' but the records never land anywhere useful.
In MITRE ATT&CK terms this maps to T1562.008, Impair Defenses: Disable or Modify Cloud Logs, under the defense evasion tactic. AWS records it in CloudTrail as UpdateTrail. The call shows up in CloudTrail but blends into normal administration, so it needs a rule to stand out.
Detection
UpdateTrailPrerequisites
cloudtrail:UpdateTrail on the trail.
Tactic
Defense Evasion
A control that would remove it: Restrict cloudtrail:UpdateTrail to a break-glass role; deny org-wide via SCP and alarm on the event.
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 cloudtrail:UpdateTrail allow?
Can repoint or degrade a trail (dead bucket, drop multi-region).
Can cloudtrail:UpdateTrail 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 degrade CloudTrail configuration detected?
Watch for UpdateTrail 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 cloudtrail:UpdateTrail to a break-glass role; deny org-wide via SCP and alarm on the event. 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.008, Impair Defenses: Disable or Modify Cloud Logs, 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.