Enhance WAF tuning guidance with policy scope details - #128695
Enhance WAF tuning guidance with policy scope details#128695Luke (Miskatonic-Electronic) wants to merge 1 commit into
Conversation
Added section on understanding policy scope impact before tuning WAF rules and clarified the implications of disabling rules in the WAF policy.
|
Luke (@Miskatonic-Electronic) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Luke (@Miskatonic-Electronic) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 771f18e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds guidance to help readers understand how WAF policy association scope affects tuning decisions, and clarifies the impact/risk of disabling managed rules based on that scope.
Changes:
- Added a new section explaining profile/domain/route association scope and precedence before tuning.
- Updated the “disable rule” warning to reflect association scope (not always global to all hosts).
- Added operational guidance for mixed-scope deployments and a “Related content” section.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| > [!WARNING] | ||
| > When assigning a new managed ruleset to a WAF policy, all the previous customizations from the existing managed rulesets such as rule state, rule actions and rule level exclusions will be reset to the new managed ruleset's defaults. However, any custom rules and policy settings will remain unaffected during the new ruleset assignment. | ||
| > |
Added section on understanding policy scope impact before tuning WAF rules and clarified the implications of disabling rules in the WAF policy.