> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/concepts/zero-standing-privilege.md).

# Zero standing privilege

Zero standing privilege (ZSP) in Devolutions PAM removes default permissions, granting access just-in-time and revoking it immediately after use.

**Zero standing privilege** (ZSP) is a security model where accounts are created with no permanent permissions or group memberships. In this model, access rights are granted only when required and revoked immediately after use. This minimizes the attack surface and limits what an attacker could do if the account is compromised.

In Devolutions PAM, ZSP accounts are designed to exist without any default privileges. When elevated access is needed, privileges are granted [just-in-time](/pam/concepts/just-in-time-elevation.md) for the duration of the task, then automatically removed. This dynamic approach protects sensitive systems while supporting operational needs.

ZSP is often compared to the principle of [least privilege](/pam/concepts/least-privilege.md) (PoLP), which restricts users to the minimum permissions necessary to perform their tasks. The key difference is that the PoLP maintains a continuous, minimal level of access, while ZSP eliminates all standing access until explicitly required. ZSP offers greater security for high-risk environments by reducing exposure time to privileged credentials.

#### Zero standing privilege aliases

* ZSP
* No standing privilege

#### See also

* [Glossary of Common Privileged Access Management (PAM) Terms](https://blog.devolutions.net/2021/01/glossary-of-common-privileged-access-management-pam-terms/)
* [Need Cybersecurity Insurance? Then You Probably Need PAM, Too](https://blog.devolutions.net/2023/10/need-cybersecurity-insurance-then-you-probably-need-pam-too/)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/pam/concepts/zero-standing-privilege.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.