Digital Operational Resilience Act (DORA) compliance for banks

Insight — 14th November 2024
Blurred image of three people seated in a meeting room, with the text 'Digital Operational Resilience Act (DORA)' prominently displayed in the center.
Share article

The Digital Operational Resilience Act (DORA) came into force on 17 January 2025. It’s a European framework that focuses on embedding a more robust and resilient approach to delivering digital capabilities for financial entities. 

Under DORA, banks and other financial institutions must continually demonstrate their ability to withstand and recover from serious information and communications technology (ICT) disruptions. That includes effective processes for internal management and testing, as well as for overseeing any third-party providers your services depend on.

The DORA framework casts a wide net, requiring you to demonstrate readiness for potential disruptions such as:

  • Cybersecurity incidents, such as ransomware or DDoS attacks, that make critical systems unavailable. 
  • Technology and infrastructure failures, such as software defects or system outages. 
  • Third-party and business continuity risks, including supplier outages or insolvency. 

One thing to keep in mind is that no single platform or provider can make your institution compliant, and outsourcing technology doesn’t outsource accountability. 

In this article, we’ll cover: 

  • The intent behind the DORA framework 
  • What are the risks of DORA non-compliance?  
  • The 5 pillars: What’s needed for ongoing DORA compliance 
  • What to consider when assessing third-party partners under DORA 
  • How ClearBank approaches DORA and operational resilience

Note: ClearBank provides accounts and payment infrastructure to regulated financial institutions across the EU and UK. To learn how we can support your banking operations, get in touch with our team.  

The intent behind the DORA framework

The European Commission proposed DORA in 2020 as part of its Digital Finance Package, with the aim of strengthening the financial sector’s resilience to ICT-related disruptions. ICT failures or cybersecurity threats can impact not only a firm and its direct customers, but also other connected financial institutions and partners across the ecosystem.

In response, DORA introduces a single, consistent supervisory approach across 21 types of financial market participants, including credit institutions, payment institutions, electronic money institutions, investment firms, and exchanges and clearing houses. It also establishes an EU oversight framework for ICT third-party providers designated as critical to the financial sector.  

What are the risks of DORA non-compliance?

Failing to meet DORA obligations can mean administrative penalties or other supervisory action from your relevant national authority. Regulators may require your firm to stop conduct that breaches DORA or take steps to address weaknesses and prevent further non-compliance.  

The exact penalties vary by Member State and the nature of the breach. In some jurisdictions, individual managers can face significant financial sanctions. In France, for example, penalties can reach up to €5 million where a senior manager’s direct and personal responsibility is established. 

Even designated critical ICT third-party providers face a separate EU oversight regime. Continued failure to comply with requests from their Lead Overseer can result in daily penalty payments of up to 1% of the provider’s average daily worldwide turnover, up to a maximum of 6 months. 

Formal penalties are only part of the risk. ICT disruption can also lead to service interruptions and remediation costs, as well as potential loss of customer trust.

The 5 pillars: What’s needed for ongoing DORA compliance

Ongoing DORA compliance for banks means building around five central provisions of the DORA framework:

  1. ICT Risk Management framework: You must guarantee an adequate level of separation and autonomy among your ICT risk management functions, control functions, and internal audit functions, based on either the IIA’s three lines of defence model or an internal risk management and control model. 
     
  2. ICT-related Incident Management, Classification & Reporting: Establishing an ICT-related incident management process and developing the necessary abilities to supervise, manage and track such incidents. Significant incidents must be reported to the appropriate competent authority. 
     
  3. Digital Operational Resilience Testing: Creating a digital operational resilience testing program including open-source analyses, vulnerability assessments, gap analyses, and network security assessments. Critical ICT systems and applications must undergo yearly testing, and certain firms must conduct advanced threat-led penetration testing at least once every three years. 
     
  4. ICT Third Party Risk Management: Implementing a strategy for managing and periodically evaluating third-party risk. This requires maintaining records of all contractual agreements with ICT third-party service providers in a dedicated Register of Information. 
     
  5. Information Sharing Arrangements: Permitting financial institutions to exchange cyber threat information and intelligence with one another, provided that the sharing of information takes place within trusted communities, bolsters the digital operational resilience of financial entities and is conducted in compliance with relevant legislation. 

DORA also requires assessments of concentration risk associated with outsourcing critical operational functions to external companies. 

