dora-audit-2026-how-to-prepare-for-a-supervisory-review (1)
  • Dora
  • 16th Nov 2026
  • 1 min read

DORA Audit 2026: How to Prepare for a Supervisory Review

In Short..
  1. Register of Information gaps are the first thing NCAs catch: NCAs cross-check submissions automatically against xBRL-CSV data, and incomplete sub-outsourcing chains are the most common finding.

  2. Board-level sign-off is what examiners look for on the ICT risk framework: Examiners treat CISO- or CTO-only approval as a finding requiring a documented board resolution.
  3. A zero-notification incident classification methodology is itself a red flag: Examiners read a clean notification record as a sign that classification thresholds are set too conservatively.
  4. TLPT capacity is running out: Every entity designated under Article 26 must complete a Threat-Led Penetration Test (TLPT) by 17 January 2028, and accredited providers are already booking 12 to 18 months ahead.
  5. Readiness is an operating rhythm, sustained quarter after quarter: A 90-day plan gets you audit-ready, but the evidence library only holds up if it's maintained on that cadence.

The tolerance period is over. If your programme only exists on paper, an examiner will find that out quickly.

 

Updated: November 2026

Introduction

A DORA supervisory review in 2026 tests whether your operational resilience programme runs in practice: live processes, tested controls, and evidence examiners can trace back to every obligation. The Digital Operational Resilience Act (Regulation (EU) 2022/2554) has applied since 17 January 2025, and by mid-2026 national competent authorities (NCAs) had shifted from guidance to active inspection.

NCAs are now cross-checking Register of Information data automatically, issuing supervisory letters to institutions with material gaps, and scoping the first wave of mandatory penetration tests. The EBA completed a formal peer review of DORA implementation quality in Q3 2026, the first cross-EU supervisory comparison of its kind, and its findings have sharpened examiner expectations considerably.

sc_platform_gracie
EXPLORE MORE DORA RESOURCES
DORA has applied since 17 January 2025. Guides, roadmaps and tools for every pillar, from third-party oversight to resilience testing.
Visit the DORA hub

Expert View

Matt Davies

Matthew-Davies-1536x1022-Dec-11-2023-11-07-34-7484-AM

Chief Product Officer, SureCloud

LinkedIn

 

What our experts say about why board evidence decides DORA outcomes

 

"The boards that pass a DORA review are the ones that already know what a bad finding sounds like. I've watched risk teams describe a control perfectly and still get flagged, because nobody could show it running under pressure. Evidence beats explanation every time."

 

The GRC brief
DORA changes and supervisory priorities, monthly.

What Is a DORA Supervisory Review?

A DORA supervisory review is a regulatory examination of how your organisation meets DORA's operational resilience obligations in practice. Examiners look for live processes, tested controls, and traceable evidence that your programme operates as documented. This goes well beyond the paperwork checks of an ISO certification audit. An on-site inspection may accompany or follow a desk review, giving examiners direct access to assess controls in operation.

Who Conducts It

Your NCA conducts the review, coordinated against common standards set by the three European Supervisory Authorities: the European Banking Authority (EBA), the European Securities and Markets Authority (ESMA), and the European Insurance and Occupational Pensions Authority (EIOPA). For entities designated as Critical Third-Party Providers (CTPPs), oversight runs at EU level through a Lead Overseer and Joint Examination Teams.

November 2025 update: On 18 November 2025, the ESAs published the first official list of 19 CTPPs under Article 31(9) of DORA. Designated providers, including AWS, Microsoft, Google Cloud, Deutsche Telekom, Oracle, SAP, IBM, Accenture, Bloomberg, and Capgemini, are now subject to direct ESA inspection rights, annual risk assessments, and binding recommendations. The list is updated annually.

Who This Applies To

DORA applies to financial entities regulated under EU financial services law, including banks, insurers, investment firms, and payment institutions in scope under Regulation (EU) 2022/2554, alongside ICT third-party providers carrying flow-down obligations and those designated, or likely to be designated, as CTPPs under DORA's third-party oversight framework (Articles 28 to 44).

This guide is aimed at compliance, risk, and IT teams preparing for a first formal DORA supervisory review, or responding to a supervisory letter already in hand. SureCloud's DORA Compliance Guide and the five pillars of DORA explained cover the regulatory foundations in detail; this guide picks up where they leave off, focusing on operational readiness and evidence preparation.

