If you run technology or risk for a bank, insurer, investment firm, or payment institution in the EU, the DORA register of information is probably the single compliance artifact keeping your team up at night. It is the inventory of every ICT third-party arrangement your organization relies on, and it is now the first document national regulators pull when they open a supervisory file. Get it wrong — incomplete fields, mismatched contract data, an outdated exit strategy — and it becomes the fastest route to a formal enforcement letter. Get it right, and it becomes a genuine map of your operational risk. This guide explains what the register is, who has to file one, what belongs inside it, the 2026 deadlines, and a practical path to building (and maintaining) one, including where a compliance audit can shortcut the process.
What Is the DORA Register of Information?
The DORA register of information is a structured, continuously updated record of every contractual arrangement a financial entity has with ICT third-party service providers — cloud vendors, SaaS platforms, data centers, managed security providers, and any subcontractor that supports a critical or important business function. It is mandated under Article 28 of Regulation (EU) 2022/2554, better known as the Digital Operational Resilience Act (DORA).
The register exists to solve a specific supervisory problem: regulators previously had no system-wide view of how many banks and insurers were quietly dependent on the same handful of cloud and infrastructure providers. The register of information gives the European Supervisory Authorities (ESAs) and national competent authorities (NCAs) that visibility. It feeds three things directly:
1. Oversight of concentration risk — regulators can see when too much of the financial sector depends on one provider.
2. Designation of Critical ICT Third-Party Providers (CTPPs) — providers deemed systemically important come under direct ESA oversight.
3. Supervisory review of your own ICT risk management — an incomplete or inconsistent register is treated as a governance failure in itself.
Who Has to Maintain a DORA Register of Information?
DORA's scope is deliberately broad. If your organization holds an EU financial services license, you are almost certainly in scope. That includes:
Credit institutions and payment institutions, including e-money institutions and account information service providers.
Investment firms, fund managers, and management companies operating under MiFID or the UCITS/AIFMD frameworks.
Insurance and reinsurance undertakings, including intermediaries above the small-entity thresholds.
Crypto-asset service providers and crowdfunding platforms brought into scope under DORA's extended definitions.
Non-EU entities with an EU branch or subsidiary — DORA's extraterritorial reach means a US or UK-headquartered firm with an EU license has the same obligation as a domestic one.
Critical ICT third-party providers themselves — including major cloud and hyperscaler platforms designated under the oversight framework — face a parallel but separate reporting regime supervised directly by the ESAs, as described by the European Banking Authority.
What's Inside the Register: Templates and Mandatory Fields
This is where most teams underestimate the effort. The register of information isn't a single spreadsheet under Commission Implementing Regulation (EU) 2024/2956, it's a set of roughly 15 interconnected templates that must reconcile with each other before submission. Every ICT provider, contract, service line, and subcontractor needs its own record, cross-referenced by consistent identifiers.
Template areaWhat it capturesEntity & provider identityLegal Entity Identifier (LEI), country, provider type, and CTPP designation status for every direct ICT providerContractual arrangementsOne record per contract: counterparty, reference date, governing law, notice period, and criticality flagServices & business functionsEach contract broken into individual ICT service lines, mapped to the business function each one supportsSub-outsourcingMaterial subcontractors used by providers that deliver critical or important functionsCost dataActual prior-year spend and estimated current-year cost per arrangement, reported in EURCriticality & exit strategyClassification of critical or important functions (CIF) and the documented exit plan for each oneWhat's Inside the Register: Templates and Mandatory Fields
Once populated, the whole package is exported as an xBRL-CSV report — a table-oriented data format with an accompanying metadata file — using the taxonomy published by the ESAs. This is not a format most compliance or risk teams work with natively, which is why register-building is increasingly treated as a joint effort between compliance, procurement, and infrastructure engineering.
2026 Submission Deadlines (and What "Consolidated" Actually Means)
Financial entities don't submit straight to the ESAs — they submit to their national competent authority first, which validates, consolidates, and forwards the data. Deadlines vary by country and sector, but they cluster tightly around Q1 2026:
Jurisdiction / sectorFinancial entity submission window (2026)Netherlands (DNB)By 20–22 March 2026Germany, France, Belgium, Ireland, Italy, SpainBy 31 March 2026Luxembourg (CSSF, via eDesk)11 February – 31 March 2026Insurance/reinsurance undertakings (e.g., CAA-supervised)By 1 March 2026ESA consolidation deadline (all NCAs)31 March 20262026 Submission Deadlines (and What "Consolidated" Actually Means)
According to De Nederlandsche Bank, national competent authorities must forward their fully consolidated registers to the ESAs by 31 March of each calendar year — meaning your own internal submission window will close weeks earlier to give your NCA time to validate the file. Miss the internal deadline and you risk being flagged before the ESA even sees the data.
One detail teams frequently miss: the register isn't a once-a-year exercise. Per ESMA's DORA guidance, the underlying register must be kept continuously accurate — the annual submission is simply a snapshot of a system that should already be current.
Why the Register of Information Is the First Thing Regulators Check
Enforcement moved from "readiness checks" to active supervision in 2026, and Article 28 has become one of the two most frequently examined provisions (alongside Article 5 governance requirements). The financial exposure is real: material non-compliance carries fines of up to 2% of global annual turnover or EUR 10 million, whichever is higher, and individual board members can face personal liability of up to EUR 5,000,000 under national governance provisions. Designated critical providers face their own penalty track, including periodic payments of EUR 500,000 to EUR 5,000,000 per day.
In practice, national competent authorities are now cross-checking register of information data automatically against other regulatory filings. An incomplete provider record, a contract missing a termination notice period, or an exit strategy that was never actually tested tends to surface immediately — and has already become the leading cause of first-round supervisory letters.
How to Build a DORA Register of Information: A Step-by-Step Approach
Whether you're starting from scratch or cleaning up a register assembled under deadline pressure last year, the same sequence applies:
Inventory every ICT third-party arrangement — including shadow IT and SaaS tools procured outside central IT, which are the most common gaps.
Classify which functions are "critical or important" (CIF) — this classification determines how much detail each contract needs and whether sub-outsourcing has to be tracked.
Standardize provider identity data — obtain and validate LEIs for every direct provider; inconsistent identifiers are one of the most common reconciliation failures between templates.
Map contracts to the ITS template structure — decompose each contract into individual service lines and link each to the business function it supports.
Trace sub-outsourcing chains for any provider supporting a critical function, down to material subcontractors.
Document (and actually test) exit strategies for every critical arrangement — a written plan that has never been rehearsed is a common audit finding.
Convert to xBRL-CSV and validate against the ESA taxonomy before your NCA's internal deadline, then establish an owner and a quarterly review cadence so the register never goes stale between annual submissions.
Most of this work is less about compliance paperwork and more about infrastructure visibility — knowing exactly which cloud accounts, environments, and vendors sit behind each business function. Teams that already have clean infrastructure documentation from an IT audit typically move through steps 1–4 in a fraction of the time.
Common mistakes that trigger regulator follow-up
Most register problems trace back to a handful of recurring habits. Teams treat the register as a one-time export instead of a living record tied to procurement and vendor-management workflows, so it drifts out of date within weeks of submission. Subcontractors one or two levels down the chain get missed for critical functions, because nobody owns visibility that deep into a provider's own vendor stack. Exit strategies exist on paper but were never operationally validated, which surfaces the moment an auditor asks for evidence of a test run. And inconsistent LEIs or provider names across templates quietly break the automated cross-checks an NCA runs the moment the file lands.
How Gart Solutions Helps You Get (and Stay) DORA-Ready
Building an accurate DORA register of information is fundamentally an infrastructure and vendor-visibility problem before it's a paperwork problem — you can't document dependencies you haven't fully mapped.
Gart Solutions works with fintech, insurance, and payments teams on exactly that groundwork:
Compliance audits that map every ICT vendor, contract, and subcontractor against DORA's Article 28 requirements before you build the register.
Infrastructure audits that surface shadow IT and undocumented cloud dependencies — the most common source of register gaps.
SRE and disaster-recovery engineering to design and actually test the exit strategies your critical-function contracts require.
Fractional CTO support for teams that need senior technical ownership of the register-building process without adding full-time headcount.
Talk to our team about your DORA readiness
Fedir Kompaniiets
Co-founder & CEO, Gart Solutions · Cloud Architect & DevOps Consultant
Fedir is a technology enthusiast with over a decade of diverse industry experience. He co-founded Gart Solutions to address complex tech challenges related to Digital Transformation, helping businesses focus on what matters most — scaling. Fedir is committed to driving sustainable IT transformation, helping SMBs innovate, plan future growth, and navigate the "tech madness" through expert DevOps and Cloud managed services. Connect on LinkedIn.
The Digital Operational Resilience Act (DORA) and the Network and Information Security Directive (NIS2) have transformed ICT risk from an IT problem into a board-level, legally enforceable responsibility for European financial and critical-infrastructure organisations. With full compliance deadlines already passed (NIS2: 18 Oct 2024; DORA: 17 Jan 2025), the regulatory era has moved from preparation into active supervision. Regulators now expect demonstrable, auditable capabilities to detect, contain, recover and report ICT incidents — quickly and with legal certainty.
This blog post explains
why jurisdictional risk — not just technical security — is the dominant strategic challenge;
the Sovereign Cloud model (operated and governed within the EU by EU legal entities and EU personnel) is the structural answer to that challenge;
automation (SIEM + SOAR with DORA-specific playbooks) is mandatory to meet 24-hour / 72-hour reporting timelines.
Strategic nexus: sovereignty, resilience, and the new EU mandate
The regulatory shift
DORA and NIS2 replace principle-based guidance with prescriptive requirements covering ICT risk management, incident reporting, operational resilience testing, and third-party oversight. The practical effect is twofold:
Immediate operational requirements — fast incident detection, classification, reporting and recovery processes (24-hour initial notification; 72-hour detailed report).
Systemic, upstream impact — regulators now scrutinize the providers that underpin financial services: cloud and other ICT third parties can be designated as Critical ICT Third-Party Providers (CTPPs) and come under direct ESAs oversight.
The core strategic problem: jurisdictional risk
Technical controls alone are insufficient. Legal exposure — the risk that a cloud provider can be compelled by a foreign law (for example, the US CLOUD Act) to disclose data or to operate under extraterritorial commands — creates a material compliance failure for EU-regulated entities. A financial institution that cannot demonstrate legal and enforceable control over its operational data and processes risks regulatory sanctions, regardless of how sophisticated its technical controls might be.
Implication: For regulated entities, ICT risk = technical risk + jurisdictional/legal risk. Solving the latter requires structural, governance and operational realignment — not just encryption and access controls.
II. The geopolitical advantage: mitigating extra-territorial risk with a Sovereign Cloud
Why “data residency” is not enough
Hosting data physically inside the EU (data residency) is necessary but not sufficient. If the cloud provider’s corporate structure or operational control remains subject to non-EU law, the provider can still be legally compelled to disclose data. The Schrems II jurisprudence and DORA/NIS2 expectations make clear that customers must be able to demonstrate legal enforceability of data protection and operational controls.
Sovereign Cloud: fundamentals and safeguards
A credible Sovereign Cloud must combine technical, operational, and legal design choices:
Operational and data localization
Data and logs must be hosted in exclusive EU regions.
Operational activities (monitoring, support, incident forensics) must be performed by EU-resident personnel subject to EU law.
Dedicated EU legal entities and governance
The cloud must be operated by EU-incorporated legal entities with boards and executive control inside the EU.
This structural separation lets the provider lawfully resist or legally challenge extraterritorial demands, creating a legal firewall that is often more effective than purely technical mitigations.
Contractual guarantees (DPA alignment)
DPAs must codify procedures for third-party requests, subcontracting visibility, audit rights and defined incident handling aligned to DORA/NIS2.
A governance committee should maintain and review DPAs and operational procedures to ensure continued alignment with evolving regulation.
Strategic outcome
A Sovereign Cloud removes the primary source of regulatory uncertainty for highly regulated customers, enabling them to demonstrate due diligence before national competent authorities and ESAs. In markets where regulators are focused on systemic concentration and legal enforceability, this structural assurance becomes a competitive differentiator.
III. Automation blueprint: meeting the 24-hour / 72-hour mandates
DORA’s time-critical reporting obligations
DORA imposes strict timeframes:
Initial notification to the competent authority: no later than 24 hours after detection.
Intermediate/detailed report: within 72 hours of the initial notification (or sooner if circumstances change).
These timelines demand rapid triage, classification against regulatory thresholds, automated evidence collection, and securely auditable reporting. Manual processes will routinely fail under these constraints.
SIEM + SOAR: the closed-loop automation stack
A reliable automation architecture has three integrated layers:
SIEM (detection & centralization)
Collects and normalizes logs from cloud, network, applications and endpoints.
Applies correlation rules and baselines to surface anomalies and potential incidents.
SOAR (orchestration & response)
Hosts playbooks that automate enrichment (AD, CMDB, asset ownership), classification against DORA thresholds, containment actions, and reporting workflows.
Automatically composes the initial regulatory notification template and the 72-hour intermediate report, including forensics and mitigation narratives.
Sovereign Cloud enablers
Native, high-fidelity logging APIs and secure retention to guarantee forensic integrity and residency.
Secure channels for digitally-signed submissions to competent authority portals.
DORA playbooks: practical design
24-Hour Playbook — triggered for incidents meeting ‘Major’ thresholds: auto-enrich, auto-classify, populate the regulator template, and submit the signed initial notification within the 24-hour window.
72-Hour Playbook — continues the data collection, correlates mitigation activity, produces the detailed intermediate report and captures artefacts for RCA and learning.
Automation reduces human error, speeds decision cycles, and creates machine-readable audit trails — transforming compliance from an ad-hoc activity into a measurable operational capability.
IV. Supply-chain resilience: how do you manage Critical ICT Third-Party Providers (CTPP)?
DORA’s focus on concentration and systemic risk
DORA recognises that systemic vulnerability can emerge when many financial entities rely on a small number of ICT providers. The regulation grants ESAs powers to designate and supervise CTPPs based on systemic impact, substitutability and concentration of reliance.
Contractual non-negotiables for financial entities
Article 30 and associated requirements define mandatory contractual and oversight elements:
Transparent governance and audit rights — clients and competent authorities must have inspection, audit and access rights commensurate with risk.
Termination & exit strategies — contracts must include enforceable termination rights and tested exit plans when supervision becomes ineffective.
Subcontracting visibility — full transparency into subcontractors and their jurisdictions is required to feed client registers and maintain continuous oversight.
How a Sovereign Cloud addresses CTPP obligations
A structurally sovereign provider directly fulfils many Article 30 expectations: EU governance and operations, pre-agreed audit scope and frequency, contractually guaranteed exit plans and demonstrable counters to jurisdictional interference. This lowers the provider’s risk of CTPP designation friction and simplifies the client’s regulatory reporting.
V. Quantifying the investment: ROI framework for operational resilience
Reframing compliance as strategic value
Boards and investors demand that resilience investment be tied to measurable business outcomes. A robust ROI model includes:
Avoided penalties — quantify the expected value of avoided maximum fines under NIS2/DORA (e.g. €10M or 2% global revenue for essential entities) multiplied by incident probability, then offset by resilience investment cost.
Operational efficiency — measure reductions in MTTD/MTTR, revenue saved per hour of downtime avoided, and FTE productivity gains from automation.
Strategic revenue unlocked — estimate NPV of new contracts and market access that become achievable because of jurisdictional guarantees and regulatory compliance.
Reduced compliance overhead — lower audit and compensating control costs where the Sovereign Cloud offers pre-approved controls and DPA assurances.
Example ROI formula (simplified)
Avoided Cost = (Probability of Major Incident × Maximum Fine) − Cost of Sovereign Cloud Strategy
Total ROI = Avoided Cost + Operational Savings + NPV(New Contracts) − Implementation Cost
Accelerating ROI with pre-integrated services
Providers that deliver both sovereignty and pre-built automation (SIEM + SOAR playbooks) shorten time-to-compliance, reducing implementation risk and accelerating the commercial benefits of market differentiation.
DORA Compliance Playbook
DORA-Compliance-PlaybookDownload
For the full picture of what 2026 enforcement means, download our DORA compliance whitepaper.
VI. Conclusion — a three-point imperative for boards
The combined pressures of DORA and NIS2 have permanently re-ordered the risk calculus for European financial and critical infrastructure organisations. The path to resilient, compliant operation is defined by three imperatives:
Resolve geopolitical/jurisdictional risk — adopt providers with EU legal entities, EU governance and EU-resident operations to ensure enforceability and resist extraterritorial compulsion.
Achieve automation speed — implement SIEM + SOAR with DORA-specific playbooks to meet strict 24-hour and 72-hour reporting mandates.
Re-engineer supply-chain contracts — demand Article 28/30-compliant clauses: audit rights, subcontracting transparency, enforced exit plans and termination mechanics tied to regulatory supervision effectiveness.
Adopting a Sovereign Cloud that couples structural legal assurance with automated incident response converts regulatory obligation into a market advantage: fewer regulatory exposures, faster time-to-reporting, demonstrable audit trails, and new revenue unlocked by compliance credibility. In short, operational resilience should be framed and measured as a strategic growth engine — not merely an IT expense.
Healthcare technology solutions must navigate a complex web of regulations designed to protect patient data and maintain confidentiality, integrity, and availability.
Six significant compliance frameworks that healthcare providers and technology developers must adhere to are HIPAA, CCPA, GDPR, NIST, HiTECH, and PIPEDA.
Let’s take a closer look at each of those frameworks:
What Does HIPAA Compliance Require?
The Health Insurance Portability and Accountability Act (HIPAA) is a critical regulation for any technological solutions developed for the US market. Enacted in 1996, HIPAA mandates the protection of Protected Healthcare Information (PHI). It ensures that electronically protected health information maintains its confidentiality, integrity, and availability. Compliance with HIPAA involves implementing robust security measures to prevent unauthorized access, breaches, and misuse of patient data. This includes encryption, access controls, and regular audits to ensure that all processes align with HIPAA standards.
CCPA Compliance
The California Consumer Privacy Act (CCPA) is another cornerstone of data protection in the United States. Although it primarily targets businesses operating in California, its implications are far-reaching, especially for healthcare providers handling large volumes of personal data. The CCPA focuses on transparency, requiring organizations to inform clients about the data collected, its purpose, and how it will be used. Patients have the right to request a detailed report of their data, demand its deletion, or opt out of data sharing with third parties. Ensuring CCPA compliance necessitates rigorous data management practices and responsive mechanisms to address patient requests promptly.
What Does GDPR Compliance Require?
The General Data Protection Regulation (GDPR) represents one of the most stringent data protection laws globally. Introduced in Europe in 2018, GDPR applies to any healthcare apps and services operating within the European Union. Its reach extends to any company processing data related to EU citizens, regardless of the company's location. GDPR emphasizes patient consent, data minimization, and the right to be forgotten. Healthcare providers must ensure that data is collected and processed transparently, securely, and only for specified purposes. Non-compliance can result in severe financial penalties, making adherence to GDPR a top priority for any organization handling personal health data in Europe.
NIST Compliance
The National Institute of Standards and Technology (NIST) framework is another collection of standards, tools, and technologies designed to protect users’ data in the United States. According to research, 70% of surveyed organizations consider the NIST framework as the best cybersecurity practice, but many say it requires significant investment. The NIST framework is renowned for its comprehensive approach to cybersecurity, offering guidelines for identifying, protecting, detecting, responding to, and recovering from cyber incidents. Implementing NIST standards helps healthcare organizations bolster their security posture, ensuring they can safeguard sensitive health information effectively.
HiTech Compliance
The Health Information Technology for Economic and Clinical Health (HiTECH) Act focuses more on the Electronic Health Record (EHR) systems' data security and is also valid in the United States. Enacted in 2009 and integrated into the HIPAA Final Omnibus Rule in 2013, HiTECH aims to promote the adoption and meaningful use of health information technology. Now, HIPAA-compliant applications are considered HiTECH compliant. This alignment simplifies compliance efforts for healthcare providers, ensuring they meet rigorous standards for data protection and patient privacy across multiple regulatory frameworks.
PIPEDA Compliance
The Personal Information Protection and Electronic Documents Act (PIPEDA) governs cloud storage and other medical software working in the Canadian market. Compliance with PIPEDA is crucial for any healthcare technology solutions operating in Canada. An interesting fact is that if your app is compliant with PIPEDA, it’s most likely compliant with the GDPR since these two laws are quite similar. PIPEDA emphasizes obtaining consent for data collection, ensuring data accuracy, and implementing safeguards to protect personal information. Compliance with PIPEDA helps organizations build trust with Canadian patients and ensures robust data protection practices.
Project Example: Gart's Expertise in ISO 27001 Compliance
Challenges:
Our client, Spiral Technology, faced significant challenges related to data security and cloud migration. The primary concerns were ensuring compliance with ISO 27001 standards and seamlessly transitioning their data and operations to the cloud without compromising security or disrupting their services.
Proposed Solutions:
ISO 27001 Compliance
Gart Solutions provided expert guidance and support to Spiral Technology, helping them achieve ISO 27001 certification. This involved implementing comprehensive security measures, conducting thorough risk assessments, and establishing robust data protection protocols.
Seamless Cloud Migration
To address the challenge of cloud migration, Gart Solutions developed a detailed migration plan that minimized downtime and ensured data integrity, utilizing advanced encryption and secure data transfer methods to protect sensitive information during the transition.
Continuous Monitoring and Audits
For post-migration, Gart Solutions set up continuous monitoring and regular audits to maintain ISO 27001 compliance and address any emerging security threats promptly.
More details about this Case Study – by the link.
Interested in being prepared for a compliance audit & certification - contact Us!
We will help you to understand the specifics and be prepared, as well as from a technology integration and data management perspective.
Conclusion
Compliance in healthcare is an ongoing challenge that requires constant vigilance, investment in technology, and a thorough understanding of regulatory requirements.
By adhering to HIPAA, CCPA, GDPR, NIST, HiTECH, and PIPEDA, healthcare providers can protect patient data, build trust, and avoid costly penalties. As the regulatory landscape continues to evolve, staying informed and proactive in compliance efforts will remain essential for success in the healthcare industry.