Password Vault
A password vault is a central, encrypted store for privileged credentials — passwords, SSH keys, certificates and API keys — that controls who may use them and when, rotates them and records every checkout.
What is a password vault?
A password vault is a central, encrypted store for privileged credentials: administrator and root passwords, service account passwords, SSH keys, certificates and API keys. Unlike an ordinary repository, a vault does not just store secrets — it also decides who may use them, under what conditions and for how long, and it records every checkout.
In many organisations, passwords to key systems still live in spreadsheets, notes, scripts and the memory of a few people. They go unchanged for years because nobody knows what will stop working. A password vault brings order to this area and is one of the pillars of Privileged Access Management (PAM).
Password vault definition
A password vault is a PAM component that stores privileged credentials in encrypted form, releases them according to an access policy, changes them automatically and keeps a complete log of operations. The goal is a state in which no privileged credential is permanently known to any person, and every use of it can be attributed to a specific person and a specific task.
How a password vault works
Central, encrypted storage
Secrets are kept in one place, encrypted and organised into collections that reflect systems, teams or customers. Rights to collections are granted to roles rather than to individuals, which makes it easier to uphold the principle of least privilege.
Checkout and check-in
An administrator who needs a password checks it out of the vault: they give a reason, and the policy may require approval from a manager or the security team. A checkout can be exclusive (only one person uses the secret at a time) and time-limited. When the work is done, the password goes back to the vault, and every checkout and check-in is logged.
Secret rotation
Rotation is the automatic change of a credential on the target system and the storage of the new value in the vault. The vault connects to the server, database or network device and changes the password or key:
- on a schedule (for example, at a set interval),
- after every checkout, so that a password known to the administrator stops working,
- after an event, such as an employee leaving or a suspected leak.
Credential injection
The highest level of protection comes when the user never learns the password at all. The PAM gateway authenticates the user with their own account and injects the credential from the vault directly into the session with the target system. The password then cannot be written down, passed on or used outside the controlled connection.
Detecting compromised passwords
Some systems compare stored passwords against lists of passwords exposed in known breaches and flag those that need to be changed immediately.
Password vault vs password manager
Both tools store passwords in encrypted form, but they serve different purposes:
- A password manager helps an individual user manage their own passwords for applications and websites. It is about convenience and avoiding password reuse.
- A PAM password vault protects shared and privileged credentials that belong to the organisation. It enforces access rules, approvals and time-limited access, rotates passwords on target systems, records every use for audit and can hide the password from the user.
A password manager cannot replace a vault for administrative accounts, and a vault is not a tool for employees’ everyday passwords.
Use cases
- Administrative account passwords for servers, domain controllers, hypervisors and network devices.
- Service and application accounts — passwords previously stored in configuration files and scripts.
- SSH keys — control over who holds a key to which server, and regular key replacement.
- Vendor access — a technician gets access for the duration of a job, and the password is changed when it ends.
- Emergency accounts (“break glass”) — a password sealed in the vault whose checkout triggers an alert and a review.
How it works in practice — the Fudo Enterprise example
In Fudo Enterprise, the vault role is played by the Password Vault module: it provides encrypted storage, lifecycle management, controlled access and full auditability of credentials, including passwords, SSH keys, X.509 certificates and API keys. Operations on secrets, such as viewing, checkout and check-in, are tracked in the vault’s log. Rotation is handled by Secret Changer mechanisms, which change secrets over SSH, LDAP, Telnet or WinRM, with ready-made templates for systems including Unix, MySQL, Cisco and MS Windows, plus the option of custom scripts. The vendor states that the vault automatically rotates passwords and SSH keys and injects them into sessions without exposing them to users. After a list of compromised passwords (plaintext or SHA-1 hashes) is uploaded, Password Vault scans all stored passwords against it.
Benefits
- No more permanently known passwords — after rotation, a password someone remembered or wrote down stops working.
- Accountability — every checkout has an author, a time and a reason, which makes audits and incident investigations easier.
- Smaller impact of a leak — a stolen credential has a short lifetime.
- Smooth departures and role changes — revoking access does not require manually changing dozens of passwords.
- Order — the organisation knows which privileged accounts exist and who may use them.
Limitations and challenges
- Inventory — a vault only protects the accounts you know about. The first stage of a deployment is usually discovering privileged accounts scattered across systems.
- Application dependencies — rotating a service account password can stop an application that has it hard-coded. Map the dependencies before switching on automatic changes.
- The vault as a target — a central store needs strong multi-factor authentication, backups, high availability and an emergency procedure in case it becomes unavailable.
- The password is not everything — a vault does not show what was done after login. That gap is filled by privileged session recording.
Summary
A password vault turns scattered, rarely changed privileged passwords into secrets that are stored centrally, issued for the duration of a task, rotated automatically and logged. It delivers the most value together with a gateway that injects credentials into sessions and with recording of what happens after login.
Related Terms
- Privileged Access Management - managing privileged access
- Privileged Access - the level of access to administrative operations
- Privileged Session Recording - capturing work on administrative accounts
- Least Privilege - the principle of least privilege
- Just-in-Time Access - temporary access on demand
Explore Our Services
Want to bring privileged account passwords under control and switch on rotation? Explore:
- PAM Implementation - design, deployment and operation of privileged access control
Frequently asked questions
+ What is a password vault in PAM?
It is a central, encrypted store for privileged credentials: administrator and root passwords, service account passwords, SSH keys, certificates and API keys. The vault decides who may use a given secret and under what conditions, records every checkout and changes passwords after use or on a schedule, so that no credential lives for years in a spreadsheet or a script.
+ How is a password vault different from a password manager for employees?
A password manager helps an individual user store their own passwords for applications and websites. A PAM password vault protects shared and privileged credentials that belong to the organisation: it enforces access rules, approvals and time-limited access, rotates passwords on target systems, records every use for audit and can inject a password into a session so the user never sees it.
+ What is secret rotation?
Secret rotation is the automatic change of a password, SSH key or other credential on the target system and the storage of the new value in the vault. It runs on a schedule, after every checkout or after an event such as an administrator leaving. As a result, even a leaked password quickly stops working.
+ Is a password vault enough to protect privileged accounts?
No. A vault reduces the risk of password theft and misuse, but it does not show what was done after login. A complete PAM programme combines the vault with a gateway that brokers connections, session recording, access granted for the duration of a task and strong authentication of the people who use the vault.