AWS STS AssumeRole Misuse
Identifies the suspicious use of AssumeRole. Attackers could move laterally and escalate privileges.
Detection logic
Detection requirements
- Platform
- ContainersIaaSIdentity ProviderLinuxmacOSOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- aws
- Log source service
- cloudtrail
Known benign triggers
- AssumeRole from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
- AssumeRole may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
- Automated processes that uses Terraform may lead to false positives.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html | 4from 2 sources |
| github.com/elastic/detection-rules/pull/1214 | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 905d389b-b853-46d0-9d3d-dea0d3a3cd49
- Tagged by the source as
- attack.lateral-movementattack.privilege-escalation
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1