Skip to content
All articles
AI regulation and governance

DORA and AI: an assistant is an ICT dependency, not an experiment

DORA does not treat artificial intelligence as a special case. An AI service that supports a business process is an ICT service, so it enters the ICT risk framework and the register of the financial entity.

BastionUpdated 4 min read

Who stays responsible when a supplier runs the service

Article 28(1) states that financial entities “shall manage ICT third-party risk as an integral component of ICT risk within their ICT risk management framework”. Point (a) keeps the responsibility with the entity:

financial entities that have in place contractual arrangements for the use of ICT services to run their business operations shall, at all times, remain fully responsible for compliance with, and the discharge of, all obligations under this Regulation and applicable financial services law

Regulation (EU) 2022/2554, Article 28(1)(a)

Recital 64 says the same in plainer words: “A financial entity should at all times remain fully responsible for complying with its obligations set out in this Regulation.” Article 28(1)(b) then makes the effort proportionate, taking into account “the nature, scale, complexity and importance of ICT-related dependencies”. A pilot with two users is not treated like a production workflow in credit operations.

What has to be in the contract

Article 30(2) lists the minimum contents of an arrangement on the use of ICT services. Point (b) is the one that catches AI services:

the locations, namely the regions or countries, where the contracted or subcontracted functions and ICT services are to be provided and where data is to be processed, including the storage location, and the requirement for the ICT third-party service provider to notify the financial entity in advance if it envisages changing such locations

Regulation (EU) 2022/2554, Article 30(2)(b)
  • Point (a) requires a clear and complete description of the functions and services, and whether subcontracting of a service that supports a critical or important function is permitted.
  • Point (c) covers availability, authenticity, integrity and confidentiality.
  • Point (d) covers access, recovery and return of data if the provider fails or the contract ends.

For a cloud AI service, the location answer can depend on a deployment setting, subprocessing has to be described, and the exit path has to exist before it is needed.

The questions a supplier has to answer in writing

  • Where is the service provided, and where is the data processed and stored?
  • Who else processes it, and under what terms?
  • What happens during an outage, and what is the recovery objective?
  • Can the service be substituted, and how long would that take?
  • What happens when the model version is retired?
  • What notice is given before any of these change?

What a local appliance changes, and what it does not

A local AI appliance does not remove operational risk. Hardware fails, software fails, and a model can be confidently wrong. Those risks move onto the entity's own register. The dependency changes in three ways:

  • The processing location is the entity's own site and does not move with a console setting.
  • There is no external inference endpoint whose availability sits outside the contract.
  • The model version is fixed until somebody chooses to change it.

For a workflow that must keep running, those are the properties the register cares about. For everything else, a well-documented cloud service may be the better answer. DORA does not prescribe one or the other; the entity must be able to show why it chose.

With Bastion

What Bastion changes

Bastion is a private AI system delivered as one sealed box that runs inside your building. One monthly fee covers the hardware, the model, the hardened operating system and support, and nothing your team types leaves the building.

For the register row, a Bastion node gives short answers. The service is provided and the data is processed where the box stands: the customer's site, or a partner's data centre that the contract names. When the box stands at the customer's site, there is no subcontracted processing location. The unit has no internet connection.

Everything else on the row, criticality, recovery objectives, access control and exit strategy, is the financial entity's to define. Article 28(1)(a) does not let a supplier take it.

Questions this article answers

Does DORA apply to AI services?
DORA does not name AI, and it does not need to. An AI service that supports a business process is an ICT service, so it falls inside the ICT risk management framework and the third-party arrangements of Articles 28 and 30.
Can a bank transfer AI compliance risk to its provider?
No. Article 28(1)(a) states that financial entities with contractual arrangements for ICT services shall at all times remain fully responsible for compliance with all obligations under the Regulation and applicable financial services law.
What must the contract with an AI provider say?
Article 30(2)(b) requires the locations, the regions or countries where the services are provided and where data is processed, including the storage location, plus a requirement that the provider give advance notice before changing them.

On the record

  1. 1
  2. 2