AWS CloudTrail GetSigninToken Requests with Suspected Console User-Agent

Flags CloudTrail GetSigninToken sign-in token requests with non-matching console user-agent patterns.

FreeReviewedSigma · Medium · v5
Product
aws
Service
cloudtrail
Author
Chester Le Bron (@123Le_Bron) (SigmaHQ), DRL 1.1
Published
2024-02-26
Updated
2026-07-31

ATT&CK techniques

Defense Evasion → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags AWS CloudTrail events where GetSigninToken is called against signin.amazonaws.com, excluding requests that match a specific Jersey-based user agent pattern. Attackers can use GetSigninToken to obtain temporary federated credentials that may help pivot from tooling to AWS console access while reducing reliance on MFA tied to an original identity. The detection relies on CloudTrail eventSource/eventName fields and the userAgent substring observed in the request.

Related detections9 linkedT1550.001 — drag to rearrange
Suspicious Federated Identity Credential On-Behalf-Of Token Flow via Sign-In Logs
Suspicious Salesforce Bulk API Export via aiohttp User Agent
Suspicious Remote Command Execution to EC2 Instances via AWS SSM
Suspicious SSM Session or Command Execution on EC2 Instance (via cloudtrail)
Suspicious EC2 Instance Connect SSH Public Key Push (via cloudtrail)
Suspicious Entra Sign-In With Axios Automation User-Agent via AiTM Token Replay (via azure)
Malicious Azure AD Token Abuse via Roadtx
Suspicious M365 Sign-In from Synthetic iPhone User Agent via m365
Possible Illicit Consent Grant to OAuth Application via Azure AD
AWS CloudTrail GetSigninToken Requests with Suspected Console User-Agent
Pivot detection · T1550.001 · 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.