Skip to main content

Blog

DORA and NIS2 Compliance Training at Risk Management Summit 2027

Understanding DORA and NIS2

The Digital Operational Resilience Act (DORA) is a regulation directly enforceable across all EU member states, governing how financial institutions manage digital risk. The Network and Information Security 2 Directive (NIS2) is a broader framework applying across critical sectors including energy, transport, health and finance. For financial entities, DORA is the sector-specific framework that takes precedence under a legal principle called lex specialis, which means the specific law overrides the general law.

Wrapping up Day 4 at PulseCore Events on Digital Banking Excellence, we delved into the fascinating world of Artificial Intelligence in the financial sector.
Wrapping up Day 4 at PulseCore Events on Digital Banking Excellence, we delved into the fascinating world of Artificial Intelligence in the financial sector.

Many compliance teams initially assume they must comply with both simultaneously. The reality is simpler: DORA became enforceable for EU financial services organisations from January 2025, and where DORA addresses a matter also covered by NIS2, the DORA provisions take precedence for financial entities.

Who falls under each regulation

DORA applies to financial entities defined broadly across approximately 20 categories, including credit institutions, investment firms, insurance and reinsurance undertakings, payment institutions, electronic money institutions, and crypto-asset service providers. The scope is wide: if you hold a financial services licence or provide critical ICT services to entities that do, you are very likely in scope.

NIS2 applies to essential and important entities across sectors including energy, health, transport, and digital infrastructure, with size thresholds such as 50 or more employees or EUR 10 million or more in annual turnover for important entities.

The overlap exists primarily for credit institutions and financial market infrastructure operators, which are listed as essential entities under NIS2 but are governed by DORA as the sector-specific framework. ICT service providers serving the financial sector may fall under both DORA and NIS2 depending on their own business operations.

The lex specialis principle

The relationship between DORA and NIS2 is governed by lex specialis derogat legi generali—the specific law overrides the general law. This principle means that where DORA addresses a matter also covered by NIS2, DORA's provisions apply to financial entities. NIS2 itself acknowledges this in Recital 28, which states that where sector-specific legislation requires financial entities to adopt ICT risk-management frameworks with equivalent or stronger requirements than NIS2, those sector-specific rules should apply.

For financial entities, this means DORA is your primary compliance framework for digital resilience. You do not need to separately comply with NIS2's cybersecurity risk-management provisions—DORA's requirements are deemed to meet or exceed them. For non-financial entities in NIS2's scope, NIS2 is the governing framework.

Training obligations for boards and staff

DORA's training requirements are embedded throughout the regulation: Article 5(4) requires financial entities to ensure that their management body maintains sufficient knowledge and skills to understand and assess ICT risk, and Article 13(6) requires entities to develop ICT security awareness programmes and digital operational resilience training as part of their ICT risk-management framework. The training must be compulsory for all staff, proportionate to their function, and extended to relevant third-party service providers.

NIS2's training requirement sits primarily in Article 20(2), which requires management body members to follow training sufficient to identify risks and assess cybersecurity risk-management practices. DORA's obligation is wider, covering all staff with role-based content, whereas NIS2 mandates training for the management body and encourages it for broader staff.

Neither regulation specifies a training format, but financial supervisors typically require demonstrated competence—scenario-based training is more effective than compliance documentation alone.

Third-party risk and incident reporting

DORA Chapter V establishes an entire framework for managing ICT third-party risk, including contractual requirements, concentration risk assessment, and for critical ICT third-party providers, an oversight framework led by a designated Lead Overseer from the European Supervisory Authorities. Financial entities must build a register of information compliant with Article 28 of DORA covering all ICT service providers supporting critical or important functions, including service scope, data processing location, criticality level, and the existence of exit strategies.

Under DORA, the deadline for the interim report of 72 hours is calculated from the time the initial report is submitted; you have 24 hours to submit the initial report and then 72 hours for the interim report. Under NIS2, the timeline starts from the moment the entity becomes aware of the incident, making the window for follow-up reporting shorter in practice. This difference can be particularly challenging for ICT service providers covered by both regulations, as the reporting templates and required level of detail also differ between DORA and NIS2.

Building a compliance programme that covers both

If your organisation faces dual obligations, build from DORA outward. DORA's requirements are more detailed and more demanding—a training programme that satisfies DORA's standards will in almost every case exceed what NIS2 requires.

The practical approach is to map your regulatory obligations first through a legal assessment, establish which entities in your group fall under which regulation, and then design your core training programme around DORA's ICT risk-management framework covering risk identification, protection and prevention, detection, response and recovery, and third-party risk management. For entities or business units that fall under NIS2 but not DORA, add NIS2-specific modules addressing incident reporting through the NIS2 channel and supply chain security obligations under Article 21(2)(d).

Practical steps to implement resilience testing

