[New Rule] AWS IAM CompromisedKeyQuarantine Policy Attached to User

Issue link(s): Related : https://github.com/elastic/infosec/issues/18053 Tracked : https://github.com/elastic/ia-trade-team/issues/346

Summary - What I changed

This rule looks for use of the IAM AttachUserPolicy API operation to attach the CompromisedKeyQuarantine or CompromisedKeyQuarantineV2 AWS managed policies to an existing IAM user. This policy denies access to certain actions and is applied by the AWS team in the event that an IAM user's credentials have been compromised or exposed publicly.

-- Although a support case is opened on behalf of the account and additional information is sent to the contact information provided to AWS for the account, this rule is created as an additional alert to help increase response time for exposed credentials.

How To Test

I've used production results provided by our Infosec team to test this rule and included the event in the screenshot below, ask if you need to see the full event as it contains PII.

Checklist

[ ] Added a label for the type of pr: bug, enhancement, schema, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
[ ] Added the meta:rapid-merge label if planning to merge within 24 hours
[ ] Secret and sensitive material has been managed correctly
[ ] Automated testing was updated or added to match the most common scenarios
[ ] Documentation and comments were added for features that require explanation

Rule: New - Guidelines

These guidelines serve as a reminder set of considerations when proposing a new rule.

Documentation and Context

[ ] Detailed description of the rule.
[ ] List any new fields required in ECS/data sources.
[ ] Link related issues or PRs.
[ ] Include references.

Rule Metadata Checks

[ ] creation_date matches the date of creation PR initially merged.
[ ] min_stack_version should support the widest stack versions.
[ ] name and description should be descriptive and not include typos.
[ ] query should be inclusive, not overly exclusive, considering performance for diverse environments. Non ecs fields should be added to non-ecs-schema.json if not available in an integration.
[ ] min_stack_comments and min_stack_version should be included if the rule is only compatible starting from a specific stack version.
[ ] index pattern should be neither too specific nor too vague, ensuring it accurately matches the relevant data stream (e.g., use logs-endpoint.process-* for process data).
[ ] integration should align with the index. If the integration is newly introduced, ensure the manifest, schemas, and new_rule.yaml template are updated.
[ ] setup should include the necessary steps to configure the integration.
[ ] note should include any additional information (e.g. Triage and analysis investigation guides, timeline templates).
[ ] tags should be relevant to the threat and align/added to the EXPECTED_RULE_TAGS in the definitions.py file.
[ ] threat, techniques, and subtechniques should map to ATT&CK always if possible.

New BBR Rules

[ ] building_block_type should be included if the rule is a building block and the rule should be located in the rules_building_block folder.
[ ] bypass_bbr_timing should be included if adding custom lookback timing to the rule.

Testing and Validation

[ ] Provide evidence of testing and detecting the expected threat.
[ ] Check for existence of coverage to prevent duplication.

elastic / detection-rules