Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

Zero trust: definition, principles and architecture according to NIST

Domains

Cloud and platforms · Engineering

In brief

Zero trust is a cybersecurity model in which no trust is granted to a user or a device solely because of its location on the network: every access to a resource is authenticated, authorised and reassessed. The NIST SP 800-207 publication describes zero trust as a set of guiding principles, not as a single architecture.

Page contents

Definition of zero trust according to NIST

Zero trust, sometimes rendered in French as “confiance zéro”, is a cybersecurity model that strips network location of its value as proof. The NIST SP 800-207 publication, “Zero Trust Architecture” (August 2020), gives a public definition of it: the term refers to an evolving set of cybersecurity paradigms that move defences from static, network-based perimeters to focus on users, assets and resources.

No implicit trust is granted to an account or a device solely because of its location, physical or network, or because it belongs to the organisation. Authentication and authorisation, of both the subject and the device, precede the opening of any session to a resource. NIST specifies that zero trust is not a single architecture but a set of guiding principles.

The limits of the perimeter model

The perimeter model protects a boundary: whatever is inside the organisation’s network is considered safe. NIST sets two observations against it. Remote users, personal devices and cloud services no longer sit behind a single boundary. And once the perimeter has been crossed, nothing hinders an attacker’s lateral movement from one resource to another.

Zero trust therefore assumes that an attacker is already present in the environment, and seeks to reduce implicit trust zones.

Seven tenets, three logical components

The publication sets out seven tenets. It presents them as an ideal, whose application may remain partial.

  1. All data sources and computing services are resources.
  2. All communication is secured regardless of network location.
  3. Access to each resource is granted on a per-session basis, with least privilege.
  4. Access is determined by dynamic policy, which takes into account identity, the application and the state of the requesting device.
  5. The organisation monitors the integrity and security posture of all its assets.
  6. Authentication and authorisation are dynamic and strictly enforced before any access.
  7. The organisation collects as much information as possible about the state of its assets, its network and its communications, and uses it to improve its security.

A zero trust architecture (ZTA) applies these tenets through three core logical components. The policy engine decides whether to grant, deny or revoke access. The policy administrator establishes or shuts down the communication path. The policy enforcement point, placed in front of the resource, enables, monitors and terminates the connection.

NIST describes three approaches to achieving this, intended to be combined: through enhanced identity governance, through micro-segmentation, and through network infrastructure and software-defined perimeters.

Zero trust, products, cyber resilience: not to be confused

The expression does not mean the absence of all trust. Trust is never implicit: it is assessed with each request.

It does not refer to a product to be installed. According to NIST, the transition is not achieved by a wholesale replacement of technologies: it is carried out in stages.

Nor can zero trust be reduced to multi-factor authentication, which is only one of its means. For the cloud, configuring identities and access is described in our article on how to secure a cloud infrastructure. Finally, zero trust is distinct from cyber resilience: it limits an attacker’s access and movement, without saying how to keep the business running when an incident occurs nonetheless.

Textbook case: access for a maintenance provider

Take a provider responsible for maintaining an inventory management application. In a perimeter model, remote access can place the provider on a segment of the internal network, from which other servers can be reached.

In a zero trust architecture, the request arrives at a policy enforcement point placed in front of the application. The policy engine examines the technician’s identity, verified by several factors, the state of the workstation, the requested resource and the time of day. The session is opened to this application only, with the rights needed for the work. Another resource would require a new decision. If the workstation stops complying with the policy, access is revoked.

Zero trust reduces the reach of an intrusion. Business continuity and recovery after an incident are covered in our page on cyber resilience.

FAQ

Frequently asked questions

Another question? Ask us

What does zero trust mean?

Zero trust refers to a cybersecurity model in which trust is never granted implicitly. A user or a device is not considered safe because it is on the internal network or because it belongs to the organisation. Every access to a resource is authenticated and authorised before the session is opened, then reassessed.

Where does the term zero trust come from?

The NIST SP 800-207 publication traces this origin. It recalls that the Jericho Forum publicised the idea of de-perimeterisation in 2004, which limits implicit trust based on network location. It attributes the term zero trust itself to John Kindervag, who coined it while working at Forrester.

What is the difference between zero trust and zero trust architecture?

According to the NIST SP 800-207 publication, zero trust is a set of concepts and ideas, and zero trust architecture (ZTA) is an organisation's cybersecurity plan that applies them. This plan covers the relationships between components, the organisation of workflows and access policies. The former is a doctrine, the latter its translation into a given information system.

Does zero trust do away with the network perimeter?

No. The NIST SP 800-207 publication describes implementing zero trust as a gradual journey, not as a wholesale replacement of infrastructure. It expects most organisations to operate in a hybrid mode, both zero trust and perimeter-based, for an indefinite period. Perimeter defences remain, but they no longer count as access authorisation.

Is zero trust required by the NIS2 Directive?

Directive (EU) 2022/2555, known as NIS2, names zero trust principles only in its recital 89, among the basic cyber hygiene practices that essential and important entities should adopt. A recital serves to interpret the text: the risk management measures are set out in Article 21 of the directive and in the national law transposing it. Determining what applies to a given entity is a matter for legal analysis.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.