Digital Operational Resilience Act (DORA): 8 Actions for MSPs 

DORA

Very few MSPs got into managed services to become experts in financial regulation. Yet if a bank, insurer, payment firm, asset manager, or crypto platform appears anywhere on your client list—or on your clients’ client lists—the EU’s Digital Operational Resilience Act (DORA) is already shaping your contracts, your incident runbooks, and your sales conversations. Your company name doesn’t need to appear in the regulation for its requirements to land on your desk.

DORA has now been live for almost two years, the first wave of supervisory designations is done, and the contractual knock-on effects are flowing down the supply chain. Here’s what it means for MSPs in Europe, and for the many outside it who serve European financial clients.

The DORA Explorer: Regulation at a glance

DORA (Regulation (EU) 2022/2554) entered into force in January 2023 and has applied since January 17, 2025. Its main job is harmonization. Before DORA, a bank in Frankfurt and an insurer in Dublin followed different national rules and guidelines for ICT security and outsourcing. DORA replaces that patchwork with one framework covering 21 different types of financial entities, from credit institutions and investment firms to payment institutions, insurers, and crypto-asset service providers.

The regulation rests on five pillars:

1.     ICT risk management—governance, asset mapping, monitoring, backup, business continuity, and recovery

2.     ICT third-party risk management—due diligence, a register of all ICT contracts, mandatory contract clauses, concentration risk, and exit strategies

3.     Digital operational resilience testing—from vulnerability scanning up to threat-led penetration testing for the largest firms

4.     ICT-related incident management and reporting—classification of incidents and tightly timed reports to supervisors

5.     Information sharing—voluntary exchange of threat intelligence between financial entities

Pillar two is where MSPs come in.

Why DORA lands on the MSP’s desk

DORA’s core principle is that a financial entity can outsource a service but never its responsibility for it. To stay compliant, regulated firms have to push DORA’s standards down to every ICT provider they use—and MSPs sit squarely in that category.

The mechanism is the contract. Article 30 sets out clauses that must appear in every agreement with an ICT provider, including a clear description of services, data processing locations, service levels, incident assistance, cooperation with supervisors, and termination rights with minimum notice periods.

Where your service supports what the client classifies as a “critical or important function,” the bar rises a lot higher. We hope you’re ready for:

•      Full service-level descriptions with quantitative and qualitative performance targets

•      Unrestricted rights of access, inspection, and audit for the client, its appointed auditors, and its regulator

•      Participation in the client’s resilience testing, including threat-led penetration testing where it applies

•      Business continuity plans and security measures that you also test

•      Exit support with a defined transition period, so the client can move to another provider or bring the service in-house

That last point connects to Article 28, which requires financial entities to hold documented exit strategies for every ICT arrangement supporting a critical or important function. In practice, that means data portability, documentation, and handover plans become something your clients will ask to see—not something you can improvise at the end of a contract.

It’s also worth noting that not being on any regulator’s list doesn’t buy smaller providers an easier ride. As TLT points out, non-designated vendors should still expect to meet DORA’s contractual standards, and financial firms shouldn’t assume specialist or smaller suppliers face lighter requirements.

Your subcontractors are now your client’s business

DORA’s reach doesn’t stop at your front door. Financial entities must maintain a Register of Information covering every ICT contract, and supervisors collect these registers annually. Each provider has to be identified by a standardized code: the Central Bank of Ireland confirms that ICT providers listed in a register need a valid LEI or EUID for the submission to pass validation. Where a service underpins a critical or important function, subcontractors further down the chain must be identified too.

Then there’s subcontracting itself. After a long delay, the Commission’s regulatory technical standards on subcontracting—Delegated Regulation (EU) 2025/532—entered into force on July 22, 2025. They spell out what a financial entity must assess before allowing an ICT provider to subcontract services that support critical or important functions.

For a typical MSP stack, that’s a lot of moving parts. Hyperscaler infrastructure, RMM and PSA platforms, backup vendors, security tooling, an outsourced NOC or SOC, a white-label helpdesk—any of these can show up in your client’s supply-chain map. If you can’t say clearly who does what, where, and under which contract, expect pointed questions delivered in a sharp tone at renewal time.

Four hours on the clock

Incident reporting is where DORA gets most operational. Once a financial entity classifies an ICT incident as major, it has to file an initial notification within four hours of classification—and no later than 24 hours after becoming aware of it. An intermediate report follows within 72 hours of the initial notification, and a final report with root cause analysis within a month after that.

The client can’t classify an incident it doesn’t know about. If the outage, ransomware event, or misconfiguration starts in your environment, your notification is what starts their clock. So DORA-aligned contracts increasingly specify how quickly the MSP must alert the client, what information goes with that alert, and how you’ll support the follow-up reports. MSPs with mature incident response, clear escalation paths, and good forensic logging are in a much stronger position than those still running on goodwill and a shared inbox.

The critical 19—and what the list tells MSPs

On November 18, 2025, the European Supervisory Authorities published the first list of designated critical ICT third-party providers (CTPPs). The 19 names are directly overseen at EU level.

The hyperscalers were expected—Amazon Web Services, Google Cloud, Microsoft, and Oracle all feature. More revealing for the MSP GLOBAL  audience is who else made the cut. Accenture, Capgemini, IBM, Kyndryl, NTT DATA, and Tata Consultancy Services are, at heart, the largest managed and IT services businesses on the planet. Alongside them sit colocation operators Equinix and InterXion, telcos Deutsche Telekom, Orange, and Colt, and specialist players such as SAP, Bloomberg, FIS, and LSEG Data and Risk.

