Service · Software development

Custom DORA compliance software development.

Custom software for the five pillars of the Digital Operational Resilience Act: ICT risk management, incident reporting within four hours, resilience testing, a third-party register and threat intelligence sharing. We don't replace ProcessUnity or OneTrust at enterprise level, but we build the layer that connects your core systems, your own risk model and your DNB or AFM reporting.

ICT risk registerIncident reportingThird-party registerResilience testing

Custom DORA compliance software: what we do and don't do.

The Digital Operational Resilience Act (Regulation (EU) 2022/2554) came into force on 17 January 2025 and affects virtually every financial entity in the Netherlands: banks, insurers, investment firms, pension funds, payment institutions, credit rating agencies, asset managers and crypto-asset service providers. Critical ICT third-party service providers, such as the large cloud vendors, also fall under direct supervision by the European supervisory authorities via a separate route. In the Netherlands, DNB and the AFM supervise most entities.

Good enterprise platforms already exist for the GRC work around it: ProcessUnity, OneTrust, ServiceNow GRC, MetricStream, Diligent, LogicGate and Archer. If your organisation already uses such a suite and it fits, we advise you to keep using it. We don't want to get in the way of that, and we rarely recommend replacing a platform as a standalone solution for DORA.

What we do build is the custom layer that your existing GRC platform doesn't solve for your situation: a DORA register that connects to your ICT landscape and your own risk classification, an incident management flow that prepares the right report for the competent authority within DORA's four-hour deadline, a third-party register with deep integration into your procurement, contract and monitoring systems, and integration with core banking, investment administration or policy systems that a standard suite doesn't support out of the box. We do this as an addition to KYC/AML software when both projects run in parallel, or as a standalone building block within a broader risk management software project.

If your DORA project runs alongside obligations that apply to the product itself, it touches the Cyber Resilience Act. And because the reporting deadlines in both frameworks start from the moment you identify something, vulnerability management is often the component that needs to be in place first.

Three types of DORA software we build.

Most projects start with one of these three and grow organically as the other pillars mature. In the first conversation, we advise which variant delivers the most for your type of institution, your supervisory regime and your existing ICT landscape.

First engagement · fixed sprint budget

DORA register and ICT risk management

A central register of your ICT assets, critical business functions, supporting processes and their interdependencies, with a risk classification that matches your own established policy. This includes a governance flow for periodic review by the risk function, sign-off by the board of directors, and demonstrable logging for inspection by DNB or the AFM. It doesn't replace your GRC suite, but it does feed it with data that is currently often scattered across spreadsheets and ticketing systems.

Asset registerCritical functionsRisk classificationBoard sign-off
Mid-sized project · fixed sprint budget

Incident management and 4-hour reporting

The software your security operations team uses when a major ICT-related incident has been classified: a case management environment that handles the incident, applies the DORA classification criteria (impact on clients, geographical spread, duration, data loss, reputational damage, economic impact), automatically prepares the templates for the initial, intermediate and final notifications, and tracks the deadlines towards DNB, AFM or the relevant ESA. Includes integration with your SIEM, ticketing system and the communication flows to clients and the press.

DORA classificationNotification templatesSIEM integrationFour-hour tracking
Larger project · fixed sprint budget

ICT third-party register and vendor monitoring

A complete third-party register that maps all outsourced ICT services: contracts, subcontractors, data flows, processing location, exit strategy, criticality rating and ongoing SLA monitoring. Includes due diligence workflows for new suppliers, periodic reassessments, and automatic alerts when a contract does not meet DORA requirements or when measured availability falls short of the agreed level. Deeply integrated with procurement, contract management and monitoring systems for one consistent view.

If you are designated for an advanced resilience test, a separate process follows, with a scope that the supervisor validates. Our page on software for the TLPT process under DORA covers this.

Vendor registerSLA monitoringExit strategyDue diligence

What you get at the end of a project.

