Skip to content

DORA and data

We populate the DORA register of information with contract, supplier and CMDB data and keep it up to date. For SNG, we automated the release process.

For SNG, we automated releases across the DTAP pipeline, eliminating human error

New Docker applications pass through the DTAP pipeline in SNG’s Google Cloud Platform. We automated the release process so the DevOps team no longer has to carry out manual steps.

Read the case study

How do we keep the DORA register of information up to date when contracts and suppliers are spread across separate systems?

DNB found that data on ICT contracts comes from different administrative systems and often has no central owner. By linking and checking contracts, suppliers and ICT services once, you can submit a register compiled in the same way each year.

Book a meeting

The register, incident data and ICT risk draw on the same connected sources

Discuss your register

The register built from source data

Contracts, ICT services, suppliers and subcontractors from contract management, procurement and the CMDB, linked using consistent keys and ready for xBRL-CSV.

Validation rules as checks

The ESAs’ rules run as part of the pipeline, so a missing identifier or an unlinked reference is flagged before the regulator responds.

Incident data in one place

Reports from ITSM and monitoring, with timestamps, classifications and affected services, so every individual report is based on the same data.

Every change traceable

Sources and logic under version control, with a defined release pipeline, as we did when we automated the release process for SNG.

We start with the register forms and work back to the source

  1. Forms and sources side by side

    For each form, we record which system each field comes from and who maintains it.

  2. Connect and validate

    Contracts, suppliers and ICT services in one model, with validation rules as standard checks.

  3. Submit and maintain

    An export in the requested format, a dashboard for ICT risk management and an owner for each source.

Is the register a data issue for us, and what remains with compliance?

Talk it through with us

A good fit if

You’re a financial institution subject to DORA, the register is currently compiled from spreadsheets and separate exports, and you want to build it from the source systems instead of starting again each year.

Not a fit if

You’re looking for an interpretation of what DORA means for your institution or an assessment of compliance. That’s for your compliance team, legal advisers and regulator; we don’t provide legal advice.

What determines the scope

How many entities are involved, how many systems hold contracts and supplier data, whether there’s a CMDB, and whether incident reporting and dashboards are included.

Have you done this for DORA before?

Our case studies aren’t about DORA. They do cover bringing together and checking data from different systems, and making changes in a controlled way, such as the automated release process for SNG.

DNB’s Excel template, a standalone xBRL-CSV export or a register built from source data?

DNB’s Excel template

Choose this if DNB is your regulator and you have few ICT contracts. DNB converts the template to xBRL-CSV; you remain responsible for its accuracy.

A standalone xBRL-CSV export

Choose this if AFM is your regulator, which will only accept xBRL-CSV from 2026, and the register is small and stable. It will still involve manual work every year.

A register built from source data

Choose this if contracts and ICT services change often and multiple systems are involved. Our advice: build the register from source data, so the annual reporting request is mainly a matter of refreshing it.

Connecting and checking data sources, and changing them in a controlled way, is part of our everyday work

Data Science Lab has worked with data and AI since 2016, as a Databricks Partner and Microsoft Partner. For SNG, we automated the release process through the DTAP pipeline. We leave the interpretation of DORA to your compliance team and legal counsel.

Book an introductory meeting

We’ll discuss your latest submission of the register and the feedback on it in our first conversation

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your point of contact. In our first conversation, we’ll discuss your latest submission, the sources behind it and where the feedback process stalled.

Which systems currently feed your register of information?

Tell us which entities are involved and where you currently keep your contracts, supplier information and incidents. We’ll reply by email, or we can arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

The Digital Operational Resilience Act (DORA) is Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. According to DNB, the regulation entered into force on 17 January 2023 and has applied since 17 January 2025.

DNB identifies five areas: ICT risk management, ICT incidents, regular testing of digital operational resilience, risks associated with outsourcing to (critical) third parties, and sharing information about cyber threats. The data side falls under your data governance.

EIOPA states that DORA applies to twenty types of financial entity, including banks, insurers and investment firms, as well as third-party ICT service providers. In the Netherlands, DNB and the AFM supervise compliance; the Besluit EU-verordeningen Wft designates the relevant supervisory authority.

Your compliance department assesses whether and how DORA applies to your organisation. You can read how we work with data for insurers and financial and business services on those pages.

DNB states that, since DORA took effect, financial institutions must maintain a register of information covering all contractual arrangements for the use of ICT services provided by third parties (Article 28(3)).

DNB requests the register every March as the starting point for the EU process of designating critical third-party ICT service providers. The AFM says the register also covers intra-group outsourcing and contracts with advertising platforms.

To DNB, in xBRL-CSV with a table-oriented layout, or through a standardised Excel template that DNB converts itself. The AFM states that, from 2026, registers must be submitted in xBRL-CSV and Excel will not be accepted. The ESAs publish the validation rules and a representation of the data model.

Technical and data quality checks follow submission; you correct errors by resubmitting the report. In 2026, the EBA carried out additional checks on the consolidation structure (B_01.02) and third-party providers (B_05.01).

DNB wrote in 2024 that information about ICT contracts comes from several existing administrative systems and is often not managed centrally. It usually involves contract management, procurement and supplier records, the CMDB containing ICT services, and the group structure.

The AFM identifies a foreign-key error as the most common reason for rejection: a reference to a key that does not exist. That is why we check referential integrity and identifiers such as the LEI before upload, drawing on our work in data quality.

To DNB through Mijn DNB, using the Major ICT-incidents notification (Article 19(1) and Article 23). Institutions covered by NIS2 must also report the incident to the NCSC. Since mid-April 2026, DNB has validated each report stage — initial, intermediate and final — against technical requirements.

We make sure timestamps, classifications and affected services come from your ITSM and monitoring data, so each report stage is based on the same data and any resubmission comes from the same source.

An overview of ICT services by critical or important function, showing the suppliers and subcontractors behind them; dependence on a single provider; incidents by service over time; and the status of checks on the register.

We build these in Power BI using the same model as the register, with lineage from source to field. If you use AI in these processes, the arrangements for it belong in AI governance.

If you have few ICT contracts, everything is in one contract management system and your submission comes back without errors. In that case, a well-maintained list is enough, and we will tell you so.

For interpreting the regulation or assessing compliance, turn to your compliance department, your lawyers or your supervisory authority. We provide the underlying data and technology.