New reference architecture for Cloudflare One and SentinelOne

[securitypedant]

Summary

New reference architecture for Cloudflare One and SentinelOne

Documentation checklist

• The documentation style guide has been adhered to.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[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

Introduced a new reference architecture for integrating Cloudflare One with SentinelOne, enhancing security posture through device-based access policies.

• Added a comprehensive reference architecture document for Cloudflare One and SentinelOne integration.
• Outlined integration setup, configuration options, and deployment scenarios for IT and security professionals.
• Described security capabilities including device posture verification and user risk detection.

Added Files

• src/content/docs/reference-architecture/architectures/cloudflare-sase-with-sentinelone.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]

Preview URL: https://d5091a83.preview.developers.cloudflare.com
Preview Branch URL: https://sthorpe-cloudflare-and-sentinelone-reference-arch.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/reference-architecture/architectures/cloudflare-sase-with-sentinelone/	https://sthorpe-cloudflare-and-sentinelone-reference-arch.preview.developers.cloudflare.com/reference-architecture/architectures/cloudflare-sase-with-sentinelone/

[ranbel]

The article text uses the term "Cloudflare Zero Trust" instead of "Cloudflare One" (e.g. line 19). Should we change the title to match?

[vbmalik]

That works

[securitypedant]

The reason Cloudflare One is used, is because the product team are moving towards Cloudflare One as the branding and not Zero Trust. VB, you need to reflect that in this document. The document should talk about Cloudflare One not Cloudflare Zero Trust.

[ranbel]

Suggested a few places below where it makes sense to use Cloudflare One terminology.

[ranbel]

how does Microsoft relate to SentinelOne?

[vbmalik]

We will need to remove this, It is from previous architecture.

[ranbel]

Remove CASB and Email Security since they are not mentioned in the article.
Add Zero Trust WARP Client

[vbmalik]

Sure

[github-actions]

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

Pattern	Owners
/src/assets/images/reference-architecture/	@securitypedant, @haleycode, @cloudflare/pcx-technical-writing
/src/content/docs/reference-architecture/	@securitypedant, @haleycode, @cloudflare/pcx-technical-writing

[vbmalik]

all completed