DORA Compliance

DORA Compliance

DORA Compliance

TL;DR

TL;DR

DORA compliance means meeting the EU Digital Operational Resilience Act: managing ICT risk, reporting major ICT incidents, testing resilience, overseeing ICT third-party providers and keeping an audit trail.

DORA compliance means meeting the EU Digital Operational Resilience Act: managing ICT risk, reporting major ICT incidents, testing resilience, overseeing ICT third-party providers and keeping an audit trail.

What is DORA compliance?

DORA compliance means meeting the EU Digital Operational Resilience Act, Regulation (EU) 2022/2554, which has applied since 17 January 2025. It requires banks, insurers, payment firms and other financial entities to manage ICT risk, report major ICT incidents, test resilience, oversee ICT third-party providers and keep evidence a supervisor can audit.

DORA treats operational continuity in finance as a supervised outcome. It is narrower than SOC 2 Type II or GDPR in sector, but broader in subject: it covers every technology dependency behind a critical or important business function.

The five DORA pillars

  • ICT risk management: a framework owned at management-body level, covering identification, protection, detection, response and recovery.

  • Incident reporting: classify ICT-related incidents and report major ones to the competent authority in stages.

  • Resilience testing: regular testing, with threat-led penetration testing for larger entities.

  • ICT third-party risk: a register of information for every ICT provider, contract terms, risk ratings and exit plans.

  • Information sharing: voluntary exchange of cyber threat intelligence between financial entities.

Incident reporting

Reporting works on clocks. Once an incident is classified as major, the firm sends an initial notification, then an intermediate report, then a final report with root cause and remediation. Classification depends on evidence such as clients affected, duration, data loss and critical services hit, so the firm needs timestamped records from the moment of detection.

ICT third-party and vendor risk

Every ICT arrangement goes into the register of information, including the provider's own subcontractors. Contracts must give access, audit and termination rights, and the firm must have an exit plan for arrangements that support critical functions. For a support stack, that means the AI vendor, its model providers and its hosting subprocessors all appear in the register. Watch for subprocessor changes mid-contract, which make last quarter's register stale.

Audit trail and evidence

Supervisors judge DORA on evidence: a complete register, test reports, and incident records that show classification and reporting happened on time. An AI agent that retrieves data, calls tools or changes account state needs a log of each action tied to a session, so a reviewer can replay what it did. Entity extraction can lift case IDs, timestamps and account references out of transcripts into fields a query can count.

DORA and AI customer support

An AI agent in a regulated support queue is an ICT arrangement that acts, so it needs guardrails, pre-release testing and an audited control boundary. Vendor diligence and DORA mapping ask mostly the same questions; see AI support platforms for compliance officers and AI chat compliance for banking. Fini is SOC 2 Type II, ISO 27001:2022 and PCI DSS Level 1 certified and GDPR compliant, which shortens diligence but does not discharge the financial entity's own DORA duties.

Frequently Asked Questions

Who does DORA apply to?

DORA applies to EU financial entities, including banks, insurers, investment firms, payment and e-money institutions and crypto-asset service providers. ICT providers designated as critical are overseen directly, and other suppliers are pulled in through contracts when they serve an in-scope firm.

What does DORA require for incident reporting?

Financial entities must classify ICT-related incidents against set criteria and report major ones to their competent authority in stages: an initial notification, an intermediate report and a final report with root cause. That needs timestamped logs from detection to classification.

Does DORA cover AI chatbots in customer support?

Yes, when the chatbot supports a critical or important function, which most customer-facing automation in a regulated firm does. The AI vendor, its model providers and its hosting subprocessors belong in the register of information, with logs detailed enough to reconstruct what the agent did.

What is the DORA register of information?

It is a structured inventory of every contractual arrangement a financial entity holds for ICT services, recording the provider, its subcontracting chain, the functions supported, criticality and exit arrangements. Supervisors expect it to be current and machine-readable.

What is the difference between DORA and NIS2?

DORA is a regulation that applies directly and uniformly to the EU financial sector. NIS2 is a directive covering essential and important entities across many sectors, transposed into national law by each member state, so its obligations vary by country.

Learn More

Learn More

Knowledge base

K

Average handling time (AHT)

A

Telephony

T

Customer acquisition cost (CAC)

C

AI tokens

A

Human in the loop (HITL)

H

AI grounding vs retrieval-augmented generation (RAG)

A

Short message service (SMS)

S

Call center

C

Data annotation

D

Ticket routing

T

Customer service quality assurance (QA)

C

Live chat

L

Speech Synthesis Markup Language (SSML)

S

Batch inference

B

Barge-in

B

SLA compliance rate

S

Queue management

Q

Prompt versioning

P

Emotion detection

E

Retrieval-augmented generation (RAG)

R

Natural language understanding (NLU)

N

Text classification

T

Call routing

C

Customer churn rate

C

Speech-to-speech

S

Intent recognition

I

Voice of the employee (VoE)

V

Confidence score

C

Resolution-based pricing

R

AI personalization

A

Voice cloning

V

Asynchronous messaging

A

Hallucination

H

ReAct agent pattern

R

Long-term memory

L

Forecast accuracy

F

Customer feedback loop

C

Structured output

S

Outbound voice AI

O

AI guardrails

A

Direct preference optimization (DPO)

D

Prompt chaining

P

SIP transfer

S

Fallback intent

F

Conversation summarization

C

Auto-tagging

A

Cost per contact

C

VoIP jitter

V

Model card

M

Ticket prioritization

T

Sentiment analysis

S

Agent utilization rate

A

Speech-to-intent

S

Prompt engineering

P

Knowledge atlas

K

SOC 2 AI support

S

Prosody

P

Chatbot containment rate

C

Speech synthesis

S

ISO 42001

I

Intent-based search

I

After-call work (ACW)

A

Chatbot

C

AI agent

A

Prior authorization automation

P

AI customer service

A

Ticket deflection

T

AIUC-1

A

Workforce management (WFM)

W

Skill-based routing

S

Interactive voice response (IVR)

I

Contact center as a service (CCaaS)

C

Warm transfer

W

Customer segmentation

C

Reinforcement learning

R

Voice activity detection (VAD)

V

Tiered support

T

Echo cancellation

E

Net Promoter Score (NPS)

N