The Incident That Shifted Cloud Security
Updated for 2026
The 2022 LastPass breach is not mainly about password managers. It is about trust. Firms trusted a cloud vendor with their data. That trust broke. The cause was hidden flaws, not recklessness.
LastPass sold a zero-knowledge design. In practice, it was not zero-knowledge. 25 million users had their encrypted vaults stolen. The attack was first disclosed in August 2022. LastPass revised its disclosures several times. The full scope emerged by late 2022.
For firms in healthcare, finance, and legal, this was not a distant news story. These sectors face real liability when data leaks. The LastPass case was an early sign of a wider problem.
Two Flaws That Enabled the Attack
Post-incident review found two key weaknesses.
Weak key setup. LastPass used PBKDF2 for key derivation. Newer accounts had 100,100 iterations. OWASP recommends 600,000. Some old accounts had as few as 1 iteration. Fewer iterations make brute-force attacks fast and cheap. Attackers with vault files could test master passwords at high speed.
Plaintext metadata. Vault contents were encrypted. But metadata was not. URLs, usernames, and service names were all visible in the stolen data. Attackers could see which services each user had accounts with. That enabled targeted phishing and credential stuffing. No vault cracking was required.
This case shows why two questions must be asked separately. "Is the design zero-knowledge?" is one question. "Is the build correct?" is a different question.
Okta in 2023: A Different Attack, the Same Result
In October 2023, Okta reported a security incident. A stolen credential gave an attacker access to its customer support system. The attack exposed 600,000+ support records. These included files uploaded by customers during support sessions.
Okta is an identity security platform. The issue was not a design flaw. It was an access control failure. A support engineer's login was stolen. The attacker used it to reach sensitive data.
LastPass and Okta show the two main paths to a vendor compromise:
- Design failures — zero-knowledge claims that were not built correctly
- Access control failures — valid credentials used to reach data they should not reach
Zero-knowledge design prevents the first type. It does not stop an attacker with valid support credentials. But it blocks that attacker from reading customer data. The vendor never holds decryptable content. See our security and compliance overview for how this applies to PII tools.
SaaS Security Events Rose 300% in Two Years
Obsidian Security found a 300% increase in SaaS platform security events from 2022 to 2024.
This is not a 300% rise in attacker skill. Two forces drove it. SaaS use grew fast. Attackers followed the data. One vendor compromise can expose data from dozens of clients at once. That pay-off favors vendor attacks over single-firm attacks.
Enterprises that assumed cloud platforms were safe need to update that view. SaaS vendors are now primary targets.
Questions to Ask Any Cloud Vendor
For buying and security teams, this checklist covers the core areas.
Encryption setup:
- Ask for the key derivation algorithm, iteration count, and memory settings.
- Confirm iteration counts meet OWASP minimums. That is 600,000 PBKDF2-SHA256 or equivalent Argon2id.
- Verify that key derivation runs on your device, not on vendor servers.
Metadata exposure:
- Ask what metadata is stored in plaintext next to encrypted content.
- Request a data model. It should show which fields are encrypted and which are visible in an attack.
Support access:
- Ask whether support staff can access customer data.
- Confirm that support systems cannot reach customer plaintext.
Incident history:
- Ask for all prior security events, including those below public disclosure thresholds.
- Assess how complete and honest prior disclosures were.
The LastPass incident was a build failure and a trust failure. Vendors with specific answers allow real risk review. Vendors with vague claims leave risk hidden. That risk often surfaces only after an attack. See our compliance overview for vendor evaluation guidance.
anonym.legal uses zero-knowledge architecture for PII anonymization. Key derivation runs via Argon2id in your browser or desktop app. Encryption happens before data leaves your device. Servers store only ciphertext they cannot decrypt. Learn more.