> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/system-design/security/security-principles/zero-trust-security-model.md).

# Zero Trust Security Model

## About

The **Zero Trust Security Model** is a security framework that operates on the principle of **"Never Trust, Always Verify."** Unlike traditional security models that assume everything inside an organization's network is safe, Zero Trust requires strict verification for every user, device, and application trying to access resources—regardless of whether they are inside or outside the network perimeter.

## **Principles of Zero Trust**

1. **Continuous Verification** – Every access request must be authenticated, authorized, and continuously validated before granting permissions.
2. **Least Privilege Access** – Users and systems get only the minimum necessary access required for their tasks.
3. **Micro-Segmentation** – Networks are divided into small, isolated zones to limit the impact of breaches.
4. **Assume Breach Mentality** – Always operate under the assumption that an attacker is already inside the system.
5. **Device and Endpoint Security** – Verification extends beyond users to the security posture of devices accessing the system.
6. **Strong Authentication** – Multi-factor authentication (MFA) and risk-based authentication are enforced.
7. **Comprehensive Logging and Monitoring** – All access and activities are continuously monitored and logged to detect anomalies.

## **Difference Between Zero Trust Security Model & Zero Trust Architecture**

<table data-full-width="true"><thead><tr><th width="148">Aspect</th><th>Zero Trust Security Model</th><th>Zero Trust Architecture</th></tr></thead><tbody><tr><td><strong>Definition</strong></td><td>A security philosophy and approach based on continuous verification and least privilege.</td><td>A practical implementation of the Zero Trust principles using specific security technologies and strategies.</td></tr><tr><td><strong>Scope</strong></td><td>High-level security concept that applies to policies, identity management, and access control.</td><td>Technical implementation, including network segmentation, endpoint security, and policy enforcement mechanisms.</td></tr><tr><td><strong>Implementation</strong></td><td>Can be implemented across different architectures, including cloud and on-premises environments.</td><td>Defines how to design an IT infrastructure that enforces Zero Trust principles.</td></tr><tr><td><strong>Focus</strong></td><td>Focuses on security policies and principles.</td><td>Focuses on how to enforce and implement these principles.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/system-design/security/security-principles/zero-trust-security-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.