Skip to content

Commit 171f7f2

Browse files
[Docs] Threat score follow up changes
1 parent e2fd147 commit 171f7f2

File tree

3 files changed

+3
-9
lines changed

3 files changed

+3
-9
lines changed

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,10 @@ title: Security Level
66

77
import { Render } from "~/components";
88

9-
<Render file="security-level-description" product="waf" />
10-
11-
---
9+
<Render file="security-level-scores" product="waf" />
1210

1311
<Render file="threat-score-definition" product="waf" />
1412

15-
<Render file="security-level-scores" product="waf" />
13+
1614

1715
---

src/content/partials/waf/security-level-scores.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
{}
33
---
44

5-
## Security level
6-
75
Cloudflare provides _I'm Under Attack!_ as a security level.
86

97
Cloudflare's Under Attack mode performs additional security checks to help mitigate layer 7 DDoS attacks.

src/content/partials/waf/threat-score-definition.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,7 @@
44

55
## Threat score
66

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.
7+
Previously, a threat score represented a Cloudflare threat score from 0–100, where 0 indicates low risk. Now, a threat score is default to 0.
108

119
:::note[Recommendation]
1210
Currently we do not recommend creating rules based on the threat score, since this score is no longer being populated.

0 commit comments

Comments
 (0)