Malicious Disabling of AWS GuardDuty Threat Detection (via cloudtrail)

PremiumReviewedSigma · High · v1
Product
aws
Service
cloudtrail
Author
HuntRule
Published
2026-11-06
Updated
2026-11-06

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule detects API calls that delete or suspend GuardDuty detectors or members, a defense-evasion technique that blinds AWS threat detection before an attacker continues operating. Disabling cloud security monitoring is tracked in the Red Canary Threat Detection Report cloud coverage. Detecting these calls surfaces an attacker turning off detection.

Related detections9 linkedT1685.002 — drag to rearrange
Malicious Disabling or Deletion of AWS CloudTrail Logging (via cloudtrail)
Suspicious AWS GuardDuty Detector Tampering
Suspicious CloudTrail Logging Tampering for Defense Evasion (via aws)
Malicious Mailbox Audit Bypass Association in Exchange Online (via exchange)
Suspicious AWS CloudTrail Logging Disabled
Suspicious GCP Log Sink Tampering for Defense Evasion (via gcp)
AWS CloudTrail GuardDuty Detector Deleted or Disabled via UpdateDetector
AWS CloudTrail: AWS Config Delivery Channel/Recorder Disabled
AWS CloudTrail Trail Stop/Update/Delete Activity
Malicious Disabling of AWS GuardDuty Threat Detection (via cloudtrail)
Pivot detection · T1685.002 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.