Join our Newsletter — 33% off our NHI Course
Home› Guides› DORA ICT Third-Party Risk and Register of Information…
Guide Regulations & Frameworks

DORA ICT Third-Party Risk and Register of Information Guide: Templates, Subcontracting Rules and Annual Submission

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 15 min read
On this page

The DORA register of information looks like a contract list, but supervisors now validate it field by field and use it to decide which ICT providers fall under direct EU oversight, so a weak register is both a reporting failure and a blind spot in your own third-party risk. Article 28(3) of Regulation (EU) 2022/2554 requires every in-scope financial entity to keep a register of all ICT contractual arrangements, and Implementing Regulation (EU) 2024/2956 fixes the 15 templates it must use. The subcontracting standard, Delegated Regulation (EU) 2025/532, entered into force on 22 July 2025 and governs how chains behind critical or important functions are assessed, contracted and changed. This guide goes deeper than the DORA Guide on the third-party pillar: who must report what, the template set, subcontracting rules, the annual submission cycle and validation, enforcement, and how non-human identities and AI services belong in the register. It is for third-party risk, procurement, ICT risk and data teams in financial entities, and for ICT providers that must supply the data.

Status checked 27 October 2026 against EUR-Lex texts and 2026 reporting notices from the Central Bank of Ireland and De Nederlandsche Bank. This page is not legal advice.

Key takeaways

  • Every ICT arrangement, not only critical ones: the register covers all contractual arrangements for ICT services and must distinguish those that support critical or important functions from those that do not (Art. 28(3)).
  • Fifteen templates, one value per field: ITS 2024/2956 sets templates B_01.01 to B_99.01 in a relational table format with fixed columns, unlimited rows and six data quality principles.
  • The supply chain is ranked: direct providers are rank 1 and every subcontractor that effectively underpins a critical or important function must be recorded at a rank higher than 1.
  • Subcontracting now has its own rulebook: RTS 2025/532 requires due diligence before subcontracting is allowed, 12 contract conditions, a reasonable notice period for material changes and termination rights if a provider ignores an objection.
  • Submission is annual and machine-validated: for 2026 the reference date was 31 December 2025, the national windows ran in March 2026, and files went in as xBRL-CSV against EBA validation rules.

Scope: who and what is covered

DORA has applied since 17 January 2025 to the financial entities listed in Article 2, from credit institutions and insurers to payment institutions, crypto-asset service providers and trading venues. The register duty sits in Article 28(3) and applies at three levels.

ElementRequirementSource
LevelsMaintain and update the register at entity level and, where applicable, at sub-consolidated and consolidated levelDORA Art. 28(3); ITS Art. 3
ArrangementsAll contractual arrangements on the use of ICT services provided by ICT third-party service providersDORA Art. 28(3)
ICT servicesDigital and data services provided through ICT systems to internal or external users on an ongoing basis, including hardware as a service; analogue telephony excludedDORA Art. 3(21)
Critical or important functionA function whose disruption would materially impair financial performance, soundness or continuity of services, or continuing compliance with authorisation conditionsDORA Art. 3(22)
Supply chainAll subcontractors that effectively underpin ICT services supporting critical or important functionsITS Art. 3(2)(b)
Intra-groupIntra-group ICT providers are in scope; where they use subcontractors, at least the first extra-group subcontractor is recorded even if the service is not criticalITS template B_05.02
Group scopeThe parent undertaking decides which entities sit in the consolidated register, using sectoral consolidation rulesITS Art. 6

Microenterprises and the entities in Article 16(1) are excused from parts of Article 28 (for example the third-party risk strategy in Article 28(2)), but the register itself is still expected. Check your national authority's instructions on the reporting level: DNB, for instance, requires standalone institutions to report individually and group members to report at the highest EU consolidation level, while ECB-supervised banks report to the ECB.

Key obligations

