AWS waf documentation change
Summary
Consistently replaced 'protection pack or web ACL' with 'protection pack (web ACL)' to standardize terminology
Security assessment
Changes only clarify that protection packs are implemented as web ACLs. No security-related content modifications, vulnerability disclosures, or new security capabilities are introduced. Purely documentation consistency improvement.
Diff
diff --git a/waf/latest/developerguide/waf-managed-rule-groups-best-practice.md b/waf/latest/developerguide/waf-managed-rule-groups-best-practice.md index 58c4e605e..db24d0031 100644 --- a//waf/latest/developerguide/waf-managed-rule-groups-best-practice.md +++ b//waf/latest/developerguide/waf-managed-rule-groups-best-practice.md @@ -13 +13 @@ Follow this best practice guidance for handling versioning when you use a versio -When you use a managed rule group in your protection pack or web ACL, you can choose to use a specific, static version of the rule group, or you can choose to use the default version: +When you use a managed rule group in your protection pack (web ACL), you can choose to use a specific, static version of the rule group, or you can choose to use the default version: @@ -15 +15 @@ When you use a managed rule group in your protection pack or web ACL, you can ch - * **Default version** – AWS WAF always sets the default version to the static version that's currently recommended by the provider. When the provider updates their recommended static version, AWS WAF automatically updates the default version setting for the rule group in your protection pack or web ACL. + * **Default version** – AWS WAF always sets the default version to the static version that's currently recommended by the provider. When the provider updates their recommended static version, AWS WAF automatically updates the default version setting for the rule group in your protection pack (web ACL).