AWS CloudTrail: Root User Credential Usage (UserIdentity.type=Root)

Alerts on CloudTrail activity performed by AWS account root credentials.

FreeReviewedSigma · Medium · v5
Product
aws
Service
cloudtrail
Author
vitaliy0x1 (SigmaHQ), DRL 1.1
Published
2020-01-21
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule flags CloudTrail events where the acting principal is the AWS account root user (userIdentity.type set to Root), excluding events with eventType recorded as AwsServiceEvent. Root credentials provide maximum privileges, so their use can indicate account takeover attempts, privilege escalation, or persistence activity. The detection relies on CloudTrail telemetry, specifically userIdentity.type and eventType fields.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious M365 Password Spraying via Azure PowerShell AppId from Quad7 Botnet
Suspicious AWS Instance Access or Export via SSH Key or Export Task
Suspicious Azure OpenAI Model Enumeration and Deployment Creation (via azure)
Suspicious Azure Cognitive Services Account Key Enumeration via ListKeys (via azure)
Malicious Business Email Compromise OAuth Application Sign-In via Entra ID Service Principal (via azure)
Suspicious AWS API Call from TruffleHog Credential Scanner User Agent
Suspicious Compute Instance Metadata Modification in GCP
Malicious JavaGhost Security Group Creation (via cloudtrail)
Suspicious S3 Access from Desktop File Transfer Clients by Bling Libra
AWS CloudTrail: Root User Credential Usage (UserIdentity.type=Root)
Pivot detection · T1078.004 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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