Skip to content

Commit 255ea46

Browse files
[WAF] Update threat score (#18537)
--------- Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
1 parent a78c1c7 commit 255ea46

File tree

4 files changed

+39
-37
lines changed

4 files changed

+39
-37
lines changed

src/content/docs/learning-paths/application-security/default-traffic-security/security-level.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,12 @@ title: Security level
33
pcx_content_type: learning-unit
44
sidebar:
55
order: 2
6-
76
---
87

9-
import { Render } from "~/components"
8+
import { Render } from "~/components";
109

1110
<Render file="security-level-description" product="waf" />
1211

12+
<Render file="threat-score-definition" product="waf" />
13+
1314
<Render file="security-level-scores" product="waf" />

src/content/docs/waf/tools/security-level.mdx

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,22 +2,23 @@
22
pcx_content_type: reference
33
source: https://support.cloudflare.com/hc/en-us/articles/200170056-Understanding-the-Cloudflare-Security-Level
44
title: Security Level
5-
65
---
76

8-
import { Render } from "~/components"
7+
import { Render } from "~/components";
98

109
<Render file="security-level-description" product="waf" />
1110

12-
***
11+
---
12+
13+
<Render file="threat-score-definition" product="waf" />
1314

1415
<Render file="security-level-scores" product="waf" />
1516

16-
***
17+
---
1718

1819
## Customize security level
1920

20-
The default security level is *Medium*.
21+
The default security level is _Medium_.
2122

2223
### Update globally
2324

@@ -31,16 +32,14 @@ To update the security level for your entire zone:
3132

3233
To set the security level more selectively, do one of the following:
3334

34-
* Configure it via a [configuration rule](/rules/configuration-rules/).
35-
* Use the **Threat Score** as a **Field** criteria within [custom rules](/waf/custom-rules/). If you are using the Expression Editor, use the `cf.threat_score` field.
35+
- Configure it via a [configuration rule](/rules/configuration-rules/).
36+
- Use the **Threat Score** as a **Field** criteria within [custom rules](/waf/custom-rules/). If you are using the Expression Editor, use the `cf.threat_score` field.
3637

37-
***
38+
---
3839

3940
## Recommendations
4041

4142
To prevent bot IPs from attacking a website:
4243

43-
* A new website owner might set a *Medium* or *High* **Security Level** and lower [**Challenge Passage**](/waf/tools/challenge-passage/) to a value below **30 minutes** to ensure that Cloudflare is constantly protecting the site.
44-
* An experienced website administrator confident in their security settings might set **Security Level** to *Essentially Off* or *Low* while setting a higher [**Challenge Passage**](/waf/tools/challenge-passage/) for a week, month, or even year to provide a less obtrusive visitor experience.
45-
46-
You can also create [WAF custom rules](/waf/custom-rules/) to protect sensitive areas of your website — like comment form pages or login forms — using the [threat score](#threat-score) in your rule expression. The flexibility of custom rules allows you to select the action to take (for example, challenge or block) and exclude specific IP addresses.
44+
- A new website owner might set a _Medium_ or _High_ **Security Level** and lower [**Challenge Passage**](/waf/tools/challenge-passage/) to a value below **30 minutes** to ensure that Cloudflare is constantly protecting the site.
45+
- An experienced website administrator confident in their security settings might set **Security Level** to _Essentially Off_ or _Low_ while setting a higher [**Challenge Passage**](/waf/tools/challenge-passage/) for a week, month, or even year to provide a less obtrusive visitor experience.
Lines changed: 12 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,29 @@
11
---
22
{}
3-
43
---
54

6-
## Threat score
7-
8-
The threat score measures IP reputation across Cloudflare services. This score is calculated based on [Project Honeypot](https://www.projecthoneypot.org/), external public IP information, as well as internal threat intelligence from our [WAF managed rules](/waf/reference/legacy/old-waf-managed-rules/) and [DDoS](/ddos-protection/about/).
9-
10-
The threat score of a request has a value from 0 to 100, where 0 indicates low risk. Values above 10 may represent spammers or bots, and values above 40 identify bad actors on the Internet.
11-
125
## Security levels
136

14-
Security levels are based on the threat score (except *Off* and *I’m Under Attack!*). You can adjust the security level to challenge incoming requests based on the threat they pose.
7+
Security levels are based on the threat score (except _Off_ and _I'm Under Attack!_). You can adjust the security level to challenge incoming requests based on the threat they pose.
158

169
The available security levels are the following:
1710

18-
19-
20-
| Security Level | Threat score range | Description |
21-
| ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------ |
22-
| Off (Enterprise<br/>customers only) | *N/A* | Does not challenge IP addresses. |
23-
| Essentially off | 50–100 | Only challenges IP addresses with the worst reputation. |
24-
| Low | 25–100 | Challenges only threatening visitors. |
25-
| Medium | 15–100 | Challenges both threatening and moderately threatening visitors. |
26-
| High | 0–100 | Challenges all visitors that exhibited threatening behavior within the last 14 days. |
27-
| I’m Under Attack! | *N/A* | Only for use if your website is currently under a DDoS attack. |
28-
29-
11+
| Security Level | Description |
12+
| ----------------------------------- | ------------------------------------------------------------------------------------ |
13+
| Off (Enterprise<br/>customers only) | Does not challenge IP addresses. |
14+
| Essentially off | Only challenges IP addresses with the worst reputation. |
15+
| Low | Challenges only threatening visitors. |
16+
| Medium | Challenges both threatening and moderately threatening visitors. |
17+
| High | Challenges all visitors that exhibited threatening behavior within the last 14 days. |
18+
| I'm Under Attack! | Only for use if your website is currently under a DDoS attack. |
3019

3120
Selecting a higher **Security Level** value means that even requests with a lower risk (that is, with a low [threat score](#threat-score)) will be challenged. Selecting a lower **Security Level** value means that only requests posing a higher risk (that is, with a high threat score) will be challenged.
3221

33-
Security levels from *Essentially off* to *High* will challenge the visitor using a Managed Challenge. When you select *I'm Under Attack!*, which enables [I'm Under Attack mode](/fundamentals/reference/under-attack-mode/), Cloudflare will present a JS challenge page.
22+
Security levels from _Essentially off_ to _High_ will challenge the visitor using a Managed Challenge. When you select _I'm Under Attack!_, which enables [I'm Under Attack mode](/fundamentals/reference/under-attack-mode/), Cloudflare will present a JS challenge page.
3423

3524
:::caution
3625

37-
Only use [I'm Under Attack mode](/fundamentals/reference/under-attack-mode/) when a website is under a DDoS attack. I'm Under Attack mode may affect some actions on your domain, such as your API traffic.
26+
Only use [I'm Under Attack mode](/fundamentals/reference/under-attack-mode/) when a website is under a DDoS attack. I'm Under Attack mode may affect some actions on your domain, such as your API traffic.
3827

39-
To set a custom security level for your API or any other part of your domain, create a [configuration rule](/rules/configuration-rules/).
28+
To set a custom security level for your API or any other part of your domain, create a [configuration rule](/rules/configuration-rules/).
4029
:::
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
{}
3+
---
4+
5+
## Threat score
6+
7+
The threat score measures IP reputation across Cloudflare services. This score is calculated based on [Project Honeypot](https://www.projecthoneypot.org/), external public IP information, as well as internal threat intelligence from our [WAF managed rules](/waf/reference/legacy/old-waf-managed-rules/) and [DDoS](/ddos-protection/about/).
8+
9+
The threat score of a request has a value from 0 to 100, where 0 indicates low risk. Values above 10 may represent spammers or bots, and values above 40 identify bad actors on the Internet.
10+
11+
:::note[Recommendation]
12+
Currently we do not recommend creating rules based on the threat score, since this score is no longer being populated.
13+
:::

0 commit comments

Comments
 (0)