East west traffic is service to service communication inside the environment, while north south traffic is traffic entering from or leaving toward users and external systems. Zero trust must handle both. East west controls limit lateral movement between workloads, and north south controls govern who can reach protected resources from outside the service boundary.
How East West and North South Traffic Differ in Zero Trust
Zero trust treats traffic direction as a trust boundary problem, not just a networking label. East west traffic is usually internal service-to-service movement, so the control objective is to narrow blast radius and prevent lateral movement. North south traffic crosses the environment edge, so the objective is stronger ingress and egress control, user verification, and policy enforcement before anything reaches protected assets.
The practical difference matters because each path fails in a different way. Internal traffic often looks legitimate once an attacker gets a foothold, while external traffic is where authentication, device posture, and admission decisions are most visible. In a zero trust design, both must be continuously evaluated rather than assumed safe because they are “inside” or “outside.”
That is why NIST describes zero trust as Zero Trust Architecture built around verified access decisions and least privilege, not perimeter trust. For service-to-service design, SPIFFE-style workload identity and mTLS are often used to make east west trust explicit, while north south traffic is usually governed by access policy, gateway controls, and step-up checks.
What East West Controls Protect Inside the Environment
East west traffic is the traffic most likely to be abused after initial compromise because it lets an attacker move from one workload, segment, or service to another. That makes microsegmentation, service identity, and per-connection authorization central to the design. The goal is not to block every internal request, but to ensure one compromised component cannot freely reach the rest of the environment.
In a well-designed zero trust model, east west control is more than subnet separation. It should align with application dependencies so only the specific services that need to talk can do so, and only with the minimum privileges required. This is where workload identity becomes especially important: the policy should follow the calling workload, not just the network location.
When you need a deeper reference point for workload identity and trust bundles, the Guide to SPIFFE and SPIRE is directly relevant. For a broader architecture view, the Network Segmentation Guide explains how segmentation limits lateral movement and reduces blast radius.
What North South Controls Protect at the Boundary
North south traffic is the path between the protected environment and users, partners, or external systems. It is the point where zero trust usually places the strongest admission controls because this traffic arrives from a less trusted context. Authentication, authorization, and request-level policy are most obvious here, but the control objective also includes safe egress, because outbound traffic can be used for data exfiltration or command-and-control.
Practically, north south controls tend to concentrate at gateways, proxies, identity-aware access layers, and policy enforcement points. They are used to decide who or what may enter, what resource they may reach, and whether the request meets contextual requirements such as device trust, session validity, or risk signals. In other words, north south controls are about controlled entry and controlled exit, not just simple firewalling.
The NIST SP 800-207 Zero Trust Architecture Guide is useful when you want the architectural pattern behind those decisions, while the Network Security Guide helps place north south traffic in the wider perimeter and monitoring context.
Risk and Threat Considerations
East west and north south traffic fail differently, which is why zero trust needs both. If east west controls are weak, an attacker who gains one foothold can pivot internally with less resistance, especially in flat networks or loosely governed service meshes. If north south controls are weak, unauthorised entry, unsafe API exposure, and exfiltration become easier because the environment lacks a strong admission boundary.
Failure mechanism: Internal trust assumptions allow one compromised workload or session to reach additional services without sufficient re-verification, while weak boundary policy lets untrusted external traffic reach sensitive resources or move data out.
Impact: The result is larger blast radius, faster lateral movement, weaker containment, and a higher chance that initial access turns into a broader compromise or data exposure.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5, NIST Zero Trust (SP 800-207) and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-9 — Identification and Authentication (Non-Organizational Users) | Covers identity-bound access for service-to-service and external access paths in zero trust. |
| Recommendation — Enforce strong authentication for service and external identities before granting access. | ||
| NIST Zero Trust (SP 800-207) | Zero Trust Architecture | Directly addresses east west and north south policy decisions in zero trust networks. |
| Recommendation — Apply explicit policy enforcement to both internal and boundary traffic flows. | ||
| CIS Controls v8 | CIS-12 — Network Infrastructure Management | Supports segmentation and controlled traffic flows that reduce lateral movement and exposure. |
| Recommendation — Segment networks and tightly manage boundary controls to limit movement and exposure. | ||
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | Workload identities behind east west traffic can become overprivileged and widen blast radius. |
| Recommendation — Reduce workload privileges so internal service access is narrowly scoped. | ||
Practitioner Guidance
What to prioritise: Separate the policy questions. For east west traffic, ask whether each service relationship is explicitly allowed and attributable to a workload identity. For north south traffic, ask whether every entry point enforces authentication, context, and least privilege before the request touches the workload.
What to verify: Confirm that internal traffic is not being allowed simply because it originates from an “approved” subnet or cluster, and confirm that external traffic is not bypassing policy through shared gateways, legacy exceptions, or overly broad egress paths.
Practitioner takeaway: Zero trust is strongest when east west and north south are governed as different trust problems with different controls, but the same principle: no path should be trusted just because it is internal or expected.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org