In other words, the regulators view managed services at scale as systemic infrastructure for European finance. Designated providers face inspections and recommendations from a Lead Overseer, and failure to comply with oversight measures can trigger periodic penalty payments of up to 1% of average daily worldwide turnover, for up to six months. The list is reviewed annually, so it may grow.

For the vast majority of MSPs, designation isn’t a realistic prospect. The bigger story is concentration risk. DORA requires financial entities to assess their dependence on single providers and to have credible alternatives. A sector that leans heavily on a handful of global platforms now has a regulatory reason to diversify—and that opens doors for MSPs offering multi-cloud architectures, exit-ready designs, and European-jurisdiction hosting. Combine that with the EU’s wider sovereignty push (see CloudFest’s take on the Cloud and AI Development Act), and resilience starts to look like a growth market rather than a compliance cost.

Beyond the EU: the UK and the rest of the world

DORA follows the client, not the provider’s postcode. An MSP in the UK, the US, Switzerland, or India serving an EU-regulated financial entity will face the same contractual demands as one in Madrid or Munich.

The UK is also running its own version. Its critical third parties regime, created by the Financial Services and Markets Act 2023, came into force on January 1, 2025; and in July 2026 HM Treasury made the first designations: AWS, Google Cloud, Microsoft, and Oracle, now jointly overseen by the Bank of England, the PRA, and the FCA. The timing wasn’t accidental—a major Cloud outage in October 2025 had already shown how many financial firms depend on a small number of providers.

The UK list is narrower than the EU’s, and UK-regulated firms remain responsible for their own outsourcing risk under existing PRA and FCA rules. For MSPs with clients on both sides of the Channel, this means two regimes with closely aligned aims, and a strong case for building one resilience framework that satisfies both.

DORA, NIS2, and the wider compliance stack

Many European MSPs are tackling DORA at the same time as NIS2, which names managed service providers and managed security service providers as an in-scope sector in their own right. Ireland’s NCSC, for example, lists MSPs and MSSPs among essential and important entities depending on size.

The two frameworks hit MSPs from different directions. NIS2 regulates the MSP directly as an entity; DORA mostly arrives through financial clients’ contracts. For financial entities themselves, DORA operates as the sector-specific rulebook that takes precedence over NIS2’s equivalent obligations. The good news is that the controls overlap heavily—risk management, incident handling, supply-chain security, and testing—so a well-built program can serve both.

Some relief may be on the way for reporting. The Commission’s Digital Omnibus proposal, published in November 2025, includes a single EU entry point for incident notifications across NIS2, GDPR, DORA, and other regimes, built around a “report once, share often” model. It’s still working its way through the legislative process, so don’t retire any runbooks yet.

What MSPs should be doing now

If you serve financial clients—or want to—these are the practical steps worth prioritizing:

•      Map your exposure. Identify every client that’s a DORA financial entity, including indirect relationships where you’re a subcontractor to another provider.

•      Find out which services clients classify as critical or important. That classification decides which tier of contract terms applies.

•      Build a DORA-ready contract schedule. Having your own pre-prepared Article 30 addendum makes procurement faster and puts you in control of the conversation.

•      Get an LEI. It’s quick and inexpensive, and it removes friction from your clients’ register submissions.

•      Document your subcontracting chain. Know which vendors touch which services, in which locations, and under what terms.

•      Align incident response to the four-hour window. Agree notification timelines, contact points, and the information you’ll provide.

•      Prepare for scrutiny. Audit requests, resilience testing participation, and exit plans are becoming standard demands. Have the evidence ready.

•      Sell resilience. Clients are looking for partners who make DORA easier. Position your services accordingly.

Cover these DORA basics and you can turn to your team and say “We did it! We did it! ¡Lo hicimos! Yaaay!” Your next adventure, of course, is to stay on top of all of this and keep your eyes open for changes and new regulations. Good thing you have the MSP GLOBAL community to help you.

DORA Q&A

Does DORA apply directly to MSPs? DORA’s obligations sit primarily with financial entities, but they must flow DORA requirements down to their ICT providers through mandatory contract clauses. MSPs serving financial clients are therefore affected indirectly through contracts, while only designated critical providers face direct EU oversight.

My MSP is based outside the EU. Does DORA still affect me? Yes, if you provide ICT services to EU-regulated financial entities. DORA follows the client, so non-EU MSPs face the same contractual requirements. UK providers should also track the UK’s own critical third parties regime.

What contract terms will financial clients ask for? All ICT contracts need DORA’s baseline clauses, such as service descriptions, data locations, service levels, incident assistance, and termination rights. For services supporting critical or important functions, expect audit and access rights, quantitative performance targets, participation in resilience testing, business continuity commitments, and exit support.

What is a CTPP, and could my MSP become one? A critical ICT third-party provider (CTPP) is designated by the European Supervisory Authorities based on its systemic importance to EU finance. The first 19, named in November 2025, include hyperscalers and large IT services groups. Designation is unlikely for most MSPs, but the list is reviewed annually.

How quickly do incidents need to be reported under DORA? Financial entities must send an initial notification within four hours of classifying an incident as major, and no later than 24 hours after becoming aware of it, followed by an intermediate report within 72 hours and a final report within a month. MSPs need to alert clients fast enough for them to meet those deadlines.

How does DORA relate to NIS2? NIS2 regulates MSPs and MSSPs directly as in-scope entities, while DORA reaches MSPs mainly through financial clients. The controls overlap significantly, so many MSPs build a single program that addresses both

Regulation is reshaping how MSPs win and serve financial services clients. Get the insights, the peer conversations, and the partnerships to turn compliance into growth at MSP GLOBAL 2027, October 20–21 at PortAventura theme park in Spain. Register now.

Miles Kendall Avatar

This might also interest you