By · Last updated 2026-03-11

返回博客GDPR 与合规

SaaS泄露激增300%:零知识成必选项

Conduent暴露2590万条记录,NHS Digital影响900万名患者,攻击者在9分钟内攻破SaaS供应商。当您的供应商成为攻击面时。

March 11, 20269 分钟阅读
SaaS securitydata breach 2024zero-knowledge architecturevendor risk managementGDPR Article 28

供应商已成为攻击面

2026年更新

十年来,安全团队始终专注于同一个目标:将攻击者挡在网络外。保护边界、锁定端点、控制登录权限——旧模式假设攻击者会直接攻击组织本身。

2024年的数据表明这个模式已经失效。据Obsidian Security 2025年SaaS安全威胁报告显示,2024年SaaS泄露事件激增300%。攻击者不再直奔组织而去,而是瞄准了组织信任的SaaS工具。

当您的云端工具成为攻击目标时,强大的内部网络毫无帮助。客户记录、员工文件和敏感内容都存储在工具服务器上,被工具的密钥锁定,在工具遭受攻击时一并暴露。

2024年SaaS泄露数据

Conduent遭受的泄露暴露了2590万条记录。Conduent为政府机构和大型企业处理业务流程,涵盖福利、支付和公民服务。2590万名受影响者根本不知道第三方持有他们的信息。

NHS Digital的泄露影响了900万名患者。患者记录通过云端工具服务器暴露——患者将信息提供给医疗机构,根本没有理由知道这些信息曾到达过他们从未听说过的第三方平台。

这些不是偶发事件,而是新常态。大型泄露现在影响数百万信任某一机构的人,而他们的个人信息却被另一个他们从未知晓的机构持有。

为什么SaaS泄露的方式不同

传统网络入侵需要许多步骤,攻击者必须突破边界、在系统中横移、提取文件,每一步都可能被发现。

SaaS泄露的方式不同:攻击者攻破云端平台后,就能获取所有通过该平台发送内容的客户记录,一次泄露即可从数十乃至数百个客户处获取文件。

9分钟的泄露窗口——从首次访问到SaaS系统中记录被盗的时间(据Obsidian Security事件记录)——显示了这一过程的速度。在共享平台内部,攻击者同时发现来自众多客户的内容,这种价值集中使每次攻击的效率极高。

零知识匿名化作为解决方案

解决方案从一个思维转变开始:如果任何平台都可能遭到攻击——2024年的记录证明确实如此——那么任何平台都不应该收到可读形式的客户个人信息。

上传前的零知识匿名化从根本上改变了泄露风险:当持有零知识处理内容的平台遭到攻击时,攻击者获取的是没有可读客户标识符的匿名记录,无需进行主体通知,无需GDPR第82条联合责任诉讼,也不会产生监管后续。

这不是理论,而是一个简单事实:没有记录可以被盗,因为没有以可读形式发送任何记录。

请参阅FAQ了解零知识匿名化的常见问题,以及定价页面了解规模保护的成本。

参考资料

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

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