DORA Register of Information

We help you map ICT contracts to the prescribed DORA register templates, resolve data gaps and organise ongoing register maintenance.

  • 01Populated register templates with traceable data sources
  • 02A validation log with open data errors and responsible owners
  • 03An agreed export and instructions for ongoing maintenance
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

Which ICT contracts and data belong in your register?

The DORA register of information documents contractual arrangements for the use of ICT services. We reconcile your contract and provider data with the register templates and identify missing information.

We need the relevant contracts, provider and entity data, existing register versions and your mapping of supported functions. We agree the register scope, sources, export format and checks at the outset. A general IT asset inventory does not replace these contract data.

6 service modules

Register data, validation log and maintenance handover

01

Map data sources to register fields

You receive a source mapping that identifies the origin, owner and missing information for the agreed register fields.

  • Reconcile contracts, provider lists and existing register versions
  • Document field mappings and identifiers
  • Record data gaps with owners and clarification requests
02

Populate the register and maintain changes

The populated register links the agreed source data to a documented update process. Automation is limited to the interfaces that are actually available.

  • Hand over populated templates and the source-data version used
  • Distinguish manual and automated update steps
  • Walk through a change case with the future register owners
03

Link contracts, providers and services

A traceable mapping connects the recorded contracts to providers, ICT services and the entities concerned. Unclear relationships remain visible as open items.

  • Check identifiers and links between register entries
  • Record relevant subcontracting relationships from the information available
  • Flag missing or contradictory provider information for resolution
04

Validate data and assign errors

The validation log records the rules applied, identified data errors and remaining limitations. The issue list assigns unresolved errors to the relevant data owners.

  • Check required fields and permitted values within the agreed scope
  • Check links and consistency across templates
  • Document corrections and the subsequent validation run
05

Prepare the export and business approval

You receive the agreed register export with its version and validation log. Business approval and any submission to the competent authority are recorded as separate responsibilities.

  • Confirm current authority instructions for the agreed reporting route
  • Version the export and template used
  • Identify remaining errors and conditions for approval
06

Map supported functions and dependencies

The mapping records the functions supported by the registered ICT services and the assessments on which those entries are based.

  • Use existing function and criticality assessments as the starting point
  • Link services to functions transparently
  • Identify open business assessments and responsible decision-makers

Register preparation resources

Use the applicable reporting materials and authority instructions. Historical dry-run tools do not establish the current reporting package.

5 phases

From source data to a validated and maintainable register

We work with the nominated business, procurement, IT and compliance owners. The agreed register version, unresolved errors and maintenance responsibilities form the handover.

  1. Agree scope

    Confirm the register level, sources, template and export.

    Agreed work scope and data owners.

  2. Consolidate data

    Map contracts and provider information and assign gaps for clarification.

    Populated register draft and source mapping.

  3. Check relationships

    Reconcile identifiers, services and supported functions.

    Traceable links and open business questions.

  4. Validate and correct

    Apply the agreed checks and recheck corrections.

    Validation log with documented remaining errors.

  5. Hand over and rehearse an update

    Review the export, approval and a change case.

    Versioned register and maintenance instructions.

Sarah Richter

Your contact

Sarah Richter

Head of Information Security, Cyber Security

10+ years of experience, CISA, CISM, Lead Auditor, DORA, NIS2, BCM, Cyber and Information Security

6 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about DORA Register of Information

What is the DORA information register, and who must maintain it?

The register records contractual arrangements for ICT services supplied by third-party providers. Financial entities within DORA’s scope maintain it at entity level and, where applicable, at sub-consolidated and consolidated levels. It is not a general inventory of devices and software. Confirm the included entities, register levels and relevant contracts before data collection begins.

What information must the register capture per third-party provider?

The templates connect entities, contracts, ICT services, providers and relevant supply-chain and function relationships. Direct ICT services are not limited to those supporting critical or important functions. The applicable instructions determine which subcontractors and intra-group relationships must also be recorded. A provider list alone is insufficient. Confirm identifiers, permitted values and links from the prescribed templates; do not replace missing contract data with assumptions.

What software is suited to maintaining the information register?

Evaluate a tool against the applicable data model, relationships, template version, validation, export and change history. A spreadsheet or specialist tool is useful only if it supports the required process and controls. A CMDB can contribute source data but does not by itself establish a complete contract-based register. Test an update and corrected export before selecting an automation approach.

How often must the register be updated and submitted to supervisors?

Keep the register up to date as relevant contracts, providers, services or function mappings change. Maintenance and external submission are separate processes. For financial entities supervised by Germany’s BaFin, its current instructions require the complete, error-free annual submission process by 31 March, with the previous 31 December as the reference date. BaFin publishes the opening date each year. Confirm your own competent authority, reporting cycle and current instructions before planning an export; this BaFin example is not a deadline for every EU financial entity.

What happens if the register is incomplete or outdated during a review?

Record each gap or inconsistency with its source, responsible owner and resolution status. Recheck corrections and retain the result for the tested version. For BaFin submissions, the current instructions describe BaFin and ESA validation followed by further data-quality checks. Keep the feedback, corrected versions and required resubmissions traceable. Successful upload alone does not complete that process. Technical checks do not replace business review or an assessment of regulatory obligations.

What do we receive at the end of the agreed register project?

The handover comprises the agreed populated register version, source mapping, validation and open-issue log, export and maintenance instructions. The included entities, templates, sources and checks are agreed at the outset. Business approval and any technical submission support are separately assigned responsibilities.