Skip to content

Commit 7d44931

Browse files
pedrosousadaisyfaithauma
authored andcommitted
[WAF] Add changelog entry (#22292)
1 parent b27b0ae commit 7d44931

File tree

2 files changed

+19
-0
lines changed

2 files changed

+19
-0
lines changed
169 KB
Loading
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: Improved Payload Logging for WAF Managed Rules
3+
description: We have upgraded WAF Payload Logging to enhance rule diagnostics and usability.
4+
products:
5+
- waf
6+
date: 2025-05-08T11:00:00Z
7+
---
8+
9+
We have upgraded WAF Payload Logging to enhance rule diagnostics and usability:
10+
11+
- **Targeted logging**: Logs now capture only the specific portions of requests that triggered WAF rules, rather than entire request segments.
12+
- **Visual highlighting**: Matched content is visually highlighted in the UI for faster identification.
13+
- **Enhanced context**: Logs now include surrounding context to make diagnostics more effective.
14+
15+
![Log entry showing payload logging details](~/assets/images/changelog/waf/2025-05-payload-logging-update.png)
16+
17+
Payload Logging is available to all Enterprise customers. If you have not used Payload Logging before, check how you can [get started](/waf/managed-rules/payload-logging/).
18+
19+
**Note:** The structure of the `encrypted_matched_data` field in Logpush has changed from `Map<Field, Value>` to `Map<Field, {Before: bytes, Content: Value, After: bytes}>`. If you rely on this field in your Logpush jobs, you should review and update your processing logic accordingly.

0 commit comments

Comments
 (0)