What Article 28 requires

  • Register (Art. 28(3)): keep it current, report at least yearly on new arrangements, provider categories, contract types and services and functions, give the full register or sections on request, and inform the authority in a timely manner about planned arrangements for critical or important functions and when a function becomes critical or important.
  • Pre-contract assessment (Art. 28(4)): decide whether the arrangement supports a critical or important function, check supervisory conditions, assess risks including concentration (Art. 29), run due diligence and assess conflicts of interest.
  • Security standards (Art. 28(5)): contract only with providers that meet appropriate information security standards.
  • Termination grounds (Art. 28(7)): significant breach, circumstances that alter the function, weaknesses in the provider's ICT risk management, or loss of effective supervision.
  • Exit (Art. 28(8)): documented, sufficiently tested and periodically reviewed exit strategies for critical or important services, with identified alternatives and transition plans.

The contractual policy behind these duties is set by Delegated Regulation (EU) 2024/1773 (in force 15 July 2024): the management body reviews the policy at least yearly, a senior manager monitors arrangements, and every arrangement has a documented, tested exit plan (Art. 3 and 10).

The register templates

TemplateContentPractical source of data
B_01.01Entity maintaining the registerLegal entity master data (LEI)
B_01.02Entities within the scope of consolidationGroup finance consolidation list
B_01.03List of branchesLegal entity data
B_02.01Contractual arrangements: general informationContract management system
B_02.02Contractual arrangements: specific information (service, dates, data location, notice periods)Contracts plus service owners
B_02.03Intra-group contractual arrangementsIntra-group service agreements
B_03.01 to B_03.03Entities signing to receive services, providers signing, and entities providing services to others in the groupContract signatories
B_04.01Entities making use of the ICT servicesService consumption data
B_05.01ICT third-party service providers (identifier, parent, country, type)Vendor master data, LEI or EUID
B_05.02ICT service supply chains (ranks)Provider disclosures of subcontractors
B_06.01Functions identification (criticality, impact)Business impact analysis
B_07.01Assessments of the ICT services (substitutability, exit, reintegration)Third-party risk assessments, exit plans
B_99.01Definitions used by the entityInternal taxonomy

Article 3 of the ITS requires the data to be accurate, complete, consistent, of integrity, uniform and valid, and providers to be identified by a valid LEI or EUID. The Central Bank of Ireland notes that third-country providers may use other valid codes under an EBA FAQ. Because each data element holds one value, a contract that covers three services and five entities becomes multiple rows linked by a contractual arrangement reference number, which is why spreadsheets built per contract usually fail validation.

Subcontracting under RTS 2025/532

Delegated Regulation (EU) 2025/532 was adopted on 24 March 2025, published on 2 July 2025 and entered into force on 22 July 2025. It applies to ICT services supporting critical or important functions that the provider subcontracts.

ArticleRequirementWhat evidence looks like
Art. 1Apply proportionately, weighing 12 factors such as subcontractor location, chain length, data handled, concentration and transferabilityDocumented risk-based scoping
Art. 2The parent ensures consistent application across the groupGroup policy and attestations
Art. 3Before contracting, decide whether subcontracting is permitted and confirm 10 conditions, including the provider's ability to identify subcontractors, flow-down terms and equal access and audit rights; some are reassessed periodicallyDue diligence file per critical service
Art. 4Contracts set which services may be subcontracted and on what terms, covering 12 points such as provider responsibility for subcontractors, monitoring, location, continuity, security standards, audit rights and notice of material changes; existing contracts amended in a timely manner with a documented timelineContract clause matrix and remediation tracker
Art. 5Material changes notified well in time, with a reasonable notice period; changes take effect only on approval or when the period lapses without objection; the entity objects if the change exceeds its risk toleranceChange notices and decisions log
Art. 6Termination rights if the provider implements a change despite objection, before the period ends, or subcontracts what the contract does not allowTermination clause

The final text does not set a fixed notice period, so entities negotiate one. Recital 1 says identifying the overall chain behind critical or important functions is essential, which is what template B_05.02 captures. See the Fourth-Party and Nth-Party Risk Guide for practical chain mapping.

