By · Last updated 2026-03-16

返回博客技术

LastPass之后:评估零知识声明

LastPass用户的4.38亿美元在其"加密"保险库遭到攻击后被盗。ICO随后开出120万英镑罚款。这里是评估供应商零知识声明是否成立的核查清单。

March 16, 20268 分钟阅读
zero-knowledge evaluationvendor security assessmentLastPass breachcloud encryption claimsGDPR Article 32

声明与架构之间的差距

2026年更新

每个云供应商都说同样的话:"我们加密您的数据。"这个说法几乎总是正确的,却几乎总是不够的。

2022年的LastPass泄露是最好的例证。LastPass对用户密码保险库进行了加密,使用了真实的加密技术,声明是准确的。然而2500万用户的保险库被盗,到2025年,4.38亿美元已从LastPass用户那里通过加密货币盗窃案被取走,该数字由Coinbase Institutional追踪。

英国信息专员办公室于2025年12月对LastPass英国实体处以120万英镑罚款。原因是"未能实施适当的技术和组织安全措施"。加密技术是真实的,但不符合要求的标准。

LastPass案改变了任何云隐私工具的核心问题:不是"他们加密我们的数据吗?"而是:"他们能解密我们的数据吗?"

真正重要的四个问题

1. 密钥派生在哪里发生?

在真正的零知识设计中,密钥派生发生在客户端——即浏览器或桌面应用中,在任何数据发送之前。密钥在本地加密数据,只有密文到达供应商服务器。如果供应商在其服务器上派生密钥,他们持有密钥,就能解密。

2. 供应商是否曾看到明文?

某些工具在静态时加密数据,但为了处理(运行AI模型、搜索索引或审计日志)会解密。在那个窗口期间,明文存在于供应商系统上,攻击者此时攻击就会暴露未加密数据。

3. 在法律程序下会发生什么?

持有服务端密钥的供应商可能被强制交出解密内容。真正零知识的供应商只能提供密文,即使面对传票也没有任何有用的内容可以交出。

4. 完整的服务器泄露会暴露什么?

在真正的零知识系统中,完整泄露只产生加密数据块,攻击者获得没有密钥的密文。在供应商密钥系统中,入侵会同时暴露密钥和数据。

LastPass实施缺陷

LastPass事件揭示了一个具体缺陷:旧账户使用的PBKDF2只有少至1次迭代用于密钥派生,而安全计数为60万次迭代。这一弱设置使对被盗保险库的暴力破解变得可行。

这表明仅检查设计是不够的,供应商可以使用零知识设计但实施不当。需要同时询问:密钥在哪里派生,以及算法强度如何。

实际评估清单

架构审查:

  • 询问密钥派生发生在客户端还是供应商服务器
  • 索取加密算法、密钥长度和迭代次数
  • 确认明文从不发送至供应商服务器

泄露场景测试:

  • 询问完整服务器泄露会暴露什么
  • 唯一正确答案:"我们无法解密的加密密文"
  • 任何其他答案意味着声明不是真正的零知识

法律程序审查:

  • 询问供应商是否能根据传票提供客户明文
  • 真正的零知识供应商无法提供他们没有的内容

合规核查:

  • 索取供应商的GDPR第32条文件
  • ISO 27001,特别是附件A密码控制,提供外部验证

请参阅安全合规概述了解anonym.legal如何处理零知识,以及合规文档了解GDPR第32条的完整内容。

参考资料

准备好保护您的数据了吗?

开始使用 285 种实体类型在 48 种语言中匿名化 PII。

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.