> 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/secrets-management.md).

# Secrets management

Secrets management in Devolutions PAM securely stores and rotates passwords, API keys, and certificates using vaults and just-in-time access.

**Secrets management** in privileged access management (PAM) focuses on securely storing, controlling, and [rotating](/pam/concepts/password-rotation.md) sensitive information such as administrative passwords, API keys, and certificates. It is a foundational aspect of protecting [privileged accounts](/pam/concepts/privileged-account.md) and minimizing the risk of credential theft or misuse.

In Devolutions PAM, secrets are stored securely in PAM vaults and can be configured for automatic rotation and expiration. By using [just-in-time access](/pam/concepts/just-in-time-elevation.md), users can request temporary access to a secret without ever viewing the password. This ensures better accountability and reduces exposure of high-value credentials. Permissions and audit trails further enhance security and [compliance](/pam/concepts/compliance-reporting.md).

Secrets can be used interactively—where users inject credentials into a remote session without seeing them—or through automation, such as scripting access for maintenance tasks. This flexibility helps organizations streamline operations while protecting critical assets.

#### Related topics

* [Permissions/RBAC/Roles](https://docs.devolutions.net/rdm/concepts/advanced-concepts/permissions-rbac-and-roles)
* [Password management](https://docs.devolutions.net/rdm/concepts/basic-concepts/password-management)
* [External PAM integrations](https://docs.devolutions.net/rdm/concepts/advanced-concepts/external-pam-integrations)


---

# 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/secrets-management.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.