From d9d7058f7811f0ea89412c0aeb4417e20b2669e6 Mon Sep 17 00:00:00 2001 From: "hyperlint-ai[bot]" <154288675+hyperlint-ai[bot]@users.noreply.github.com> Date: Sun, 9 Mar 2025 06:11:11 +0000 Subject: [PATCH] Fix issue: WorkspaceTaskSubType.META_DESCRIPTION --- .../docs/ddos-protection/change-log/index.mdx | 28 +------------------ 1 file changed, 1 insertion(+), 27 deletions(-) diff --git a/src/content/docs/ddos-protection/change-log/index.mdx b/src/content/docs/ddos-protection/change-log/index.mdx index 1a0cb31926765ba..034c82c3aa6c435 100644 --- a/src/content/docs/ddos-protection/change-log/index.mdx +++ b/src/content/docs/ddos-protection/change-log/index.mdx @@ -1,27 +1 @@ ---- -title: "Changelog" -pcx_content_type: changelog -release_notes_file_name: - - ddos-network - - ddos-http - - ddos -release_notes_name: DDoS Protection -sidebar: - order: 20 -description: Stay updated with Cloudflare's DDoS protection. Discover the latest rule updates, accuracy improvements, and threat landscape adaptations. -head: - - tag: title - content: Changelog for global changes to DDoS protection ---- - -Cloudflare has a regular cadence of releasing updates and new rules to the DDoS managed rulesets. The updates either improve a rule's accuracy, lower false positives rates, or increase the protection due to a change in the threat landscape. - -The release cycle for a new rule within the regular cadence follows this process: - -- Cloudflare adds a new rule configured with the _Log_ action, and announces the rule in the "Scheduled changes" section of each managed ruleset. -- From that point on, if this rule matches any traffic, the matched traffic will be visible in one of the [analytics dashboards](/ddos-protection/reference/analytics/). If you suspect this might be a false positive, you can lower the sensitivity for that rule. Refer to [Handle a false positive](/ddos-protection/managed-rulesets/adjust-rules/false-positive/) for details. -- Cloudflare updates the rule action to mitigate traffic (for example, using the _Block_ action) after a period of at least seven days, usually on a Monday. The exact date is shown in the scheduled changes list. - -Changes to existing rules follow the same process, except that Cloudflare will create a temporary updated rule (denoted as `BETA` in rule description) before updating the original rule on the next release cycle. - -Cloudflare is very proactive in responding to new attack vectors, which may need to be released outside of the 7-day cycle, defined as an Emergency Release. This emergency release is only used to respond to new high priority threats with a low false positive probability. +---\ntitle: "Changelog"\npcx_content_type: changelog\nrelease_notes_file_name:\n - ddos-network\n - ddos-http\n - ddos\nrelease_notes_name: DDoS Protection\nsidebar:\n order: 20\ndescription: Stay informed with Cloudflare's DDoS Protection changelog. Access updates on rule accuracy, false positive rates, and threat landscape changes.\nhead:\n - tag: title\n content: Changelog for global changes to DDoS protection\n---\n\nCloudflare has a regular cadence of releasing updates and new rules to the DDoS managed rulesets. The updates either improve a rule's accuracy, lower false positives rates, or increase the protection due to a change in the threat landscape.\n\nThe release cycle for a new rule within the regular cadence follows this process:\n\n- Cloudflare adds a new rule configured with the _Log_ action, and announces the rule in the "Scheduled changes" section of each managed ruleset.\n- From that point on, if this rule matches any traffic, the matched traffic will be visible in one of the [analytics dashboards](/ddos-protection/reference/analytics/). If you suspect this might be a false positive, you can lower the sensitivity for that rule. Refer to [Handle a false positive](/ddos-protection/managed-rulesets/adjust-rules/false-positive/) for details.\n- Cloudflare updates the rule action to mitigate traffic (for example, using the _Block_ action) after a period of at least seven days, usually on a Monday. The exact date is shown in the scheduled changes list.\n\nChanges to existing rules follow the same process, except that Cloudflare will create a temporary updated rule (denoted as `BETA` in rule description) before updating the original rule on the next release cycle.\n\nCloudflare is very proactive in responding to new attack vectors, which may need to be released outside of the 7-day cycle, defined as an Emergency Release. This emergency release is only used to respond to new high priority threats with a low false positive probability.