AWS CreateAccessKey
Description
This hunting query identifies successful AWS IAM access key creation events where a named IAM user creates a key for a different named IAM user. Such activity may indicate persistence or privilege escalation, particularly when the target user has elevated permissions. The query compares the caller and target usernames; it does not assess the target user's permissions. Hunting queries are designed to be run manually during threat hunting activities.
Query · spl
`cloudtrail`
eventName = CreateAccessKey
| where (isnull(errorCode) OR errorCode="success")
AND 'userIdentity.type'="IAMUser"
AND isnotnull('userIdentity.userName')
AND isnotnull('requestParameters.userName')
AND 'userIdentity.userName'!='requestParameters.userName'
| eval
caller_arn='userIdentity.arn',
caller_principal_id='userIdentity.principalId',
caller_user='userIdentity.userName',
dest=coalesce(dest,eventSource),
signature=coalesce(signature,eventName),
src=coalesce(src,sourceIPAddress),
target_user='requestParameters.userName',
user_agent=coalesce(user_agent,userAgent),
user_arn=coalesce(user_arn,caller_arn),
vendor_account=coalesce(vendor_account,recipientAccountId),
vendor_product=coalesce(vendor_product,"AWS"),
vendor_region=coalesce(vendor_region,awsRegion)
| stats count min(_time) as firstTime
max(_time) as lastTime
values(dest) as dest
values(eventID) as eventIDs
values(signature) as signature
values(src) as src
values(user_agent) as user_agent
values(user_arn) as user_arn
values(vendor_product) as vendor_product
values(vendor_region) as vendor_region
by vendor_account caller_user caller_principal_id target_user
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `aws_createaccesskey_filter`
Implementation guide
You must install splunk AWS add on and Splunk App for AWS. This search works with AWS CloudTrail logs.
Known false positives
- While this search has no known false positives, it is possible that an AWS admin has legitimately created keys for another user.
Analyst notes
Known false positives: While this search has no known false positives, it is possible that an AWS admin has legitimately created keys for another user.