Guides · DORA

Under DORA, every AI provider is an ICT third party.

Your AI models are not a tool you bought once. DORA treats each one as an ICT third-party arrangement that has to be in your register, assessed for concentration risk, and shown to be substitutable. Vidai's record of every call is where much of that evidence comes from.

What it is

The operational resilience law for finance.

Regulation (EU) 2022/2554, the Digital Operational Resilience Act, has applied to EU financial entities since 17 January 2025. It treats technology dependency as a prudential risk: firms must know every ICT third party they rely on, understand where they are concentrated, and show a critical function could keep running if a provider failed.

AI providers fall squarely inside its definition of an ICT service.

01

AI is an ICT dependency

Each model and provider your traffic reaches is a third-party arrangement DORA expects to see in your register, with its risk assessed.

02

Concentration is the risk

Leaning on one provider for a critical function, such as fraud screening, claims or correspondence, is the systemic dependency DORA and the UK's critical third parties regime are written to surface.

03

Substitutability is evidence

"We could switch provider" is a claim until you can show the exit path and the moment it was used. DORA asks for the evidence, not the intention.

Why this got harder

Agents multiplied the third-party surface DORA governs.

In the chat era, an AI feature was a handful of provider calls. Agents changed the shape of the dependency: one task now fans out into ten or more autonomous calls, and a multi-step workflow can cross several providers, regions and jurisdictions in a single run.

See the traffic multiplier at your scale →

Jurisdiction is not in the contract

A data-residency clause covers one corridor. It does not follow an agent through every sub-processor and model it reaches mid-task, which is where the real exposure now sits.

The dependency is extraterritorial

A model served by a provider headquartered elsewhere can carry obligations that reach back across borders. DORA expects you to have understood that, provider by provider.

The register has to be live

A spreadsheet refreshed each quarter cannot describe a dependency that changes with every agent run. The inventory has to come from the traffic itself.

The articles

Where Vidai's records give the evidence.

For these duties the evidence is the traffic record itself, not a document assembled alongside it.
Art. 28Register of ICT third-party arrangements Financial entities keep a register of every contractual arrangement for ICT services. Each AI provider is one. Approved destinations list the models any call may reach, and every call record names the model that served it, so the register can be checked against real traffic.
Art. 29Concentration risk Firms assess the risk of relying on a few ICT providers. Calls and cost broken down by model show how much of a function's traffic each provider carries, measured rather than estimated.
Art. 28(8)Exit strategies For services that support critical or important functions, firms need exit strategies and alternatives. Fallback chains move calls to another model when one fails, and routing changes are recorded in the audit log.
Art. 9 to 10Protection, prevention and detection ICT risk management needs controls and the means to detect anomalous activity. Guardrails and model access act on every call, and blocks, refusals and changes go to your SIEM as signed events (Enterprise).
Art. 17 to 19Incident management and reporting Major ICT-related incidents are detected, classified and reported. Request logs and the tamper-evident audit log are the source for reconstructing what happened and when; the classification and the report are yours.

Sourced from Regulation (EU) 2022/2554 as in force. The ICT risk management framework, resilience testing, incident classification and reporting, and board accountability remain the firm's own. Vidai gives you the evidence; your auditor and supervisor make the call.

Where Vidai fits

Evidence from the traffic, not a DORA badge.

Vidai is not a DORA certification and cannot make a firm compliant. What it does is turn the slowest parts of the evidence into a by-product of running the traffic.

Providers you can see

Every provider and model your traffic actually reaches is in the call record, so the AI part of the register is observed, not just declared.

Concentration as a number

Traffic and cost per model turn "are we too dependent on one provider" into a share you can act on.

An exit path you have used

Fallback chains and routing send calls to another provider or region, and a Stop switch can suspend one provider entirely. Each change is on the record.

DORA as a label

In the Control room, DORA tags the policies that serve it so you can find them. It sets no retention and no controls by itself: those come from the regulations you follow and the rules you write.

Routing · Fallback

Substitution you can show

A fallback chain names the models a call may move to, in order, when one fails or is rested. Each call records the models it tried, so the exit path is something that happened, not a line in a plan.

Vidai Control room · Routing
A fallback chain: the models a call may move to, in order.
A fallback chain: the models a call may move to, in order.

How we start together

Walk through your AI third-party evidence.

A 20-minute walkthrough: the providers your traffic really reaches, concentration per model, the fallback path, and exactly where Vidai's boundary is.
  1. 01

    Pick one app or team

    Point it at the Control room. One configuration change; nothing else changes.

  2. 02

    Watch for two weeks

    Every call priced, checked and recorded. Rules start in observe mode.

  3. 03

    See the evidence

    What it cost, what it caught and what it would have stopped, from your own traffic.