Zero Trust for Cloudflares
Zero Trust in Cloudflare replaces network-based trust with identity-based checks on every request. Cloudflare Access puts a login and policy in front of internal apps, and Cloudflare Tunnel connects private services outward to Cloudflare through cloudflared, so no inbound firewall ports need to be opened.
Stage: Security · Part of the Cloudflare roadmap · Last reviewed 19 November 2026
What to learn in Zero Trust
- Create an Access application with an identity provider login
- Write an Access policy that allows a specific email domain
- Run cloudflared to expose an internal web app through a Tunnel
- Explain why a Tunnel removes the need for a public origin IP
- Describe how Zero Trust differs from a traditional VPN
Zero Trust interview questions
How does Cloudflare Tunnel work without opening inbound ports?
The cloudflared daemon on your server makes outbound connections to Cloudflare, and Cloudflare forwards approved requests back through them. Because the origin only initiates outbound traffic, firewalls can block all inbound connections.
What is the Zero Trust principle?
Never trust a request because of where it comes from. Each request is verified for user identity, device posture and context, and given the least access needed. This differs from a VPN, which usually trusts anyone who is inside the network.
Where Zero Trust fits in the Cloudflare roadmap
Zero Trust belongs to the Security stage (intermediate level), which takes about 14 hours. Protect applications.
Other units in this stage
Back to the full Cloudflare roadmap