← Back to Insights
November 18, 2026 · 5 min read · DORA Supplier
DORA Third-Party Risk: What Suppliers Must Prove
DORA makes financial entities responsible for their ICT suppliers. If you're one of those suppliers — cloud, software, data, managed services — DORA reaches you through your clients' contracts. Here's what you must prove, and why "we have ISO 27001" won't be enough.
What DORA requires from financial entities
DORA's Article 28 requires financial entities to manage third-party risk across five pillars:
- ICT risk management — assess the risk of each supplier
- Incident reporting — suppliers must notify the financial entity of incidents within specific timeframes
- Digital operational resilience testing — suppliers must support the entity's testing programme
- Third-party information — the entity must maintain a register of all ICT suppliers
- Concentration risk — the entity must assess dependency on single suppliers
What this means for suppliers in practice
If you provide ICT services to a bank, insurer, or investment firm, you'll be asked for:
- Tested security controls — not "we have security" but "here's the test that proves it works"
- Incident notification within hours — if you're breached, you must tell the financial client fast. Not "when we investigate." Not "within a reasonable timeframe." Hours.
- Resilience testing support — you may need to participate in the client's recovery testing, chaos exercises, or threat-led testing
- Supply chain transparency — the client may need to know who your suppliers are, where your data goes, and what dependencies you have
- Contract terms aligned to DORA — specific security obligations, not generic "maintain appropriate security"
DORA doesn't regulate you directly. It regulates your client, who must regulate you. But the effect is the same: you need DORA-level evidence. If you can't provide it, the client can't use you — or faces fines for using a non-compliant supplier.
The liability chain
If a financial entity gets breached through a supplier's compromise:
- The regulator fines the financial entity (management liability under DORA)
- The financial entity pursues the supplier for breach of contract (they pushed DORA terms down)
- The supplier faces contractual claims if they couldn't prove their security worked
The fine stays with the financial entity. But the contractual liability can reach the supplier — and it can be significant.
How to protect yourself as a supplier
- Prepare DORA-aligned evidence now — test results, detection verification, incident response times, resilience testing participation. Before the client asks.
- Review your contracts — check what you've already agreed to. If a financial client hasn't asked for DORA terms yet, they will.
- Map your own supply chain — DORA expects financial entities to know their suppliers' suppliers. If you can't show your own supply chain, you're a gap in their register.
- Test your notification process — can you detect and notify a client within the timeframe DORA expects? If not, fix the gap before a real incident tests it.
DORA's third-party requirements are already in force. Financial companies are assessing their suppliers now. Being ready with DORA-level evidence before they ask is the difference between keeping the contract and losing it.
Questions about DORA supplier requirements?
Get in touch. 15-minute call, no obligation.
Get in touch
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.