[Rules, WAF] Update security level and threat score

public/_redirects

@@ -777,7 +777,7 @@
 /learning-paths/secure-o365-email/ /learning-paths/secure-o365-email/concepts/ 301
 /learning-paths/workers/ /learning-paths/workers/concepts/ 301
 /learning-paths/zero-trust-web-access/ /learning-paths/zero-trust-web-access/concepts/ 301
-
+/learning-paths/application-security/default-traffic-security/security-level/ /learning-paths/ 301
 
 # more redirects in the /dynamic/ section
 

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

@@ -2,6 +2,9 @@
 pcx_content_type: reference
 source: https://support.cloudflare.com/hc/en-us/articles/200170056-Understanding-the-Cloudflare-Security-Level
 title: Security Level
+sidebar:
+  badge:
+    text: Deprecated
 ---
 
 import { Render } from "~/components";

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

@@ -4,22 +4,16 @@
 
 ## Security levels
 
-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.
+Security levels aim at protecting websites from malicious activity. 
 
 The available security levels are the following:
 
 | Security Level                      | Description                                                                          |
 | ----------------------------------- | ------------------------------------------------------------------------------------ |
-| Off (Enterprise<br/>customers only) | Does not challenge IP addresses.                                                     |
-| Essentially off                     | Only challenges IP addresses with the worst reputation.                              |
-| Low                                 | Challenges only threatening visitors.                                                |
-| Medium                              | Challenges both threatening and moderately threatening visitors.                     |
-| High                                | Challenges all visitors that exhibited threatening behavior within the last 14 days. |
+| Always protected                                                   | Your domain is protected by default.
 | I'm Under Attack!                   | Only for use if your website is currently under a DDoS attack.                       |
 
-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.
-
-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.
+When you select _I'm Under Attack!_, which enables [Under Attack mode](/fundamentals/reference/under-attack-mode/), Cloudflare will present a JS challenge page.
 
 :::caution
 

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

@@ -5,6 +5,16 @@ productLink: "/fundamentals/"
 productArea: Core platform
 productAreaLink: /fundamentals/reference/changelog/platform/
 entries:
+
+  - publish_date: "2025-03-17"
+    title: "Security Center: Security level and Threat Score are deprecated"
+    description: |-
+      Deprecation date: March 17, 2025
+
+      End of life date: March 31, 2026
+
+      Security Level and Threat Score are deprecated and will be removed on March 17, 2025. They will no longer be available via the Rulesets API or Terraform. They will not be available to be configured on the Cloudflare dashboard.
+
   - publish_date: "2025-03-11"
     title: "Cloudflare Radar: Layer 7 attack magnitude parameter"
     description: |-