Cloudflare Zero Trust and Tunnels. Secure Access to Your Systems Without Opening Ports
Cloudflare Tunnel and Access can publish an internal system safely, with no inbound firewall ports open and a login check in front.
Cloudflare offers a set of services under the name Cloudflare One, often referred to as Zero Trust, which can replace parts of a traditional VPN and firewall set up for a small business. Three pieces are worth understanding: Tunnel, Access and Gateway. They are most useful when you have an internal system, such as a web application, a file server interface or a remote desktop, that people need to reach from outside the office.
Cloudflare Tunnel uses a small piece of software called cloudflared, installed on a machine inside your network. It makes an outbound connection to Cloudflare, and traffic for your application travels back down that connection. Because the connection starts from the inside, you do not need to open any inbound ports on your firewall or expose your office's address to the internet. That removes a common route for attackers, who constantly scan the internet for open ports.
Cloudflare Access sits in front of the application and checks who is asking. It connects to an identity provider, such as Microsoft Entra ID, so staff sign in with the accounts and MFA they already use. You write policies saying which people or groups may reach which application, and you can add conditions such as country, or whether the device is managed. Every request is checked, and access can be removed immediately by disabling the user or the policy.
Cloudflare Gateway covers the other direction, protecting people as they browse. It can filter DNS requests and web traffic to block known malicious or unwanted sites, apply policies on content categories and log activity. It can be rolled out to laptops with a small client app, which is useful for staff who work away from the office.
Cloudflare has offered a free plan for Zero Trust for small teams, which has covered up to 50 users, but plans and limits change, so check Cloudflare's current pricing page before relying on it. Be sure to think about the dependency too. You are placing a third party in the path of your access, so protect the Cloudflare account with MFA, limit who can administer it, and plan what happens if the service is unavailable.
A sensible start is to pick one internal application, publish it through Tunnel with an Access policy, test it with a few people and then expand. Dragonfly IT can help you decide whether it suits your setup. Contact us to talk it through.
