<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Zero-Trust-Network-Access on mishraJi</title>
    <link>https://blog.mishraji.org/tags/zero-trust-network-access/</link>
    <description>Recent content in Zero-Trust-Network-Access on mishraJi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 09 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.mishraji.org/tags/zero-trust-network-access/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Part 2: Cloudflare Zero Trust - TLS Inspection</title>
      <link>https://blog.mishraji.org/posts/cloudflare-ztna-part-2/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mishraji.org/posts/cloudflare-ztna-part-2/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://blog.mishraji.org/posts/cloudflare-ztna-part-1/&#34;&gt;Part 1&lt;/a&gt;, we enabled TLS inspection to get HTTP policies working against HTTPS traffic — that&amp;rsquo;s how we blocked social media sites on port 443. We got it working, but I didn&amp;rsquo;t really explain &lt;em&gt;what&lt;/em&gt; TLS inspection is actually doing under the hood. Let&amp;rsquo;s fix that.&lt;/p&gt;&#xA;&lt;p&gt;TLS inspection is essentially a sanctioned man-in-the-middle. When your device initiates an HTTPS connection, Cloudflare Gateway intercepts it, terminates the TLS session, decrypts the traffic, inspects it, and re-encrypts before forwarding to the destination. Same thing in reverse on the way back. The Cloudflare root CA certificate we installed on the client device is what makes this work without your browser throwing certificate errors on every page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Part 1: Cloudflare Zero Trust — Web Filtering</title>
      <link>https://blog.mishraji.org/posts/cloudflare-ztna-part-1/</link>
      <pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mishraji.org/posts/cloudflare-ztna-part-1/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;This is Part 1 of the 4-part Cloudflare Zero Trust series. In Part 0 we set up the Cloudflare One Client and tested a successful ZTNA connectivity. If you have not read that yet, I would recommend starting there before following along here.&lt;/p&gt;&#xA;&lt;p&gt;In this post we are looking at &lt;strong&gt;web filtering&lt;/strong&gt; — what it is and how to configure it using Cloudflare Zero Trust.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;what-is-web-filtering-and-why-is-it-required&#34;&gt;What is Web Filtering and Why is it Required?&lt;/h3&gt;&#xA;&lt;p&gt;Web filtering controls what a user can or cannot access on the internet. The reasons for doing it depend on who you are.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Part 0: Cloudflare One Client (Warp Client) Initial Setup </title>
      <link>https://blog.mishraji.org/posts/cloudflare-ztna-part-0/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mishraji.org/posts/cloudflare-ztna-part-0/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;If you have been working in IT or security for a while, you have probably heard the term &lt;strong&gt;Zero Trust&lt;/strong&gt; thrown around a lot. But what does it actually mean in practice?&lt;/p&gt;&#xA;&lt;p&gt;Traditional network security worked on a simple assumption — if you are inside the network, you are trusted. VPNs were the go-to solution. You connect to the VPN, and suddenly you are &lt;em&gt;&amp;ldquo;on the network&amp;rdquo;&lt;/em&gt; with access to everything. The problem? Once an attacker gets in — through a compromised credential, a phishing attack, or a misconfigured endpoint — they can move laterally across the entire network with very little resistance. Trust was implicit, and that was the fundamental flaw.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
