Skip to content

Conversation

@Maddy-Cloudflare
Copy link
Contributor

No description provided.

@Maddy-Cloudflare Maddy-Cloudflare requested review from a team and pedrosousa as code owners March 13, 2025 17:07
@Maddy-Cloudflare Maddy-Cloudflare marked this pull request as draft March 13, 2025 17:07
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Mar 13, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Deprecated the security level and threat score in the documentation, indicating that these features are no longer recommended for use.

  • Added 'Deprecated' badge to security level documentation pages
  • Removed detailed descriptions of security levels and their implications
  • Updated references to security levels in related documentation

Modified Files

  • src/content/docs/learning-paths/application-security/default-traffic-security/security-level.mdx
  • src/content/docs/waf/tools/security-level.mdx
  • src/content/partials/waf/security-level-scores.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

What is Hyperlint?

Hyperlint is an AI agent that helps you write, edit, and maintain your documentation.

Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 14, 2025

This PR changes current filenames or deletes current files. Make sure you have redirects set up to cover the following paths:

  • /learning-paths/application-security/default-traffic-security/security-level/

@github-actions github-actions bot added the product:rules Related to rules label Mar 14, 2025
@pedrosousa pedrosousa changed the title [Security Center] Deprecate security level and threat score [Rules, WAF] Update security level and threat score Mar 17, 2025
@Maddy-Cloudflare Maddy-Cloudflare marked this pull request as ready for review March 17, 2025 11:11
@Maddy-Cloudflare Maddy-Cloudflare marked this pull request as draft March 17, 2025 11:19
@Maddy-Cloudflare Maddy-Cloudflare marked this pull request as ready for review March 17, 2025 11:58
@Maddy-Cloudflare Maddy-Cloudflare merged commit 5f49888 into production Mar 17, 2025
11 checks passed
@Maddy-Cloudflare Maddy-Cloudflare deleted the maddy/security-center-pcx-14467 branch March 17, 2025 14:13
RebeccaTamachiro pushed a commit that referenced this pull request Apr 21, 2025
* [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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants