[Rule Tunings] AWS WAF Rules

[imays11]

Pull Request

Issue link(s):

• https://github.com/elastic/ia-trade-team/issues/616

Summary - What I changed

Telemetry for both rules are low as expected. It should be noted that Support for AWS WAF Classic ended on September 30, 2025, however, in telemetry, it seems that there are still customers who have not fully migrated to AWS WAF V2. For this reason, I've decided to keep support for both the Classic and V2 versions of AWS WAF service.

AWS WAF Access Control List Deletion

• reduced execution window
• updated tags
• added event.provider fields to query
• updated Mitre mapping
• updated description, fp and ig sections
• added highlighted fields

AWS WAF Rule or Rule Group Deletion

• reduced execution window
• updated tags
• updated Mitre mapping
• updated description, fp and ig sections
• added highlighted fields

How To Test

Scripts for triggering the rules found here: WAF

screenshots of expected alerts and both API calls triggered via currently supported AWS WAF V2 API

[github-actions]

Rule: Tuning - Guidelines

These guidelines serve as a reminder set of considerations when tuning an existing rule.

Documentation and Context

• Detailed description of the suggested changes.
• Provide example JSON data or screenshots.
• Provide evidence of reducing benign events mistakenly identified as threats (False Positives).
• Provide evidence of enhancing detection of true threats that were previously missed (False Negatives).
• Provide evidence of optimizing resource consumption and execution time of detection rules (Performance).
• Provide evidence of specific environment factors influencing customized rule tuning (Contextual Tuning).
• Provide evidence of improvements made by modifying sensitivity by changing alert triggering thresholds (Threshold Adjustments).
• Provide evidence of refining rules to better detect deviations from typical behavior (Behavioral Tuning).
• Provide evidence of improvements of adjusting rules based on time-based patterns (Temporal Tuning).
• Provide reasoning of adjusting priority or severity levels of alerts (Severity Tuning).
• Provide evidence of improving quality integrity of our data used by detection rules (Data Quality).
• Ensure the tuning includes necessary updates to the release documentation and versioning.

Rule Metadata Checks

• updated_date matches the date of tuning PR 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. Review to ensure the original intent of the rule is maintained.

Testing and Validation

• Validate that the tuned rule's performance is satisfactory and does not negatively impact the stack.
• Ensure that the tuned rule has a low false positive rate.