Securing Networks ยท 3.3

๐Ÿ”€ Network Segmentation

Dividing a network so one breach doesn't compromise everythingโฑ ~2 min

๐ŸšขWatertight compartments stop one leak from sinking the whole ship

The Titanic had watertight compartments designed to contain flooding. When multiple compartments flooded simultaneously, the ship sank โ€” the design failed because the compartments weren't truly isolated. Network segmentation works the same way: divide the network so that a breach in one segment (say, the guest WiFi) cannot spread to critical systems (the payment servers or hospital records). When segmentation is done right, lateral movement is stopped.

The Broadcast Domain Problem

In a flat network (everything on one subnet), every device can communicate with every other device. This creates two problems: (1) performance โ€” broadcast traffic from one device goes to every device; (2) security โ€” malware or an attacker on one device has direct access to every other device with no barriers. Segmentation solves both.

Segmentation Techniques

TechniqueHow It WorksUse Case
VLANs (Virtual LANs)Logically divide a single physical network into isolated segments at Layer 2; traffic between VLANs must go through a router/firewallSeparate Finance, HR, Guest, IoT, and Security cameras onto different VLANs on the same physical switches
SubnettingDivide IP address space into smaller networks; routers control inter-subnet communicationGive each department its own subnet (192.168.1.0/24 for Finance, 192.168.2.0/24 for Marketing)
DMZ (Demilitarized Zone)Network segment between the internet and internal network for public-facing serversWeb servers, email servers, public APIs โ€” accessible from internet but isolated from internal network
Air GapComplete physical separation โ€” no network connection between segments at allCritical infrastructure (power grid controls), classified government networks, nuclear facility controls
Micro-segmentationSoftware-defined networking creates very fine-grained policies between individual workloadsCloud environments; zero-trust architectures where even internal east-west traffic is controlled

Why Segmentation is a Core Defense-in-Depth Control

  • โ€ขLimits lateral movement โ€” after breaching one device, an attacker cannot freely reach other segments
  • โ€ขContains malware โ€” ransomware spreading via network shares is stopped at segment boundaries
  • โ€ขIsolates IoT/OT devices โ€” smart TVs, HVAC systems, printers are notoriously insecure; segment them from critical systems
  • โ€ขRegulatory compliance โ€” PCI-DSS requires card processing systems to be isolated from other networks
  • โ€ขReduces attack surface โ€” a compromised guest WiFi device cannot scan or reach internal servers
  • โ€ขEnables zero-trust โ€” segmentation is the physical/logical enforcement mechanism for 'never trust, always verify'
โ˜… FactThe 2013 Target breach exploited a lack of network segmentation. Attackers entered through the HVAC vendor network and pivoted directly to the point-of-sale network โ€” two networks that had no business reason to communicate. PCI-DSS compliance requires that payment card systems be isolated. Target was PCI-compliant on paper but had network connections that violated the spirit of the standard. Proper segmentation would have contained the breach to the HVAC network.
๐Ÿ”’ SecurityA properly segmented network for a school might have: VLAN 10 (Staff), VLAN 20 (Student), VLAN 30 (Guest/BYOD), VLAN 40 (Administration/Finance), VLAN 50 (Servers), VLAN 60 (Security cameras), VLAN 70 (IoT/HVAC). A student on VLAN 20 trying to reach the administration server on VLAN 40 would be blocked by the inter-VLAN firewall policy. A compromised camera on VLAN 60 has no path to the grade database on VLAN 50.
๐Ÿง Quick Checkfirst try = +5 XP

A hospital has one flat network. A ransomware infection starts on a nurse's workstation after she opens a phishing attachment. Within 4 hours, the ransomware has spread to billing computers, the patient records database, and medical device controllers. If the hospital had implemented proper network segmentation, what would most likely have happened differently?

โญ 0 XP๐Ÿ”ฅ 0 days