Rachel Rice
f09b3ea4b1
aws_ec2_disable_encryption.yml Remove `status: success` from selection criteria, not required aws_ec2_vm_export_failure.yml Remove filter3: ``` eventName: 'ConsoleLogin' responseElements|contains: 'Failure' ``` Incompatible with selection criteria `eventName: 'CreateInstanceExportTask'` aws_ec2_download_userdata.yml, aws_iam_backdoor_users_keys.yml, aws_rds_change_master_password.yml, aws_rds_public_db_restore.yml Update reference aws_sts_assumedrole_misuse.yml Rename to aws_sts_assumerole_misuse.yml Update references to "AssumedRole" to "AssumeRole" Update selection criteria of `userIdentity.sessionContext: Role` to `userIdentity.sessionContext.sessionIssuer.type: Role`
31 lines
1.1 KiB
YAML
31 lines
1.1 KiB
YAML
title: AWS IAM Backdoor Users Keys
|
|
id: 0a5177f4-6ca9-44c2-aacf-d3f3d8b6e4d2
|
|
status: experimental
|
|
description: Detects AWS API key creation for a user by another user. Backdoored users can be used to obtain persistence in the AWS environment. Also with this alert, you can detect a flow of AWS keys in your org.
|
|
author: faloker
|
|
date: 2020/02/12
|
|
modified: 2021/08/20
|
|
references:
|
|
- https://github.com/RhinoSecurityLabs/pacu/blob/master/pacu/modules/iam__backdoor_users_keys/main.py
|
|
logsource:
|
|
service: cloudtrail
|
|
detection:
|
|
selection_source:
|
|
eventSource: iam.amazonaws.com
|
|
eventName: CreateAccessKey
|
|
filter:
|
|
userIdentity.arn|contains: responseElements.accessKey.userName
|
|
condition: selection_source and not filter
|
|
fields:
|
|
- userIdentity.arn
|
|
- responseElements.accessKey.userName
|
|
- errorCode
|
|
- errorMessage
|
|
falsepositives:
|
|
- Adding user keys to their own accounts (the filter cannot cover all possible variants of user naming)
|
|
- AWS API keys legitimate exchange workflows
|
|
level: medium
|
|
tags:
|
|
- attack.persistence
|
|
- attack.t1098
|