What to consider when assessing third-party partners under DORA

Your firm is accountable for managing the risks associated with outsourced ICT services, including services that support critical or important functions. That means you need to assess potential partners before working together and continue reviewing them throughout the relationship. Requirements are detailed in Commission Delegated Regulation (EU) 2024/1773. 

As part of your wider DORA framework, there are several areas you may need to consider when assessing and overseeing third-party providers:

Can the provider demonstrate operational resilience?

Ask potential partners how they protect critical services against outages, cyberattacks, and technology failures. They should be able to explain their business continuity and disaster recovery arrangements, how regularly these are tested, and what happens if part of their infrastructure becomes unavailable. 

Look for concrete evidence, such as: 

  • Resilience and recovery testing processes 
  • Service availability records 
  • Recovery time and recovery point objectives 
  • Redundant systems and failover arrangements 

How will the provider manage and communicate ICT incidents?

Disruption at your provider can quickly become your incident, too. Before entering a relationship, establish how the provider detects, escalates, and resolves ICT incidents, as well as when and how it will inform you. 

Ask what information you’ll receive during an incident, including its cause, affected services, expected resolution time, and potential impact on your customers. The contract should also require the provider to cooperate with your investigations and supply the information you need to assess whether an incident meets DORA’s reporting thresholds.

How does the provider manage subcontractors and concentration risk?

Your direct provider may rely on cloud platforms, data centres, security vendors, and other subcontractors to deliver its service. This can create dependencies that aren’t immediately visible during procurement. Ask which subcontractors support the services you’ll use, where those services are delivered, and how changes to the provider’s supply chain will be communicated.  

You should also consider concentration risk, as relying too heavily on one provider or underlying technology can create a single point of failure across several critical services. Assess whether multiple critical processes depend on the same provider or on the same technology environment.

Will the contract support your DORA obligations?

DORA requires contracts for ICT services to provide financial institutions with enough visibility and control to oversee the relationship. For services supporting critical or important functions, check that the agreement covers incident cooperation, audit and access rights, subcontractors, business continuity, termination and transition support. 

Also, establish whether the provider will supply the information needed for your Register of Information. 

Can you exit the relationship without disrupting critical services?

A strong provider relationship still requires a workable exit plan. Consider how you would move the service elsewhere if the provider breached the agreement or no longer met your institution’s risk or other requirements. 

DORA requires that your financial entity have a comprehensive and well-documented exit plan, and that you can exit contracts without: 

a) disruption to their business activities, 
b) limiting compliance with regulatory requirements, 
c) detriment to the continuity and quality of services provided to clients. 

Your assessment should cover access to data, migration support, notice periods, and the time required to transfer critical services safely. 

How ClearBank approaches DORA and operational resilience

ClearBank is a fully regulated bank in Europe and the UK. ClearBank Europe is based in the Netherlands, where it’s authorised by the European Central Bank and regulated by De Nederlandsche Bank, and operates in more than 20 EU countries. 

As a regulated European bank operating, ClearBank Europe has its own responsibilities under DORA. We’ve therefore embedded DORA requirements into our approach to operational resilience, third-party risk, business continuity, and incident management. 

For our clients, this means working with a banking provider that can demonstrate how it approaches these areas as part of its own supplier assessment and oversight.  

Please note that ClearBank is only one part of that wider framework, and working with us does not automatically make an institution DORA-compliant.

DORA is embedded in our approach to operational resilience

ClearBank Europe began preparing for DORA well before the regulation started applying in January 2025. A cross-functional working group assessed the bank’s existing controls against the regulation and identified areas for improvement across the business. 

This included reviewing and documenting relevant capabilities and strengthening contractual arrangements with suppliers. ClearBank Europe also established governance processes to review changes and maintain oversight as regulatory requirements and operational risks evolve. 

That programme has now moved from initial implementation into ongoing compliance. DORA requirements form part of ClearBank Europe’s wider approach to third-party risk, including business continuity, incident management, and supplier oversight. 

Learn more about how ClearBank Europe manages operational resilience and third-party risk in our annual Pillar 3 disclosures. 

Our cloud-native infrastructure is designed to keep critical services available

ClearBank’s API delivers 99.9% uptime, while our cloud-native architecture is designed to support high-volume, real-time payment processing. For SEPA Instant, payments typically settle in two to three seconds and are processed end-to-end within the scheme’s ten-second requirement. 

