Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A password vault stores credentials encrypted under a key derived from a master secret, so people can use long unique passwords everywhere without remembering any of them.

What Is a Password Vault?
The arithmetic of passwords has never worked. People hold accounts in the dozens, security advice demands that each has a long and unique password, and human memory supports neither requirement. The predictable result is reuse, and reuse is what turns one breached website into compromised accounts everywhere else, as described in credential stuffing.
A password vault resolves the arithmetic by removing memory from the equation. Credentials live in an encrypted store, and the user remembers one strong passphrase that unlocks it.
The master passphrase is not the encryption key. It is fed into a key derivation function—PBKDF2 with a high iteration count, or preferably a memory-hard function such as Argon2id or scrypt—which produces the key and makes brute forcing deliberately slow and expensive. The vault contents are then encrypted with AES-256 or an equivalent.
Reputable products do this client-side, which is what “zero-knowledge” means in their marketing: the provider’s servers receive and store only ciphertext, and the derived key never leaves the user’s device. The provider cannot read your vault, and equally cannot recover it if you forget the passphrase.
Two consequences follow. First, the strength of everything depends on the master passphrase and the iteration count. Second, a breach of the provider is survivable in principle—but only in principle, and the LastPass incident of 2022 showed why the detail matters. Attackers obtained encrypted vault backups, and because URL fields in those vaults were not encrypted and many older accounts were still using low PBKDF2 iteration counts inherited from earlier defaults, the stolen data was considerably more useful to them than a zero-knowledge claim would suggest. Subsequent cryptocurrency thefts have been traced to credentials recovered from that data.
Using a personal vault for application secrets, or a human vault for service accounts, is a common and poor substitution. The access patterns, rotation needs, and audit requirements are different.
Browser autofill is the honest competitor, and it is what staff will keep using if the alternative is inconvenient. So prioritise the extension working properly, mobile access, and a sharing mechanism that is easier than sending a password over chat—because a vault that makes legitimate sharing hard guarantees that sharing continues to happen elsewhere.
Beyond usability, the controls that matter are: multi-factor authentication on the vault itself, since it is now the single most valuable account each person holds; a master passphrase policy demanding genuine length rather than character classes; separate vaults or collections for privileged credentials; and recovery arranged in advance, through an enterprise recovery key held under dual control, because “the provider cannot help you” is a real constraint.
The reporting is the underused part. Enterprise vaults will tell you which credentials are reused across sites, which appear in known breach corpora, and which have not changed in years. That report is usually the clearest picture of credential risk an organisation can obtain cheaply, and it directly supports the password management expectations in Cyber Essentials.
It does not stop phishing. Autofill offers mild protection—the extension will not fill a credential on a domain that does not match, which a user may notice—but a determined phishing page simply asks the user to copy and paste, and most will.
It does not protect against a compromised endpoint. Malware running with the user’s privileges can capture the master passphrase, read the unlocked vault from memory, or steal the session afterwards. Vault security is bounded by endpoint security.
And it keeps passwords in the picture. The longer-term direction is to remove them: passkeys for the accounts that support them, with the vault increasingly acting as the passkey store rather than a password store. Treat a vault as the control that makes today’s password estate survivable while you reduce it.
At Privia Security, we review credential management practice across the estate in our cyber risk analysis services.
It concentrates risk, which is a fair concern, but the alternative is reuse across dozens of sites and that is measurably worse. A vault protected by a long passphrase and multi-factor authentication, with client-side encryption, is far stronger than the password habits it replaces. Treat the vault account as the most valuable one each person holds and protect it accordingly.
Encryption and decryption happen on your device, so the provider stores only ciphertext and never holds the key. They cannot read your vault, and they also cannot recover it if you lose the passphrase. The LastPass breach showed the limits: unencrypted metadata such as URLs and weak key derivation settings on older accounts still gave attackers useful material.
No. Applications need programmatic retrieval, frequent rotation, and audit trails that human vaults are not designed for. Use a dedicated secrets manager for workloads, and a privileged access management platform for administrative accounts where sessions should be brokered and credentials rotated after each use rather than displayed to a person.
Only weakly. The browser extension will decline to autofill on a domain that does not match the stored entry, which gives an alert user a hint that something is wrong. But a phishing page can simply ask the user to type or paste the credential, and most will comply. Phishing resistance requires origin-bound authentication such as passkeys.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.