<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microsegmentation on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/microsegmentation/</link>
    <description>Recent content in Microsegmentation on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/microsegmentation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Microsegmentation: Container Network Security Platforms in 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-27-self-hosted-microsegmentation-container-network-security-platforms/</link>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-27-self-hosted-microsegmentation-container-network-security-platforms/</guid>
      <description>&lt;p&gt;Traditional perimeter firewalls are insufficient for modern containerized workloads. Once traffic passes the network boundary, lateral movement between services is unrestricted. &lt;strong&gt;Network microsegmentation&lt;/strong&gt; solves this by enforcing security policies at the individual workload level — controlling which pods, containers, or VMs can communicate with each other.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
