What does a password manager actually protect you from, and what does it quietly leave exposed? That question sounds academic until you remember that in 2022, attackers walked off with encrypted vaults from a major provider and nobody could say for sure how well the master passwords would hold up under offline guessing. Three names come up again and again when people weigh this tradeoff: 1Password, LastPass, and RoboForm. They look similar on a features page. Underneath, they make different bets about where your secrets live and who can reach them. This comparison focuses on those bets, not on sticker prices or interface polish, and it flags where each tool’s protection ends.
The 2022 Breach That Reset the Conversation
Any honest discussion of these three tools starts with the LastPass incident. In August 2022 the company disclosed a compromise of a developer environment. By late 2022 it confirmed that attackers had taken customer vault data, including encrypted password vaults plus unencrypted fields such as website URLs. The encrypted contents stayed locked behind each user’s master password. The metadata did not.
That distinction matters more than most people realize. Encryption at rest protects the contents of a vault. It says nothing about the shape of the vault, which sites you use, or when you last logged in. After the breach, researchers also pressed LastPass on its default PBKDF2 iteration counts for older accounts, which were historically low enough to make offline guessing of weak master passwords more feasible. The company later raised those defaults. The episode became a case study in how breach-notification duties work under regimes like the GDPR, where scope and timing are scrutinized as closely as the intrusion itself.
The practical lesson for anyone choosing a manager in 2027 is simple: ask what happens if the vendor’s servers are compromised. That single question separates these three products more than any feature list.
What 1Password Actually Protects
1Password’s core design choice is the Secret Key, a second secret generated on your device and combined with your account password. The vault blob stored on the server is useless on its own, because an attacker cannot begin offline guessing without the Secret Key. This is documented in the company’s security white paper, and it is the reason a stolen server-side copy of your data is less dangerous than it would be under a single-password model.
What that protects:
- Server-side breaches. A stolen encrypted blob without the Secret Key is a dead end for most attackers.
- Weak master passwords. The Secret Key adds entropy the user never has to remember.
- Cross-device sync. You get convenience without handing the vendor a decryptable copy.
Where the limits begin: a compromised endpoint still defeats it. Malware or a keylogger on your own machine can capture what you type and what you see. A phished master password combined with a weak second factor is another gap. And the Secret Key does not protect metadata the way vault contents are protected, so the architecture reduces risk rather than eliminating it. If you are evaluating alternatives more broadly, a breakdown of 1Password alternatives for beginners covers how other tools handle the same two-secret problem. (Lastpass alternatives explained beginners which password)
What LastPass Protects Now
LastPass has spent the years since 2022 rebuilding trust through transparency and hardening. Its model is zero-knowledge encryption in the architectural sense: encryption and decryption happen on the client, and the vendor does not hold your master password. Vault contents are protected by your master password and the key-derivation settings attached to your account.
What that protects:
- Vault contents under normal conditions. A stolen encrypted vault is only as strong as your master password and the iteration count behind it.
- Everyday credential sprawl. Generated passwords, autofill, and breach monitoring all reduce the human habit of reuse.
Where the limits begin: the 2022 case showed that metadata can be exposed even when contents stay encrypted. The strength of the model also depends heavily on user behavior. A short or reused master password, combined with a low iteration count, is a much softer target than the architecture suggests. LastPass has raised defaults and added stronger key-derivation options, but the burden of a strong master password sits more visibly with the user here than with a two-secret design. If you are weighing a switch, this guide to moving off LastPass and picking a manager that fits walks through the migration steps without the marketing noise. (Password manager)
What RoboForm Protects
RoboForm, from Siber Systems, dates back to the late 1990s as a form filler and has long offered local-only storage as an alternative to cloud sync. That option is its most distinctive security feature. If your vault never leaves your device, a server-side breach of RoboForm’s infrastructure cannot expose it, because there is nothing of yours on the server to take.
What that protects:
- Vendor-side exposure. Local-only mode removes the cloud from your threat model entirely.
- Form-heavy workflows. RoboForm’s heritage is filling long forms, and that focus shows in how it handles identities and addresses.
Where the limits begin: local-only storage shifts risk to you. Device loss, disk failure, and malware on that one machine become the whole ballgame unless you maintain your own encrypted backups. Sync users get convenience back but return to a cloud model with its own tradeoffs. RoboForm’s security architecture also differs from both competitors in ways that deserve a direct read of its own documentation rather than a summary. (Xbox game pass cost 2025 real prices whether its worth)
Side-by-Side: Architecture and Exposure
| Feature | 1Password | LastPass | RoboForm |
|---|---|---|---|
| Second secret beyond master password | Yes, Secret Key | No | No |
| Client-side encryption | Yes | Yes | Yes |
| Local-only storage option | No | No | Yes |
| Metadata exposure risk in a breach | Lower | Higher (demonstrated in 2022) | Depends on storage mode |
| Passkey support | Yes | Yes | Yes |
| Recovery options that weaken the model | Limited by design | More recovery paths | Varies by setup |
The table compresses a lot. The important row is the first one. A second secret changes what a server breach means. Local-only storage changes it differently, by removing the server. LastPass relies on the strength of a single user-chosen secret plus strong key derivation, which is a legitimate design but a thinner margin.
The Passkey Shift Changes the Question
By 2025, all three vendors supported passkeys, the phishing-resistant credentials built on the FIDO2 and WebAuthn standards. This quietly changes what a password manager is for. A passkey is bound to the site it was created for, so a fake login page cannot harvest it the way it harvests a typed password. That removes an entire attack class from the manager’s job description.
But passkeys do not make the manager irrelevant. Someone still has to store them, sync them, and recover them when a phone is lost. The recovery flow becomes the new weak point. A manager that lets you reset access through email alone has effectively downgraded its security to the strength of your email account. When comparing these three in 2027, look at how each handles passkey recovery, not just whether the feature exists.
Limits That Apply to All Three
No password manager fixes certain problems, and pretending otherwise is how people get hurt.
- A compromised device defeats every model. If malware runs on your machine while the vault is unlocked, the vault is open.
- Phishing plus a weak second factor still works. Passkeys help enormously, but only where sites support them.
- Legal compulsion is outside the architecture. A court order or coercion can require disclosure regardless of encryption.
- Metadata leaks are structural. Encryption protects contents, not always the pattern of your accounts.
- Recovery features trade security for convenience. Every “forgot password” path is a potential entry point.
The broader lesson connects to supply chain security for beginners: your risk rarely sits in one product. It sits in the chain of devices, vendors, and recovery flows around it.
How to Choose Without Overthinking It
- Decide whether you can tolerate any cloud copy of your vault. If not, RoboForm’s local mode is the only one of the three that fits.
- If you accept cloud sync, ask whether you want a second secret. 1Password’s Secret Key is the strongest answer here.
- Check the key-derivation settings on your account, especially if it is old. Raise them if the option exists.
- Turn on the strongest second factor available and prefer passkeys where sites offer them.
- Test your recovery flow before you need it. Log out on one device and walk through getting back in.
- Keep an encrypted emergency backup of your vault somewhere you control.
A common mistake is treating the master password as the only lock. It is one lock among several, and the weakest one usually decides the outcome. Another is skipping the recovery test until a phone dies on a trip. Five minutes of practice beats an hour of panic.
Common Mistakes People Make
People pick a manager based on a review’s star rating, then reuse a master password they already use elsewhere. That single habit undoes the strongest architecture on this list. Others enable every recovery option for convenience and later discover those options are the easiest path in. A third mistake is ignoring metadata: users assume that because their passwords are encrypted, their account list is private too. It often is not.
The fix is unglamorous. Use a long, unique master password stored somewhere physical. Raise iteration counts where you can. Keep recovery minimal. And revisit the choice every couple of years, because the threat model moves. If you are comparing two of the most-recommended cloud options directly, this 1Password versus Proton Pass comparison shows how the second-secret idea plays out against a newer entrant. (NIST Block Cipher Techniques project)
Conclusion
The 1Password vs LastPass vs RoboForm question is really three questions about exposure. 1Password reduces what a server breach yields by requiring a second secret. LastPass relies on strong client-side encryption and the discipline of a strong master password, with a documented 2022 breach showing exactly where metadata can leak. RoboForm offers the one thing the others do not: a way to keep your vault off the cloud entirely. None of them protects against a compromised device, a phished master password, or legal compulsion. In 2027, the smartest move is to match the architecture to your actual risk, then test your recovery flow before you need it. Pick the model whose failure mode you can live with.
Frequently Asked Questions
Is 1Password more secure than LastPass?
Not in every dimension, but its two-secret design means a stolen server-side vault cannot be attacked offline without the Secret Key. LastPass relies on a single master password plus key derivation, so its security depends more heavily on user behavior and account settings.
What did the 2022 LastPass breach actually expose?
Attackers took encrypted vault data along with unencrypted fields such as website URLs. Vault contents stayed protected by each user’s master password, but the metadata exposure was real and became the central criticism of the incident.
Does RoboForm store my passwords in the cloud?
Only if you choose sync. RoboForm has long offered a local-only storage mode, which keeps your vault on your device and removes vendor-side exposure. The tradeoff is that backups and device security become entirely your responsibility.
Are passkeys making password managers obsolete?
No. Passkeys reduce phishing risk but still need storage, sync, and recovery. The recovery flow becomes the new weak point, so how a manager handles a lost device matters more than whether it lists passkey support.
Can a password manager protect me from malware?
No. If malware or a keylogger runs on your device while the vault is unlocked, it can capture what you type and see. A manager limits credential sprawl and breach damage, but it cannot secure a compromised endpoint.
How often should I reconsider my password manager?
Every couple of years, or after any major breach disclosure. Threat models shift, defaults change, and recovery features get added. Re-test your recovery flow and check your key-derivation settings at the same time.
