> For the complete documentation index, see [llms.txt](https://learn.goodhearttech.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.goodhearttech.org/tech-guides/security-guides/cloudflare-zero-trust-setup.md). # Cloudflare Zero Trust Setup ## :closed\_lock\_with\_key: What is Zero Trust? [Cloudflare Zero Trust](https://www.cloudflare.com/zero-trust/) is a security approach that ensures trust verification for every user and device, wherever they are. It boosts security by confirming identities and **reducing risks in remote work**. It's also cost-effective, offering free access for up to 50 users and easy integration with identity providers like Microsoft or Google. ## :pen\_ballpoint: Sign Up For Cloudflare Zero Trust * Log in with your [Cloudflare account](https://dash.cloudflare.com/). * Ensure you have a credit on file. You can't proceed without this, even though Zero Trust is free for 50 users. To add a credit card, navigate to **Billing** > **Payment Info** * ![](/files/0nXp9VtUHUI7tLdeJ63K) * Navigate back to the [main dashboard](https://dash.cloudflare.com/). * Click on **Zero Trust** on the left sidebar. * A wizard will launch for you to set up a Cloudflare Team name. Use the name of your organization without spaces. For example, [Good Heart Tech](https://goodhearttech.org/) could be goodhearttech. * Select the **FREE** Plan. ## :hammer: Setup Zero Trust Once in the Zero trust portal, setup the rest of the Team and portal and configure the following settings: * Settings < Custom Pages < make a note of the **Team domain**. This is what users will use to log in to Cloudflare Zero Trust using the [WARP client ](https://developers.cloudflare.com/warp-client/)or URL. * Settings < Custom Pages < Login Page < Customize. * Set the message to: *If you are not authorized, close this page immediately.* * (Optional branding) Update the background color and logo URL. * Settings < Authentication < **Configure Azure AD SSO** according to the Cloudflare Documentation * If you'd like to integrate Azure AD or another identity provider for signing into Cloudflare Zero Trust, you can use these docs: [Azure AD](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/azuread/) / [Others](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/) ## :construction\_site: Setup Access Group, Tunnels, & Applications ### Access Group Access groups allow organizations to create specific access policies based on user roles, devices, and locations. This enhances security by ensuring that only authorized individuals can access sensitive data, applications, and services. In the Zero Trust Portal, navigate to: **Access** < **Access Groups** < Create an Access group for each group needed, usually just one. Add in the company email domains. ### Tunnels Cloudflare Tunnels provide a secure and efficient way to connect your infrastructure to Cloudflare's global network. They enable organizations to route traffic through Cloudflare for enhanced performance and security. This ensures that web applications and services remain highly available and protected from online threats. * In the Zero Trust Portal, navigate to **Network** < **Tunnels** < + **Create a Tunnel.** Name the tunnel. * Use the code displayed on the screen to install the Tunnel ([cloudflared](https://github.com/cloudflare/cloudflared)) on the server hosting the services. * If configuring APPLICATION access (specific port on a server), do the following: * On the first screen, select self-hosted. * In the **Public hostname** tab of the Tunnel, create an entry for each web-based resource you want to publish to the Zero-Trust portal. Add a public hostname using a subdomain, and point the application to the correct local host and port. Creating a public hostname entry creates a public DNS CNAME record. * For services running without valid SSL certs, check the Do Not Verify TLS option. * If configuring NETWORK access, do the following: * In the **private network** tab of the Tunnel, specify the IPs that Zero Trust will have access to, typically the whole network. Example: *192.168.1.0/24* * Go to *Settings < WARP Client < Default profile < **Split Tunnels** < Manage* < and delete the class of IP Addresses that represent the primary corporate network and tunneled resources. * If you have a local Active Directory domain, you should add the domain to **Local Domain Fallback** setting under *Settings < WARP Client < Default profile.* This ensures that connected agents will use the on-premise DNS options provided by Active Directory but bypasses Cloudflare's logging. ## :man\_technologist: Applications We'll create an application for all applications that are required on the portal (typically all web-based applications). Each application must relate to an existing DNS entry or tunnel public hostname. * Go to Access < Applications < Add an application * Select Self-Hosted * Enter the application name, subdomain, domain, and path if applicable. * Enable App in App Launcher * By default, enable all ID providers unless the client has other requirements. Click **Next**. * For the Policy, give it a name, then select the **Access Group** you made previously. Hit **Next**. * The last tab, Setup, can be left as-is. ## :computer: WARP Client Deployment & Setup The [Cloudflare WARP client ](https://1.1.1.1/)should be deployed to all PCs that need to connect to the Cloudflare Network and access the internet securely. * Deploy [Cloudflare WARP](https://1.1.1.1/) using your preferred method for software deployment (we like [Chocolatey](https://community.chocolatey.org/packages/warp)) * Have users follow the following steps to configure Zero Trust on endpoints: * In the WARP Client, right-click the tray icon and go to **Preferences**. Then go to **Account** < Login with Cloudflare Zero Trust. * Instruct users to log in with their Cloudflare team name, which should be similar to their company name. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://learn.goodhearttech.org/tech-guides/security-guides/cloudflare-zero-trust-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.