<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Private Resource Access on mishraJi</title>
    <link>https://blog.mishraji.org/tags/private-resource-access/</link>
    <description>Recent content in Private Resource Access on mishraJi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.mishraji.org/tags/private-resource-access/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Part 3: Cloudflare Zero Trust - Private Resource Access</title>
      <link>https://blog.mishraji.org/posts/cloudflare-ztna-part-3/</link>
      <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mishraji.org/posts/cloudflare-ztna-part-3/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;Private resources don&amp;rsquo;t have public IPs, which means they&amp;rsquo;re not directly reachable from the internet. That&amp;rsquo;s intentional — and usually a good call.&lt;/p&gt;&#xA;&lt;p&gt;Take an internal file-share server. If it&amp;rsquo;s exposed to the internet without authentication, you&amp;rsquo;ve got a problem. Same with a self-hosted GitLab instance for your dev team, or an SSH endpoint for managing infrastructure. These aren&amp;rsquo;t meant for the public internet.&lt;/p&gt;&#xA;&lt;p&gt;But here&amp;rsquo;s the catch: keeping something private often means setting up a VPN, which adds complexity. You need to manage certificates, client software, authentication layers — it all adds friction, especially if you just want something quick and temporary.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