Timeline and current status

DateEvent
15 July 2024RTS 2024/1773 on the contractual policy in force
22 December 2024ITS 2024/2956 on register templates in force
17 January 2025DORA applies; registers must be maintained
2025First register collection by national authorities and the ESAs
22 July 2025RTS 2025/532 on subcontracting in force
18 November 2025ESAs publish the first list of designated critical ICT third-party providers, built from register data
31 December 2025Reference date for the 2026 submission
March 2026National submission windows (Central Bank of Ireland 2 to 31 March; DNB 2 to 20 March)
April 2026EBA data quality checks on submitted registers (per the Central Bank of Ireland)

The 2026 format was xBRL OIM-CSV under the EBA DPM 4.0 data model, packaged as a zip; DNB also offered an Excel template that it converts. DNB said the taxonomy and template were unchanged from 2025. Expect a similar cycle each year, but check your authority's notice, because windows differ by country and the ESAs revise validation rules.

Enforcement and penalties

  • Financial entities (Art. 50): DORA sets no EU fine level; Member States set administrative penalties and remedial measures that must be effective, proportionate and dissuasive, including cessation orders, pecuniary measures and public statements, and these can reach management body members where national law allows.
  • Supervisory follow-up: authorities return validation errors and request resubmission (the Central Bank of Ireland asked for corrections before 31 March 2026), and data quality findings feed ongoing supervision.
  • Critical ICT third-party providers: Lead Overseers can impose periodic penalty payments of up to 1% of average daily worldwide turnover for up to six months (Art. 35), and designation itself relies on register data. Financial entities remain fully responsible for their own compliance (Art. 28(1)).
  • Contractual leverage: RTS 2025/532 Art. 6 and DORA Art. 28(7) give termination rights; supervisors can expect entities to use them where a provider's chain becomes unacceptable.

The examples of data quality checks published by the Central Bank of Ireland are telling: placeholder identifiers for a provider's ultimate parent and generic provider names such as "not applicable" are flagged. Treat each as a finding, not a formatting issue.

What it means for AI agents and non-human identities

The register is about contracts, but the risk it is meant to expose travels through machine credentials. Every ICT service in B_02.02 is reached by API keys, OAuth grants, service accounts or federated workload identities, and AI services are ICT services like any other.

  • AI and model providers are ICT third parties: an LLM API, an AI coding assistant or an agent platform used for a critical or important function belongs in the register, with its subcontractors (for example the cloud hosting the model) in B_05.02. See the Third-Party AI Risk Guide.
  • Link credentials to arrangements: tag every non-human identity that a provider holds or uses with the contractual arrangement reference number. That makes exit (Art. 28(8)) executable: you know which keys to revoke and which integrations break. See the Third-Party Access Guide.
  • Find unregistered services through identities: OAuth consents, API keys in secrets stores and egress logs reveal SaaS and AI services that procurement never saw. Reconcile them against the register each cycle. See the SaaS OAuth App Governance Guide.
  • Subcontractor change is an access change: a provider moving processing to a new subcontractor (an Art. 5 material change) can mean your data and tokens reach a new party. Require notice that names the identities and data flows affected.
  • Token theft is the realistic scenario: in the Salesloft Drift breach, OAuth tokens held by an integration provider gave attackers access to customers' Salesforce data, exactly the kind of downstream exposure the supply chain templates are meant to surface.

