Detectionlowtest

AWS STS GetSessionToken Misuse

Identifies the suspicious use of GetSessionToken. Tokens could be created and used by attackers to 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 09b45ab1d2-712f-4f01-a751-df3826969807cloud
Log Source
AWScloudtrail
ProductAWS← raw: aws
Servicecloudtrail← raw: cloudtrail
Detection Logic
Detection Logic1 selector
detection:
    selection:
        eventSource: sts.amazonaws.com
        eventName: GetSessionToken
        userIdentity.type: IAMUser
    condition: selection
False Positives

GetSessionToken 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. GetSessionToken from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.

Rule Metadata
Rule ID
b45ab1d2-712f-4f01-a751-df3826969807
Status
test
Level
low
Type
Detection
Created
Sat Jul 24
Modified
Sun Oct 09
Path
rules/cloud/aws/cloudtrail/aws_sts_getsessiontoken_misuse.yml
Raw Tags
attack.lateral-movementattack.privilege-escalationattack.defense-evasionattack.t1548attack.t1550attack.t1550.001
View on GitHub