<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Segmentation on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/segmentation/</link><description>Recent content in Segmentation on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 30 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/segmentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Network Segmentation Pitch: From VLANs to Microsegmentation to TrustSec</title><link>https://blog.it-learn.io/posts/2026-04-30-network-segmentation-vlans-microsegmentation-trustsec/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-04-30-network-segmentation-vlans-microsegmentation-trustsec/</guid><description>&lt;p&gt;Every SE has heard this objection at least once: &amp;ldquo;We already have VLANs. Our network is segmented.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The customer is not wrong. VLANs exist. Ports are assigned. There may even be a spreadsheet somewhere that maps VLANs to building floors. But when you ask whether a compromised workstation on VLAN 10 can reach the database servers on VLAN 50, the room goes quiet. Nobody has tested it. Nobody has looked at the inter-VLAN ACLs — if there are any — in months. The VLAN spreadsheet has not been updated since the last network refresh.&lt;/p&gt;</description></item></channel></rss>