更新时间:2024-10-28 17:27:37
Reading time: About 5 minutes
Prerequisites: None
A security policy is a complete set of protection configurations for a hostname, covering traffic scrubbing (DDoS), vulnerability protection (WAF), bot detection, API security, access control (Rate Limiting, IP/Geo Firewall, Whitelist, Threat Intelligence), and custom rules. Each module can be independently enabled or disabled.
To access: Go to Security Settings > Policies
| Status | Meaning | Recommended Action |
|---|---|---|
| Protected | The hostname is onboarded to the security service and the service order is active | None required |
| Not Protected | The hostname is onboarded but the service order has expired | Renew the service as soon as possible |
| Status | Meaning | Recommended Action |
|---|---|---|
| Deploying | Configuration changes are being deployed to edge nodes | Wait 2–3 minutes and refresh |
| Deployed Successfully | The configuration has been deployed to all edge nodes and is active in the production environment | None required |
Single hostname:
Batch operations:
When a policy is disabled, its configuration is retained. Re-enabling it restores the original configuration immediately.
When multiple hostnames require the same configuration, you can avoid configuring each one individually:
Important: The copy operation overwrites the existing policy configurations of the target hostname. Before proceeding, verify that the target hostname does not have any special configurations that need to be preserved.
When a hostname no longer needs protection from this product:
After removal, all policy configurations for the hostname are permanently deleted. If you need to re-enable protection later, you must onboard the hostname again and reconfigure all policies.
Recommendation: Before removing a hostname, take a screenshot of its configuration as a backup, or use Copy Policies to back up the configuration to another hostname.
When a service order expires, the hostname enters the Not Protected state. After renewal:
Note: After reactivation, WAF (in auto mode) and DDoS managed rules are automatically updated to the latest version. All other configurations remain as they were before the service was suspended.