[Draft] Document hardware backed registration

[lpraneis]

Summary

Screenshots (optional)

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.
• 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.

[github-actions]

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

Pattern	Owners
/src/content/docs/cloudflare-one/team-and-resources/devices/	@ranbel, @cf-rhett, @csujedihy, @lpraneis, @jiulingz, @tojens-ietf, @cloudflare/cf1-reviewers, @elithrar, @cloudflare/product-owners

[ask-bonk]

Content is clean — no build breakers, frontmatter errors, or style guide violations. Two process items need attention before this leaves Draft.

Issues:

• MEDIUM: PR body is empty. Fill in the Summary section and complete the checklist before marking Ready for review.
• MEDIUM: No changelog entry for this new feature. Consider adding one in so customers can discover hardware-backed registration via RSS and Discord.

Summary of changes:

• Adds — a concept page explaining how hardware-backed registration uses TPM/Secure Enclave to bind device registrations to non-exportable keys and authenticate API requests with mTLS.
• Adds parameter documentation to , including feature availability matrix and value definitions.

[ask-bonk]

Review completed for PR #31354.

Labels applied: product:cloudflare-one, documentation, content:new, triage

Review posted: #31354 (review)

---

What this PR changes

• New page: hardware-backed-registration.mdx — explains how the Cloudflare One Client can bind device registrations to non-exportable hardware keys (TPM 2.0 / Secure Enclave) and authenticate API requests with mTLS.
• Updated page: parameters.mdx — adds the hardware_backed_registration parameter definition, feature availability matrix, and value options.

Issues flagged

• MEDIUM: The PR body is empty (still using the template). The author should fill in the Summary and complete the checklist before marking Ready for review.
• MEDIUM: No changelog entry was added for this new feature. Adding one to src/content/changelog/cloudflare-one/ would help customers discover it via RSS, Discord, and X.

Content assessment
No build breakers, frontmatter errors, or style guide violations found. The new page has correct frontmatter (title, description, pcx_content_type), imports Details from ~/components, uses sentence-case headings, root-relative links with trailing slashes, and active voice. The parameter addition in parameters.mdx is consistent with the existing reference format.

github run

[github-actions]

Preview URL: https://ca62c590.preview.developers.cloudflare.com
Preview Branch URL: https://lpraneis-hardware-backed-reg.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/hardware-backed-registration/	https://lpraneis-hardware-backed-reg.preview.developers.cloudflare.com/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/hardware-backed-registration/
https://developers.cloudflare.com/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/	https://lpraneis-hardware-backed-reg.preview.developers.cloudflare.com/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/parameters/