Put NIST 800-207 zero trust principles into practice
NIST SP 800-207 is a NIST Special Publication, published in August 2020, that defines zero trust and zero trust architecture (ZTA). It sets out seven tenets, such as securing all communication regardless of network location and granting access per session based on dynamic policy. It is guidance, not a certifiable standard, and describes logical components, deployment models and migration steps rather than a control checklist.
Is NIST 800-207 right for your organisation?
US federal agencies use NIST SP 800-207 as the reference definition of zero trust when planning their architectures. Private organisations, including UK and international companies, adopt it voluntarily as a vendor-neutral model when moving away from perimeter-based security, supporting remote work, cloud services and personal devices, or answering customer questions about zero trust.
Adopting it is voluntary, though customers and auditors often expect it.
- Issued by
- National Institute of Standards and Technology (NIST)
- Published
- August 2020
- Latest version
- SP 800-207 (final, no revision)
- Type
- Voluntary guidance, not a certifiable standard
- Core content
- Seven tenets of zero trust, logical components, deployment models and migration steps
- Assessment route
- No certification; organisations self-assess or use independent assessors against its tenets
- Availability in OneClickComply
- Mapped in the control library, available on request
- Region
- United States, US
OneClickComply makes it simple
NIST SP 800-207 is mapped in OneClickComply's control library and available on request. We link each zero trust tenet to practical controls such as access control, authentication, device posture and monitoring, then collect evidence from your identity, device and cloud tools so you can show how your environment reflects each tenet. Continuous monitoring alerts you when access or configuration controls drift.
Requirements covered
Seven sections and two appendices, with the seven zero trust tenets in Section 2.1, logical components in Section 3 and seven network requirements for supporting ZTA in Section 3.4.1.
Manual NIST 800-207 vs. OneClickComply
- Translating abstract zero trust tenets into concrete, checkable controls
- Gathering access, device and logging evidence from many separate consoles
- No clear way to show progress towards zero trust to customers or leadership
- Configuration and access drift goes unnoticed between reviews
- Duplicating zero trust work already done for ISO 27001 or SOC 2
- Each tenet linked to specific controls in one control library
- Evidence collected automatically from connected identity, device and cloud tools
- A clear, evidence-backed view of how your environment reflects each tenet
- Continuous monitoring flags drift as soon as it happens
- Controls mapped once, so evidence counts towards every relevant framework
Everything you need for NIST 800-207
Map each of the seven zero trust tenets to practical controls
Collect access and authentication evidence from identity providers automatically
Track device security posture with direct integrations and the Companion browser agent
Alert on control drift through continuous monitoring
Fix supported misconfigurations in one click with OneClickFix, logged as evidence
Reuse evidence across ISO 27001, SOC 2 and other mapped frameworks
Three steps to NIST 800-207 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against NIST 800-207 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates NIST 800-207-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
NIST SP 800-207 Zero Trust Architecture requirements
The seven zero trust tenets from Section 2.1 and the seven network requirements for supporting a zero trust architecture from Section 3.4.1.
| Reference | Requirement |
|---|---|
| Tenet 1 | All data sources and computing services are considered resources |
| Tenet 2 | All communication is secured regardless of network location |
| Tenet 3 | Access to individual enterprise resources is granted on a per-session basis |
| Tenet 4 | Access to resources is determined by dynamic policy |
| Tenet 5 | The enterprise monitors and measures the integrity and security posture of all owned and associated assets |
| Tenet 6 | All resource authentication and authorisation are dynamic and strictly enforced before access is allowed |
| Tenet 7 | The enterprise collects as much information as possible about assets, network and communications to improve its security posture |
| 3.4.1 (1) | Enterprise assets have basic network connectivity |
| 3.4.1 (2) | The enterprise can distinguish owned or managed assets and their current security posture |
| 3.4.1 (3) | The enterprise can observe all network traffic |
| 3.4.1 (4) | Enterprise resources are not reachable without accessing a policy enforcement point |
| 3.4.1 (5) | The data plane and control plane are logically separate |
| 3.4.1 (6) | Enterprise assets can reach the policy enforcement point |
| 3.4.1 (7) | The policy enforcement point is the only component that accesses the policy administrator in a business flow |
Always check the official NIST 800-207 text for the exact wording.
NIST 800-207 FAQs
What is NIST SP 800-207?
NIST SP 800-207 is the National Institute of Standards and Technology's Special Publication on zero trust architecture, published in August 2020. It defines zero trust as moving defences from static network perimeters to users, assets and resources, sets out seven tenets of zero trust, and describes the logical components, deployment models, threats and migration approaches for building a zero trust architecture.
What are the seven tenets of zero trust in NIST 800-207?
The seven tenets are: all data sources and computing services are resources; all communication is secured regardless of network location; access is granted per session; access is decided by dynamic policy; the enterprise monitors the integrity and security posture of all assets; authentication and authorisation are dynamic and strictly enforced before access; and the enterprise collects as much information as possible to improve its security posture.
Is NIST 800-207 mandatory?
No. NIST SP 800-207 is guidance, not a law or certifiable standard. US federal agencies use it as the reference definition of zero trust in their zero trust programmes, but there is no legal obligation for private organisations to follow it and no penalties attached to it. Most companies outside government adopt it voluntarily as a design blueprint.
Can you get certified against NIST 800-207?
No. There is no official certification for NIST SP 800-207. It describes principles and architecture patterns rather than auditable control requirements. Organisations typically self-assess their architecture against the seven tenets, sometimes with an independent assessor, and pair that with a certifiable framework such as ISO 27001 or a SOC 2 report to give customers formal assurance.
What are the main components of a zero trust architecture in NIST 800-207?
NIST SP 800-207 describes three core logical components. The policy engine decides whether to grant access to a resource, the policy administrator establishes or shuts down the communication path based on that decision, and the policy enforcement point enables, monitors and terminates connections between a subject and the resource. These are fed by data sources such as identity, device posture, threat intelligence and activity logs.
How does NIST 800-207 relate to ISO 27001 and SOC 2?
NIST SP 800-207 describes an architecture approach, while ISO 27001 and SOC 2 define auditable security controls. They complement each other: zero trust practices such as strong authentication, least privilege access, device management and continuous monitoring also satisfy many ISO 27001 Annex A controls and SOC 2 criteria. With control mapping, the same evidence can support all three.
How long does it take to implement zero trust under NIST 800-207?
There is no fixed timeline. NIST SP 800-207 expects most organisations to migrate gradually, running a hybrid of zero trust and perimeter-based architecture for some time. It recommends identifying actors, assets and business processes, formulating policies, selecting candidate solutions, then deploying and monitoring incrementally. Duration depends on the size and complexity of your environment.
Does OneClickComply support NIST 800-207?
Yes, on request. NIST SP 800-207 is mapped in OneClickComply's control library and is available to customers who ask for it, rather than being a standard framework you can switch on today. It links the zero trust tenets to practical controls and uses automated evidence collection and continuous monitoring to show how your environment reflects each tenet.
Related standards
All standards- NIST SP 800-82 Rev. 3Guidance · US
- NIST SP 800-171A Rev. 3Guidance · US
- NIST SP 800-82 Rev. 3 High OT OverlayGuidance · US
- NIST SP 800-82 Rev. 3 Moderate OT Overlay BaselineGuidance · US
- NIST SP 800-171AGuidance · US
- NIST SP 800-161 Rev. 1Guidance · US
- NIST SP 800-161 Rev. 1 Level 3 (Operational C-SCRM)Guidance · US
- NIST AI 600-1 Generative AI ProfileGuidance · US
Get NIST 800-207 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.