By · Last updated 2026-05-14

Back to BlogSMB Security

DORA ICT Vendor Management with ISO 27001

DORA requires financial institutions to maintain rigorous oversight of ICT vendors including annual assessments and incident notification requirements.

May 14, 20268 minute read
DORA ICT vendor managementISO 27001 DORA compliancefinancial institution vendor riskannual vendor assessmentMiFID II vendor oversight

What DORA Requires

DORA became EU law in January 2025. Banks, insurers, investment firms, and payment firms must now manage risk from every tech supplier they use. Three rules stand out.

Mandatory contract terms (Article 30). Each contract with a tech provider must cover four points: audit rights, incident alerts, exit plans, and performance targets. These clauses are not optional.

Annual reviews (Article 28). Firms must check every key supplier at least once a year. A provider is "key" if its failure would stop normal work. Anonymization tools used in compliance tasks fall into this group.

Supplier register (Article 28(3)). Firms must keep a live list of all key third-party contracts. The list must include security records for each one.

Running yearly reviews for dozens of providers takes time. One custom review — done from scratch — takes an estimated 40–80 hours per provider. A Dutch bank with 50 key suppliers faces up to 4,000 hours of review work each year. That is two full-time staff working on reviews and nothing else.

ISO 27001 Cuts Review Hours

ISO 27001 certification gives firms a faster route through DORA's yearly review rule. The certification body runs a check audit every year and a full audit every three years. The certificate has an end date. It stays valid only while annual checks pass.

Under DORA's yearly review rule, a firm can pull the provider's current ISO 27001 certificate once a year and check the date. A valid date means an outside audit body checked the provider's 93 security controls in the past twelve months. The firm logs this in the supplier register. The review is done.

The time gain is real. A Dutch bank checking a certified anonymization tool spends a few hours on the review. The same review done from scratch takes weeks. Across 20 certified third parties, the yearly saving can reach 1,200 hours. That time can go to other work.

Why Privacy Tools Are in Scope

Privacy and anonymization tools fall under DORA when a firm uses them to handle client data, meet GDPR rules, or process KYC files. If the tool goes down and the firm cannot produce GDPR-safe output, the tool is a key third party under DORA. It must be reviewed each year.

Our GDPR compliance guide explains data minimization rules. See also ISO 27001 downstream compliance value and ISO 27001 vendor assessment shortcuts for more on how certification cuts compliance work.

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

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.