By · Last updated 2026-03-03

返回博客GDPR 与合规

零知识与零信任云加密

LastPass也对用户数据进行了加密——但4.38亿美元仍然被盗。了解服务端加密与真正零知识架构之间的区别。

March 3, 20269 分钟阅读
zero-knowledgeencryptionGDPRdata protectionSaaS securityLastPass

加密幻觉

2026年更新

2022年12月,LastPass告知用户发生了数据泄露。他们的措辞很平静:密码已"加密",保险库内容已"安全保护"。

到2025年,超过4.38亿美元已从LastPass用户那里被盗。盗窃直接来自他们那些"安全"的保险库。

原因是什么?LastPass持有密钥。

您的安全团队在选择任何云工具之前都必须了解这一点,包括PII匿名化平台。

服务端加密与零知识架构对比

大多数云工具声称"加密您的文件",但它们使用的是服务端加密(SSE)。以下是具体区别:

属性服务端加密零知识架构
加密发生位置供应商服务器上您的设备上(浏览器/桌面)
密钥持有者供应商仅限您
供应商能否读取您的内容不能
服务器泄露是否暴露文件否(仅密文)
供应商能否被强制共享内容不能(他们没有)
执法机构访问通过供应商没有您的密钥则不可能

LastPass持有密钥,这是致命缺陷。攻击者入侵后同时获得了密文和破解工具。他们利用社会工程、弱密码暴力破解和旧账户元数据。

为什么这对GDPR第25条很重要

GDPR第25条(隐私设计)非常明确。控制者必须使用"适当的技术和组织措施",且这些措施必须从一开始就内置于系统中。

仅靠服务端加密无法满足这一要求:

  • 供应商可以在法律要求下交出明文内容
  • 服务器泄露会暴露实际数据
  • 供应商员工可以访问内容以提供支持

零知识架构满足第25条要求:

  • 明文数据从未到达供应商服务器
  • 法律命令只能产生密文
  • 即使是完整的服务器泄露也只暴露密文

零信任如何融入其中

零信任是一种网络安全架构,假设默认情况下没有人可信任——包括内部网络上的人。"永不信任,始终验证"。

零信任和零知识是不同的,但互补的概念:

零信任解决了可以访问系统的问题。它控制身份验证、网络访问和横向移动。

零知识解决了供应商能否读取您数据的问题。即使在完全授权的访问下,供应商也看不到明文内容。

一个声称"零信任"的工具可能仍然持有您的加密密钥。最好的问题不是"他们使用零信任吗?"而是"他们能读取我的数据吗?"

请参阅我们的安全合规概述了解anonym.legal的零知识实现,以及零知识声明评估指南了解供应商评估框架。

参考资料

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

开始使用 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.