Skip to content

Commit c21058e

Browse files
Maddy-Cloudflarepedrosousa
authored andcommitted
[Docs] Threat score follow up changes (#20953)
* [Docs] Threat score follow up changes * adding always protected * Apply suggestions from code review Co-authored-by: Pedro Sousa <[email protected]> * Updating yaml file * Apply suggestions from code review Co-authored-by: Pedro Sousa <[email protected]> --------- Co-authored-by: Pedro Sousa <[email protected]>
1 parent 788db0e commit c21058e

File tree

4 files changed

+7
-11
lines changed

4 files changed

+7
-11
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/fields/index.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -602,9 +602,9 @@ entries:
602602
data_type: Number
603603
categories: [Request]
604604
keywords: [request, cloudflare, score, client, visitor]
605-
summary: Represents a Cloudflare threat score from 0–100, where 0 indicates low risk.
605+
summary: Represents a Cloudflare threat score.
606606
description: |-
607-
Values above 10 may represent spammers or bots, and values above 40 identify bad actors on the Internet. It is rare to see values above 60. A common recommendation is to challenge requests with a score above 10 and to block those above 50.
607+
Previously, a threat score represented a Cloudflare threat score from 0–100, where 0 indicated low risk. Now, the threat score is always `0` (zero).
608608
609609
- name: cf.tls_cipher
610610
data_type: String

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

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

5-
## Security level
5+
In the Cloudflare dashboard, security level has the value _Always protected_ and you cannot change this setting. To turn Under Attack mode on or off, use the separate toggle.
66

7-
Cloudflare provides _I'm Under Attack!_ as a security level.
7+
In the API and in Terraform, use security level to turn Under Attack mode on or off.
88

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

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, the threat score is always `0` (zero).
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)