AWS waf documentation change
Summary
Removed entries related to URI fragment logging, Security Lake integration, and headers/cookies inspection from doc history
Security assessment
Changes appear to be routine documentation updates removing outdated entries without indicating security vulnerabilities or fixes
Diff
diff --git a/waf/latest/developerguide/doc-history.md b/waf/latest/developerguide/doc-history.md index 99fabb58a..6febd19c1 100644 --- a/waf/latest/developerguide/doc-history.md +++ b/waf/latest/developerguide/doc-history.md @@ -13,2 +12,0 @@ Change| Description| Date -[URI fragment in log match details](./logging.html)| Rule match details in the logs now include the URI fragment from the web request. You can configure logging to redact this field from the logs. | March 17, 2025 -[New AWS WAF request component](./waf-rule-statement-fields-list.html)| You can now inspect the URI fragment. | March 17, 2025 @@ -55 +52,0 @@ Change| Description| Date -[Integration with Amazon Security Lake](./logging.html)| You can now use Security Lake to collect web ACL traffic data. For information, see [Collecting data from AWS services](https://docs.aws.amazon.com/security-lake/latest/userguide/internal-sources.html) in the _Amazon Security Lake user guide_. | May 22, 2024 @@ -199 +195,0 @@ Change| Description| Date -[New AWS WAF request components: Headers and Cookies](./waf-rule-statement-fields-list.html)| You can now inspect cookies and you can inspect all headers, in addition to just a single header.| April 29, 2022