AWS CreateAccessKey
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,…
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.
Detection logic
Detection requirements
- Platform
- IaaSIdentity ProviderOffice SuiteSaaS
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- aws_cloudtrail_createaccesskey
Known benign triggers
- While this search has no known false positives, it is possible that an AWS admin has legitimately created keys for another user.
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 |
|---|---|
| bishopfox.com/blog/privilege-escalation-in-aws | 8 |
| rhinosecuritylabs.com/aws/aws-privilege-escalation-methods-mitigation-part-2/ | 8 |
From the source
- At source
- Open at source
- Upstream identifier
- 2a9b80d3-6340-4345-11ad-212bf3d0d111
- Tagged by the source as
- AWS IAM Privilege EscalationAWS AccountcloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securitynetwork
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Oct 20, 2026
- Version
- 2