Network Segmentation Analysis
What you'll learn: How to assess how a network is divided into zones, identify trust boundaries, and understand the architecture of security perimeters like DMZs.
What Is Network Segmentation Analysis?
After you've discovered gateways and routers (from previous reconnaissance), the next step is understanding how the network is divided. Network segmentation analysis means examining how an organization isolates different parts of their network to limit damage if one area is compromised.
Think of it like a submarine with watertight compartments—if one section floods, sealed doors prevent the entire vessel from sinking.
Core Concepts
Network Isolation
You assess whether critical systems (like databases or payment processors) are separated from general-purpose networks (like guest WiFi or employee workstations). Poor isolation means an attacker who compromises one laptop might directly access sensitive servers.
Trust Boundaries
These are the invisible lines where security policies change. Crossing from the "untrusted Internet" into the "internal network" is one boundary. Moving from "employee network" to "finance department servers" is another. Each boundary should have controls (firewalls, access lists) enforcing who and what can cross.
Security Zones and DMZ
A DMZ (Demilitarized Zone) sits between the Internet and internal network—public-facing web servers live here. If attackers breach the DMZ, they still face another firewall before reaching internal resources. Security zones are labeled areas: Public, DMZ, Internal, Management, etc., each with different trust levels and access rules.
During analysis, you map which systems belong to which zones based on routing paths, firewall rules visible from scans, and access patterns discovered through reconnaissance.
Key Takeaway:
Network segmentation analysis reveals how a network is divided into security zones and trust boundaries—critical for understanding attack paths and defensive architecture.