Configure CC attack defense

This topic describes how to configure Challenge Collapsar (CC) attack defense.

Contents

KAD-based CC attack defense

• Enable or disable CC attack defense

Resource record-based CC attack defense

• Enable or disable CC attack defense

• Add a custom CC attack defense rule

• Modify CC attack defense configuration

---

KAD-based CC attack defense

Enable or disable CC attack defense

1. Log in to the KAD console.
2. Select the target KAD instance from the KAD instance list.
3. Move the pointer to More, and select CC Turn On.

Note: Make sure that the KAD instance is enabled.

To disable CC attack defense, click CC Turn Off.

Back

---

Resource record-based CC attack defense

Enable or disable CC attack defense

1. Log in to the KAD console.
2. Select the target KAD instance from the KAD instance list.
3. In the lower part of the page, click the CC Config tab.
4. Select a resource record, and click Start.

Note: Make sure that the KAD instance is started and CC attack defense is enabled.

You can disable CC attack defense for a DNS record in the same manner.

Back

---

Add a custom CC attack defense rule

1. Select the target KAD instance.
2. In the lower part of the page, click the CC Config tab.

3. Click Manage Rules.
4. Click Add. In the dialog box that appears, enter the rule group name, and click Add.
5. Select the rule group. In the lower part of the page, click Add Subrule.
6. Set rule information, including IP, UA, Referrer, and Path.

Back

---

Modify CC attack defense configuration

1. Select the target KAD instance.
2. In the lower part of the page, click the CC Config tab.
3. Select a resource record, and click Edit in the Operation column.
4. In the editing mode, you can modify the request threshold (QPS) and the CC rules group.

Request threshold (QPS): The maximum number of requests (queries) allowed to be processed by a web server per second (QPS). When the actual number of requests exceeds this threshold, the system detects and blocks malicious attack requests, and sends verification codes to the suspected hosts to verify whether they are attackers. If the number of requests is smaller than this threshold, CC attack defense will not be triggered.

Back