AWS Security ChangesHomeSearch

AWS waf: Bot Control targeted rules now compare token acquisition vs presentation IP category

Service: waf · 2026-11-05 · Documentation medium

File: waf/latest/developerguide/waf-tokens-usage.md · Type: bot-mitigation

Summary

Updates the AWS WAF Bot Control bullet to state that at the targeted protection level the rule group compares the IP address category that acquired a token with the category that presents it and labels requests where the categories differ.

Security assessment

Describes a new detection signal (token provenance label) in the managed Bot Control rule group that flags tokens moved between IP address categories, a common proxy/bot evasion pattern. It is security feature documentation with medium impact, not a specific vulnerability fix.

Evidence

+  * **AWS WAF Bot Control** – The targeted rules in this rule group place a limit on the number of web requests that a client can send without a valid token, and they use token session tracking for session-level monitoring and management. As needed, the rules apply the Challenge and CAPTCHA rule actions to enforce token acquisition and valid client behavior. At the targeted protection level, the rule group also compares the category of the IP address that acquired a token with the category of the IP address that presents it. It labels requests where the two categories differ. For more information about the rule group and its labels, see [AWS WAF Bot Control rule group](./aws-managed-rule-groups-bot.html).

Diff

diff --git a/waf/latest/developerguide/waf-tokens-usage.md b/waf/latest/developerguide/waf-tokens-usage.md
index aafacd1..d0aa9a3 100644
--- a//waf/latest/developerguide/waf-tokens-usage.md
+++ b//waf/latest/developerguide/waf-tokens-usage.md
@@ -38 +38 @@ Tokens are required by many of the rules in the intelligent threat AWS Managed R
-  * **AWS WAF Bot Control** – The targeted rules in this rule group place a limit on the number of web requests that a client can send without a valid token, and they use token session tracking for session-level monitoring and management. As needed, the rules apply the Challenge and CAPTCHA rule actions to enforce token acquisition and valid client behavior. For more information, see [AWS WAF Bot Control rule group](./aws-managed-rule-groups-bot.html).
+  * **AWS WAF Bot Control** – The targeted rules in this rule group place a limit on the number of web requests that a client can send without a valid token, and they use token session tracking for session-level monitoring and management. As needed, the rules apply the Challenge and CAPTCHA rule actions to enforce token acquisition and valid client behavior. At the targeted protection level, the rule group also compares the category of the IP address that acquired a token with the category of the IP address that presents it. It labels requests where the two categories differ. For more information about the rule group and its labels, see [AWS WAF Bot Control rule group](./aws-managed-rule-groups-bot.html).