We have not been able to test, simulate or build datasets for it, use at your own risk!

Try in Splunk Security Cloud


This search provides detection of suspicious use of sts:GetSessionToken. These tokens can be created on the go and used by attackers to move laterally and escalate privileges.

  • Type: Hunting
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel:
  • Last Updated: 2020-07-27
  • Author: Rod Soto, Splunk
  • ID: 85d7b35f-b8b5-4b01-916f-29b81e7a0551


ID Technique Tactic
T1550 Use Alternate Authentication Material Defense Evasion, Lateral Movement
`aws_cloudwatchlogs_eks` ASIA  userIdentity.type=IAMUser
| spath eventName 
| search eventName=GetSessionToken 
| table sourceIPAddress eventTime userIdentity.arn userName userAgent user_type status region 
| `aws_detect_sts_get_session_token_abuse_filter`

Associated Analytic Story

How To Implement

You must install splunk AWS add-on and Splunk App for AWS. This search works with cloudwatch logs

Required field

  • _time
  • userIdentity.type
  • eventName
  • sourceIPAddress
  • eventTime
  • userIdentity.arn
  • userName
  • userAgent
  • user_type
  • status
  • region

Kill Chain Phase

  • Lateral Movement

Known False Positives

Sts:GetSessionToken can be very noisy as in certain environments numerous calls of this type can be executed. This search can be adjusted to provide specific values to identify cases of abuse. In specific environments the use of field requestParameters.serialNumber will need to be used.


Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1