When zero trust focuses only on north-south access, the internal environment remains permissive enough for lateral movement after the first foothold. That leaves attackers free to move from one compromised asset to the next. Microsegmentation closes that gap by applying explicit policy to east-west communication inside the network.
Where zero trust fails when east-west traffic stays open
When zero trust is reduced to perimeter and user-entry controls, it leaves a large trust zone inside the environment. Once an attacker gets a foothold, that trust lets them pivot between systems, discover reachable services, and turn one compromised asset into many. The core failure is not authentication at the edge, but the absence of enforcement between internal peers.
North-south controls can still block some initial access, but they do little to contain post-compromise movement if internal flows remain broadly permitted. That is why zero trust needs to cover internal communication paths as well as entry points, with explicit policy for every relevant connection.
East-west traffic matters because internal trust assumptions are exactly what lateral movement exploits. A single compromised host, workload, or service can often reach far more than the business intended when network policy is coarse or inherited from flat segmentation.
Why microsegmentation changes the containment model
Microsegmentation limits the blast radius by treating internal communications as policy decisions rather than default trust. Instead of assuming that anything inside the network can talk freely, it allows only the specific paths needed for an application, service, or workflow. That changes the attacker’s next step from easy traversal to repeated policy violations.
The practical value is containment. If a database, application tier, or management endpoint is separated by explicit rules, compromise of one segment does not automatically expose its neighbors. In mature environments, microsegmentation also forces better visibility into application dependencies, because teams must know what truly needs to talk to what.
This is why microsegmentation is often the missing control when organisations say they “have zero trust” but still behave like a flat network internally. The network may be authenticated at the edge, yet permissive inside. That mismatch creates a security design gap that attackers routinely exploit after initial access.
What practitioners should look for in a real zero trust design
Zero trust is not complete until the policy model follows the traffic pattern. If the design only protects remote login, VPN entry, or SaaS access, it does not meaningfully address lateral movement inside servers, clusters, or hybrid networks. Internal segmentation, workload-aware policy, and monitored allowlists are what turn the idea into containment.
In practice, the hardest part is usually not the enforcement technology, but the dependency mapping. Teams often overestimate how much east-west access their systems genuinely need, then keep exceptions alive because no one wants to break legacy integrations. That is where scoped rollout matters: start with high-value segments, prove the dependency map, then tighten the policy boundary as confidence grows.
The best signal that the design is working is not that traffic is silent, but that permitted internal paths are intentional, reviewable, and minimal. If the environment still depends on broad subnets, shared trust zones, or “temporary” exceptions that never expire, the zero trust model is only partial.
Risk and Threat Considerations
When east-west traffic is left permissive, the main risk is that one compromised identity, host, or workload becomes a bridge to the rest of the environment. Attackers do not need to defeat every control at once if internal connectivity lets them enumerate, move, and stage follow-on compromise after the first foothold.
Failure mechanism: Broad internal trust and flat segmentation let a successful compromise turn into lateral movement, privilege discovery, and multi-system exposure without repeated authentication or policy checks.
Impact: The attacker’s blast radius expands, containment gets harder, and recovery often becomes slower and more disruptive because multiple internal systems may need to be treated as exposed.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack surface, NIST Zero Trust (SP 800-207), CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST Zero Trust (SP 800-207) | PR.AA-05 — Network segmentation and access enforcement | Zero trust depends on policy enforcement for internal traffic, not only user entry. |
| Recommendation — Enforce policy at internal boundaries to limit east-west movement after initial access. | ||
| CIS Controls v8 | CIS-12 — Network Infrastructure Management | Microsegmentation and internal traffic control are core network hardening practices. |
| Recommendation — Segment internal networks to reduce lateral movement and contain compromise. | ||
| NIST SP 800-53 Rev 5 | SC-7 — Boundary Protection | Internal segmentation and controlled flow paths are boundary protection concerns. |
| Recommendation — Implement controlled internal boundaries to restrict unauthorized east-west communication. | ||
| ISO/IEC 27001:2022 | A.8.22 — Segregation of networks | The question is about separating internal traffic paths to contain compromise. |
| Recommendation — Separate network zones so only necessary internal communications are permitted. | ||
| MITRE ATT&CK | T1021 — Remote Services | Lateral movement commonly uses internal services once a foothold exists. |
| Recommendation — Hunt for internal service abuse and constrain pathways used for lateral movement. | ||
Practitioner Guidance
What to prioritise: Treat east-west policy as the containment layer, not an optimisation. The first question should be which internal paths are truly required for each application or workload, not which ones are easiest to keep open.
What to verify: Validate that every segmentation rule maps to a documented business or technical dependency, and that exceptions have owners and review dates. If you cannot explain why a service can reach another service, you probably cannot defend that path either.
What good looks like: A compromised segment can no longer reach adjacent systems by default, and internal communication is narrow enough that violations are visible instead of blending into normal traffic.
Practitioner takeaway: Zero trust only reduces lateral movement when internal trust is also removed, because containment depends on enforced boundaries between systems, not just stronger entry controls.
Related resources from NHI Mgmt Group
- How should security teams build a zero trust architecture that covers both internal traffic and user access from outside the network?
- What breaks when AI agents need access to internal enterprise tools but no zero trust tunnel exists?
- How do teams know if their internal access model is actually zero trust?
- What breaks when Zero Trust stops at authentication?