Our active-active infrastructure uses multiple live systems that automatically reroute requests in real time if part of the platform experiences an outage. This helps payments continue to be processed with minimal disruption, rather than relying on a single primary system and a dormant backup. 

The API’s near-real-time webhooks also send payment status updates directly into your systems. This gives your teams faster visibility into payment statuses and exceptions. They can investigate issues sooner and communicate with customers more quickly.

Accessing the right payment rails and account structures for your use case

DORA requires financial institutions to understand and oversee the third parties supporting their ICT services. When assessing banking infrastructure, this can include understanding which providers, integrations, and payment rails sit behind the services you rely on. 

ClearBank provides regulated account infrastructure and connectivity to European and UK payment schemes through our APIs. Depending on the entity and service, this includes: 

ClearBank Europe can also support regulated institutions exploring digital settlement through our Digital Asset Rails, which use EURC to move value before settling funds back into fiat through SEPA Instant.

Building operational resilience under DORA

DORA makes operational resilience an ongoing responsibility for financial institutions, including how they assess and oversee the third parties their services depend on. 

ClearBank Europe is itself subject to DORA, and we’ve incorporated its requirements into our wider approach to operational resilience.  

Note that working with ClearBank does not make an institution DORA-compliant or replace its own controls, governance, or oversight responsibilities. What we can do is provide regulated banking infrastructure and evidence about our own resilience and controls to support clients as they assess and manage their supplier relationships. 

Looking for resilient banking infrastructure for your European operations? Get in touch with ClearBank’s team.

FAQs

DORA requires in-scope banks and other financial institutions to manage ICT risk and demonstrate their ability to withstand, respond to and recover from technology-related disruption. 

Its requirements cover areas including ICT risk management, incident management and reporting, operational resilience testing, third-party risk management and information sharing. Compliance is an ongoing responsibility for each financial institution rather than something that can be achieved through a particular technology, supplier or certification.

DORA is an EU regulation covering ICT risk and operational resilience across in-scope financial entities. The UK doesn’t have a domestic version of the Digital Operational Resilience Act. Instead, UK-regulated firms follow a separate operational resilience regime that requires them to identify important business services, set impact tolerances and prepare to remain within those tolerances during disruption. 

The UK has also introduced an oversight framework for third parties designated as critical to the financial sector. Although the UK and EU regimes cover some of the same risks, meeting the UK requirements doesn’t automatically demonstrate compliance with DORA. 

DORA doesn’t generally apply directly to financial institutions operating solely in the UK. However, a UK-headquartered group may still need to comply if it has an in-scope entity operating in the EU. 

UK technology providers may also be affected when they provide information and communication technology services to EU financial institutions. Their clients may need additional contractual information and oversight to meet their own DORA obligations, while providers designated as critical ICT third parties can fall under direct EU oversight.

No. Banks remain accountable for their DORA obligations when they outsource ICT services. A suitable provider can support compliance by supplying evidence of its controls, cooperating during incidents, and meeting the contractual requirements needed for ongoing oversight. 

This is particularly relevant when working with cloud service providers and other technology businesses that support critical or important functions. Banks still need to assess the risks these relationships introduce and monitor them throughout the contract lifecycle.

The Register of Information is a record of a financial institution’s contractual arrangements with ICT third-party providers. It helps firms and regulators understand which providers support particular functions, including critical or important services. 

Financial institutions need to keep this information current as providers, subcontractors, and contractual arrangements change, making continuous monitoring of third-party relationships an important part of the wider DORA framework.

The three European Supervisory Authorities play a central role in DORA: the EBA for banking, EIOPA for insurance and occupational pensions, and ESMA for securities and markets. Together, they develop parts of DORA’s technical framework and oversee ICT third-party providers designated as critical. 

This means DORA applies beyond banks. Its scope also covers other regulated financial entities, including insurance companies, investment firms, and payment institutions.

Geoffrey Whitehouse 1

Geoff Whitehouse

Content Lead

Further reading

CTA 2

Ready to collaborate?

Experience the ClearBank difference and begin your journey today.

Begin

Let’s stay in touch

You're subscribed!

Subscribe for our insights, news and exclusive events – straight to your inbox

Thanks for connecting with us.