Home / Services / EU DORA Compliance

Under DORA, a plan is not proof. A tested recovery is.

EU DORA compliance under Regulation (EU) 2022/2554 for financial entities and their ICT providers.

DORA has applied since January 17, 2025. Responsibility for ICT risk sits with the management body itself. Identiqa connects the governance with the technology auditors ask about: separate, locked backups, verified servers, and an incident response team you can reach around the clock.

DORA, the EU's Digital Operational Resilience Act, requires banks, insurers, investment firms, payment institutions, and crypto-asset service providers in the EU to prove their digital operational resilience. Article 5 puts the responsibility on the management body. Article 19 and Commission Delegated Regulation (EU) 2025/301 require the initial notification of a major incident within four hours of classification. Article 12 requires restoring data on systems that are physically and logically segregated from the source system.

Four hours to the initial notification.

The clock runs from the moment you classify an incident as major. The report goes to the competent authority of the Member State in which the entity is authorized.

  1. 0The incident is classified as major
  2. 4 hoursInitial notification, no later than 24 hours after becoming aware
  3. 72 hoursIntermediate report, counted from the initial notification
  4. 1 monthFinal report, counted from the latest intermediate report

Not to scale. Deadlines from Commission Delegated Regulation (EU) 2025/301.

Jan 17, 2025DORA has applied since this date
Article 5The management body bears the responsibility
YearlyTesting of the systems that support critical or important functions
Every 3 yearsThreat-led penetration testing (TLPT) for designated financial entities

Five areas, one responsibility.

DORA sorts the duties into areas. The management body answers for all of them.

What DORA requires and what Identiqa contributes
AreaWhat DORA requiresWhat Identiqa contributes
Management body and risk framework (Art. 5 to 16)The management body defines the ICT risk framework, approves it, oversees it, and bears the responsibility.CISO advisory: risk analysis, decision papers, and reports to the management body
Backup and recovery (Art. 11 and 12)Tested procedures, and restoration on systems that are physically and logically segregated from the source system.AuraLink: locked backups on its own 2U hardware, outside your domain
Incidents (Art. 17 to 23)Detect incidents, classify them, and report major ones to the competent authority within fixed deadlines.24/7 incident response and prepared reporting lines
Testing (Art. 24 to 27)A testing program, at least yearly for the systems that support critical or important functions.Penetration tests with proven attack paths
ICT third parties (Art. 28 to 30)A register of information on all ICT contracts and exit strategies for critical services.CISO advisory: building and maintaining the register

Regulation (EU) 2022/2554. Text of the Regulation at EUR-Lex

What supervisors want to see.

A smooth examination and a hard one rarely differ in the policy. They differ in the records from production.

On paper

  1. Backup policy
  2. Incident response plan
  3. List of providers

Necessary, but no proof that it works when it has to.

From production

  1. Record of the last recovery test
  2. Lock record of the separate backup
  3. Rehearsed reporting line with timestamps
  4. Register of information with exit plan

These are the records supervisors ask for.

What DORA changes compared with earlier rules

DORA moves the bar from the policy to the proof. Supervisors and auditors ask for the record of the last recovery test, for the separation of the backup systems, and for the exit clauses in the contracts with cloud and ICT providers.

The window for incidents is tight. A team that spends it working out who reports and what was hit will miss the deadline.

Identiqa advises your security function, supplies the technical evidence from AuraLink and AuraCore, and is reachable through 24/7 incident response when an incident hits.

Common questions

Which companies fall under DORA?

Almost every supervised financial entity in the EU: credit institutions, payment and e-money institutions, investment firms, fund managers, insurers, and crypto-asset service providers. DORA reaches their ICT providers indirectly through the contracts Article 30 prescribes. Providers the European Supervisory Authorities designate as critical are overseen directly.

Does DORA or NIS2 apply to financial entities?

For ICT risk management and incident reporting, DORA takes precedence as the more specific regime. Financial entities follow DORA on those points and report to their financial supervisor.

What does Article 12 of DORA require of a backup?

Backup and restoration procedures that are tested regularly. When restoring, entities must use systems that are physically and logically segregated from the source system and protected against unauthorized access. AuraLink keeps the backup on its own 2U hardware, outside your domain and locked in the storage controller. Restoring onto segregated systems remains part of your own procedure, and whether it is sufficient is for your supervisor to judge.

Where do you stand on DORA?

In the architecture briefing we walk through your position along the five areas: management body, backup, incidents, testing, and providers. You learn where evidence is missing and what to do first.

Architecture briefing & advisory

This page summarizes the Regulation. It is not legal advice.