A security framework that requires strict identity verification for every person and device attempting to access resources on a network, regardless of whether they are inside or outside the network perimeter. ZTNA operates on the principle of "never trust, always verify" and provides granular access control based on user identity, device posture, and context.
Zero Trust Network Access
Zero Trust Network Access (ZTNA) is the access-control approach that grew out of the broader Zero Trust model. Instead of dropping a user or device onto a trusted network the way a VPN does, ZTNA brokers access to individual applications and resources one request at a time, after verifying identity, device posture, and context. Nothing is trusted because of where it sits on the network — every connection has to earn its access.
- Never trust, always verify - No implicit trust is granted based on network location; inside and outside the perimeter are treated the same.
- Per-resource, least-privilege access - Users reach only the specific applications they are authorized for, not the whole network segment behind a tunnel.
- Continuous context evaluation - Identity, device health, location, and other signals are checked on an ongoing basis, not just at initial login.
- A policy broker in the path - A control point sits between the requester and the resource, brokering and enforcing access decisions in real time.
In API operations, ZTNA is how the “never trust the network” idea gets enforced at the connection layer, and it pairs naturally with per-request OAuth 2.0 authorization at the API layer. As more of an organization’s real usage moves to internal and partner APIs, the old assumption that the private network is a safe zone stops holding, and ZTNA gives teams a way to gate access to those services by identity and posture rather than IP address. For the agentic turn, where automated clients and services call APIs continuously, this per-request, identity-anchored model is far more defensible than a flat trusted network.
Referenced on the API Evangelist blog
Where this standard shows up across sixteen years of my writing at apievangelist.com — how it fits into API design, governance, and the agentic turn.