https://rochanewton.github.io/tags/dmz/Recent content in Dmz on Newton RochaHugo -- gohugo.ioen© 2026 Newton RochaTue, 08 Sep 2026 00:00:00 +0000https://rochanewton.github.io/posts/sterling-b2bi-06-perimeter-servers/Tue, 08 Sep 2026 00:00:00 +0000https://rochanewton.github.io/posts/sterling-b2bi-06-perimeter-servers/<h2 class="relative group">The connection runs backward from what you&rsquo;d guess <div id="the-connection-runs-backward-from-what-youd-guess" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-connection-runs-backward-from-what-youd-guess" aria-label="Anchor">#</a> </span> </h2> <p>Most people&rsquo;s first assumption about a box sitting in the DMZ is that your trusted, internal network reaches out to it — the secure side initiates, the exposed side listens. A Perimeter Server does the opposite. The core B2Bi engine sitting safely inside your network never opens a connection out into the DMZ at all. Instead, the Perimeter Server — the box actually facing partners and the internet — dials <em>back in</em> to the core engine and holds that connection open. Partner traffic lands on the DMZ box first, and only then gets forwarded inward over a channel the DMZ side itself established.</p>