Zero trust treats least privilege as a per-request decision, not a one-time grant
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
NIST SP 800-207 puts least privilege inside zero trust: its definition calls for accurate, least privilege per-request access decisions, and its third tenet grants access with the least privileges needed to complete the task. Least privilege is the access rule, and zero trust is the architecture that enforces it on each request. Read 16 Nov 2026.
Open the calculator ยท The field guide
NIST defines zero trust in terms of least privilege
NIST SP 800-207, Zero Trust Architecture, was published in August 2020. Its operative definition reads, verbatim: "Zero trust (ZT) provides a collection of concepts and ideas designed to minimize uncertainty in enforcing accurate, least privilege per-request access decisions in information systems and services in the face of a network viewed as compromised." The text is on the NIST publication page and in the full PDF, both read on 16 Nov 2026.
The same section says the initial focus should be on restricting resources to those with a need to access and granting only the minimum privileges, with the examples read, write and delete, needed to perform the mission. It adds that access rules are made as granular as possible to enforce least privileges needed to perform the action in the request.
Three of the seven tenets carry the rule
Tenet 3 reads: "Access to individual enterprise resources is granted on a per-session basis." It continues that access should also be granted with the least privileges needed to complete the task, and that authentication and authorization to one resource will not automatically grant access to a different resource.
Tenet 4 says access to resources is determined by dynamic policy, and states: "Least privilege principles are applied to restrict both visibility and accessibility." Tenet 6 says all resource authentication and authorization are dynamic and strictly enforced before access is allowed. Together they turn least privilege from a state of the account into a decision made at each request.
The two ideas are related and not the same
Least privilege is a rule about how much access a subject holds. Zero trust is an architecture that decides, for each request, whether the subject holds the access, using the subject's identity, the asset's state and other attributes. A zero trust deployment with wide grants still makes wide decisions, and a narrow grant behind a flat network is still exposed to the network.
SP 800-207 also says that a collection of privileges given to multiple subjects could be thought of as a role, but that privileges should be assigned to a subject on an individual basis and not simply because they may fit into a particular role in the organization. That is stricter than most cloud role design, and it explains why the document keeps pushing toward attributes and conditions, covered on least privilege access control.
The migration advice applies to cloud access clean-up
SP 800-207 notes that users with special privileges, such as developers or system administrators, require additional scrutiny when being assigned attributes or roles, and that in many legacy architectures such accounts hold broad permissions. It also says a new zero trust workflow could be operated in "reporting-only mode" for some time to make sure the policies are effective and workable.
Reporting-only mode is the audit mode that cloud boundaries offer, and the scrutiny of administrator accounts is the first step in the first 90 days. The NIST AC-6 requirement behind both is on the principle of least privilege.
A practical reading for a cloud team: write the least privilege rule once, as policy and boundaries, and let the platform evaluate it on every request instead of relying on a review that runs quarterly. The review stays, since AC-6(7) asks for it, but it checks the rules rather than approving each call. That division of work is why the zero trust documents and the cloud IAM documents describe the same controls from two directions.
Cloud providers give you the enforcement points
The cloud mechanisms in the table are where the per-request decision is made. This site does not review zero trust products. It covers the access rules the clouds enforce.
| Zero trust element in SP 800-207 | Cloud mechanism that enforces it |
|---|---|
| Least privileges for the task | Narrow roles and scoped policies |
| Dynamic policy using attributes | ABAC tags, IAM Conditions, role assignment conditions |
| Per-session access | Temporary credentials, time-bound assignments |
| Reporting-only mode | Audit or dry-run modes for boundaries and simulators |
Related pages
Sources
- NIST SP 800-207, Zero Trust Architecture (PDF), read 16 Nov 2026
- NIST CSRC, SP 800-207 publication page, read 16 Nov 2026
- AWS, security best practices in IAM, read 16 Nov 2026
- Google Cloud, overview of IAM Conditions, read 16 Nov 2026
- Microsoft, what is Privileged Identity Management, read 16 Nov 2026
Last reviewed 16 Nov 2026.