Skip to content

Commit 5f49888

Browse files
[Rules, WAF] Update security level and threat score (#20794)
* [Security Center] Deprecate security level and threat score * Changing end of life date, updating security level table * Deleting page and adding redirect * Remove deprecate pill, update content in other parts of the docs * Fixing redirect * Update src/content/docs/rules/configuration-rules/settings.mdx Co-authored-by: Pedro Sousa <[email protected]> * Updating api-deprecations file * Apply suggestions from code review Co-authored-by: Pedro Sousa <[email protected]> * Removing security level mentions * Updating api deprecations yaml file --------- Co-authored-by: Pedro Sousa <[email protected]>
1 parent 62a45db commit 5f49888

File tree

6 files changed

+19
-65
lines changed

6 files changed

+19
-65
lines changed

public/_redirects

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -777,7 +777,7 @@
777777
/learning-paths/secure-o365-email/ /learning-paths/secure-o365-email/concepts/ 301
778778
/learning-paths/workers/ /learning-paths/workers/concepts/ 301
779779
/learning-paths/zero-trust-web-access/ /learning-paths/zero-trust-web-access/concepts/ 301
780-
780+
/learning-paths/application-security/default-traffic-security/security-level/ /learning-paths/application-security/default-traffic-security/browser-integrity/ 301
781781

782782
# more redirects in the /dynamic/ section
783783

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

Lines changed: 0 additions & 14 deletions
This file was deleted.

src/content/docs/rules/configuration-rules/settings.mdx

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -266,16 +266,12 @@ API configuration property name: `"rocket_loader"` (boolean).
266266

267267
[Security Level](/waf/tools/security-level/) controls Managed Challenges for requests from low reputation IP addresses.
268268

269-
Use this setting to select the security level for matching requests:
269+
On the Cloudflare dashboard, you can turn Under Attack mode on or off.
270270

271271
- Off
272-
- Essentially Off
273-
- Low
274-
- Medium
275-
- High
276272
- I'm Under Attack
277273

278-
Refer to [Security levels](/waf/tools/security-level/#security-levels) for more information on these values.
274+
Refer to [Under Attack mode](/fundamentals/reference/under-attack-mode/) for more information.
279275

280276
<Details header="API information">
281277

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

Lines changed: 1 addition & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -14,32 +14,4 @@ import { Render } from "~/components";
1414

1515
<Render file="security-level-scores" product="waf" />
1616

17-
---
18-
19-
## Customize security level
20-
21-
The default security level is _Medium_.
22-
23-
### Update globally
24-
25-
To update the security level for your entire zone:
26-
27-
1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and zone.
28-
2. Go to **Security** > **Settings**.
29-
3. For **Security Level**, select an option.
30-
31-
### Update selectively
32-
33-
To set the security level more selectively, do one of the following:
34-
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.
37-
38-
---
39-
40-
## Recommendations
41-
42-
To prevent bot IPs from attacking a website:
43-
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.
17+
---

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

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

5-
## Security levels
5+
## Security level
66

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.
7+
Cloudflare provides _I'm Under Attack!_ as a security level.
88

9-
The available security levels are the following:
9+
Cloudflare's Under Attack mode performs additional security checks to help mitigate layer 7 DDoS attacks.
1010

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. |
19-
20-
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.
21-
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 [Under Attack mode](/fundamentals/reference/under-attack-mode/), Cloudflare will present a JS challenge page.
11+
When you select _I'm Under Attack!_, which enables [Under Attack mode](/fundamentals/reference/under-attack-mode/), Cloudflare will present a JS challenge page.
2312

2413
:::caution
2514

src/content/release-notes/api-deprecations.yaml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,17 @@ productLink: "/fundamentals/"
55
productArea: Core platform
66
productAreaLink: /fundamentals/reference/changelog/platform/
77
entries:
8+
9+
- publish_date: "2025-03-17"
10+
title: "Security Center: Security level and Threat Score are now automated"
11+
description: |-
12+
13+
Change date: March 17, 2025
14+
15+
Cloudflare now combines the IP address threat signal with threshold and botnet data, no longer requiring you to set a sensitivity level. Users will no longer be able to set Security level via the Cloudflare dashboard. However, users can still rely on the existing API or Terraform configuration to set a Security level.
16+
17+
If you are using threat score in rule expressions, you should review those expressions to make sure the rule still triggers when appropriate. Cloudflare will audit and migrate your configuration in the future to update any references to threat score. If you are using the Rulesets API or Terraform to push your configuration, you should review your scripts and pipelines before the end of Q1 2026 to prevent issues.
18+
819
- publish_date: "2025-03-11"
920
title: "Cloudflare Radar: Layer 7 attack magnitude parameter"
1021
description: |-

0 commit comments

Comments
 (0)