AWS waf documentation change
Summary
Updated terminology from 'protection pack or web ACL' to 'protection pack (web ACL)' for consistency
Security assessment
The changes are purely terminological clarifications to standardize references to web ACLs. No security vulnerabilities, mitigations, or new security features are mentioned or implied in the documentation updates.
Diff
diff --git a/waf/latest/developerguide/waf-rule-action.md b/waf/latest/developerguide/waf-rule-action.md index 757a7d9a2..4daa46066 100644 --- a//waf/latest/developerguide/waf-rule-action.md +++ b//waf/latest/developerguide/waf-rule-action.md @@ -17 +17 @@ The rule action tells AWS WAF what to do with a web request when it matches the -Rule actions can be terminating or non-terminating. A terminating action stops the protection pack or web ACL evaluation of the request and either lets it continue to your protected application or blocks it. +Rule actions can be terminating or non-terminating. A terminating action stops the protection pack (web ACL) evaluation of the request and either lets it continue to your protected application or blocks it. @@ -25 +25 @@ Here are the rule action options: - * **Count** – AWS WAF counts the request but does not determine whether to allow it or block it. This is a non-terminating action. AWS WAF continues processing the remaining rules in the protection pack or web ACL. In rules that you define, you can insert custom headers into the request and you can add labels that other rules can match against. + * **Count** – AWS WAF counts the request but does not determine whether to allow it or block it. This is a non-terminating action. AWS WAF continues processing the remaining rules in the protection pack (web ACL). In rules that you define, you can insert custom headers into the request and you can add labels that other rules can match against. @@ -37 +37 @@ These rule actions can be terminating or non-terminating, depending on the state - * **Non-terminating for valid, unexpired token** – If the token is valid and unexpired according to the configured CAPTCHA or challenge immunity time, AWS WAF handles the request similar to the Count action. AWS WAF continues to inspect the web request based on the remaining rules in the protection pack or web ACL. Similar to the Count configuration, in rules that you define, you can optionally configure these actions with custom headers to insert into the request, and you can add labels that other rules can match against. + * **Non-terminating for valid, unexpired token** – If the token is valid and unexpired according to the configured CAPTCHA or challenge immunity time, AWS WAF handles the request similar to the Count action. AWS WAF continues to inspect the web request based on the remaining rules in the protection pack (web ACL). Similar to the Count configuration, in rules that you define, you can optionally configure these actions with custom headers to insert into the request, and you can add labels that other rules can match against. @@ -50 +50 @@ For information about adding labels to matching requests, see [Web request label -For information about how protection pack or web ACL and rule settings interact, see [Using protection pack or web ACLs with rules and rule groups in AWS WAF](./web-acl-processing.html). +For information about how protection pack (web ACL) and rule settings interact, see [Using protection packs (web ACLs) with rules and rule groups in AWS WAF](./web-acl-processing.html).