Glossary / Network Segmentation

Network Segmentation

Dividing a network into smaller, isolated zones so that a compromise in one segment can't automatically reach every other system on the network.

Segmentation is implemented through VLANs, firewall rules between zones, or microsegmentation (isolation enforced per workload rather than per subnet), and its purpose is limiting lateral movement specifically — not just organizing traffic for performance or convenience.

A common, concrete example: guest Wi-Fi kept off the internal network, or a point-of-sale network segmented from general office traffic — the latter being a specific expectation under PCI-DSS. The segment boundary is what turns "one compromised laptop" into a contained incident instead of a path to the rest of the network.

Segmentation is cheap to design correctly during initial network setup and expensive to retrofit later onto a live, business-critical network — which is a large part of why it shows up disproportionately often in post-incident "what would have contained this" reviews, as the control that existed on paper but wasn't actually enforced.

How Nexus handles this

Nexus applies the same segmentation logic to its own architecture — tenant isolation enforced at both the application layer and PostgreSQL row-level security means one tenant's data is walled off from every other, the multi-tenant SaaS equivalent of segmenting a network so a breach in one zone doesn't reach the rest.

Ready to see it in the platform?

Join the design-partner cohort and we'll show you exactly where this lives.