AWS waf documentation change
Summary
Added references to 'protection packs' alongside web ACLs in CAPTCHA/challenge token configuration documentation. Updated token domain configuration guidance.
Security assessment
Introduces documentation for configuring security features (CAPTCHA/challenge tokens) through new 'protection packs' alongside existing web ACLs. While not fixing security issues, it expands documentation about security controls by including a new configuration entity (protection packs).
Diff
diff --git a/waf/latest/developerguide/web-acl-captcha-challenge-token-domains.md b/waf/latest/developerguide/web-acl-captcha-challenge-token-domains.md index b2145baef..9f7336633 100644 --- a//waf/latest/developerguide/web-acl-captcha-challenge-token-domains.md +++ b//waf/latest/developerguide/web-acl-captcha-challenge-token-domains.md @@ -4,0 +5,4 @@ +**Introducing a new console experience for AWS WAF** + +You can now use the updated experience to access AWS WAF functionality anywhere in the console. For more details, see [Working with the updated console experience](./working-with-console.html). + @@ -7 +11 @@ -You can configure options in your web ACL for the rules that use the CAPTCHA or Challenge rule actions and for the application integration SDKs that manage silent client challenges for AWS WAF managed protections. +You can configure options in your protection pack or web ACL for the rules that use the CAPTCHA or Challenge rule actions and for the application integration SDKs that manage silent client challenges for AWS WAF managed protections. @@ -11 +15 @@ These features mitigate bot activity by challenging end users with CAPTCHA puzzl -In your web ACL configuration, you can configure how AWS WAF manages these tokens: +In your protection pack or web ACL configuration, you can configure how AWS WAF manages these tokens: @@ -13 +17 @@ In your web ACL configuration, you can configure how AWS WAF manages these token - * **CAPTCHA and challenge immunity times** – These specify how long a CAPTCHA or challenge timestamp remains valid. The web ACL settings are inherited by all rules that don't have their own immunity time settings configured and also by the application integration SDKs. For more information, see [Setting timestamp expiration and token immunity times in AWS WAF](./waf-tokens-immunity-times.html). + * **CAPTCHA and challenge immunity times** – These specify how long a CAPTCHA or challenge timestamp remains valid. The protection pack or web ACL settings are inherited by all rules that don't have their own immunity time settings configured and also by the application integration SDKs. For more information, see [Setting timestamp expiration and token immunity times in AWS WAF](./waf-tokens-immunity-times.html). @@ -15 +19 @@ In your web ACL configuration, you can configure how AWS WAF manages these token - * **Token domains** – By default, AWS WAF accepts tokens only for the domain of the resource that the web ACL is associated with. If you configure a token domain list, AWS WAF accepts tokens for all domains in the list and for the domain of the associated resource. For more information, see [AWS WAF web ACL token domain list configuration](./waf-tokens-domains.html#waf-tokens-domain-lists). + * **Token domains** – By default, AWS WAF accepts tokens only for the domain of the resource that the protection pack or web ACL is associated with. If you configure a token domain list, AWS WAF accepts tokens for all domains in the list and for the domain of the associated resource. For more information, see [AWS WAF protection pack or web ACL token domain list configuration](./waf-tokens-domains.html#waf-tokens-domain-lists).