
DORA requirements: Which roles financial entities need
7

Morten Laufer
Founder
DORA has been in force since 17 January 2025, requiring banks, payment institutions, and fintechs to have robust ICT resilience. We map the roles you need to fill across each of the five pillars, showing where internal structures are sufficient and where external talent can achieve compliance faster. Nova Search recruits precisely these DORA and compliance roles within the fintech sector.
DORA (Regulation (EU) 2022/2554) consolidates requirements across five pillars, ranging from ICT risk management to third-party risk.
Hardly any institution implements DORA completely evenly; the FinmadiG provides for fines of up to five million euros for violations.
From 1 January 2027, non-CRR KWG institutions will only apply the simplified ICT risk management framework pursuant to Art. 16 DORA.
Institutions often have to adapt hundreds of ICT contracts to DORA, which requires dedicated third-party management.
Profiles that combine DORA expertise with banking and payments domain knowledge are scarce; specialised recruitment speeds up hiring.
What requirements does DORA impose?
DORA, Regulation (EU) 2022/2554 on digital operational resilience for the financial sector, came into force in 2023 and has applied since 17 January 2025. The German accompanying legislation, the Financial Market Digitalisation Act (FinmadiG), supplements responsibilities and broadens the scope of application. Since early 2025, internal audit, statutory auditors, BaFin, and the European supervisory authorities have also been reviewing whether institutions are genuinely meeting the requirements.
In terms of content, the Regulation bundles obligations into five pillars:
ICT risk management: a framework of strategies, policies, procedures, and controls overseen by the management body
ICT incident management: detecting, classifying, and reporting major incidents to supervisors
Digital operational resilience testing: regular testing, with threat-led penetration testing for selected institutions
ICT third-party risk management: minimum contractual requirements, registers, and governance of all ICT service providers
Oversight framework for critical ICT third-party service providers: direct supervision of systemically important providers
Two points turn DORA into a staffing issue. First, the management body bears ultimate responsibility for ICT risk management, defines and oversees the framework, and its members must actively keep their ICT skills up to date (Art. 5 DORA). Second, the required resilience strategy goes deeper into substantive matters than the previous IT strategy under BAIT, while sectoral outsourcing rules like MaRisk continue to apply in parallel.
The hook for the budget: FinmadiG classifies violations as administrative offences, carrying fines of up to five million euros. This is not legal advice, but rather the benchmark scale against which you should align your role planning for 2026.
Who is covered by DORA?
Article 2(1) DORA defines who must meet the requirements; exceptions are set out in Article 2(3) in conjunction with Article 3. The catalogue covers almost the entire financial sector:
Credit institutions
Payment institutions
Investment firms and trading venues
Insurance and reinsurance undertakings
Crypto-asset service providers
Institutions for occupational retirement provision and data reporting services
For payment institutions and licensed fintechs, this means DORA applies even if the team is small. The specific obligations depend on an institution's size and interconnectedness; we clarify the exemptions for micro and small institutions in detail below.
The second group comprises ICT third-party service providers. While they are not supervised as financial entities, they are held accountable via the contractual minimum contents under Article 30: cloud services, IT consulting, data processing, and hardware services all fall under this, and providers classified as critical are additionally subject to direct oversight by the European authorities. A nuance: if a supervised financial entity provides a regulated financial service to another, this does not count as an ICT service in terms of third-party risk management (Art. 3 DORA). Anyone serving banks as a fintech should understand this distinction before building registers and contracts around it.
In Germany, the FinmadiG extends the scope of application to insurance holding companies and institutions under Section 1(1b) of the German Banking Act (KWG). Non-CRR KWG institutions only need to implement the simplified ICT risk management framework under Article 16 instead of the standard framework in Articles 5 to 15, do not have to perform threat-led penetration tests, and can skip third-party obligations if they qualify as microenterprises. These obligations apply from 1 January 2027, though reporting requirements have already been active since 17 January 2025.
What roles are needed to implement DORA?
DORA doesn’t prescribe organisational charts, but it does mandate responsibilities. Once you assign each pillar to a named individual, you have your hiring profile. KPMG's benchmark study highlights where firms across the board are struggling: governance structures are mostly in place, but third-party governance, testing, and operational evidence suffer from a lack of staff and documentation.
Governance and ICT risk control
The framework is the responsibility of an independent control function, typically a risk or compliance manager with DORA knowledge (Art. 6(4) DORA). The profile demands regulatory depth beyond DORA, MaRisk, ZAG, and KWG, along with enough of a payments background to identify critical functions within the business model. In addition, there is documentation: each contractual relationship requires a designated contact person, and contracts including SLAs must be versioned and centrally available (Art. 30 DORA).
ICT third-party management
This is where the heaviest workload arises. A vast number of existing ICT contracts do not meet the stricter requirements and must be updated—often hundreds of contracts per institution in practice. What organisations are looking for are profiles that blend contract management, vendor management, and ICT literacy; we have outlined how to find and hire a GRC manager in a separate post.
Information security and incident management
Testing, classification, and reporting require security engineering close to the CISO role: a risk-based testing programme, threat-led penetration testing at least every three years for selected institutions, and initial, intermediate, and final reports in the event of major incidents (Art. 19(4) DORA). This is precisely where the talent market is stretched: the Lünendonk study with KPMG paints the same picture: 97 per cent of surveyed financial firms consider digital resilience important, but only 12 per cent rate their own maturity level as very high. We compare options from permanent hires to vCISOs in the linked article on the CISO role.
DORA Pillar | Role in the institution | Core task |
|---|---|---|
ICT risk management | Risk or compliance manager | Lead framework, control function, and documentation |
ICT third-party risk | Vendor and contract management with Legal and IT | Adapt contracts, maintain tiering, secure exit options |
Resilience testing and incidents | Security engineering close to the CISO role | Manage testing programme, classify and report incidents |
All pillars | Management body | Bear ultimate responsibility, keep knowledge up to date |
Build in-house or hire externally?
The decision comes down to three criteria. First, continuity: the ICT risk management framework isn't a project with an end date, but rather ongoing governance—core roles belong in permanent employment. Second, accountability: you can buy in capacity, but ensuring ICT risk management remains entirely the institution's responsibility (Art. 6(10) DORA). Third, proportionality: smaller institutions are permitted leaner structures, which the simplified framework under Article 16 explicitly allows for.
As permanent hires: risk and compliance leadership, security leadership, and any role with visibility into critical functions
Contracted on a project basis: peak workloads like contract campaigns, building the register, or TLPT preparation
Never outsourced: the ultimate responsibility of the management body
The market makes all the difference. Profiles combining tech or compliance skills with payments and banking domain knowledge are scarce, and the skills shortage hits the very roles that DORA demands. Anyone hiring for such a role in 2026 is competing for a narrow top tier; salary and market data for fintech recruiting help to set salary bands and employer pitches realistically.
This is precisely what permanent recruitment by Nova Search is built for: following a briefing of around 60 minutes covering the role, tech stack, and team culture, you receive a shortlist of three vetted candidates within five business days—screened via in-depth technical assessments and culture interviews, backed by a 90-day guarantee. The role is filled before the next supervisory audit asks for the named individuals.
Sources
FAQ
Since when does DORA apply, and who must implement the requirements?
DORA is Regulation (EU) 2022/2554 on digital operational resilience for the financial sector and has applied since 17 January 2025. It affects financial entities such as credit institutions, payment institutions, investment firms, insurance undertakings, and crypto-asset service providers; ICT third-party service providers are covered through contractual requirements.
What are the five pillars of DORA?
The five pillars are ICT risk management, ICT-related incident management with reporting obligations, digital operational resilience testing, managing ICT third-party risk, and the oversight framework for critical ICT service providers. The management body bears responsibility for implementation.
What roles does a financial entity need for DORA implementation?
Core roles include a compliance or risk manager with DORA expertise for the ICT risk management framework, a specialist for third-party risk management including contract review and the register of information, as well as security engineers or CISO-adjacent roles for resilience testing, incident classification, and reporting.
Do smaller institutions also need to implement the full DORA framework?
No, DORA follows the principle of proportionality. Non-CRR institutions under the German Banking Act (KWG), such as guarantee banks, will only apply the simplified ICT risk management framework under Art. 16 DORA from 1 January 2027; microenterprises are exempt from ICT third-party risk management. Incident reporting has already been mandatory since 17 January 2025.
How many contracts need to be updated for DORA?
The number depends heavily on the size of the institution: large firms and groups manage several hundred to thousands of ICT contracts, while smaller institutions have significantly fewer.
What happens if DORA requirements are not met?
In principle, fines may be imposed, which can amount to up to five million euros depending on the nature and severity of the breach. However, supervisory authorities can weigh their response in line with the proportionality principle for smaller firms. This does not constitute legal advice; you should seek legal counsel for an assessment of individual cases.
Is it better to fill DORA roles via permanent employment or external hiring?
For ongoing responsibilities such as ICT risk control and information security, permanent employment is preferable, as regulations require continuity and designated accountable individuals. Since candidates with tech or compliance skills combined with banking domain expertise are scarce, many institutions collaborate with specialised recruitment consultancies such as Nova Search, which has been filling fintech and compliance roles since 2018.

