DORA gets mentioned constantly in compliance conversations, and plenty of teams still aren't sure whether it actually applies to them.
What DORA actually is
DORA, the Digital Operational Resilience Act, is an EU regulation requiring financial entities, and the critical third-party ICT providers supporting them, to demonstrate genuine operational resilience against technology disruption and cyber risk. It's been in force since January 2025, and enforcement is now the phase that actually matters, not the initial compliance scramble.
The regulation exists because financial services has become deeply dependent on technology infrastructure, much of it provided by third parties, and a failure anywhere in that chain can cascade into a genuine systemic risk. DORA's answer is to require demonstrable resilience, not just a policy that exists to be shown to an auditor.
Who DORA actually covers
Directly, DORA applies to a long list of regulated financial entities operating in the EU: banks, payment institutions, e-money institutions, investment firms, insurance undertakings, and several other categories of regulated financial business.
Indirectly, but increasingly directly, it also extends to critical ICT third-party providers, cloud services, core banking infrastructure, payment processing platforms, that these regulated entities depend on. This is the part that surprises people most. If you're a BaaS provider, a payment processor, or infrastructure sitting underneath a bank or fintech, you're increasingly part of the regulatory conversation directly, not just indirectly through a client's own compliance obligations.
What DORA actually requires
Four main pillars make up DORA's requirements:
ICT risk management. A documented, genuinely operational framework for identifying, managing, and mitigating technology risk, not a policy sitting unused in a folder.
Incident reporting. Mandatory reporting of significant ICT-related incidents within defined timeframes, which requires having a process that can actually produce a compliant report quickly, while you're also dealing with the incident itself.
Resilience testing. Regular testing of ICT systems, including, for some entities, advanced threat-led penetration testing that simulates a real, sophisticated attack rather than a routine vulnerability scan.
Third-party risk management. Active oversight of technology vendors and providers, including contractual requirements and ongoing monitoring, rather than a one-time due diligence check at the start of a vendor relationship.
The test worth running on your own setup
Here's a genuinely useful diagnostic: if a critical system went down tomorrow, could your organisation produce documented evidence of your incident response process within the required reporting window, or would you be building that process from scratch under pressure.
If the honest answer involves a scramble to figure out who's responsible for what, that's a sign the documentation exists on paper but hasn't actually been operationalised, which is precisely the gap DORA enforcement is designed to catch.
What this means for evaluating infrastructure vendors
If you're a regulated entity relying on third-party infrastructure, DORA gives you a genuinely useful question to ask any vendor: can they demonstrate DORA-aligned resilience with actual evidence, documented incident response processes, recent test results, clear escalation paths, or do they simply say the word "compliant" without being able to show the underlying work.
This matters because your own DORA obligations don't disappear just because a critical function is outsourced. Regulators increasingly expect financial entities to have done genuine diligence on the resilience of the infrastructure they depend on, not just a signed contract.
Frequently asked questions
Does DORA apply to companies outside the EU? Yes, if a non-EU company provides critical ICT services to EU-regulated financial entities, DORA's third-party provider requirements can apply regardless of where that company is headquartered.
What happens if a financial entity fails to comply with DORA? Enforcement varies by member state and the specific national regulator involved, but can include significant penalties, and non-compliance also creates real reputational and counterparty risk, since DORA compliance is increasingly a factor in how financial entities evaluate potential partners.
Is DORA a one-time compliance project, or ongoing? Ongoing. Resilience testing, incident reporting readiness, and third-party oversight are meant to be continuous practices, not a single certification achieved once and then forgotten.
Be1B's infrastructure is built with DORA-aligned resilience as a core operating principle, documented incident response, regular testing, and genuine third-party risk management, not a policy written to satisfy an audit checklist.
If you're evaluating whether your current infrastructure setup genuinely meets DORA's requirements, talk to our team to talk through what that actually looks like in practice.