Detectionlowtest

AWS STS AssumeRole Misuse

Identifies the suspicious use of AssumeRole. Attackers could move laterally and escalate privileges.

Convert In Phoenix Studio

Open this Sigma rule in the converter with the YAML preloaded and ready for backend selection.

Launch
Austin SongerCreated Sat Jul 24Updated Sun Oct 09905d389b-b853-46d0-9d3d-dea0d3a3cd49cloud
Log Source
AWScloudtrail
ProductAWS← raw: aws
Servicecloudtrail← raw: cloudtrail
Detection Logic
Detection Logic1 selector
detection:
    selection:
        userIdentity.type: AssumedRole
        userIdentity.sessionContext.sessionIssuer.type: Role
    condition: selection
False Positives

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.

AssumeRole from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.

Automated processes that uses Terraform may lead to false positives.

Rule Metadata
Rule ID
905d389b-b853-46d0-9d3d-dea0d3a3cd49
Status
test
Level
low
Type
Detection
Created
Sat Jul 24
Modified
Sun Oct 09
Path
rules/cloud/aws/cloudtrail/aws_sts_assumerole_misuse.yml
Raw Tags
attack.lateral-movementattack.privilege-escalationattack.defense-evasionattack.t1548attack.t1550attack.t1550.001
View on GitHub