You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/waf/managed-rules/troubleshooting.mdx
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,12 +8,14 @@ sidebar:
8
8
9
9
import { RuleID } from"~/components";
10
10
11
-
By default, WAF managed rulesets are compatible with most websites and web applications. However, false positives and false negatives may occur:
11
+
By default, WAF's managed rulesets are compatible with most websites and web applications. However, false positives and false negatives may occur:
12
12
13
13
-**False positives**: Legitimate requests detected and mitigated as malicious.
14
14
-**False negatives**: Malicious requests that were not mitigated and reached your origin server.
15
15
16
-
## Handle false positives
16
+
## Troubleshoot false positives
17
+
18
+
You can use [Security Events](/waf/analytics/security-events/) to help you identify what caused legitimate requests to get blocked. Add filters and adjust the report duration as needed.
17
19
18
20
If you encounter a false positive caused by a managed rule, do one of the following:
0 commit comments