Understanding the Enforcement Escalation Ladder

DORA enforcement in 2026 involves escalating supervisory measures, from initial engagement and requests for remediation through to formal sanctions. NCAs take different approaches depending on the nature and severity of non-compliance, and constructive engagement at the earlier stages can prevent matters from escalating.

The typical escalation sequence runs as follows:

  1. Desk review or data request: triggered by Register of Information analysis or incident report patterns
  2. Supervisory letter or findings letter: identifies gaps and sets a remediation timeline of 60 to 90 days
  3. On-site inspection: reserved for significant institutions or where desk review findings are material
  4. Formal remediation order: a legally binding requirement to fix specific gaps by a specific date
  5. Compulsion payment notice: a daily penalty for continued non-compliance after the deadline passes
  6. Administrative fine or public censure: the final sanction for wilful or repeated non-compliance

Most institutions that engage constructively at step two close their gaps before an on-site inspection is ever scheduled. The Netherlands' DNB issued the first batch of supervisory letters to institutions with material ICT risk gaps in early 2026. Italy's regulators finalised national Register of Information submission timelines over the same period. BaFin has announced formal follow-up audits running through 2026 and 2027, targeting specifically the quality of information registers, ICT risk frameworks with board sign-off, and TLPT follow-through.

The costliest outcomes are reserved for entities that ignore supervisory correspondence entirely or fail to remediate material gaps after a formal order lands.

What Penalties Actually Look Like

Article 50 of DORA sets the principle: penalties must be effective, proportionate, and dissuasive. The exact ceiling is set by each member state, which has produced real divergence across jurisdictions.

Jurisdiction

Financial Entity Ceiling

Senior Manager Exposure

Italy

€20 million or 10% of annual turnover (higher applies)

Up to €5 million

Ireland

€10 million or 10% of turnover

Up to €1 million

Germany

Up to 2% of annual worldwide turnover

Up to €5 million

Finland

Proportionate to severity

From €100,000

For Critical Third-Party Providers under direct EU oversight, the penalty structure is harmonised: the Lead Overseer can impose daily penalty payments of up to 1% of the provider's average daily worldwide turnover, for a maximum of six months.

The practical takeaway: check the specific penalty regime your NCA enforces. The gap between a flat national ceiling and Italy's €20 million or 10% of turnover is wide enough to change how a board thinks about risk appetite. For a detailed breakdown by member state, DLA Piper's analysis of DORA penalty regimes is the most comprehensive publicly available reference.

What NCAs Are Examining in 2026

Supervisory communications and industry intelligence from the first half of 2026, including findings from the EBA's Q3 peer review and BaFin's published audit priorities, point to six areas receiving the highest examination attention. A DORA readiness assessment can help organisations identify gaps across each of them before examiners arrive.

1. Register of Information Quality

The Register of Information (RoI) is the first thing NCAs cross-check, and it is now machine-readable. Supervisors run automated queries across submitted xBRL-CSV data, identifying missing ICT providers, anomalous concentration patterns, and discrepancies against previously reported incident data.

The most common deficiencies in the first submission wave: missing sub-contracting chain information, incorrect criticality classification (critical, important, or supporting), and incomplete geographic data-residency fields. Entities with incomplete registers received formal supervisory letters requiring remediation within 60 days.

Examiners expect every ICT-related contractual arrangement logged, including cloud marketplace purchases, SaaS subscriptions, managed services, and sub-outsourcing chains. Classification decisions need documented reasoning: a wrong classification is a finding even when the contract itself is filed correctly.

2. Board-Level ICT Risk Framework Approval

Examiners expect the ICT risk management framework to carry the full board's formal approval. They will ask for the board resolution, the framework document, and evidence that the board receives ICT risk reporting at least quarterly.

A framework signed off only by the CISO or CTO is a finding in itself. Examiners look for minuted board engagement, not just a signature. Institutions whose ICT risk taxonomy conflicts with their incident-reporting taxonomy under Article 18 are being flagged too. The fix is straightforward: reconcile the two taxonomies before the review begins.

3. Article 30 Contract Compliance

Article 30, DORA's mandatory-contract-clauses provision, requires service level agreements, access and audit rights, data portability, termination assistance, and sub-outsourcing approval to appear in every contract with an ICT provider supporting a critical or important function.

