Suspicious AWS Federated Console Login From Programmatic Credentials

PremiumReviewedSigma · Medium · v1
Product
aws
Service
cloudtrail
Author
HuntRule
Published
2026-08-04
Updated
2026-08-28

ATT&CK techniques

Initial Access → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Collection

  7. C2

  8. Exfiltration

  9. Impact

What it detects

This rule detects an AWS Management Console sign-in performed by a federated user identity which indicates a session created from long-term or temporary programmatic credentials rather than an IAM user or SSO login. Wiz shows attackers exchange stolen keys for a federated console session to obfuscate their real identity and break session traceability. This matters because it lets an adversary operate interactively in the console while evading the account owner attribution normally provided by ConsoleLogin.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious AWS Role Assumption via Cognito Web Identity
Suspicious M365 Legacy Authentication via BAV2ROPC Client via m365
Suspicious AWS STS Session Token and Role Chaining Abuse via CloudTrail (via aws)
Suspicious AWS GetFederationToken Console Access by JavaGhost (via cloudtrail)
Suspicious AWS STS Role Chaining From Temporary Session Credentials (via cloudtrail)
Suspicious Federated Identity Credential On-Behalf-Of Token Flow via Sign-In Logs
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 Federated Console Login From Programmatic Credentials
Pivot detection · T1078.004 · 9 related

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