4 min read

What Is NIST SP 800-207, and What Are the Seven Tenets of Zero Trust Architecture?

“Adopt Zero Trust” is easy to say, but NIST SP 800-207 turns that mandate into seven concrete principles for building systems that never assume trust.

What Is NIST SP 800-207, and What Are the Seven Tenets of Zero Trust Architecture?

Agencies across government have been told to “adopt Zero Trust.” The Office of Management and Budget’s memo M-22-09 directed federal agencies toward specific Zero Trust goals, and the phrase now appears in strategies, procurements, and audit findings. But “adopt Zero Trust” is a mandate, not a design. It becomes actionable when grounded in the standard that defines it.

That standard is NIST Special Publication 800-207, Zero Trust Architecture, published in August 2020. This explainer walks through its seven tenets and shows what each one means for identity, data, and access decisions in government systems.

What is NIST SP 800-207?

NIST SP 800-207 is the National Institute of Standards and Technology’s foundational publication defining Zero Trust Architecture for the United States. It is the reference that later federal guidance builds upon, including CISA’s Zero Trust Maturity Model and agency implementation plans.

The core idea is a shift in where security lives. Traditional models put defenses at the network perimeter: once you were inside, through a VPN or an office port, you were largely trusted. NIST 800-207 rejects that. As the standard puts it, “no implicit trust” is granted to accounts or assets based on their physical or network location. Instead, defenses move to users, assets, and resources, and every access request is evaluated on its own merits.

This is often described as an “assume breach” posture: Zero Trust treats the possibility that an attacker is already present in the environment as a working assumption, and treats an enterprise-owned network as no safer by default than the open internet. A request from the agency receives the same scrutiny as one from a coffee shop connection. If you want the ground-level version of this idea, see What Is Zero Trust? The Basics Explained.

The seven tenets of Zero Trust

NIST 800-207 lists seven tenets that describe an ideal Zero Trust deployment. Below is each tenet in the standard’s own words, followed by what it means for a government system.

1. “All data sources and computing services are considered resources.” A benefits database, an internal API, a caseworker’s laptop, and a document-intake service are all resources to be protected, not just servers behind a firewall. Nothing is trusted simply because it sits inside the agency network.

2. “All communication is secured regardless of network location.” Traffic between a resident’s phone and an eligibility system must be encrypted and authenticated, whether it crosses the public internet or an internal segment. Location confers no safety.

3. “Access to individual enterprise resources is granted on a per-session basis.” Signing in once does not grant standing access to everything. A caseworker who authenticates to view a case file gets access to that resource, for that session, not a blanket pass to every system the agency runs.

4. “Access to resources is determined by dynamic policy - including the observable state of client identity, application/service, and the requesting asset - and may include other behavioral and environmental attributes.” The decision to grant access weighs who is asking, what they are trying to reach, and the state of their device. A login from an unmanaged device, or an unusual request pattern, can change the outcome in real time.

5. “The enterprise monitors and measures the integrity and security posture of all owned and associated assets.” Agencies continuously check the health of devices and services (patch level, configuration, known compromise) rather than assuming a device stays trustworthy after it first connects.

6. “All resource authentication and authorization are dynamic and strictly enforced before access is allowed.” Verification is not a one-time gate at the front door. It is a continuous cycle of authenticating identity and authorizing the specific action, re-evaluated as sessions and risk change.

7. “The enterprise collects as much information as possible about the current state of assets, network infrastructure and communications and uses it to improve its security posture.” Telemetry feeds policy. What the system learns about access patterns and asset health continuously sharpens the rules that govern future decisions.

Read together, the tenets translate the “assume breach” mindset into concrete design rules: treat everything as a resource, secure every connection, and decide access request by request using live signals about identity and device.

The logical components behind the tenets

NIST 800-207 also describes the machinery that carries out these decisions. A Policy Engine (PE) makes the grant-or-deny decision. A Policy Administrator (PA) executes it, establishing or shutting down the connection. And a Policy Enforcement Point (PEP) sits in the path of the request, enabling and monitoring the session. Together, they form the policy decision and enforcement layer that every access request passes through.

We cover how these components interact and how data actually moves through them in a public-sector context in Applying Zero Trust to Government Data Flows. The point to hold onto here is simple: those components are only as good as the identity signal they receive.

Identity is the connective tissue

Every tenet in NIST 800-207 assumes one thing: that the system can answer “who or what is making this request?” with confidence. Per-session access, dynamic policy, and strict authorization all depend on identity that is not weak, shared, or unverifiable. Deciding on access requests by request requires a trustworthy answer about who is asking.

This is why strong, verifiable identity is a precondition for Zero Trust rather than an add-on. Phishing-resistant authentication, cryptographically bound credentials, and verifiable attributes give the Policy Engine something concrete to reason about. When identity is verifiable and privacy-preserving, agencies can enforce least privilege without turning every login into an interrogation, and without collecting more personal data than a decision requires.

That is also what “assume breach” calls for in practice. If you design as though attackers may already be inside, you rely less on network position and more on proof. For a deeper look at building systems around that assumption, see Secure by Design: Building Systems That Assume Breach.

NIST SP 800-207 gives the government a shared vocabulary for Zero Trust. Its seven tenets turn a mandate into architecture, and identity is the layer that makes that architecture implementable.

Working with SpruceID

SpruceID builds the verifiable digital credential and infrastructure that supplies the strong identity signals a Zero Trust architecture depends on. If your agency is translating a Zero Trust mandate into an architecture that needs verifiable, privacy-preserving identity at its core, get in touch with our team.

Building digital services that scale take the right foundation.
Talk to our team

About SpruceID: SpruceID builds digital trust infrastructure for government. We help states and cities modernize identity, security, and service delivery — from digital wallets and SSO to fraud prevention and workflow optimization. Our standards-based technology and public-sector expertise ensure every project advances a more secure, interoperable, and citizen-centric digital future.