Skip to main content
MyITCyberBack to home
← Insights·Infrastructure Security

Network Segmentation: Do Not Put Everything on the Same VLAN

·2 min read
Side-by-side comparison of a flat network and a segmented network. On the left, a single rectangle places users, servers, printers, cameras, Wi-Fi, and backup on the same plane with an amber mesh connecting every node to every other node, labeled 'risk: lateral movement'. On the right, a segmented design organizes the same resources into clearly bordered VLANs on-prem (users, servers, IoT / printers, management, backup) and clearly bordered cloud subnets inside a VPC / VNet (public, app, db, management / backup), with only specific ALLOW lines drawn between the paths that real workflows need, and a footer strip listing route tables, security groups, NSG, firewall rules, and private endpoints, labeled 'reduced blast radius'.

Network segmentation is one of the most basic security principles, and one of the most ignored. Flat networks are easy to build but easy to abuse, one compromised endpoint can reach far too much. Whether it is VLANs on-prem or subnets, security groups, and private endpoints in the cloud, every system should only talk to what it really needs.

Network segmentation is one of the most basic security principles, but many environments still ignore it.

In on-prem environments, this usually means everything sits too close together. Users, servers, printers, cameras, Wi-Fi, management interfaces, and backup systems may all have too much access to each other.

It works until something goes wrong.

If one endpoint is infected or one user account is compromised, a flat network makes it much easier for an attacker to move laterally across the organization.

Segmentation reduces that risk.

  • Users should not have direct access to every server.
  • Printers and cameras should not talk freely to business systems.
  • Management networks should be isolated.
  • Backup infrastructure should be protected.
  • Critical servers should be separated from regular user traffic.

The same idea applies in the cloud.

Instead of putting everything in one large VPC, VNet, subnet, or security group, cloud networks should be designed with clear separation. Public services, private applications, databases, management access, and backup systems should not all live in the same open network.

In the cloud, segmentation is built with subnets, route tables, security groups, network security groups, firewall rules, private endpoints, and identity-based access.

Good segmentation does not only improve security. It also makes troubleshooting easier, reduces noise, limits the impact of mistakes, and gives IT teams better control.

A flat network is easy to build, but hard to protect.

A segmented network takes more planning, but it helps keep the business safer when something goes wrong.

// related reading