Zero trust explained: what NIST and CISA actually mean by it
Zero trust is a design principle, not a product: no implicit trust by network location, verify every request. What NIST SP 800-207 and CISA's maturity model say - and what a small team can take from them.
Few security terms get attached to as many products as "zero trust." The idea underneath the marketing is simpler and more specific: NIST's Special Publication 800-207 defines zero trust as an evolving set of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users, assets and resources. Here is what that actually commits you to - and what it doesn't.
What zero trust actually says
NIST's definition has a sharp edge: no implicit trust is granted to assets or user accounts based solely on their physical or network location - being on the office LAN versus the internet - or based on asset ownership, company laptop or personal phone. Authentication and authorization, of both the user and the device, are discrete functions performed before any session to a resource is established. The idea is a response to how work actually happens now: remote users, bring-your-own-device and cloud services mean the interesting resources are rarely inside one perimeter anyway.
The maturity model
CISA's Zero Trust Maturity Model, version 2.0 from April 2023, turns the principle into a roadmap. It names five pillars - identity, devices, networks, applications and workloads, and data - plus three cross-cutting capabilities that span them, and describes what traditional, initial, advanced and optimal implementations look like in each. The model was written to guide federal agencies, aligned to the White House's OMB M-22-09 directive, but CISA presents it as a reference any organization can use to plan its own transition.
What a small team can take
Very few small teams need a formal zero-trust program, and nothing in NIST's or CISA's documents asks them to buy one. The portable parts are the instincts: don't treat the office network as trusted by default, verify the person and the device on each request rather than once at the door, and keep access as narrow as the job allows. CISA is candid that zero trust may require a change in an organization's philosophy and culture, not just its tooling - which is another way of saying the maturity model's early stages are about habits you can start before any procurement.
The calm version
Zero trust is not a box you install and it is not a claim that nothing can be trusted. It is the discipline of not trusting location - your network may already be hostile - and checking each request on its own merits. NIST wrote the definition, CISA drew the map; the starting point is smaller than the sales pitch suggests.
Sources: NIST SP 800-207, "Zero Trust Architecture" (definition and principles) and CISA's Zero Trust Maturity Model page and version 2.0 document (five pillars, cross-cutting capabilities, maturity stages, OMB M-22-09 alignment).
Frequently asked questions
Is zero trust a product you can buy?
No. NIST defines it as an evolving set of cybersecurity paradigms used to plan infrastructure and workflows, and CISA's maturity model is a roadmap across five pillars - neither is something a vendor can sell you in a box.
Does zero trust mean trusting nothing at all?
It means no implicit trust: being on the company network or using a company device does not by itself grant access. Users and devices are authenticated and authorized before each session to a resource.
Is zero trust only for governments and big enterprises?
CISA's maturity model was written to guide federal agencies, but the NIST principles respond to remote work, personal devices and cloud services - conditions any small team already has. The early maturity stages are habits, not purchases.
What are the five pillars of CISA's model?
Identity, devices, networks, applications and workloads, and data - with three cross-cutting capabilities running across them, and maturity stages from traditional to optimal in each.