Skip to content

Commit 01be12a

Browse files
Updating api-deprecations file
1 parent 41e86d2 commit 01be12a

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,14 @@ productAreaLink: /fundamentals/reference/changelog/platform/
77
entries:
88

99
- publish_date: "2025-03-17"
10-
title: "Security Center: Security level and Threat Score are deprecated"
10+
title: "Security Level and Threat Score changes"
1111
description: |-
12-
Deprecation date: March 17, 2025
12+
13+
Change date: March 17, 2025
1314
14-
End of life date: March 31, 2026
15+
Cloudflare now combines the IP address threat signal with threshold and botnet data, no longer requiring you to set a sensitivity level. Setting Security Level via API or Terraform to `low`, `medium`, or `high` will have no effect. Values `off`, `essentially_off`, and `under_attack` will still work as before.
1516
16-
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.
17+
Additionally, threat score values will no longer be populated. If you are using threat score in rule expressions, you will not need to make any changes; Cloudflare will audit and migrate your configuration in the future to update any references to threat score. However, 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.
1718
1819
- publish_date: "2025-03-11"
1920
title: "Cloudflare Radar: Layer 7 attack magnitude parameter"

0 commit comments

Comments
 (0)