DORA Compliance: Supplier Evidence Guide¶
The EU Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) has been in force since January 2025. Its promise is simple to state and expensive to ignore: financial entities keep operating through ICT disruptions, and the third parties who run their technology formally share the risk. What most outside the industry underestimate is the regulation's second wave — the one that reaches companies outside the financial sector, as suppliers who serve it.
Key facts
DORA requires ICT suppliers to EU financial entities to provide verifiable resilience evidence and contractual audit rights, though regulators act on the financial entity.
- DORA applies to EU financial entities and their ICT suppliers; the financial entity keeps regulatory responsibility.
- Suppliers must provide verifiable security and incident-response evidence and contractual audit rights.
- DORA is an evergreen annual cycle; contracts and audit rights are the first checkpoint.
- Unremediated gaps typically end in supplier review or replacement.
If you sell software, hosting, infrastructure, audit support, or data services to a bank, insurer, asset manager, or payments business in the EU, you are already inside its perimeter. This guide is the supplier-side version: what DORA demands of your customers, which questions consequently end up in your inbox, and the evidence that answers them without a bespoke project per client.
The Required Asset: Supplier Resilience Evidence They Can Verify
- Asset: Published security and incident-response evidence tied to your services, and contractual support for DORA-style audit rights
- Issued by: you; the financial entity retains regulatory responsibility for your critical functions
- Deadline: continuous — DORA is evergreen annual-cycle, with contracts and audit rights the first checkpoint
- Mandatory elements: resilience controls, incident reporting support, register-of-information data, exit strategy, audit-rights clause
- Enforcement: supervisory penalties land on the financial entity, but the mechanism is contract: expect unremediated gaps to end in supplier review/replacement
- Publish yours: Publish DORA-grade supplier evidence →
The Five Pillars, Supplier-Eye View¶
DORA's architecture has five components. Each creates direct or indirect demands on suppliers:
- ICT risk management. Financial entities must run an ICT risk framework with controls, testing, and governance. Suppliers feel this as due-diligence questionnaires: control documentation, access-management policy, encryption posture, staff-training evidence.
- Incident management and reporting. Financial entities must classify and report ICT incidents to supervisors on a strict timeline. Suppliers are expected to feed the pipeline — your incident-notification SLAs and data become part of their regulatory clock.
- Digital operational resilience testing. Regular resilience testing up to threat-led penetration testing (TLPT) for larger /critical entities. Suppliers to those entities can be in scope for tests, or asked for testing evidence of their own control environment.
- Third-party risk management. The pillar that most directly restructures supplier relationships: register of information, due diligence, contractual minimums, exit strategy, and for critical providers, oversight directly against the provider.
- Framework concentration and monitoring. Regulators watch aggregated critical-provider dependency — small cloud and niche infrastructure providers can find themselves "critical" by the math of many clients using them, not by their own size.
The supplier consequence: your DORA readiness is judged through contracts, documentation, and test participation. None can be produced after the question arrives.
Register of Information: The Artifact That Reaches You¶
Every financial entity maintains a register of information about every ICT third-party arrangement: service description, criticality, locations (including data centers), subcontracting chains, contract dates, and the exit strategy. Your obligations pop out of that register's fields —
- Service inventory and version for what you provide (be specific: environments, regions, support hours)
- All subcontractors that touch the service, with a statement of their role — unexplained links are the most commonly failed field
- Physical locations of your infrastructure and support operations, including "where staff log in from"; otherwise the register field fails the audit sample
- Contract metadata — dates, renewal terms, the contract version the clause set maps to, synonyms of "master agreement" semantics
The register is annual and query-triggered, and financial entities expect consolidated, current answers rather than a new PDF per request. This is where published-evidence pages have quietly become the supplier remedy, per audits: the register field points to one link instead of re-collecting files.
Contract Minimums in Practice¶
DORA names what contracts with critical/important function providers must contain. Supplied contracts translated into a supplier checklist to pre-accept:
- Audit and inspection rights — the financial entity (and, where relevant, its supervisor) gets access rights and, for critical providers, meaningful on-site expectations
- Security and incident clauses — the control baseline, staff access constraints, incident-notification timelines aligned to your customer's regulatory clock
- Termination and transition — exit plan costs, data return and deletion, transition window and attainable artifacts
- Business and service continuity — agreed RTO/RPO commitments, testing participation, name the recovery environments
- Data locations and protection — where data is hosted and processed, transfer clauses, sub-processing consent mechanics
- Subcontracting controls — notification of changes and a right to assess critical changes
Financial entities audit clause presence before they audit the substance. A contract without the minimums gets flagged in the buyer's contract register, and the flag follows the same renewal that keeps your account — missing clauses are the cheapest supplier problem to fix and the most expensive to rediscover at each client. If you serve multiple financial clients, one contract annex template reused per client is the cheapest version of the above.
What to Present, in Order¶
The evidence stack most financial-entity reviews actually walk through:
- Governance name + ownership. Who owns information security and operational resilience at your company, and their authority. The named party is often asked to appear at the review.
- Control framework statement. What you align to — ISO 27001, SOC 2, cloud-framework attestations — with the current report attached or linked.
- Incident-management evidence. Timeline behavior: detection, escalation, client-notification commitments that metabolize into the customer's report clock.
- Testing record. Penetration tests, tabletops, disaster-recovery tests — with dates. "Annual" beats "once" and "this year" beats "scheduled".
- Subcontractors and locations. The register-ready table; subcontractor changes feed the customer's obligations.
- Resilience/exit narrative. Your plan for a handover: data formats, return windows, transition support scope.
If your answer to all six exists in one published, verifiable page, the review is short. If it is spread across stale PDFs, the review becomes a project on both sides and the buyer's alternative is a supplier at the same price with the page.
The Second-Wave Trap for Subcontractors¶
Critical-provider classification flows to subcontractors of the register, wherever they sit. Sub-software, hosting, and managed-services companies discover their status only when the sensitivity audit arrives. The trap has a familiar signature: the question "who else touches this service" with a truthful answer the register supports. Companies that never had a compliance function navigate this by documenting a tiered subcontractor table before the bi-directional audit; firms that waited for the first bank client's audit team to discover the data trail drift into a mid-negotiation position of weakness.
DORA vs. NIS2 for Suppliers¶
Both regimes demand similar artifacts from technology suppliers to EU-critical sectors, but they route through different customers:
- DORA regulates the financial entity; the supplier's burden arrives through contracts, the register, and oversight of critical providers
- NIS2 regulates essential and important entities across 18 sectors, including suppliers' own customers, and creates direct duties on some suppliers who themselves fall into scope as entities
If your company serves finance clients from an EU entity, the answer is usually both: your own posture as an entity (NIS2 side) and your supplier posture toward clients (DORA side). One published evidence page serves both reviews; two staggered questionnaires are the old path.
Frequently Asked Questions¶
Am I DORA's risk by serving banks as an email/hosting vendor?
The obligated party under DORA is the financial entity, not you. You are inside it through third-party risk requirements: contractual minimums, register-of-information data, and audit rights. Non-EU small providers reach into the regime through critical-service subcontracting chains in most cases.Do I need ISO 27001 to answer DORA supplier questions?
Not required by the regulation, but widely expected in practice as the control-framework anchor. The alternative is control documentation of equivalent substance, which costs more to maintain than the certificate's audit cycle.What are the register of information fields I should prepare?
Service description, criticality, contract metadata, subcontractor chain with roles, data and infrastructure locations, staff locations, incident-contact details, and a pointer to your exit plan. Maintain it once per service; update on change rather than on request.How do TLPT exercises involve suppliers?
Threat-led penetration tests for larger financial entities may include your service in scenarios, and you may be asked to support remediation. Contractually, agree the scope of participation early; surprise participation requests during a TLPT are a common friction source.Related Guides¶
- NIS2 Compliance Software: Automate Cybersecurity — the sibling regime and whose entities it binds directly.
- Cybersecurity for Hardware & IoT SMEs: NIS2 & CRA — where product security (CRA) and enterprise rules meet.
- SOC 2 Type II Report Software — the attestation that most often anchors the control-framework answer.
- The DPA: The Document That Unblocks Deals — the data-protection side of the same contract family.
Last updated: November 9, 2026
Global Digital Trust & Compliance
Sustalium is the digital-first platform for managing complex business certificates and sustainability declarations across global supply chains.
- Digital Product Passport (DPP)
- Carbon & Water Footprint
- Circularity & Reuse (ISO 14021)
- De-Forestation Free
- FSMA 204 (FDA Traceability)
- REACH & RoHS Compliance
- PFAS-Free & VOC Declarations
- Prop 65 & TSCA Title VI
- ISO 26000 Responsibility
- Modern Slavery Statements
- UFLPA Forced Labor Traceability
- Ethical Labor Declarations
- Swiss Made & Origin Claims
- GDPR & AI Ethics (EU AI Act)
- CE Marking & UKCA Conformity
- Bill S-211 (Canada) Reporting
Have questions about a specific standard?
Contact our compliance team at compliance@sustalium.com