Doxis Blog  ECM & Archive

DORA compliance: requirements, penalties, and who it applies to

| Marc Volquardsen

Two professionals discussing the Digital Operational Resilience Act with a tablet and document in view.

The Digital Operational Resilience Act (DORA) has applied to banks and insurers across the European Union since January 17, 2025. On November 18, 2025, the European supervisory authorities published their first list of critical ICT third-party providers, built from the registers that financial entities had submitted, according to the European Banking Authority.

The effects reach well beyond the EU. US cloud providers appear on that list, and in July 2026 the UK named its own first critical third parties under a separate domestic regime.

DORA compliance is now checked against evidence. For a bank or insurer, or a technology provider serving one, the questions are practical: which obligations apply, and what proof to keep.

Key takeaways

  • DORA has applied since January 17, 2025 to around twenty categories of EU financial entities, including banks and insurers
  • Firms outside the EU fall in scope through their EU entities, and ICT providers anywhere are bound through their contracts with EU clients
  • Two areas depend heavily on documents: managing ICT third-party providers and keeping evidence of compliance
  • A major ICT-related incident must be notified within 4 hours of its classification, and no later than 24 hours after detection
  • UK firms face a parallel domestic regime, including an annual register of material third-party arrangements from March 18, 2027

What is DORA compliance?

DORA compliance is a financial entity's ability to meet Regulation (EU) 2022/2554, the Digital Operational Resilience Act, and to demonstrate it to its supervisor. It covers how the entity manages risks linked to information and communication technology (ICT), from internal systems to external providers.

The regulation covers around twenty categories of financial entity, from credit institutions to insurance and reinsurance undertakings. It applies proportionately: requirements reflect each entity's size and risk profile, and some are lighter for microenterprises.

DORA compliance requirements: the five pillars

DORA is organized around five pillars. For each one, the table shows what your supervisor can ask you to show and the type of solution that supports it.

Pillar

Articles

What you must be able to show

Type of solution

ICT risk management

5 to 16

A documented risk management framework and approved policies

Security tools, governed documentation

ICT-related incidents

17 to 23

Incident classification, notifications and reports

Detection and incident management tools

Resilience testing

24 to 27

A testing program, results and remediation

Testing providers, archived reports

ICT third-party risk

28 to 44

Compliant contracts, a register of information, exit strategies

Contract and document management

Information sharing

45

Cyber threat information-sharing arrangements

Documented agreements

Incident detection and penetration testing call for specialized security tools. Contracts, the register and the evidence behind them call for document management.

This second side accounts for a large share of supervisors' requests. It also involves teams that rarely share a system, from procurement to IT. That is where a clear document structure saves the most time.

Does DORA apply outside the EU?

DORA applies only in the EU, but it reaches US and UK companies in several ways. Which one applies depends on whether you are a financial firm or a technology provider.

US financial groups with EU entities

A US bank, insurer, or asset manager with an authorized subsidiary in the EU must make that subsidiary DORA compliant. Group IT services and outsourcing arrangements that support the EU entity come into scope as well.

Technology providers serving EU financial firms

EU financial entities must include DORA's mandatory clauses in their contracts with every ICT provider, wherever it is based. A US or UK software vendor with EU banking clients therefore accepts audit rights and exit provisions by contract, and appears in its clients' registers of information.

Providers designated as critical

The first EU list of critical ICT third-party providers, published in November 2025, includes US-headquartered groups such as Amazon Web Services, Google Cloud, and Microsoft. These providers come under direct oversight by the European supervisors, and a critical provider based outside the EU must set up an EU subsidiary within 12 months of its designation.

UK firms and the UK regime

UK groups are in scope of DORA for their EU activities. At home, they answer to a parallel UK regime that follows the same logic.

 

EU: DORA

UK regime

Core rules

Applies since January 17, 2025

Operational resilience rules (PRA SS1/21, FCA PS21/3) fully applied since March 31, 2025

Critical providers

ESAs designated the first list on November 18, 2025

HM Treasury designated the first four CTPs on July 10, 2026

Incident reporting

Initial notification within 4 hours of classification

Report no later than 24 hours after a threshold is met, from March 18, 2027

Third-party register

Register of information on all ICT contracts, submitted annually

Register of material third-party arrangements, submitted annually from March 18, 2027

The UK incident and third-party rules come from FCA PS26/2 and PRA PS7/26, published in March 2026. A UK group with EU entities will run both regimes side by side, so the same contract data has to serve two registers.

Your must-have guide to modernizing your legacy systems

This must-have guide shows banks and insurance the benefits of modernizing their enterprise content management and how to modernize successfully. Download your free copy.

Read now

Keep your ICT contracts audit-ready

Article 30 of DORA sets out the clauses every ICT services contract must contain. For services that support critical or important functions, it adds audit rights for the firm and its supervisor, as well as an exit strategy.

When the supervisor asks for the exit clause in your contract with your main hosting provider, the signed version needs to be found in minutes. In many firms, it sits with procurement while the latest amendment sits with legal.

A single file per contract solves this. It holds the signed contract and every amendment, along with the data the register needs, such as the function supported or the renewal date.

With Doxis contract management, each ICT contract has its own electronic file. Alerts flag renewal dates in advance, leaving time to review clauses before a contract rolls over. Reviews and terminations follow a defined process, and each step stays on record.

Turn your contract database into a reliable register of information

