DORA for EU Banks: The Cybersecurity Stack, Costs and Testing Cycle It Requires
DORA turned bank ICT resilience into a funded, supervised program. This guide covers the tooling, contract work, TLPT cycle and indicative budgets by bank size, plus what non-EU groups with EU entities owe.
What DORA cybersecurity requirements for banks actually make you pay for
The Digital Operational Resilience Act (Regulation (EU) 2022/2554) has applied since 17 January 2025. For EU credit institutions, compliance itself is settled. What's still open is whether the current program will hold up when a supervisor asks for evidence. Most banks ran their first round of DORA work as a legal and policy exercise. The real costs land in the 2026–2027 budget cycles: tooling, contract renegotiation, register maintenance and, at larger banks, threat-led testing.
DORA cybersecurity requirements for banks sit in five pillars, and each costs money in a different way:
- ICT risk management (Articles 5–16): governance, asset inventory, protection, detection, response, backup and recovery, with the management body accountable.
- ICT-related incident management and reporting (Articles 17–23): classification against harmonized criteria, with fixed reporting deadlines.
- Digital operational resilience testing (Articles 24–27): an annual testing program for every bank, plus threat-led penetration testing (TLPT) for the banks authorities select.
- ICT third-party risk (Articles 28–44): contract clauses, exit plans, concentration risk, the register of information and EU oversight of critical providers.
- Information sharing (Article 45): voluntary threat-intelligence sharing arrangements, which you have to notify to your supervisor.
Most of the detail is in the regulatory and implementing technical standards (RTS and ITS): ICT risk management, incident classification, the register of information and TLPT. Map your controls to those texts as well as to the regulation. Supervisors test against whatever the standards prescribe.
Where bank ICT risk management stacks usually fall short
Most EU banks already ran ISO 27001-style programs or followed national rulebooks such as Germany's BAIT, which BaFin has phased out for DORA-scope institutions. So the gaps are rarely about missing firewalls. They're about evidence, ownership and coverage.
Four gaps turn into spend more often than the rest:
- Asset and dependency mapping. DORA expects you to identify every ICT and information asset behind a critical or important function and map how those assets depend on each other. Past a few hundred applications, spreadsheets can't keep up. Banks usually extend a CMDB (ServiceNow is common) or add a dedicated dependency-mapping tool.
- Detection and logging. The ICT risk management RTS sets expectations for logging, anomaly detection and network monitoring. If your SIEM is thin or only covers on-premise systems, expect to pull cloud and SaaS logs into a platform such as Microsoft Sentinel, Splunk or Google Security Operations, or into a managed SOC.
- Backup and recovery testing. You'll need backups that are immutable or logically separated, plus recovery tests that record RTO and RPO results. That often means new storage and orchestration spend.
- Management body training. Board members need enough ICT risk knowledge to approve the framework. Training is cheap to deliver and easy to document badly, and supervisors check the documentation.
Article 16 offers a simplified framework, but only for a narrow set of entities. Most credit institutions don't qualify. Banks that do get a lighter control stack, but incident reporting and third-party obligations still apply.
DORA incident reporting: the four-hour clock and the workflow it forces
DORA replaced a patchwork of national, PSD2 and ECB incident reporting with one classification scheme and one timeline. Classification is the hard part. The RTS scores incidents on clients affected, data losses, duration and downtime, geographic spread, economic impact and whether critical services were hit. An incident is major when it meets set combinations of those thresholds.
| Report | Deadline | What it needs |
|---|---|---|
| Initial notification | Within 4 hours of classifying the incident as major, and no later than 24 hours after becoming aware of it | Basic facts, classification criteria met, initial impact |
| Intermediate report | Within 72 hours of the initial notification, updated when the status changes significantly | Root cause hypotheses, impact detail, recovery measures |
| Final report | Within one month of the latest intermediate report | Root cause analysis, costs and losses, lessons learned |
Four hours isn't enough to assemble a classification by email. The banks that meet the deadline build the DORA criteria into the incident workflow itself, usually in ServiceNow, Jira Service Management or a GRC platform, so analysts record client counts and downtime while the incident is still running. DORA also lets you report significant cyber threats voluntarily, and it requires you to tell affected clients about major incidents.
Red flag: if your SOC provider or outsourced IT vendor won't commit in the contract to delivering classification data within one to two hours, you can't count on meeting the deadline.
DORA ICT third-party risk: contract remediation and the register of information
For most banks, third-party risk is the most labor-intensive pillar. It pulls in procurement, legal and every business line that buys software.
Contract remediation. Article 30 sets minimum clauses for every ICT services contract. These include a clear service description, data processing locations, availability and integrity commitments, help during incidents, cooperation with authorities and termination rights. Contracts behind critical or important functions need more: full service levels with quantitative targets, notice periods, the provider's participation in your TLPT, unrestricted access, inspection and audit rights, and exit strategies with transition periods. Large vendors, including the major cloud providers and several core banking suppliers, have published DORA addenda. Smaller vendors often haven't, and they negotiate slowly. Start with them.
The register of information. The register ITS defines a structured, multi-table dataset. It covers every ICT contractual arrangement, each provider's legal entity identifier (LEI), the functions supported, subcontracting chains and substitutability. National authorities collected the first submissions in 2025 and passed them to the European Supervisory Authorities (ESAs). Reporting is now annual. The ESAs used that data to designate the first critical ICT third-party providers (CTPPs) in late 2025. Those providers are now under direct EU oversight, but that doesn't reduce your own obligations as a customer.
Banks struggle most with data quality. Common validation failures included missing LEIs, inconsistent function identifiers and incomplete subcontracting chains. Several TPRM and GRC vendors, including OneTrust, Mitratech Prevalent, ServiceNow, Archer and MetricStream, sell DORA register modules. Check that a vendor's export matches the current ESA taxonomy and validation rules before you buy. Above a few hundred ICT contracts, a maintained tool usually costs less than rebuilding the register by hand every year.
Running a TLPT cycle from scoping to attestation
Every bank needs an annual resilience testing program. That means vulnerability scanning, scenario-based testing, network security assessments and, where relevant, source code reviews. Threat-led penetration testing is a separate and much heavier requirement. Authorities decide which entities must run TLPT based on systemic importance and ICT risk profile, and G-SIIs and O-SIIs are the usual starting point. Selected banks test at least every three years, on live production systems that support critical functions. The TLPT RTS follows the TIBER-EU framework closely.
| Phase | Typical duration | Key outputs |
|---|---|---|
| Preparation | Roughly 2–4 months | Scope approved by the TLPT authority, control team in place, providers procured |
| Threat intelligence | Roughly 1–2 months | Targeted threat intelligence report and attack scenarios |
| Red team testing | At least 12 weeks of active testing | Red team test report |
| Closure | Roughly 2–3 months | Blue team report, purple team replay, test summary, remediation plan, attestation |
Allow 9–14 months from kickoff to attestation. Internal testers are allowed under conditions, but external testers have to run at least every third test, and the RTS expects threat intelligence to come from an external provider. ICT providers in scope have to take part, which is why the TLPT participation clause in your contracts matters. Pooled testing with a shared provider is allowed but takes a lot of coordination.
When you hire testers, require a demonstrable TIBER or CBEST track record, named and vetted team members, professional indemnity cover and written rules for handling your data. Both large consultancies and specialist red-team firms can meet that bar. Book early. Qualified red-team capacity is limited, and it gets tighter when many banks' three-year cycles line up.
Germany, France and the Netherlands: how supervision differs in practice
DORA is a regulation, so the obligations are identical across the EU. What varies by country is supervisory style, reporting channels and how TLPT is run. Significant institutions under the Single Supervisory Mechanism also answer to the ECB, which has named ICT and third-party risk among its supervisory priorities.
- Germany. BaFin supervises and the Bundesbank runs TIBER-DE. BAIT no longer governs DORA-scope institutions, but MaRisk still covers related outsourcing and risk topics. Audits tend to be detailed and documentation-heavy, often through Section 44 KWG inspections. German banks with mature outsourcing registers usually start the register of information ahead, but they often have to reconcile outsourcing definitions with DORA's ICT definitions.
- France. The ACPR supervises and the Banque de France leads TIBER-FR. Expect close scrutiny of governance and of how involved the management body really is. Groups with insurance arms have to align their DORA work across the banking and insurance sides of the ACPR.
- The Netherlands. DNB adopted TIBER early, so many Dutch banks already have red-team cycles behind them. DORA TLPT will feel familiar, but scope and documentation still have to match the RTS. The AFM covers conduct-side entities in the same groups.
In smaller markets, including the Baltics, Central and Eastern Europe and parts of Southern Europe, the national authority's TIBER setup and supervisory capacity affect how fast TLPT designations arrive. Don't assume you're exempt. Ask your supervisor what TLPT timeline it expects.
Indicative DORA budgets by bank size
The ranges below are typical 2026 market ranges in USD, covering annual run costs plus remediation. They vary widely with existing maturity, contract volume and the terms you negotiate, and local pricing differs by country. Use them for early planning and confirm figures with vendors and advisers.
| Cost line | Smaller bank (under ~$10bn assets) | Mid-size bank ($10–100bn) | Large or systemic bank |
|---|---|---|---|
| TPRM/GRC platform and register tooling | $40k–$150k/yr | $150k–$500k/yr | $500k–$2m/yr |
| Contract remediation (legal, procurement) | $100k–$400k one-off | $400k–$1.5m one-off | $1.5m–$5m+ one-off |
| SIEM, logging and detection uplift | $100k–$500k/yr (often a managed SOC) | $500k–$2m/yr | $2m–$8m+/yr |
| Annual resilience testing program | $50k–$200k/yr | $200k–$700k/yr | $700k–$2m/yr |
| TLPT (per test, at least every three years) | Usually not required | $300k–$800k if designated | $500k–$1.5m+ including internal effort |
| Dedicated DORA program staff | 1–3 FTE | 4–10 FTE | 10–30+ FTE |
Three things drive cost more than anything else: how many ICT contracts support critical functions, how fragmented your logging estate is, and how hard your vendors push back on audit and exit clauses. Here's a hypothetical. A mid-size bank has 600 ICT contracts, and 80 of them support critical functions. It will usually spend more on legal hours renegotiating those 80 contracts than on the register tool.
What non-EU banking groups with EU entities owe
DORA applies to EU-authorized financial entities. That includes EU subsidiaries of banks headquartered in the UK, US, Switzerland, Japan, India, the Gulf states and elsewhere. Global groups often miss one point: ICT services from the parent or a group shared-service center count as ICT third-party services. They have to appear in the subsidiary's register of information, and the intragroup agreements behind them have to meet Article 30, including audit rights and exit planning. Proportionality gives intragroup arrangements some leeway. It doesn't remove the obligation.
What this means in practice:
- The EU entity needs its own ICT risk framework, approved by its own management body, even if most controls come from the group. Supervisors want to see local ownership, not a headquarters policy with a new cover page.
- The group SOC has to deliver classification data to the EU entity fast enough to meet the four-hour window, 24/7 and across time zones.
- Group red-team programs, such as CBEST in the UK or exercises run in other jurisdictions, don't automatically count as DORA TLPT. EU authorities recognize each other's TLPT. For tests run outside the EU, you'll need to map scope and documentation to the RTS.
- Branches of third-country banks are in a less clear position that depends on national law and the CRD VI third-country branch regime. Confirm their status with the host supervisor.
Other regimes overlap with DORA. The UK's critical third parties regime, Singapore's MAS technology risk management guidelines, the Reserve Bank of India's IT outsourcing directions and US interagency third-party guidance ask for similar evidence in different formats. Build one control library and map it to each regime. That's much cheaper than collecting evidence separately in every jurisdiction.
Decision rule for your next budget cycle: if your last register of information failed validation or needed heavy manual correction, fund TPRM tooling and contract remediation before you add detection spend. Third-party data is the gap that takes longest to close, and supervisors are now using the register to supervise. Before you commit, have outside counsel confirm your scope, your TLPT status and any intragroup arrangements.
Quick answers
Does every EU bank have to run threat-led penetration testing (TLPT) under DORA?
No. Every bank needs an annual digital operational resilience testing program. TLPT applies only to entities the competent authority identifies, usually starting with G-SIIs and O-SIIs, plus others with a significant ICT risk profile. Selected banks test at least every three years. If you haven't been notified, ask your supervisor about its designation timeline instead of assuming you're out of scope.
How often must the DORA register of information be submitted?
You have to keep the register current at all times and submit it to your national competent authority every year, in the format set by the ESAs' implementing technical standard. Authorities can also ask for it at any time. The validation rules are strict, so many banks keep the register as a live dataset in a TPRM platform instead of rebuilding it once a year.
Do contracts with major cloud providers already meet DORA's Article 30 requirements?
Not on their own. Major cloud providers offer DORA addenda that cover most Article 30 clauses, but your bank still has to check them against its own critical or important functions. Pay particular attention to audit rights, TLPT participation, subcontracting and exit terms. A standard addendum won't reflect your exit strategy or concentration risk, so have legal counsel review the final terms.
Do intragroup IT services count toward DORA third-party requirements?
Yes. ICT services from a parent company or group shared-service center count as ICT third-party services. They have to be recorded in the EU entity's register of information and covered by agreements that meet Article 30. Proportionality allows some flexibility for intragroup arrangements but doesn't remove the requirement. Have counsel review the structure.
Written by the Trustdeskapp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.