Compliance steps

  1. Assign ownership: one accountable owner for the register (often third-party risk), with data owners for contracts, vendor master, functions and group structure.
  2. Build the data model, not a spreadsheet: implement the ITS relational model with contractual arrangement reference numbers as keys, and load contracts, entities, providers, functions and assessments separately.
  3. Fix identifiers first: collect LEIs or EUIDs for every provider and ultimate parent; resolve placeholders before anything else.
  4. Map functions: take critical or important functions from the business impact analysis and link each ICT service to them (B_06.01).
  5. Collect the chain: request subcontractor disclosures from providers of critical services, rank them and record them in B_05.02; build this into RTS 2025/532 contract remediation.
  6. Remediate contracts: compare existing contracts to DORA Art. 30, RTS 2024/1773 and RTS 2025/532 Art. 4, prioritise critical services, and log the timeline as Art. 4 requires. The Third-Party Security Contract Clauses Template is a starting point.
  7. Validate and dry run: run the EBA validation rules against your xBRL-CSV output before the window opens and fix every error; keep the previous year's file to compare.
  8. Submit, resubmit, learn: submit early, handle validation feedback within the window, and log data quality findings as remediation items.
  9. Keep it live: update the register on contract signature, renewal, subcontractor change and exit, not once a year.

Decision guidance

ProfileApproachTrade-off
Small payment or e-money institutionAuthority Excel template where offered, small number of providers, manual chain collectionLow cost, but manual updates drift; schedule quarterly reconciliation
Mid-size investment firm or insurerGRC or TPRM tool with a DORA register module exporting xBRL-CSVTool configuration effort; data quality still depends on contract and vendor master hygiene
Banking or insurance groupCentral data model fed from procurement, CMDB and legal entity systems, consolidated register owned by the parentHighest build effort; the only way to keep thousands of rows consistent across entities

Measurement and framework mapping

  • Metrics: validation errors per submission; percentage of providers with a valid LEI or EUID; percentage of critical services with a complete ranked chain; contracts for critical services compliant with RTS 2025/532 Art. 4; exit plans tested in the last 12 months; non-human identities linked to a contractual arrangement.
DORA dutyNIST SP 800-53 Rev. 5NIST CSF 2.0ISO/IEC 27001:2022 Annex A
Register of information (Art. 28(3))SA-9, SR-3GV.SC-04A.5.19
Pre-contract due diligence (Art. 28(4))SR-6GV.SC-06A.5.21
Contract terms (Art. 30, RTS 2025/532 Art. 4)SA-4GV.SC-05A.5.20
Monitoring and material changesSA-9, CA-7GV.SC-07A.5.22
Exit strategy (Art. 28(8))CP-2GV.SC-10A.5.23
Function mapping (B_06.01)RA-9ID.AM-05A.5.30

Common failure patterns

  • Critical-only registers: omitting non-critical ICT arrangements, which Art. 28(3) includes.
  • Placeholder identifiers: dummy LEIs and "not applicable" provider names that the EBA's data quality checks flag.
  • Contract-per-row thinking: one row per contract instead of the relational model, producing inconsistent entity and service links.
  • No chain beyond rank 1: providers asked once for subcontractors and never again, so material changes go unrecorded.
  • Annual scramble: a register rebuilt every March rather than updated at each contract event, which is where Art. 28(3) expects it to be.

Practitioner checklist

  • Confirm your reporting level and authority (individual, highest EU consolidation, or ECB).
  • Load every ICT arrangement, flagging those supporting critical or important functions.
  • Obtain valid LEIs or EUIDs for all providers and their ultimate parents.
  • Rank and record subcontractors behind every critical or important service.
  • Add RTS 2025/532 Art. 4 terms and a defined notice period to critical contracts.
  • Log every material subcontracting change with your approval or objection.
  • Run EBA validation rules on the xBRL-CSV file before the national window opens.
  • Test exit plans for critical services and record the result in B_07.01.
  • Link API keys, OAuth grants and service accounts to their contractual arrangement.
  • Include AI and model providers used for critical or important functions.

Standards and references

Related NHI Mgmt Group resources: DORA Guide · DORA Major ICT Incident Reporting Guide · Third-Party Risk Management Guide · Cloud Concentration Risk and Exit Strategy Guide · Financial Services Cyber Regulation Map. This guide summarises the DORA register of information and ICT third-party rules as of October 2026 and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.