Many institutions signed DORA-compliant addenda in 2024 and 2025. Examiners are now checking whether those addenda cover every subcontractor in the chain, not just the primary contract most teams remember signing.

4. Incident Classification Methodology

Examiners request the internal decision tree or criteria matrix used to classify whether an event is a major ICT incident requiring regulatory notification under Article 18, using the materiality thresholds set out in Commission Delegated Regulation (EU) 2024/1772.

A zero-notification track record is itself a finding. Examiners read it as evidence that classification thresholds are calibrated too conservatively. A methodology that has never produced a notification triggers scrutiny of the classification criteria, not just the incidents.

5. Resilience Testing Programme

Every in-scope entity needs a documented annual testing programme covering vulnerability assessments, network security assessments, and scenario-based tests. Entities designated under Article 26 also need a Threat-Led Penetration Testing (TLPT) scheduling plan.

Every entity designated by its NCA must complete at least one TLPT by 17 January 2028. The methodology is binding EU law under Commission Delegated Regulation (EU) 2025/1190, and a full cycle from provider procurement to attestation takes 9 to 14 months. With fewer than 40 TIBER-EU accredited providers across the entire EU, institutions that have not started planning are competing for scarce capacity.

Deloitte's Wave 3 DORA compliance survey found that only 50% of institutions expected to reach full compliance by end of 2025, with 38% pushing their target into 2026. NCAs are treating progress plans as insufficient on their own; proving the programme runs in practice is what matters now.

6. AI Governance in ICT Operations (New in 2026)

This is the area that caught many teams off-guard in the first supervisory wave. Examiners are now asking how AI tools used in ICT operations or decision-making are governed, following the ESAs' stated priority of assessing the implications of technological developments, including AI, across financial sector supervision.

The question is not whether you use AI. It is whether you have documented governance, accountability, and oversight for the AI tools that touch critical or important functions. If AI assists in incident triage, risk scoring, or vendor assessments, examiners want to see the governance wrapper around it: who is accountable, how outputs are validated, and what the human review process looks like. ESMA confirmed in its September/October 2026 newsletter that AI governance will remain a supervisory priority through 2027.

Step 1: Conduct a Self-Assessment

Run an internal gap analysis against DORA's five pillars before examiners arrive. Any findings that surface on your own terms, with time to remediate and evidence closure, are far less costly than the same findings surfaced by an examiner.

Use the five pillars as your frame: ICT risk management, incident reporting, resilience testing, third-party risk, and information sharing. For each pillar, perform a control-by-control check against the relevant RTS obligations, capture gaps with owners and due dates in your risk register, confirm testing calendars run year-round with retests built in, and check that incident classification logic and report clocks are defined, rehearsed, and recorded.

Using Existing Frameworks to Your Advantage

