Skip to content

Commit 99eb252

Browse files
committed
rephrase the note
1 parent a568f17 commit 99eb252

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/web-application-firewall/afds/waf-sensitive-data-protection-configure-frontdoor.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: halkazwini
55
ms.author: halkazwini
66
ms.service: azure-web-application-firewall
77
ms.topic: how-to
8-
ms.date: 04/29/2025
8+
ms.date: 04/30/2025
99
---
1010

1111
# How to mask sensitive data on Azure Web Application Firewall on Azure Front Door
@@ -27,7 +27,7 @@ The following table shows examples of log scrubbing rules that can be used to pr
2727
| Request IP Address <sup>2</sup> | Equals Any | NULL | {"matchVariableName":"ClientIP","matchVariableValue":"****"} |
2828
| Request URI | Equals Any | NULL | {"matchVariableName":"URI","matchVariableValue":"****"} |
2929

30-
<sup>1</sup> The whole request body is scrubbed if this rule is triggered and the request content type is `application/x-www-form-urlencoded` or `application/json`.
30+
<sup>1</sup> If a request triggers a rule that scans the request body, and the content type is either `application/x-www-form-urlencoded` or `application/json`, the WAF will scrub all request details from the logs to prevent any potential storage of PII.
3131

3232
<sup>2</sup> Request IP Address and Request URI rules only support the *equals any* operator and scrubs all instances of the requestor's IP address that appears in the WAF logs.
3333

0 commit comments

Comments
 (0)