-
Notifications
You must be signed in to change notification settings - Fork 10k
[WAF] Update managed rules troubleshooting #24670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
This PR requires additional review attention because it affects the following areas: RedirectsThis PR changes current filenames or deletes current files. Make sure you have redirects set up to cover the following paths:
|
|
|
||
| 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. | ||
|
|
||
| If you encounter a false positive caused by a managed rule, do one of the following: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The content below this point about false positives already existed (you can skip it while reviewing).
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
|
|
||
| `http.host eq "example.com" and starts_with(http.request.uri.path, "/admin")` | ||
|
|
||
| ## Troubleshoot false negatives |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New content, based on the troubleshooting page for a previous implementation: https://developers.cloudflare.com/waf/reference/legacy/old-waf-managed-rules/troubleshooting/#troubleshoot-false-negatives.
Co-authored-by: Jun Lee <[email protected]>
Summary
Addresses PCX-17622.
Documentation checklist