Advanced threat-led penetration testing (TLPT) is mandatory for financial entities designated as systemically important by the competent supervisory authority, based on DORA criteria such as size, complexity, and significance to financial stability. Other entities run basic ICT resilience tests on an annual cycle. The difference between basic ICT resilience testing and advanced TLPT under the TIBER-EU framework should be clarified in implementation planning, and test results translate into concrete remediation actions in the risk register.

Implementation should start with an inventory of ICT assets and critical functions, since that inventory defines the scope of every other pillar including resilience testing. The starting point is classifying critical functions, then designing an incident reporting procedure aligned with RTS/ITS deadlines, and finally planning a resilience testing programme matched to the institution's risk profile.

Common implementation challenges

Given the complexity of the regulations and the strict deadlines, organisations should take five essential steps for preparing for a cyber incident: develop an incident response plan that includes procedures, escalation paths, and key contacts; identify the most critical assets and assess the risks associated with them; implement monitoring and detection systems to identify incidents as early as possible; clearly assign roles and responsibilities both internally and for external service providers; and conduct regular staff training and simulation exercises to build awareness and readiness.

Having an incident response plan is important, but it must be tested in practice, and it should be clear beforehand who has which role during an incident, from the cybersecurity teams to the C-suite and the board of directors.

Getting ready for 2027

DORA compliance was due on 17 January 2025. Many organisations are now in their mature implementation phase, moving from one-time remediation to continuous compliance. For 2027, the focus shifts to demonstrating evidence of resilience testing, documented third-party oversight, and effective incident classification and response. Senior risk, compliance and audit leaders are gathering at events such as the Risk Management Summit 2027 in Amsterdam (25–27 May) to discuss how to operationalise DORA alongside cyber supervision, fraud defence, AMLA transition, and credit and liquidity stress testing.

Day 3 at PulseCore Events on Digital Banking Excellence was a dynamic journey filled with insights from industry leaders. Theme was Fintech!
Day 3 at PulseCore Events on Digital Banking Excellence was a dynamic journey filled with insights from industry leaders. Theme was Fintech!

The key challenge is not just compliance documentation but operationalisation—turning static compliance policies into continuous capability across CISO, CRO and legal teams. Organisations should also prepare for emerging DORA-related topics such as how the EU AI Act meets DORA requirements and governance over third-party machine learning dependencies, particularly as agentic AI becomes more prevalent in banking.

Frequently asked questions

How do I determine whether my organisation falls under DORA or NIS2?

DORA applies if you hold any of approximately 20 types of financial services licence—credit institution, investment firm, insurance undertaking, payment institution, crypto-asset service provider, and many others. If you are a financial entity, DORA is your primary framework regardless of NIS2 status. For non-financial organisations in critical sectors, check NIS2's coverage across sectors and size thresholds (50+ employees or EUR 10 million turnover for important entities). If you are unsure, treat DORA as the higher standard and build your compliance programme from there.

When was the DORA compliance deadline, and what happens if we are not yet compliant?

The DORA compliance deadline was 17 January 2025. Many member states and supervisors are currently in an enforcement period where they are building maturity assessments rather than applying penalties immediately. However, this period is temporary. Organisations that have not begun implementation should do so immediately. The key requirements—ICT risk management framework, incident reporting procedures, resilience testing, and third-party risk oversight—are non-negotiable, and supervisory expectations are rising.

What is the difference between basic ICT resilience testing and threat-led penetration testing (TLPT)?

Basic ICT resilience testing is annual vulnerability assessment and security testing required for all financial entities. Threat-led penetration testing is advanced, targeted testing mandated for entities designated as systemically important by regulators. TLPT involves live red-teaming under supervision, drawing on threat intelligence and testing defensive response capability under realistic attack scenarios. TLPT is more resource-intensive and requires specialist external providers. Determining which category your organisation falls into is part of the ICT risk management framework scoping exercise.

What penalties apply for DORA non-compliance?

Financial supervisory authorities can impose administrative penalties, require remediation plans, and in extreme cases restrict an institution's scope of activity. The specific penalties vary by member state and competent authority. Beyond formal sanctions, non-compliance increases operational risk from unmanaged ICT incidents and provider dependencies—the real cost of DORA non-compliance is not the fine, but the incident your controls fail to prevent.

Sources

  1. DORA Implementation Training for Financial Institutions | EITT
  2. DORA vs. NIS2: Which Applies to Your Organisation?
  3. Navigating DORA and NIS2 Compliance for Financial Sector Organisations in the EU
  4. DORA & NIS2 Compliance Training UK | Advanced GRC Course
  5. Schedule – Risk Management Summit 2027
  6. DORA Financial Operational Resilience Summit 2027 | Frankfurt
  7. Tickets – Risk Management Summit 2027

Share this article

Blog