[Security] Update settings (new nav)

[pedrosousa]

Summary

Addresses PCX-17609.

[hyperlint-ai]

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

Updated security settings documentation to enhance clarity and organization, and added a new use case for blocking traffic by geographical location.

• Reorganized the content structure for better readability in the security settings documentation.
• Added a new use case for blocking traffic by geographical location.
• Updated existing use cases to reflect changes in country codes for blocking traffic.

Modified Files

• src/content/docs/security/settings.mdx
• src/content/docs/waf/custom-rules/use-cases/allow-traffic-from-specific-countries.mdx
• src/content/docs/waf/custom-rules/use-cases/block-traffic-from-specific-countries.mdx
• src/content/docs/waf/rate-limiting-rules/use-cases.mdx

Added Files

• src/content/docs/waf/custom-rules/use-cases/block-by-geographical-location.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.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/docs/api-shield/	@patriciasantaana, @cloudflare/pcx-technical-writing
/src/content/docs/bots/	@patriciasantaana, @cloudflare/pcx-technical-writing
/src/content/docs/cloudflare-challenges/	@patriciasantaana, @cloudflare/pcx-technical-writing
/src/content/docs/page-shield/	@pedrosousa, @cloudflare/pcx-technical-writing
/src/content/docs/security-center/	@jason-cf, @cloudflare/pcx-technical-writing
*	@cloudflare/pcx-technical-writing
/src/content/docs/waf/	@pedrosousa, @cloudflare/firewall, @cloudflare/pcx-technical-writing

[github-actions]

Preview URL: https://f5863446.preview.developers.cloudflare.com
Preview Branch URL: https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/security/settings/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/security/settings/
https://developers.cloudflare.com/api-shield/security/schema-validation/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/api-shield/security/schema-validation/
https://developers.cloudflare.com/security-center/infrastructure/security-file/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/security-center/infrastructure/security-file/
https://developers.cloudflare.com/api-shield/management-and-monitoring/developer-portal/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/api-shield/management-and-monitoring/developer-portal/
https://developers.cloudflare.com/waf/custom-rules/use-cases/block-by-geographical-location/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/waf/custom-rules/use-cases/block-by-geographical-location/
https://developers.cloudflare.com/bots/additional-configurations/managed-robots-txt/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/bots/additional-configurations/managed-robots-txt/
https://developers.cloudflare.com/bots/get-started/bot-management/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/bots/get-started/bot-management/
https://developers.cloudflare.com/waf/rate-limiting-rules/use-cases/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/waf/rate-limiting-rules/use-cases/
https://developers.cloudflare.com/waf/tools/browser-integrity-check/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/waf/tools/browser-integrity-check/
https://developers.cloudflare.com/api-shield/security/jwt-validation/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/api-shield/security/jwt-validation/
https://developers.cloudflare.com/waf/get-started/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/waf/get-started/
https://developers.cloudflare.com/waf/custom-rules/use-cases/block-traffic-from-specific-countries/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/waf/custom-rules/use-cases/block-traffic-from-specific-countries/
https://developers.cloudflare.com/api-shield/management-and-monitoring/endpoint-labels/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/api-shield/management-and-monitoring/endpoint-labels/
https://developers.cloudflare.com/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/
https://developers.cloudflare.com/page-shield/get-started/	https://pedro-pcx-17609-new-nav-q2-update-settings.preview.developers.cloudflare.com/page-shield/get-started/

[Oxyjun]

I know this is just documenting UI - but I think unsecure would be the better term to use, than insecure.

[pedrosousa]

cc @db-cloudflare

I asked Google and the AI summary included the following:

"Insecure" and "unsecure" can be synonyms, but "insecure" often carries a connotation of lacking confidence or feeling anxious, while "unsecure" is more commonly used to describe a lack of physical security or stability. In cybersecurity, "insecure" is the preferred term, while "unsecured" might describe a system with security measures that are not properly utilized.

So I think we can keep "insecure" for now (also, it's the word used in the dashboard).