Network Segmentation
Internet → public layer → application network → database network → management network: crossings are explicit and narrow.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
Routes and rules permit broad lateral movement or bypass the inspected service path.
The important question is not “what is Network Segmentation?” but “which assumption let untrusted data or an over-scoped identity cross one network zone → a more privileged zone?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Default-deny between zones Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Default-deny between zones · Permit exact service-to-service flows · Separate management access and identities | Unexpected cross-zone flows and denied connection attempts | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: High-value services that should not share one failure domain.
- Boundary: One network zone → a more privileged zone
- Primary control: Default-deny between zones
- Detection signal: Unexpected cross-zone flows and denied connection attempts
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: A compromised component in a less-trusted network segment.
- 2Routes and rules permit broad lateral movement or bypass the inspected service path.
- 3The weak or missing boundary control is crossed: One network zone → a more privileged zone
- 4Impact: A public-service compromise reaches databases or management interfaces.
- A public-service compromise reaches databases or management interfaces.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Default-deny between zones
- • Permit exact service-to-service flows
- • Separate management access and identities
- • Unexpected cross-zone flows and denied connection attempts
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.