Protection Policies Must Be Configured for Domain Names Protected with WAF
Rule Details
Parameter |
Description |
---|---|
Rule name |
waf-instance-policy-not-empty |
Identifier |
Protection Policies Must Be Configured for Domain Names Protected with WAF |
Description |
If a protection policy is not configured for a domain name protected with a dedicated WAF instance, the WAF policy is non-compliant. |
Tag |
waf |
Trigger Type |
Configuration change |
Filter Type |
waf.instance |
Rule Parameters |
None |
Application Scenarios
WAF protection policies help you defend against common web application attacks, including XSS attacks, SQL injection, crawlers, and web shells. You can customize protection rules to let WAF better protect your website services using these custom rules. For details, see Protection Configuration Overview.
This rule checks whether your dedicated WAF instances are configured protection policies for domain names.
Solution
When you buy new dedicated WAF instances, associate them with domain name protection policies. Based on the check result of this rule, associate existing dedicated WAF instances with protection policies for domain names.
Rule Logic
- If a protection policy is not configured for a domain name protected with a dedicated WAF instance, the WAF policy is non-compliant.
- If a protection policy is configured for a domain name protected with a dedicated WAF instance, the WAF policy is compliant.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot