ASL AWS Create Access Key
The following analytic identifies the creation of AWS IAM access keys by a user for another user, which can indicate privilege escalation. It leverages AWS CloudTrail logs to detect instances where the user creating…
Description
The following analytic identifies the creation of AWS IAM access keys by a user for another user, which can indicate privilege escalation. It leverages AWS CloudTrail logs to detect instances where the user creating the access key is different from the user for whom the key is created. This activity is significant because unauthorized access key creation can allow attackers to establish persistence or exfiltrate data via AWS APIs. If confirmed malicious, this could lead to unauthorized access to AWS services, data exfiltration, and long-term persistence in the environment.
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
- asl_aws_cloudtrail
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
- 81a9f2fe-1697-473c-af1d-086b0d8b63c8
- Tagged by the source as
- AWS IAM Privilege EscalationScattered Lapsus$ HuntersAWS 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
- Aug 26, 2026
- Version
- 1