A production-ready DORA environment that connects to your existing GRC, security and core systems, plus everything around it so you can manage it yourself or have your IT partner manage it.

  • The DORA environment itselfProduction and staging environments, running in your cloud (Microsoft Azure, AWS or GCP) or managed by us in an EU region with demonstrable data residency.
  • Integrations with your core systemsAPI integrations with core banking, policy administration, investment administration, your GRC suite (ProcessUnity, OneTrust, ServiceNow GRC), SIEM, ticketing system and procurement/contract management.
  • Risk model tailored to your institutionA transparent rules engine that classifies critical business functions, ICT assets, suppliers and incidents according to your own established policy and the DORA Regulatory Technical Standards.
  • Reporting templates for the supervisorInitial, intermediate and final notification formats for DNB, AFM or another competent authority, plus exports for the annual ICT risk report and the third-party register.
  • Codebase and architecture documentationComplete source code in a Git repository, build and deployment instructions and an architecture overview for your IT partner or in-house IT.
  • Audit trail for inspectionDemonstrable logging of every action in the system (who changed which risk classification, who classified which incident, who approved which supplier contract), retained in line with the DORA retention periods.
  • Training for the risk and compliance functionSessions for the CISO, risk officer, compliance officer and first-line staff who assess alerts, plus a short video introduction for suppliers who submit data themselves via the third-party portal.
  • Maintenance contract (optional)Monitoring, backups, security patches, integration maintenance and further development based on new Regulatory Technical Standards or changes in the ESAs' joint examination approach. Fixed monthly price, multiple response time tiers.

When custom is the right choice for your DORA implementation.

Four patterns we see time and again at institutions that approach us as a DORA implementation partner. If you recognise one of them, we would be happy to talk further.

No GRC suite

No ProcessUnity or OneTrust available

You're a small or mid-sized financial entity, such as an investment firm, a payment institution, a crypto-asset service provider or a pension fund, for which the enterprise governance and compliance platforms don't fit in terms of cost and complexity. A leaner, custom DORA environment of your own is then often more efficient than a suite where you don't use 80 per cent but still pay for licences every year.

Fragmented sources

Data lives in five places

Your ICT assets sit in a CMDB, critical business functions in a Visio diagram, suppliers in an Excel procurement list, incidents in the ticketing system and risk acceptances in a SharePoint folder. Nobody has one complete view that maps to the DORA requirements. A custom layer that links these sources and feeds the DORA register from the systems where the truth lives prevents duplicate administration.

Your own risk model

Generic classification doesn't work

Off-the-shelf solutions apply the same DORA classification criteria to a major bank and a specialist asset manager. As a CISO or risk officer, you know your critical functions have a different profile from that standard assumption. A custom rules engine in which you can configure criticality, impact and geographic factors, and which you can justify to DNB, gives you better-substantiated classifications.

Deep integration

Core system integration required

For incident detection and SLA monitoring, a hard-wired feed from the core banking, policy or investment administration system is essential. A standard SaaS product sits apart from your core landscape and only raises a flag once someone enters the data manually. A custom build lets the DORA system read the transaction and availability streams in real time, so a major incident is classified within minutes, not hours.

How a DORA implementation project runs.

1

Introduction and intake

A conversation in which we learn which supervisor you fall under (DNB, AFM or an ESA as a critical third party), which GRC and security tools you currently use, which core systems you run, and where your current flow falls short of the DORA requirements. We also map which integrations are needed with core banking, policy administration, your SIEM and your procurement and contract management. That way, before the scoping workshop, we already know which smart API integrations are part of the project.

2

Discovery, scope and gap analysis

A workshop with the CISO, risk officer, compliance officer and procurement, plus interviews with the people who currently do the ICT risk and third-party work. We map out the current process flows and compare them against the five DORA pillars and the Regulatory Technical Standards. We identify where your existing GRC platform is sufficient and where custom software adds value. At the end, you have a concrete scope, a sprint plan and an initial screen flow for the DORA register or incident management.

3

Building in sprints

We work in two-week sprints and deliver a working, testable version every sprint. The CISO or a delegated owner acts as product owner, and a member of the board or the CRO is the sponsor. Early in the project we test incident management with a tabletop exercise based on a realistic scenario, such as a SaaS supplier going down or a ransomware attack, so we can see where the flow runs rough before the first real four-hour notification arrives. A first pillar is in place after a few sprints; a full DORA implementation across all five pillars runs over a project of several sprints.

4

Rollout, training and ongoing maintenance

A phased rollout to the risk and compliance function, running in parallel with the existing process so that no incident and no supplier review is missed. Training for key users and a short video introduction for suppliers who submit data themselves via the third-party portal. From go-live we handle monitoring, security patches, integration maintenance and further development based on new RTS publications, ITS updates or changes in Joint Examination practice. With every new guideline or supervisory update, we take on the impact analysis and the adjustments at our own cost.

Frequently asked questions about DORA compliance software.

The questions CISOs, risk officers and compliance officers usually ask us before a DORA project begins.

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.

Talk to us about your DORA compliance software.

A no-obligation introductory call of half an hour. We listen to which supervisor you fall under, which GRC, security and core systems you have in place and where the friction is, and we give you direction you can use straight away, even if we don't end up working together.

Edit content