If your organisation holds ISO 27001 certification or aligns to NIS2 (the EU's Network and Information Security Directive, now transposed into national law in 24 of 27 EU member states as of November 2026), significant work is already done. Map existing controls to DORA obligations, record the equivalence so auditors can trace each requirement to a live control, and reuse artefacts where they already meet the same DORA outcomes.

SureCloud's DORA vs NIS2 vs ISO 27001 comparison guide walks through where the three frameworks overlap and how to run one mapped control set across all of them instead of three parallel evidence trails.

Mock-Audit Methodology

Self-review against Annexes I to IV with a regulator-style request list is the most reliable way to stress-test your readiness before the real thing. Walk through real incidents and tests, show artefacts live, and time each step. Check traceability end-to-end: from obligation to control to owner to evidence to last refresh.

Document outcomes in your risk register, and track owners and due dates on a standing quarterly cadence.

Step 2: Build Your Audit Evidence Library

Supervisors expect traceable, verifiable evidence for every obligation, including TLPT evidence. Centralising it means requests get answered quickly and consistently. An evidence library assembled in the two weeks before a request lands creates real exposure at exactly the wrong moment.

Recommended Evidence Categories

Policies and procedures

  1. ICT risk management policy
  2. Incident response policy
  3. Outsourcing and third-party management rules
  4. Change management policy
  5. ICT business continuity policy

Registers and logs

  1. Register of Information in xBRL-CSV format
  2. Incident log
  3. Asset register
  4. Vulnerability register
  5. Vendor tiering register with criticality classifications and documented rationale

Reports

  1. Risk reviews with KRIs and KPIs
  2. Resilience test results and retest evidence with timestamps
  3. Board and committee packs showing quarterly ICT risk reporting

Records and proof

  1. Board resolutions approving the ICT risk management framework
  2. Meeting minutes with ICT risk agenda items
  3. System exports, screenshots, tickets, and version histories
  4. Article 30 contract-clause confirmations for critical and important providers

Tag each artefact to the DORA obligation and RTS or ITS field it proves, with a named owner and a refresh cadence. Keep version history and snapshot sets before major changes.

The Incident Reporting Clock

The four-hour initial-notification window for major ICT-related incidents is where institutions get caught out most often. Examiners verify:

  1. When the clock starts and who authorises the major-incident classification
  2. That the initial notification goes out within four hours of classification and no later than 24 hours from detection
  3. That the intermediate report follows within 72 hours
  4. That the final report lands within one month of the initial notification
  5. That the timing model holds across weekends and public holidays

Pre-assemble a model incident evidence pack covering: the incident summary with classification decision and clock start; a timeline with key timestamps and approvals; RTS- and ITS-aligned report drafts; root-cause notes; impact assessment; and follow-up actions with owners and due dates. Examiners reviewing incident response governance expect this pack to be ready to produce on request, not drafted on the day.

Step 3: Engage Internal Stakeholders

DORA cannot sit with a single team. The regulation touches governance, ICT operations, legal, procurement, and business continuity simultaneously, and a cross-functional coordination model is what examiners look for when they ask how the programme runs.

Build the Audit Coordination Team

Role

Responsibility

Risk and Compliance

Overall coordinator; owner of the regulator request log

IT and Security

Technical SMEs for controls, testing, and RoI data

Legal

Regulatory interpretation; Article 30 clause review

Procurement

Contract artefacts; sub-outsourcing disclosure

Business owners

Service-impact assessments; continuity assumptions

Internal Audit

Independent challenge; mock-review execution

Clarify ownership early. You need: a single point of contact for the regulator with a named backup; evidence custodians per pillar with ready-to-show folders; a live request tracker with status and due dates; a scribe capturing commitments and timestamps during meetings; and an escalation path for overdue items.

Prepare Pillar Briefing Packs

For each of DORA's five pillars, prepare a one-page summary covering:

  1. How the obligation is met
  2. The key controls and policies in place
  3. The primary evidence location
  4. Open issues with owners and due dates
  5. Talking points for subject-matter experts

These packs do double duty: they prepare your team for walkthroughs, and a subject-matter expert working from one can answer three examiners in three different rooms without contradicting each other. Consistency under examination pressure is itself a credibility signal.

Step 4: Prepare for Regulator Questions

Supervisors test how your programme runs in practice, including how you meet your board obligations under DORA. The questions below reflect where examination attention concentrated most in the first 2026 supervisory wave, updated to include the AI governance line of questioning that emerged in the second half of the year.

Sample Questions Examiners Are Asking in 2026

  1. How is your ICT risk framework integrated with enterprise risk management, and where is the board's approval documented?
  2. Show us your incident classification decision tree, and walk us through the last time it produced a notification.
  3. When did you last test critical system failovers, and what did the retest evidence show?
  4. Which ICT providers are classified as critical or important, and how did you reach that classification?
  5. Walk us through your Register of Information. How do you capture sub-outsourcing chains?
  6. What is your exit strategy for your three largest cloud providers?
  7. How do you govern AI tools used in ICT operations or decision-making, and who is accountable when an AI output is wrong?

How to Answer Well

Keep answers short and show the artefact live. Reference the control and, where relevant, the RTS or ITS field it satisfies. Point to time-bound outcomes: test dates, findings, retests, and the owner of each. Name the accountable owner and the next scheduled refresh. Log any remediation as a dated action during the session.

The answer pattern examiners reward: name the control, show the evidence, give the date it was last tested, state the finding and when the retest confirmed closure, then name the owner and the next review date.

Vague answers that reference policy documents without live evidence are a red flag. Examiners are trained to tell the difference between a programme that operates and one that only documents.

Step 5: Simulate and Improve

A mock supervisory review is the single most effective preparation activity available. It surfaces the gap between what your policies say and what your team can actually produce under exam conditions.

Use Internal Audit or an external specialist to issue a regulator-style request list, and recreate the end-to-end flow: intake, evidence collection, walkthroughs, findings, and dated remediation actions. Time every stage so you know where delays happen and who unblocks them.

What the Mock Review Must Test

  1. Whether you can produce a current, complete Register of Information on request, including sub-outsourcing chains
  2. Whether an incident-classification tabletop can actually produce a major-incident notification (an exercise that cannot produce one is telling you the classification criteria are the problem)
  3. Whether your team can hit the four-hour, 72-hour, one-month timeline under realistic conditions, including weekends
  4. Whether you can demonstrate TLPT planning progress and a realistic timeline to completion if designated or likely to be designated
  5. Whether you can produce the documentary board-evidence file examiners want to see: training certificates, risk committee minutes, signed risk appetite statements, and quarterly ICT risk reports
  6. Whether you can articulate your AI governance framework for any AI tools used in ICT operations

Close Gaps as You Find Them

Assign owners and due dates for each finding. Schedule retests and attach proof to the original finding. Update policies and registers and capture version history. Snapshot the before-and-after evidence set so improvement is visible at the next checkpoint.

Audit readiness is an operating rhythm. The organisations that perform best under DORA supervision treat every quarter as though a supervisory letter could land the following Monday.

90-Day Plan to Audit-Ready

Use this as a planning model and adapt durations to your size, complexity, and current maturity.

Days 0 to 15: Establish the Baseline

Confirm scope, owners, and operating rhythm across Risk, Compliance, IT, Legal, and Procurement. Stand up or audit the consolidated Register of Information, covering services, systems, data, and vendors including sub-outsourcing chains. Align incident intake forms to RTS and ITS data fields and reporting clocks. Verify whether the ICT risk framework is board-approved and minuted. Map any AI tools used in critical or important functions and confirm governance accountability.

Days 16 to 30: Build the Evidence Library

Populate the evidence library with tagged artefacts and assign refresh cadences. Publish the annual resilience testing plan and schedule retests for open findings. Identify critical and important ICT suppliers, confirm Article 30 clause compliance in each contract, and assess TLPT applicability, seeking clarity from your NCA proactively if guidance has not yet been issued.

Days 31 to 60: Test the Programme

Run the first incident tabletop designed to produce a major-incident notification, and execute a business continuity drill with captured evidence. Launch supplier evidence collection on a documented calendar. Prepare TLPT scoping notes if designated or likely to be designated. Run a tabletop on AI governance accountability for any AI tools in scope.

Days 61 to 90: Mock Review and Closure

Execute a full mock supervisory review with a realistic regulator-style request list. Close high-risk remediation items and snapshot updated evidence before and after. Produce an executive pack with current status, open gaps, and next-quarter actions. Confirm the board evidence file is complete: minutes, risk appetite sign-offs, and quarterly ICT risk reports.

Ongoing After Day 90

Treat this as a quarterly operating cycle. Submit the Register of Information to your NCA annually; most member states set a 31 March deadline, though some national regulators, including the Netherlands' DNB and AFM, set earlier dates in March depending on which body supervises your entity. NCAs consolidate and report to the ESAs by 30 April. Run retests, update the testing programme, and keep the evidence library current.

Typical Regulator Request List

Pre-assemble these categories so your team can respond to a supervisory data request within days, not weeks.

Governance and framework

  1. Board resolution approving the ICT risk management framework
  2. Governance charter and RACI
  3. Committee minutes showing quarterly ICT risk reporting
  4. Signed and dated ICT risk appetite statement
  5. AI governance policy and accountability register (if AI tools are used in critical functions)

Risk and incident management

  1. Risk register with KRIs, KPIs, and treatment plans
  2. Incident classification decision tree or criteria matrix
  3. Model incident evidence pack: summary, timeline, RTS- and ITS-aligned reports, root-cause notes, and follow-up actions

Resilience testing

  1. Annual resilience testing plan
  2. Test results and retest evidence with timestamps
  3. TLPT scope memo and planning evidence if designated or under assessment

Third-party risk and Register of Information

  1. Current Register of Information in xBRL-CSV format, per Commission Implementing Regulation (EU) 2024/2956
  2. Vendor tiering register with criticality classifications and documented rationale
  3. Article 30 contract-clause confirmation for critical and important providers
  4. Sub-outsourcing disclosure and flow-down evidence
  5. Exit-strategy documentation for significant providers

Board evidence file

  1. Board member ICT risk training certificates
  2. Risk committee minutes referencing ICT risk topics
  3. Quarterly ICT risk reports submitted to the management body

Per the ITS on the Register of Information, mandatory fields include the function supported, criticality classification with documented rationale, the location of data processing and storage, the sub-outsourcing chain, and an exit-strategy assessment. Missing fields in any of these categories make up the most common supervisory finding.

Keeping the Evidence Library Current Between Reviews

Audit readiness holds up when the evidence library stays current every quarter: policies, registers, reports, and records tagged consistently to DORA obligations and RTS or ITS fields, each with a named owner, a refresh cadence, and version history.

The teams that sustain this rhythm report measurable gains. Third-party risk assessments complete 50% faster when evidence is pre-assembled rather than collected on request. Vendor onboarding drops by 40% when the evidence is already structured and tagged. Audit preparation time falls by 75% when the library is maintained continuously rather than rebuilt each cycle.

Gracie AI Agents with Personas and Skills performs activities across that workflow: chasing third-party evidence, drafting evidence requests and audit narratives, flagging gaps against obligations, and maintaining the evidence library between audit cycles, with every action immutably logged and reviewable by a person. The aim is a programme examiners can watch operate live, not one assembled in the week before they arrive.

The standard examiners are applying in 2026: not whether your programme is documented, but whether it runs. Evidence of operation beats evidence of

See it in action

DORA is live. Supervisors want evidence.

See risk, third-party, incident and resilience testing evidence in one platform, mapped to all five DORA pillars.
Google preferred sources
Found this useful?

Choose SureCloud as a preferred source in Google and you will see more of our GRC guidance in Top Stories, AI Overviews and AI Mode. It takes one click and you can undo it at any time.

Your next step
PRICING

Price your DORA programme

A short form, no sales call. Pricing built around your GRC estate and the DORA scope you need to cover.

Get Pricing
4.2 / 5 · 46 reviews on G2
ANALYST REPORT

IDC names SureCloud the industry's first cross-domain agentic GRC platform"

Read the independent analyst view on how SureCloud is redefining risk and compliance.

Download for free

FAQ’s

What is a DORA audit?

A DORA audit or supervisory review is a regulatory examination by your National Competent Authority (NCA) that checks whether your organisation meets DORA's operational resilience obligations in practice. It covers ICT risk management, incident reporting, resilience testing, third-party oversight, and documentation completeness, going beyond an ISO-style certification check to test live processes and evidence that traces back to each obligation.

Who conducts DORA supervisory reviews?

Your National Competent Authority conducts the review locally, coordinated by common standards from the European Supervisory Authorities: EBA, ESMA, and EIOPA. For Critical Third-Party Providers, examinations run at EU level through a Lead Overseer and Joint Examination Teams, supported by the Oversight Forum.

What are NCAs examining most in 2026?

The first formal supervisory review wave points to five priority areas: Register of Information completeness and accuracy, board-level approval of the ICT risk management framework, Article 30 contract-clause compliance, incident classification methodology, including whether it has ever produced a notification, and the resilience testing programme, including TLPT planning. These are the deficiencies actually generating supervisory letters in 2026.

What is the TLPT deadline?

Every financial entity designated by its NCA under Article 26 must complete at least one Threat-Led Penetration Test (TLPT) by 17 January 2028. The methodology is binding EU law under Commission Delegated Regulation (EU) 2025/1190, and a full cycle from provider procurement to attestation takes 9 to 14 months. With fewer than 40 TIBER-EU accredited providers across the entire EU, institutions that haven't started planning are competing for scarce capacity.

What happens if my Register of Information is incomplete?

NCAs issue a supervisory letter requiring remediation within 60 days. Systematic deficiencies can escalate to formal remediation orders and fines under national law. When a major incident involves a provider that wasn't registered as critical, the supervisory response tends to be markedly stricter, because concentration risk went unmanaged.

What are the DORA penalties?

DORA leaves the exact penalty amounts to each member state under Article 50, so figures vary widely. Italy's ceiling is €20 million or 10% of annual turnover, whichever is higher; Ireland's is €10 million or 10% of turnover. Individual senior managers face personal exposure too, from €100,000 in Finland up to €5 million in Germany, and Critical Third-Party Providers under direct EU oversight face daily penalty payments of up to 1% of average daily worldwide turnover, capped at six months.