DORA, the Digital Operational Resilience Act, is Regulation (EU) 2022/2554 — an EU regulation that requires banks, insurers, investment firms and a long list of other financial entities to manage information and communication technology (ICT) risk to one harmonized standard, instead of the patchwork of national rules that existed before it. ESMA's own DORA page states the regulation entered into force on 16 January 2023 and has applied since 17 January 2025. Because it is a Regulation rather than a Directive, DORA takes direct effect in every EU member state without needing separate national transposition laws.
Key takeaways
- Yes, when the vendor supplies an ongoing ICT service to a financial entity, and DORA's definition says so explicitly.
- Article 30 lists the minimum content of every ICT services contract, and a longer list when the service supports a critical or important function.
- Delegated Regulation (EU) 2024/1774, Article 10, sets out the financial entity's vulnerability and patch management procedures, and several points reach straight into the supply chain.
- The reporting duty sits with the financial entity under Article 19, but the clock it runs on shapes what it needs from you.
Who it covers
ESMA's page describes DORA's scope as "more than 20 different types of financial entities," noting that 12 of those entity types fall directly under ESMA's own supervisory remit; EIOPA's page similarly describes coverage of "20 different types of financial entities and ICT third-party service providers." The European Parliament's legislative file summary for the proposal (2020/0266(COD)) describes the practical reach as "almost all financial entities," while flagging specific carve-outs: micro, small or medium-sized insurance intermediaries are excluded from the outset, and auditors are not currently in scope but were noted as candidates for inclusion in a future review. Critically, DORA's third-party provisions reach beyond financial entities themselves to their ICT third-party service providers — including the ones designated "critical," which fall under a dedicated EU-level oversight framework.
The six requirement areas
ESMA and EIOPA's own pages describe the same six pillars:
| Area | What it covers |
|---|---|
| ICT risk management | Governance and a risk-management framework for ICT-related risk |
| ICT third-party risk management | Contractual safeguards and ongoing monitoring of external ICT providers |
| Digital operational resilience testing | Regular testing, including advanced testing for some entities |
| ICT-related incident reporting | Notifying competent authorities of major ICT incidents on set timelines |
| Information and threat-intelligence sharing | Voluntary exchange of cyber threat information across the sector |
| Oversight of critical ICT providers | A dedicated EU-level framework for providers designated as "critical" to the sector |
Does DORA reach a hardware or firmware vendor?
Yes, when the vendor supplies an ongoing ICT service to a financial entity, and DORA's definition says so explicitly. Article 3, point (21), of Regulation (EU) 2022/2554 defines "ICT services" as "digital and data services provided through ICT systems to one or more internal or external users on an ongoing basis, including hardware as a service and hardware services which includes the provision of technical support via software or firmware updates by the hardware provider." Point (19) makes any undertaking providing ICT services an "ICT third-party service provider." A maker of payment terminals, branch network appliances or HSM-style devices that ships firmware updates under a support contract is therefore in the chain.
DORA places its obligations on the financial entity, not the vendor: under Article 28(1)(a), the entity "remain[s] fully responsible" for compliance even when it outsources. The vendor meets DORA through the contract and through the evidence the customer's due diligence requests. The weight of those requests depends on whether the service supports a "critical or important function" (Article 3(22)): a function whose disruption would materially impair the entity's financial performance, the soundness or continuity of its services, or its compliance with its authorisation.
Which contract clauses will a financial-entity customer ask for?
Article 30 lists the minimum content of every ICT services contract, and a longer list when the service supports a critical or important function. The left column paraphrases the Regulation; the right column is what a device or software supplier typically has to produce.
| Article 30 clause | What the supplier provides |
|---|---|
| 30(2)(a) Full description of functions and services; whether subcontracting is allowed and on what terms | Service description; list of subcontractors (cloud hosting, contract manufacturer, update CDN) |
| 30(2)(b) Locations where services are provided and data is processed, with advance notice of changes | Hosting regions, support locations, a change-notice process |
| 30(2)(c)-(d) Data availability, authenticity, integrity, confidentiality; access, recovery and return of data on exit or insolvency | Data-handling description; export format; deletion procedure |
| 30(2)(e) Service level descriptions | Support and patch SLAs |
| 30(2)(f) Assistance in an ICT incident related to the service, at no extra cost or a cost set in advance | Incident contact, response times, a price agreed up front |
| 30(2)(g) Full cooperation with competent and resolution authorities | Contract acceptance |
| 30(2)(h)-(i) Termination rights and notice periods; participation in the entity's security awareness programmes | Contract acceptance; training participation |
| 30(3)(a)-(b) Critical or important functions: precise quantitative service levels; notice of developments that could affect delivery | Measurable SLAs; early-warning commitment |
| 30(3)(c) Business contingency plans and appropriate ICT security measures, tools and policies | BCP test evidence; secure development and vulnerability handling records |
| 30(3)(d) Participation in the entity's threat-led penetration testing (TLPT) | Willingness and a contact for test windows |
| 30(3)(e) Unrestricted access, inspection and audit rights for the entity, its appointees and the competent authority | Audit-ready documentation; on-site access terms |
| 30(3)(f) Exit strategy with a mandatory transition period | Transition and migration support terms |
Before signing, Article 28(4) requires the entity to run due diligence and check that the provider is suitable. Delegated Regulation (EU) 2024/1773, Article 6, lets the entity's policy rely on its own audits, independent audit reports, the provider's internal audit reports, "appropriate third-party certifications" or other information the provider supplies. That is where security documentation from the supplier is used.
What do the technical standards ask about vulnerabilities and third-party code?
Delegated Regulation (EU) 2024/1774, Article 10, sets out the financial entity's vulnerability and patch management procedures, and several points reach straight into the supply chain. The procedures must:
- verify whether ICT third-party service providers handle vulnerabilities related to the services they provide, and whether they report "at least the critical vulnerabilities and statistics and trends in a timely manner";
- track the usage of "third-party libraries, including open-source libraries, used by ICT services supporting critical or important functions", and monitor their versions and updates, "where appropriate in collaboration with the ICT third-party service provider";
- run automated vulnerability scanning on ICT assets supporting critical or important functions "on at least a weekly basis";
- set deadlines for installing software and hardware patches, with escalation if a deadline is missed.
The same article requires the entity to ask providers to investigate relevant vulnerabilities, find root causes and implement mitigations. In practice a supplier that can hand over a component list (an SBOM), state which known CVEs affect each release, and show a working disclosure process answers most of these questions. Our guides to firmware SBOMs and setting up a PSIRT cover both.
How fast must a major ICT incident be reported, and what does that mean for suppliers?
The reporting duty sits with the financial entity under Article 19, but the clock it runs on shapes what it needs from you. Delegated Regulation (EU) 2025/301, Article 5, sets these limits:
| Report | Time limit |
|---|---|
| Initial notification | Within 4 hours of classifying the incident as major, and no later than 24 hours after becoming aware of it |
| Intermediate report | Within 72 hours of the initial notification |
| Final report | No later than one month after the latest intermediate report |
If an incident starts in a supplied device or service, the customer needs facts from the supplier within hours, not days. Article 30(2)(f) already requires incident assistance in the contract; a named contact, a severity scheme and a first-response time in the SLA make that clause usable.
How is DORA's detail still being filled in?
DORA's base text sets the framework; the European Supervisory Authorities (EBA, EIOPA and ESMA, acting jointly) and the European Commission have continued adopting Regulatory and Implementing Technical Standards (RTS/ITS) on top of it well past the January 2025 application date. The Commission's own finance page lists, among others:
| Delegated regulation | Date | Subject |
|---|---|---|
| (EU) 2025/301 | 20 February 2025 | RTS specifying content and time limits for ICT incident notifications and major-incident reports |
| (EU) 2025/420 | 24 March 2025 | RTS on joint examination team composition, designation, tasks and procedures |
| (EU) 2025/532 | 2 July 2025 | RTS on elements for assessing ICT service subcontracting that supports critical or important functions |
| (EU) 2024/1774 | 13 March 2024 (adoption) | RTS on ICT risk management tools, methods, processes and policies, and the simplified framework |
| (EU) 2024/1773 | 13 March 2024 (adoption) | RTS on the policy for contracts covering ICT services that support critical or important functions |
| (EU) 2024/2956 (implementing) | 29 November 2024 (adoption) | ITS with standard templates for the register of information (Article 28(3) and (9)) |
The first three rows in this table give the Official Journal publication dates the Commission's page lists; the last three give the adoption dates from the Commission's full list of DORA Level 2 measures. The register of information matters to suppliers. Under Article 28(3), every financial entity keeps a register of all its ICT service contracts and makes it available to its competent authority on request, so customers will ask vendors for the legal-entity and service details needed to fill it in.
A financial entity — or a vendor supplying one — should treat the base Regulation as the floor and expect this secondary-legislation layer to keep moving; the Commission's page is the live index of what has been adopted, rejected or amended.
Legislative path
DORA began as Commission proposal 2020/0266(COD); the European Parliament's legislative file records that Parliament adopted its position at first reading on 10 November 2022, with a vote of 556 in favor, 18 against and 38 abstentions. That first-reading agreement became the Regulation that entered into force two months later, on 16 January 2023, ahead of the 17 January 2025 application date noted above.
Where DORA sits next to NIS2
DORA is financial-sector-specific, while the NIS2 Directive sets cross-sector baseline cybersecurity and incident-reporting obligations for a much wider range of "essential" and "important" entities across the EU. Both regimes cover ICT/cyber incident reporting. DORA's recital 16 states that the Regulation "constitutes lex specialis with regard to Directive (EU) 2022/2555", the NIS2 Directive, because its ICT risk and incident reporting requirements for financial entities are more detailed. Where a financial entity is also an essential or important entity under NIS2, the national transposition law decides how the two interact, so the national text is the place to check.
Worked example: a payment-terminal maker's evidence pack
Synthetic example. The company and product are invented to show the flow; they describe no real vendor or contract.
Classify the relationshipA maker of card-payment terminals sells to an EU bank and pushes signed firmware updates under a support contract. Under Article 3(21) that is an ICT service. The bank tells the vendor that card acceptance is a critical or important function, so Article 30(3) applies in full. Answer the register questionsThe vendor sends its legal-entity details, the service description, the countries where support and the update server operate, and its subcontractors (cloud host, contract manufacturer). Assemble due-diligence evidenceFor the Delegated Regulation 2024/1773 assessment it supplies its secure development policy, its latest independent audit report and its vulnerability disclosure policy. Prove component trackingFor each firmware release it provides an SBOM and a list of matched CVEs with fix status, which answers the bank's third-party library question under RTS 2024/1774 Article 10. A free browser tool such as SoftWSP's SBOM viewer lets the bank's team open a CycloneDX file without installing anything. Set incident termsThe contract names a 24/7 contact, a one-hour first response for incidents affecting transactions, and an incident-assistance rate agreed in advance (Article 30(2)(f)). Agree audit and exit termsOn-site audit rights for the bank and its supervisor, participation in TLPT, and a transition period with continued updates if the contract ends.
What are the common pitfalls?
- "DORA doesn't apply to us, we sell hardware." The Article 3(21) definition names hardware services with firmware updates; the contract will carry DORA clauses anyway.
- Undisclosed subcontractors. Delegated Regulation (EU) 2025/532, Article 3, makes the entity check that the provider can identify all subcontractors supporting a critical or important function and pass on the same access and inspection rights.
- SLAs without numbers. Article 30(3)(a) asks for precise quantitative and qualitative performance targets; "best effort" patching will not pass.
- No vulnerability reporting channel to customers. RTS 2024/1774 asks entities to check that providers report critical vulnerabilities in a timely manner.
- A one-off security questionnaire. Article 28 expects ongoing monitoring, so evidence must be refreshed per release, not once at onboarding.
A workable starting point
Confirm which of the 20+ entity types you fall into, since obligations and the "simplified" regime for smaller entities differ by category — ESMA and EIOPA's own pages are a faster first check than the Regulation's full text. Inventory your ICT third-party providers now, including which ones would plausibly be "critical" — the oversight framework and the subcontracting RTS (2025/532) both hinge on that classification. Track the RTS/ITS pipeline, not just the base Regulation — the Commission's finance page shows the technical standards are still being adopted, amended and occasionally rejected well after the January 2025 application date. If you sell ICT services or devices into EU financial entities, expect their DORA third-party due-diligence to ask for documentation (security processes, incident handling, subcontracting chain) you may not have had to produce for other customers.
SoftWSP can help an ICT/device vendor put together the security documentation a DORA-covered financial-entity customer's third-party risk process will ask for: see device and firmware security services.
Where AI fits into DORA third-party documentation
Much of what a DORA-covered financial entity's third-party risk process asks for — incident history, vulnerability handling evidence, subcontracting chain detail — starts from the same deterministic firmware or software scan SoftWSP runs for any device or ICT component: a CycloneDX 1.6 SBOM extracted from the image, CVEs matched against NVD and CISA CSAF ICS advisories, and KEV/EPSS status. AI drafts the narrative sections of that documentation — summarizing which matched vulnerabilities were fixed and when, and which open findings a financial-entity customer's risk team would flag — from the scan's own evidence, not from a general-purpose judgment about ICT risk. It does not assess DORA's six requirement areas itself or draft incident notifications; those stay a compliance and engineering task, with an engineer reviewing every AI-drafted summary before it reaches a customer.
This guide summarises public ESMA, EIOPA and European Commission pages describing Regulation (EU) 2022/2554; it does not constitute legal or compliance advice.
Put this guide to work
Frequently asked questions
What is DORA?
The Digital Operational Resilience Act, formally Regulation (EU) 2022/2554, an EU regulation requiring financial entities to manage information and communication technology (ICT) risk to a harmonized standard across the sector. ESMA's own DORA page states it entered into force on 16 January 2023 and has applied since 17 January 2025; as a Regulation rather than a Directive it applies directly in all EU member states without national transposition.
Who does DORA apply to?
ESMA's page states DORA covers "more than 20 different types of financial entities" (with ESMA itself holding direct remit over 12 of them), and EIOPA's page similarly describes coverage of "20 different types of financial entities and ICT third-party service providers." The European Parliament's legislative file summary describes the scope as reaching "almost all financial entities," while noting exclusions such as micro, small or medium-sized insurance intermediaries and (for now) auditors.
What are DORA's main requirement areas?
ESMA and EIOPA's pages describe the same six areas: ICT risk management (governance and a risk-management framework), ICT third-party risk management (contractual safeguards with providers), digital operational resilience testing (including advanced testing for some entities), ICT-related incident reporting to authorities, information- and threat-intelligence sharing across the sector, and an oversight framework for ICT providers designated as "critical."
How is DORA's detail being filled in after 2025?
Through delegated and implementing acts the Commission adopts under powers DORA grants it, developed jointly by the European Supervisory Authorities (EBA, EIOPA and ESMA). The European Commission's own finance page lists, among others, Delegated Regulation (EU) 2025/301 (20 February 2025, RTS on content and timing of ICT incident notifications), Delegated Regulation (EU) 2025/420 (24 March 2025, RTS on joint examination teams), and Delegated Regulation (EU) 2025/532 (2 July 2025, RTS on assessing ICT subcontracting for critical or important functions) — each adding detail the base Regulation leaves to secondary legislation.
Sources
- ESMA: Digital Operational Resilience Act (DORA)
- EIOPA: Digital Operational Resilience Act (DORA)
- European Commission (Finance): Digital Operational Resilience Regulation — implementing and delegated acts
- European Parliament Legislative Observatory: 2020/0266(COD) — Digital Operational Resilience Act
- Regulation (EU) 2022/2554 (DORA), full text, EUR-Lex
- Commission Delegated Regulation (EU) 2024/1774, RTS on ICT risk management tools, methods, processes and policies (Article 10, vulnerability and patch management), EUR-Lex
- Commission Delegated Regulation (EU) 2024/1773, RTS on the policy for contractual arrangements on ICT services supporting critical or important functions (Article 6, due diligence), EUR-Lex
- Commission Implementing Regulation (EU) 2024/2956, ITS on standard templates for the register of information, EUR-Lex
- Commission Delegated Regulation (EU) 2025/301, RTS on content and time limits for major ICT-related incident notifications and reports (Article 5), EUR-Lex
- Commission Delegated Regulation (EU) 2025/532, RTS on subcontracting ICT services supporting critical or important functions (Article 3), EUR-Lex
About this guide
SoftWSP Regulation Desk
Covers the Medical & regulated devices cluster: 30 guides.

In this cluster
Questions about this page?
