Onboard Your First Hostname
최신 업데이트：2026-08-19 17:59:27
Reading time: About 5 minutes
Prerequisites: You have activated the product’s service, and the hostname has been onboarded to CDN acceleration on the platform
If the hostname you want to protect is not in the list, first add the hostname under the corresponding CDN acceleration service, and then return here to continue.
Step 1: Go to the Security Policy Page
- Log in to the console, find the security product you are using under the activated products, and click to enter it
- Go to Security Settings > Policies
- Click + Protected Hostname
Step 2: Select the Hostname
Select the hostname you want to protect from the list, and click Next.
Step 3: Select an Initial Policy
When onboarding, you need to select an initial protection policy for the hostname. There are two ways:
| Method | Description | Use When |
|---|---|---|
| Recommended default policies | System-preset default configuration, ready to use out of the box, and can be fine-tuned later as needed | First-time onboarding, with no other hostname to reference |
| Duplicate policies from an existing hostname | Copies the protection policy of an onboarded hostname to quickly align configuration | Adding a new hostname under the same business, when you want it to stay consistent with the existing hostname |
Important: When you select “Duplicate policies from an existing hostname”, dynamic rules and thresholds generated through automatic traffic learning are not copied, including the intelligent threshold of L7 DDoS Protection, rules generated by AI Protection, and WAF rule exception suggestions. These items need to be re-learned on the new hostname.
Step 4: Confirm the Initial Policy Configuration
Based on your selection in the previous step, confirm the initial configuration of each module:
If you select “Recommended default policies”:
If you have no special protection requirements, keep the default policy to complete onboarding. After onboarding, you can view protection details through reports and logs, and then tune the policy. If you have special requirements, you can fine-tune the following modules in this step:
| Module | Default Status | Recommended Initial Mode |
|---|---|---|
| DDoS Protection | Enabled, moderate level | Protection Mode (can take effect directly) |
| WAF | Enabled | Monitor Mode (recommended to switch to Protection after 3–7 days of monitoring) |
| Threat Intelligence | Enabled | Block Mode (low false positive rate, can take effect directly) |
| Bot Management | Disabled | Recommended to first understand the traffic composition in Log Mode before enabling |
| API Security | Disabled | Enable as needed |
If you select “Duplicate policies from an existing hostname”:
Confirm that the policy of the selected reference hostname meets your expectations, and click Next to complete onboarding.
Step 5: Deploy and Verify
After onboarding is complete, the configuration is automatically deployed to the edge PoPs and typically takes 2–3 minutes to take effect.
After deployment is complete, go to Analysis & Logs > Web Security Trends, and select the hostname to view:
- Whether Total Requests has data (to confirm that traffic has passed through the edge PoPs)
- Whether Attack Requests or Monitored Requests have any hits (to confirm the policy is running)