Persistence (TA0003)(external, opens in a new tab or window)
Privilege Escalation (TA0004)(external, opens in a new tab or window)
text code block:from logs-aws.cloudtrail-* metadata _id, _version, _index | where event.dataset == "aws.cloudtrail" and event.provider == "iam.amazonaws.com" and event.action == "CreateAccessKey" and event.outcome == "success" and user.name != user.target.name | keep @timestamp, cloud.account.id, cloud.region, event.provider, event.action, event.outcome, event.dataset, user.name, source.address, source.ip, user.target.name, user_agent.original, aws.cloudtrail.request_parameters, aws.cloudtrail.response_elements, aws.cloudtrail.user_identity.arn, aws.cloudtrail.user_identity.type, aws.cloudtrail.user_identity.access_key_id, source.geo.*, _id, _version, _index
Install detection rules in Elastic Security
Detect AWS IAM User Created Access Keys For Another User in the Elastic Security detection engine by installing this rule into your Elastic Stack.
To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).