← Back to Insights
November 18, 2026 · 4 min read · DORA Scope
DORA for Non-Financial Companies: Does It Affect You?
DORA (Digital Operational Resilience Act) is financial-sector regulation. If you're not a bank, insurer, or investment firm, you're not directly in scope. But if you provide services to financial entities — cloud, IT, software, data, payment infrastructure — DORA can reach you through your clients' obligations. Here's how.
Who DORA directly applies to
DORA applies to approximately 22,000 EU financial entities:
- Banks and credit institutions
- Insurance and reinsurance companies
- Investment firms and fund managers
- Payment institutions and crypto-asset service providers
- Trading venues and central securities depositories
If you're one of these, DORA is your regulation. You must comply directly — ICT risk management, incident reporting, resilience testing, Register of Information, third-party risk management.
How DORA reaches non-financial companies
DORA requires financial entities to manage their third-party risk. That means the institutions above must assess and oversee the ICT services they buy from external providers. If you're a provider of those services, DORA's requirements flow down to you through your clients' contracts.
Specifically, if you provide:
- Cloud services to a bank — the bank must include DORA security requirements in your contract
- Software or platforms to an insurer — the insurer must verify your resilience under DORA
- Data processing or analytics to an investment firm — the firm must assess your ICT risk controls
- IT infrastructure or managed services to any financial entity — you're in DORA's third-party scope
What this means in practice
Financial clients will start asking you for things you haven't been asked for before:
- Evidence of your ICT risk management — not just "we have security" but tested controls
- Evidence of your incident detection and response capability — detection times, containment procedures
- Evidence of your resilience testing — recovery tests, penetration tests, chaos exercises
- Security in your contract — specific DORA-aligned terms, not generic "supplier shall maintain security"
- Notification of incidents — if you're breached, you must tell the financial client within hours, not "when we get around to it"
You're not regulated by DORA — but your financial clients are, and they must push DORA requirements down to you. The practical effect is the same: you need DORA-level evidence, even though DORA doesn't directly apply to you.
What to do about it
If you serve financial entities as an ICT provider:
- Audit your current security against DORA's five pillars. Where are the gaps between what you have and what DORA expects?
- Prepare the evidence DORA clients will ask for. Test results, detection verification, resilience testing — not just policies.
- Update your contracts. If financial clients haven't asked for DORA terms yet, they will. Have DORA-aligned security terms ready.
- Test your incident notification process. Can you detect, and notify a client, within the timeframe DORA expects? If not, fix the gap.
DORA's third-party requirements are already in force. The financial companies you serve are assessing their suppliers now. Being ready with DORA-level evidence before they ask is cheaper than scrambling after they do.
Questions about DORA and third-party risk?
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.