Skip to content

Commit 12874d1

Browse files
Update frequently-asked-questions.mdx
Added additional FAQs and tweaked a few of the existing ones.
1 parent b3a03ce commit 12874d1

File tree

1 file changed

+26
-10
lines changed

1 file changed

+26
-10
lines changed

src/content/docs/ddos-protection/frequently-asked-questions.mdx

Lines changed: 26 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -25,24 +25,24 @@ There are three main DDoS mitigation systems:
2525
3. [Advanced TCP Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-tcp-protection/)
2626
4. [Advanced DNS Protection](/ddos-protection/advanced-ddos-systems/overview/advanced-dns-protection/)
2727

28-
The DDoS Managed Ruleset includes many individual rules. Each rule provides the heuristics that instructs the system how to identify attack traffic. When the DDoS Managed Ruleset identifies an attack, it will generate a real-time fingerprint to match against the attack traffic, and install an ephemeral mitigation rule to mitigate the attack.
28+
The DDoS Managed Ruleset includes many individual rules. Each rule provides the heuristics that instructs the system how to identify DDoS attack traffic. When the DDoS Managed Ruleset identifies an attack, it will generate a real-time fingerprint to match against the attack traffic, and install an ephemeral mitigation rule to mitigate the attack using that fingerprint.
2929

30-
The start time of the attack is when the mitigation rule is installed. The attack ends when there is no more traffic matching the rule. This is a single DDoS attack.
30+
The start time of the attack is when the mitigation rule is installed. The attack ends when there is no more traffic matching the rule. This is a single DDoS attack event.
3131

3232
A DDoS attack therefore has a start time, end time, and additional attack metadata such as:
3333

3434
1. Attack ID
3535
2. Attack vector
3636
3. Mitigating rule
37-
4. Total bytes
38-
5. Total packets
39-
6. Attack target
37+
4. Total bytes and packets
38+
5. Attack target
39+
6. Mitigation action
4040

4141
This information is used to populate the [Executive Summary](/analytics/network-analytics/understand/main-dashboard/#executive-summary) section in the [Network Analytics](/analytics/network-analytics/) dashboard.
4242

4343
It can also be retrieved via GraphQL API using the `dosdAttackAnalyticsGroups` node.
4444

45-
Currently, the concept of a DDoS attack only exists for the Network-layer DDoS Managed Ruleset. There is no such grouping of individual packets, queries, or HTTP requests for the other systems, although we plan to implement it.
45+
Currently, the concept of a DDoS attack event only exists for the Network-layer DDoS Managed Ruleset. There is no such grouping of individual packets, queries, or HTTP requests for the other systems, although we plan to implement it.
4646

4747
---
4848

@@ -84,9 +84,11 @@ Yes. Using our anycast network, along with Traffic Manager, Unimog, and Plurimog
8484

8585
---
8686

87-
## Where can I see DDoS trends?
87+
## Where can I see latest DDoS trends?
8888

89-
Refer to [Reports](/ddos-protection/reference/reports/) or [Radar](/radar/) for more information on viewing DDoS trends.
89+
Cloudflare publishes quarterly DDoS reports and coverage of signficant DDoS attacks. The publications are available on our [blog website](https://blog.cloudflare.com/tag/ddos-reports/) and as interactive reports on the [Cloudflare Radar Reports website](https://radar.cloudflare.com/reports?q=DDoS).
90+
91+
You can also view [Cloudflare Radar](https://radar.cloudflare.com/) for near real-time insights and trends.
9092

9193
---
9294

@@ -106,6 +108,20 @@ These tools and attacks exploit different aspects of network protocols and behav
106108

107109
---
108110

109-
## Can I exclude a user agent from DDoS protection?
111+
## Can I exclude a specific user agent from the HTTP DDoS protection?
112+
113+
Yes, you can create an [override](/managed-rulesets/http/override-expressions/) and use the expression fields to match against HTTP requests with the user agent. There are a variety of [fields](/managed-rulesets/http/override-expressions/#available-expression-fields) that you can use.
114+
You can then adjust the [sensitivity level](/managed-rulesets/http/override-parameters/#sensitivity-level) or [mitigation action](/http/override-parameters/#action).
115+
116+
Refer to the guide on how to [create an override](/managed-rulesets/http/configure-dashboard/#create-a-ddos-override).
117+
118+
The use of expression fields is subject to [availability](#availability).
119+
120+
## Does Cloudflare charge for DDoS attack traffic?
121+
122+
No. Sinece 2017, Cloudflare offers [free unmeterered and unlimited DDoS protection](https://blog.cloudflare.com/unmetered-mitigation/). There is no limit to the number of DDoS attacks, their duration, or their size. Cloudflare's billing systems automatically exclude DDoS attack traffic from your usage.
123+
124+
125+
126+
110127

111-
You can override a user agent using a low sensitivity level or `Log` if you want visibility.

0 commit comments

Comments
 (0)