Zero Trust
Also known as: zero trust architecture, ZTA
A security principle of never trusting anyone automatically - every request is checked, even from inside the network.
Draft - this entry has not been reviewed yet.
Formal
A design approach in which no user, device or network location is trusted by default; each request for access is checked for identity, device health and need, and given only the least access required for that one task.
In plain English
Like a hospital where your badge is checked at every ward door, not just at the main entrance - getting inside the building does not get you everywhere.
In practice
An employee at her desk inside a ministry opens the payroll system and is still asked to prove who she is, while her laptop is checked for current updates before the page loads.
Why it matters
Once one machine inside is taken over, a network that trusts its insiders lets the attacker roam freely; checking every request limits how far one break-in spreads.
How to put it into practice
The usual steps, in order. Adapt them to your organisation.
- Get management backing and name an owner, and plan zero trust as a staged programme over several years rather than a single product purchase.
- Map users, devices, applications, data and the flows between them, and choose the most critical resources to protect first.
- Assess current maturity for each pillar (identity, devices, networks, applications and workloads, data) with the CISA Zero Trust Maturity Model, and set a target stage.
- Make identity the main control point with one identity provider, phishing-resistant MFA and conditional access that checks both the user and the device.
- Enrol all devices in device management, and let device health such as patch level and EDR status feed into every access decision.
- Replace broad VPN access with per-application access through an access proxy or ZTNA service, starting with a few applications and expanding from there.
- Segment the network and restrict east-west traffic, so that reaching one system does not give reach to the rest.
- Grant access per session with least privilege and short token lifetimes, and harden and monitor the identity provider itself as a critical asset.
- Collect logs from identity, devices and network in one place, measure progress against the target stage every year, and adjust the roadmap.
Common pitfalls
- Buying a product labelled zero trust and assuming the work is done.
- Forgetting legacy systems, OT and file shares that cannot enforce per-request checks, and leaving them as open back doors.
- Making the identity provider the single gatekeeper without hardening and monitoring it as a critical asset.
Good guides
Technical deep dive
The ideas predate the name. The Jericho Forum argued from 2004 for "de-perimeterisation", and in 2010 Forrester analyst John Kindervag coined "zero trust" for a model that removes implicit trust based on network location. Google's BeyondCorp, described in a series of papers from 2014, was the first large-scale implementation: employees reached internal applications through an internet-facing access proxy that evaluated user identity and device inventory state, with no privileged corporate network. NIST SP 800-207 (2020) became the reference definition, with seven tenets that include treating all data sources and services as resources, securing all communication regardless of location, granting access per session, deciding access by dynamic policy, and continuously monitoring asset integrity and posture.
Architecturally, SP 800-207 separates a control plane from a data plane. The policy decision point comprises the policy engine, which evaluates a trust algorithm, and the policy administrator, which establishes or tears down the session; the policy enforcement point sits in the data path in front of the resource. Inputs to the trust algorithm include the identity provider, device management and EDR posture, threat intelligence, activity logs, data classification and access policy. NIST distinguishes criteria-based algorithms (all conditions must be met) from score-based ones (a confidence level compared with a threshold), and singular from contextual evaluation that considers recent behaviour. It describes three implementation approaches - enhanced identity governance, micro-segmentation and software-defined perimeters - and deployment models such as device agent with gateway, resource portal and enclave gateway. NIST SP 1800-35, finalised in 2025, documents example builds with commercial products.
For planning, CISA's Zero Trust Maturity Model 2.0 (2023) defines five pillars - identity, devices, networks, applications and workloads, data - with cross-cutting capabilities for visibility and analytics, automation and orchestration, and governance, and four maturity stages from Traditional through Initial and Advanced to Optimal. US federal agencies were directed by OMB M-22-09 (2022) toward phishing-resistant MFA, device inventories, encrypted DNS and HTTP, and treating internal applications as internet-accessible.
In practice the common first steps are zero trust network access (ZTNA) replacing broad VPN access with per-application brokering, conditional access that combines identity and device compliance, and segmentation that restricts east-west traffic. Pitfalls are well known: the identity provider becomes a concentration of risk and must itself be hardened and monitored; legacy protocols such as NTLM, SMB file shares and OT systems resist per-request enforcement; session tokens issued after a strong check can be stolen and replayed; and vendors label almost any access product "zero trust". The model does not eliminate trust - it makes each trust decision explicit, narrow, short-lived and logged.
What to learn first
Everything this builds on, foundations first.
Relationships
- Consists of
- Principle of least privilege
- Implemented by
- Conditional access
- Don't confuse with
- VPNPerimeter security
- Mitigates
- Lateral movement
Sources & further reading
Standards & official texts
- NIST SP 800-207 - Zero Trust Architecture · NIST
- NIST SP 1800-35 - Implementing a Zero Trust Architecture · NIST
Course material
- Cyber Security Fast Track - Ordliste
Where this data comes from
This entry was drafted by an AI from the sources above and has not yet been checked by a person. Treat it as a starting point, and check anything important against the sources.
See the review queueSuggest a correction on GitHubThis term as JSON
Check yourself
Loading…