Skip to main content

Guide

What does DORA Article 28 require from ICT providers?

Understand DORA Article 28: financial entity responsibility, provider assessment, the register of information and exit capability explained.

What does DORA Article 28 require from ICT providers?
Julian Köhn
|Read time: 3 minutes

DORA Article 28 primarily addresses financial entities. An ICT provider receiving a request “under Article 28” should first clarify which service the customer is assessing and which information it needs.

Prepare the answer in three packages: service and dependencies, suitable evidence, and switching options. This guide handles customer requests without indiscriminately distributing internal records.

The distinction matters: a provider contract does not remove the financial entity’s responsibility. It does create specific requirements for cooperation and evidence.

What the article governs

Article 28 of the DORA Regulation treats ICT third-party risk as part of ICT risk management. It addresses pre-contract assessment, the register of information and exit strategies for services supporting critical or important functions, among other areas.

Specific minimum contractual content additionally needs consideration, particularly under Article 30. Do not confuse general supplier assessment with complete contract review.

Describe the actual service precisely

Start with the service offered. Which components do you operate? Which subcontractors participate? Which data is processed, and which tasks remain with the customer?

A general security presentation provides orientation but does not automatically establish suitability of the specific service for its intended function. Keep claims and limitations traceable.

A useful response package rather than a document flood

Customer questionUseful preparation
What exactly are we purchasing?Clear service description and contract reference
What does the service depend on?Material technical and external dependencies
How is it checked?Suitable current evidence with scope
How can we switch?Data portability, handover, deadlines and remaining dependencies

This is a practical preparation aid, not an exhaustive statutory catalogue.

Fictional case: A planned provider change

A financial entity wants to replace an archive service. Downloading every file is insufficient if relationships, metadata or readability are missing. Test a small complete dataset with the customer and its adoption in an alternative process.

Our future exit assessment guide structures this trial. A documented test gives a better decision basis than “export available”.

Divide the request into three response packages

A financial customer does not need every internal record. First clarify purpose, affected service and recipients. Then assemble a targeted answer:

  1. Service and dependencies: What is contractually delivered, which relevant further providers participate and which tasks stay with the customer?
  2. Verifiable security work: Which current evidence concerns this service, what scope does it cover and which limitations apply?
  3. Switching and cooperation: Which data and support are available during transition, and which conditions need clarification?

Share confidential details selectively

A full technical report may contain information the customer does not need for its decision or should not receive without restriction. Review authority, confidentiality and scope before sharing. Record which version served which purpose.

If evidence does not answer a question, name the gap. A precise question about the required conclusion is more useful than a large attachment without service context. The customer can assess the service while you reuse work from your own ISMS.

Keep the answer connected to your own ISMS

Assign evidence to the measures it actually demonstrates. In Kopexa, those measures can be mapped to relevant controls. A customer question can reference existing work without rebuilding every answer.

Before sharing, check content, period and permission. Use evidence maintenance and coordinate register data with the customer. Our DORA register data quality article explains typical breaks between contract, service and function.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Does the ICT provider assume all the customer’s DORA responsibility through the contract?

No. The financial entity remains responsible for its obligations. The provider must enable agreed cooperation and dependable information about the specific service.

Sources

  1. Regulation (EU) 2022/2554 — Europäische Union [Accessed ]