Skip to content

fix: AWS IAM Backdoor Users Keys filter using |fieldref|contains - #6227

Open
swachchhanda000 wants to merge 1 commit into
SigmaHQ:masterfrom
swachchhanda000:fix/aws-iam-backdoor-users-keys-fieldref
Open

fix: AWS IAM Backdoor Users Keys filter using |fieldref|contains#6227
swachchhanda000 wants to merge 1 commit into
SigmaHQ:masterfrom
swachchhanda000:fix/aws-iam-backdoor-users-keys-fieldref

Conversation

@swachchhanda000

@swachchhanda000 swachchhanda000 commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

The filter compared userIdentity.arn against the literal string "responseElements.accessKey.userName" instead of the field's value, making the filter always false and causing the rule to alert on every CreateAccessKey call including self-service cases.

Fixes #6223

Summary of the Pull Request

Changelog

fix: AWS IAM Backdoor Users Keys - fix the wrong filter using |fieldref|contains

Example Log Event

Fixed Issues

SigmaHQ Rule Creation Conventions

  • If your PR adds new rules, please consider following and applying these conventions

The filter compared `userIdentity.arn` against the literal string
"responseElements.accessKey.userName" instead of the field's value,
making the filter always false and causing the rule to alert on every
CreateAccessKey call including self-service cases.

Fixes SigmaHQ#6223
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Review Needed The PR requires review Rules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aws_iam_backdoor_users_keys.yml: filter still uses |contains where |fieldref is required (same bug fixed in #4836 for a sibling rule)

1 participant