What is DORA and when did it come into force?
DORA is the Digital Operational Resilience Act, a European regulation that entered into force on 17 January 2025. It requires financial entities to have their digital operational resilience in order. DORA rests on five pillars: ICT risk management, ICT incident management and reporting, digital operational resilience testing, ICT third-party risk, and information sharing. In the Netherlands, DNB and the AFM supervise most entities; critical third parties, such as large cloud providers, fall under a separate supervisory route at European level.
Who does DORA apply to?
DORA applies to almost every financial entity in the EU: banks, insurers, investment firms, pension funds, payment institutions, credit rating agencies, asset managers, managers of alternative investment funds, credit reference agencies and crypto-asset service providers (CASPs under MiCA). Critical ICT third-party service providers are also covered, through a separate route. For smaller entities, proportionality exemptions apply to parts of the regulation; we map these out in the gap analysis.
Do you replace OneTrust, ServiceNow GRC or ProcessUnity?
No. For enterprise GRC, ProcessUnity, OneTrust, ServiceNow GRC, MetricStream, Diligent, LogicGate and Archer are strong products. That is not where we compete, and we would not advise you to switch to them either. What we do build is the custom layer that your existing GRC platform does not solve for your situation: the industry-specific DORA flows, the deep integration with your core banking or policy system, your own risk classification and the connection to your procurement, contract and security systems. Sometimes custom is the only option because there is no GRC suite in place and the licence costs do not fit your scale.
How does the four-hour notification flow work in the system?
When your security operations team classifies an incident as a major ICT-related incident, a draft notification is created in case management with all relevant fields pre-filled: nature, impact on clients, geographical spread, duration, data loss, critical functions involved and affected ICT assets. The system checks against the DORA classification criteria and automatically monitors the deadlines for the initial notification (to the competent authority within the required window), the intermediate notification and the final report. Your CISO or a delegated officer reviews it, completes the open fields and submits. The full trail, including versions, reviewers, approval and any follow-up questions from DNB or the AFM, is recorded in line with the DORA retention requirements.
How does DORA relate to the GDPR and the NIS2 Directive?
DORA, the GDPR and NIS2 overlap in places but differ in scope, legal basis and sanctions regime. The GDPR covers personal data and is broader than financial services. NIS2 covers essential and important entities across a wider range of sectors. DORA is specific to financial entities and goes deeper on ICT resilience and third-party risk. A well-designed DORA environment often also delivers NIS2-relevant data and can feed GDPR-related audit trails. We build the system so that this overlap is actively used, rather than maintaining three separate registers. On the GDPR side, we carry out a DPIA as standard for every large project.
How does the ICT third-party register work for our cloud providers?
For each outsourced ICT service, the register records the provider, the contract, the sub-outsourcers, the data flow, the processing location, the exit strategy and the criticality rating. For critical or important functions, DORA requires additional contractual provisions — covering location, audit rights, sub-outsourcing, exit and information provision, among other things — which we track explicitly in the register so you can see where contracts still need updating. Continuous SLA monitoring compares measured availability against the agreed level and flags when a vendor consistently underperforms. For critical third parties such as AWS, Microsoft Azure or Google Cloud, we also document the exit route and the fallback option.
What will resilience testing look like in software form?
DORA requires regular digital operational resilience testing and — for entities that meet certain criteria — Threat-Led Penetration Testing (TLPT) on critical functions every three years. The software supports the planning, scoping and reporting of those tests: which critical function is tested when, which scope has been agreed with the competent authority, which red-team provider carries it out, which findings are open and what the remediation status is. We don't carry out the penetration test ourselves — we work with specialist red-team firms for that — but we make the cycle demonstrable and manageable.
What if we are a critical ICT third-party service provider?
If European supervisors designate your organisation as a critical third party, parts of your activity fall directly under European oversight, with separate reporting requirements and the possibility of a Joint Examination Team. This mainly affects large cloud providers and specialist ICT service providers that create deep dependencies for financial entities. For this role, we build a mirror environment: a register that matches the specific information requests the ESAs can issue, plus the automated reporting flow to Frankfurt or Paris instead of DNB.
What determines the cost of a DORA project?
Four things: the breadth of the scope (one pillar versus all five), the number of integrations with external and internal systems (core banking, policy administration, your GRC suite, SIEM, procurement), the stringency of your supervisory regime and the complexity of your ICT landscape, and whether you hand monitoring and further development over to us or take it on in-house. We outline the range in the first conversation and always provide a fixed sprint price, so there are no surprises. For context on how we build up our pricing, see our page on
building insurance software and the wider knowledge base.
Do you also build for pension funds, payment institutions and crypto-asset providers?
Yes. For pension funds, the focus is often on the third-party register and the incident flow around the pension administrator. For payment institutions, it is on incident reporting linked to PSD2 outage notifications and the ICT risk classification of the payment chain. For crypto-asset service providers — which fall under both MiCA and DORA — we often build a combined environment in which the DORA pillars sit alongside MiCA requirements such as safekeeping controls and market abuse detection. For related AI governance questions at the same institution, see our page on
AI Act compliance software.
How does the transition from our current Excel trackers and SharePoint work?
In phases. We run your existing registers, shared drives and SharePoint folders in parallel with the new system for a while, so the team can get used to it and we can spot any shortcomings early. We handle data migration with scripts we write for your situation: ICT assets, critical functions, suppliers, historical incidents and risk acceptances are transferred in a controlled way, with a rollback option if anything goes wrong. Only once the team is comfortable and the first internal audit has gone successfully are the old registers archived.