Back to glossary

Glossary term

Zero Trust Security

A security model built on the principle that no user, device, or system is trusted by default. Every access request must be verified based on identity, device health, and context, continuously, not just at login.

A security model built on the principle that no user, device, or system is trusted by default. Every access request must be verified based on identity, device health, and context, continuously, not just at login.

The Core Idea

Zero Trust is a security philosophy, not a product. The principle is: don't assume that anything inside your network is trustworthy. Verify everything, every time. "Never trust, always verify."

The model is a direct response to the failure of perimeter-based security. Traditional network security assumed threats came from outside and that anything inside the corporate network was safe. That assumption broke down as remote work spread, as cloud applications moved data outside any perimeter, and as attackers proved repeatedly that getting past the perimeter was achievable. Once inside, they could move laterally with little resistance.

Zero Trust security model eliminates the concept of a trusted inside. Every access request, from inside the office or from a home network, is treated as potentially untrusted until verified. Identity, device health, location, and time of request are all evaluated before access is granted.

The Three Principles

Zero Trust rests on three ideas.

  • Verify explicitly: authenticate and authorize every request using all available signals, identity, location, device health, and behavioral anomalies.
  • Use least privilege: limit user rights to the minimum needed for the role, and grant access for the minimum time necessary.
  • Assume breach: design systems as if a breach has already occurred. Limit lateral movement and minimize blast radius.

What Zero Trust Requires

Implementing Zero Trust is an architecture shift, not a single product purchase. It typically requires strong identity verification (MFA, SSO through a robust identity provider), device health checks (is this device enrolled in MDM? Is it patched and encrypted?), network segmentation (can an attacker who compromises one system reach others?), and continuous monitoring (session logging, anomaly detection, audit trails).

The endpoint is central. A user authenticating with valid credentials from an unmanaged, unpatched device should not receive the same access as someone on a managed, compliant device. MDM tools enable this by reporting device compliance status to the identity provider in real time.

Zero Trust and Distributed Work

Zero Trust became the dominant security model partly because remote work made the old perimeter model unworkable. When employees work from home, coffee shops, and co-working spaces, there's no meaningful perimeter to defend. Zero Trust solves for this: the user's location becomes irrelevant; what matters is whether they can prove their identity and whether their device is compliant.

Related terms

Browse adjacent topics in the same workflow area.

Share this term

Copy a direct link for your team or documentation.

Explore more glossary terms

Keep exploring the glossary without leaving the section.