TechNational Institute of Standards and Technology

Explainer

Updated

What is zero trust?

Key facts

NIST SP 800-207 names seven tenets of zero trust and three core logical components: the policy engine, the policy administrator and the policy enforcement point.

Zero trust is a set of cybersecurity concepts for making access decisions on each request, on the view that the network may be compromised. The NIST glossary gives the definition in one sentence: "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 glossary attributes that definition to NIST Special Publication 800-207, Zero Trust Architecture.

The seven tenets

NIST SP 800-207, section 2.1 states that a zero trust architecture is designed and deployed with adherence to seven basic tenets. It calls them "the ideal goal."

TenetWhat the publication says
1. ResourcesAll data sources and computing services are considered resources.
2. Secure communicationAll communication is secured regardless of network location, and network location alone does not imply trust.
3. Per-session accessAccess to each resource is granted per session, with the least privileges needed, and access to one resource does not grant access to another.
4. Dynamic policyAccess is set by dynamic policy that includes the observable state of the client identity, the application or service, and the requesting asset.
5. Asset monitoringThe enterprise monitors the integrity and security posture of all owned and associated assets, and no asset is inherently trusted.
6. Continuous authenticationResource authentication and authorization are dynamic and strictly enforced before access is allowed, and trust is reevaluated throughout the session.
7. Information collectionThe enterprise collects as much information as possible about the state of its assets, network and communications, and uses it to improve its security posture.

Core logical components

Section 3 of the same publication names three core logical components. The table gives NIST's description of each.

ComponentRole, as NIST describes it
Policy engine (PE)Makes the decision to grant, deny or revoke access to a resource for a subject, and logs that decision.
Policy administrator (PA)Establishes or shuts down the communication path between a subject and a resource, and generates session-specific credentials.
Policy enforcement point (PEP)Enables, monitors and eventually terminates connections between a subject and an enterprise resource.

Where the firewall fits

The publication notes that many definitions of zero trust stress "removing wide-area perimeter defenses (e.g., enterprise firewalls)" as a factor. It adds that most of these definitions still describe themselves in relation to perimeters, such as micro-segmentation. A reader who knows how a firewall guards the edge of a network can compare it with the per-resource checks in the tenets table.

What changed and when

The NIST page for SP 800-207 lists the publication's document history, shown below.

DateStatus
September 23, 2019Draft
February 13, 2020Draft
August 11, 2020Final

Cases a reader meets next

  • Scope. The tenets apply to work done within an organization or in collaboration with partner organizations. They do not apply to anonymous public or consumer-facing business processes, because an organization cannot impose internal policies on customers or general internet users.
  • Partial adoption. The publication says the tenets are the ideal goal and that not all of them may be fully implemented in their purest form for a given strategy.
  • Personal devices. Tenet 5 says personally owned devices may be allowed to access some resources but not others.
  • Combined components. Some implementations treat the policy engine and the policy administrator as one service. The policy enforcement point may be a single portal, or it may split into a client side, such as an agent on a laptop, and a resource side, such as a gateway in front of the resource.
  • Authentication. Tenet 6 says an enterprise implementing zero trust would be expected to use multifactor authentication for access to some or all enterprise resources.

Have another question?