Article 28 of DORA requires a register of information covering every contractual arrangement for ICT services, including those that support no critical function. The register follows the templates in Implementing Regulation (EU) 2024/2956, and supervisors collect it every year.

A contract database is the source of the register. The register itself is a structured extract in a European format, with fields that contracts do not always hold, such as the subcontracting chain behind critical services.

Rebuilding that data every year from scattered contracts takes weeks. The more reliable approach is to record register data at contract level when each contract is signed. The annual submission then becomes an extract followed by a check.

For UK groups, this matters twice. From March 2027, the FCA and PRA expect an annual register of material third-party arrangements, and well-kept contract data feeds both submissions.

Prove who did what, and keep the evidence

A supervisor also looks at the history of your documents: who approved a policy, and when an incident report changed. Evidence that cannot be traced back to its origin carries little weight in an inspection.

Major incidents show why. Delegated Regulation (EU) 2025/301 requires an initial notification within 4 hours of classifying the incident as major, then an intermediate report within 72 hours. The final report follows no later than a month after the last intermediate report.

On that timeline, the incident file is built as events unfold, and every version needs to stay traceable. The same goes for risk assessments and test reports, which supervisors can request years later.

Doxis records the date, operation and user of every action on a document in an audit trail. Retention rules prevent deletion before the end of the retention period, and WORM-style protection ensures archived evidence can no longer be altered. You can show an inspector a document together with its full history.

What happens if you are not DORA compliant?

DORA itself sets no fine ceiling for financial entities. Article 50 requires each member state to set effective, proportionate and dissuasive administrative penalties, so the amounts depend on national law in the country where your EU entity is supervised.

Turnover-based figures quoted online come from national rules or commentary. Check the regime of the supervisor responsible for each of your EU entities.

Critical ICT third-party providers face a separate regime. Under Article 35, the lead overseer can impose periodic penalty payments of up to 1% of the provider's average daily worldwide turnover, for up to six months.

DORA compliance checklist

Use this checklist to test where your organization stands:

  • Confirm which group entities and services fall within DORA's scope in the EU
  • Map each critical or important function to the ICT services that support it
  • Document and approve your ICT risk management framework
  • Set up incident classification so that notifications can go out within 4 hours
  • Run a resilience testing program, with threat-led penetration testing where your supervisor requires it
  • Review every ICT contract against the clauses in Article 30
  • Keep the register of information in the format of Implementing Regulation (EU) 2024/2956
  • Define and document exit strategies for providers that support critical functions
  • Apply an audit trail and retention rules to all compliance evidence
  • If you operate in the UK, prepare your register of material third-party arrangements for the rules applying from March 18, 2027

Centralize the evidence behind your DORA compliance with Doxis

DORA inspections call for complete contracts and evidence with a traceable history. With Doxis, your teams find every ICT contract and its clauses in one place, and show supervisors documents whose integrity is protected.

The same platform handles compliant archiving and approval workflows. Your policies and incident reports follow the same retention and traceability rules as your contracts.

  • One electronic file per ICT contract, with amendments, SLAs and annexes
  • Renewal alerts to review clauses before each contract rolls over
  • A complete audit trail on every document
  • Retention rules that block deletion before the end of the retention period
  • WORM-style protection for archived evidence
  • Access rights and versioning for sensitive documentation

Doxis is named a Leader in the Gartner® Magic Quadrant™ for Document Management 2026. Request a free demo.

FAQs about DORA

What is DORA regulation in simple terms?

DORA is an EU regulation that requires financial firms to withstand, respond to and recover from ICT disruption. It also brings their critical technology providers under EU oversight.

What are the 5 pillars of DORA regulation?

The five pillars are ICT risk management, ICT-related incident reporting, digital operational resilience testing, ICT third-party risk management and information sharing on cyber threats.

Who does DORA regulate?

DORA regulates around twenty categories of EU financial entities, including banks and insurers. Critical ICT third-party providers are overseen directly by the European supervisory authorities.

Does DORA apply to US or UK companies?

DORA applies to US and UK groups through their EU entities, and to their technology providers through contracts with EU financial firms. US providers designated as critical are overseen directly by the European supervisors.

What happens if you are not DORA compliant?

Financial entities face administrative penalties set by each member state's national law. Critical ICT providers face periodic penalty payments of up to 1% of their average daily worldwide turnover.

How quickly must a major ICT incident be reported under DORA?

The initial notification is due within 4 hours of classifying the incident as major, and no later than 24 hours after detection. An intermediate report follows within 72 hours, then a final report.

How should DORA resilience testing be organized?

Every financial entity needs a risk-based testing program, with at least yearly tests of the systems that support critical functions. Entities identified by their supervisor also carry out threat-led penetration testing at least every three years.

Can software make a firm DORA compliant?

No single piece of software covers the whole regulation. Security tools handle detection and testing, while an ECM manages the contracts and evidence you show supervisors.

Marc Volquardsen

I am a Product Manager & Solution Architect and have been with Doxis since 2004. After 15 years as a Solution Consultant for Sales, in 2020 I switched to Product Management, where I design solutions for customers based on Doxis, SAP and Salesforce. Please feel free to contact me to talk about solutions for you!

Subscribe to Doxis News

You might also be interested in

How can we help you?

+49 (0) 30 498582-0
Please calculate 7 plus 4.

Your message has reached us!

We appreciate your interest and will get back to you shortly.

Contact us

Table of contents