Back to Guides
Guide18 September 2026

What does DORA stand for and why does it matter?

Decloak is an AI-powered web security intelligence platform that scans a site's HTTP/TLS posture, JavaScript, and third-party scripts to produce a report anyone can read. This guide is part of Decloak's library of practical, source-backed security guidance.

In this guide
  1. Key takeaways
  2. What does DORA actually stand for?
  3. Why does it matter, in practical terms?
  4. Who has to comply?
  5. Where do I go for the details?
  6. If you're looking for a different DORA

Key takeaways

What does DORA actually stand for?

Digital Operational Resilience Act. It's the EU's answer to a gap regulators identified after years of financial-sector cybersecurity rules that focused on capital requirements rather than the actual resilience of the technology underneath them - DORA is specifically about whether a bank, insurer, or investment firm's systems can withstand, respond to, and recover from an ICT disruption, not just whether it's adequately capitalized against one.

Why does it matter, in practical terms?

Because it's enforceable now, not aspirational. A financial entity in scope that hasn't implemented DORA's ICT risk-management framework, incident-classification and reporting process, resilience-testing program, and third-party oversight register is already out of compliance, not "getting ahead of" a future deadline. National competent authorities activated their administrative-penalty powers under DORA on the same date the regulation became applicable - 17 January 2025 - across all 27 EU member states.

Who has to comply?

Financial entities as DORA's Article 2 defines them - a broad list that includes credit institutions, payment and e-money institutions, investment firms, insurance and reinsurance undertakings, crypto-asset service providers, and several other regulated categories - plus, indirectly, any ICT third-party provider a financial entity relies on for a critical function. A subset of the largest third-party providers are designated "critical" and fall under a direct EU-level oversight framework of their own.

Where do I go for the details?

This page exists to settle the "which DORA" question. For the substance - the five pillars, the exact compliance requirements, who specifically has to comply, the real incident-reporting timeline - see the dedicated guides linked elsewhere on this site rather than duplicating them here.

If you're looking for a different DORA

"DORA" isn't unique to this regulation. If the context you actually care about is deployment frequency, lead time for changes, or other software-delivery metrics, you're thinking of DevOps Research and Assessment (DORA), the Google Cloud-affiliated research team behind the annual State of DevOps report - a completely separate thing with no security or compliance meaning. If you landed here looking for a US state's professional-licensing lookup or a consumer chatbot app, that's a different organization or product that happens to share the acronym, and this page - like the rest of this site - has nothing to do with it.

Free security scan

See what's actually exposed on your site.

Decloak's free scan runs in about 15 seconds, no account required, and covers:

  • HTTP/TLS security posture
  • JavaScript CVEs
  • Exposed Supabase/Lovable/Base44 misconfigurations
  • AI-written executive summary