Lex specialis under Section 28(6) BSIG explained

DORA vs NIS2: Key Differences, Overlaps & Compliance Strategy

For financial entities, DORA takes precedence over NIS2 as lex specialis: in Germany the core BSIG obligations do not apply to them (Section 28(6) BSIG).

  • 01Clear delineation of application scopes and regulatory focuses
  • 02Identification of synergies and efficiency potentials in implementation
  • 03Strategic roadmap for coordinated compliance implementation
  • 04Less duplicate work through shared processes and evidence
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

NIS2 vs. DORA: Key Differences, Lex Specialis and Compliance Strategy

DORA takes precedence over NIS2 for financial entities as lex specialis: wherever the two overlap, DORA applies, and in Germany Sections 30, 31, 32, 35, 36, 38 and 39 BSIG do not apply to financial entities within the meaning of DORA (Section 28(6) BSIG). DORA (Regulation (EU) 2022/2554) has applied since 17 January 2025, NIS2 has applied in Germany through the NIS2UmsuCG since 6 December 2025.

Both target cybersecurity and digital resilience but differ significantly: DORA applies exclusively to the financial sector, requires the initial notification of major ICT-related incidents within 4 hours of classification and no later than 24 hours after becoming aware (NIS2: early warning within 24 hours), threat-led penetration testing (TLPT) for selected financial entities and a register of information on all contractual arrangements with ICT third-party service providers.

We support you in strategic navigation between DORA and NIS2, identify synergies, and develop efficient, coordinated compliance strategies. Our approach maximizes the efficiency of your compliance investments through intelligent framework integration.

6 service modules

Service scope

01

Regulatory Gap Analysis and Framework Mapping

Systematic comparison of all DORA and NIS2 requirements with detailed analysis of overlaps, differences, and specific compliance implications.

  • Complete capture and categorization of all requirements of both frameworks
  • Detailed analysis of overlaps and regulatory synergies
  • Identification of framework-specific requirements and differentiating features
  • Assessment of impacts on existing compliance structures
02

Coordinated Compliance Strategy Development

Development of integrated compliance strategies that efficiently address both regulatory frameworks and optimally utilize synergies.

  • Design of coordinated governance structures for both frameworks
  • Development of unified risk management approaches and processes
  • Integration of incident management and reporting structures
  • Optimization of resource allocation and implementation priorities
03

Scope Analysis and Classification

Precise determination of your exposure under both regulations with detailed analysis of respective application scopes and thresholds.

  • Systematic assessment of DORA classification and requirements
  • Analysis of NIS2 exposure and classification as essential or important entity
  • Assessment of overlaps and dual regulatory requirements
  • Documentation and justification of classification decisions
04

Technical Requirements Integration

Harmonization of technical cybersecurity requirements of both frameworks into coherent, implementable security architectures.

  • Mapping of technical controls and security measures of both frameworks
  • Development of integrated cybersecurity architectures and standards
  • Coordination of penetration tests and vulnerability assessments
  • Integration of monitoring and detection systems for both frameworks
05

Third-Party Management Coordination

Development of coordinated approaches for managing ICT third-party providers considering both regulatory perspectives.

  • Harmonization of third-party risk assessments for both frameworks
  • Development of unified contract standards and due diligence processes
  • Coordination of third-party audits and monitoring
  • Integration of supply chain risk management strategies
06

Continuous Compliance Optimization

Establishment of systematic processes for continuous monitoring, assessment, and optimization of your coordinated DORA-NIS2 compliance strategy.

  • Implementation of integrated compliance monitoring systems
  • Regular assessment of regulatory developments in both frameworks
  • Continuous optimization of synergies and efficiency potentials
  • Proactive adaptation to changing regulatory landscapes

5 phases

Our Systematic Comparison Approach

We develop with you a tailored strategy for optimal coordination of DORA and NIS2 compliance, taking into account your specific business requirements.

  1. Detailed analysis of your exposure under both regulatory frameworks

  2. Systematic comparison of all relevant requirements and overlaps

  3. Identification of synergies and efficiency potentials in implementation

  4. Development of coordinated governance and implementation structures

  5. Implementation of integrated monitoring and reporting processes

Sarah Richter

Your contact

Sarah Richter

Head of Information Security, Cyber Security

10+ years of experience, CISA, CISM, Lead Auditor, DORA, NIS2, BCM, Cyber and Information Security

Strategic coordination of DORA and NIS2 is crucial for an efficient compliance strategy. Our systematic approach identifies synergies and avoids redundancies, enabling our clients to both save costs and sustainably strengthen their resilience.
ADVISORI expert opinion

Our Expertise

  • 01In-depth expertise in both regulatory frameworks and their practical application
  • 02Proven methods for integrating different compliance requirements
  • 03Practical experience with coordinated multi-framework implementations
  • 04Strategic consulting for resource-optimized compliance strategies

Who is really subject to both

Financial entities under DORA belong to NIS2 sectors such as banking and financial market infrastructures, but DORA displaces the core BSIG obligations for them (Section 28(6) BSIG). Groups with companies outside the financial sector and ICT providers serving both financial entities and other industries are the ones genuinely subject to both. For them, coordinated implementation pays off.

6 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about DORA NIS2 Comparison

What is the key difference between DORA and NIS2?

DORA (Regulation (EU) 2022/2554, applicable since 17 January 2025) is sector-specific law for the financial sector and comprehensively governs digital operational resilience there, while NIS2 sets cross-sector minimum cybersecurity requirements for essential and important entities. DORA acts as lex specialis: in Germany, Sections 30, 31, 32, 35, 36, 38 and 39 BSIG do not apply to financial entities within the meaning of Art. 2(2) DORA (Section 28(6) BSIG), including the risk management measures, incident reporting and management duties. The two do not apply in parallel in this respect.

Which companies could fall under both frameworks at once?

This mainly affects companies with mixed business lines, for example a financial group with a standalone subsidiary outside the regulated financial sector that can fall under NIS2 independently of the financial arm. ICT third-party providers serving both financial entities and other NIS2-obligated sectors can also encounter both frameworks, depending on which service is delivered to which customer.

How do you avoid or cleanly separate dual compliance obligations?

The first step is clearly determining which business unit or system component actually falls under DORA and which under NIS2; this determination should be documented and, when in doubt, confirmed with the relevant supervisory authority. Where both frameworks apply, a shared risk management documentation approach that satisfies whichever requirement is stricter at each point works well.

How does DORA differ from the Cyber Resilience Act (CRA)?

DORA targets financial entities and their ICT service providers, governing their organizational and process resilience. The CRA instead targets manufacturers of products with digital elements and mandates security requirements for the product itself, regardless of the manufacturer's industry. A software vendor selling to financial entities can therefore face CRA obligations on its product and, indirectly, DORA-driven obligations through its customer contracts at the same time.

What costs realistically arise from being subject to both DORA and NIS2?

Incremental cost stays limited if a shared risk management foundation is used, since both frameworks share core principles like risk assessment and incident reporting. Additional cost mainly arises where the frameworks require different reporting deadlines or documentation formats and separate processes have to be maintained instead of using one shared template for both reporting paths.

Which NIS2 obligations do not apply to financial entities under DORA?

In Germany, Sections 30, 31, 32, 35, 36, 38 and 39 BSIG do not apply to financial entities within the meaning of Art. 2(2) DORA (Section 28(6) BSIG). Risk management measures, reporting of major ICT-related incidents and management duties then follow DORA, with reports going to the competent financial supervisor, in Germany usually BaFin. The exemption applies per legal entity: a group subsidiary outside the financial sector can still be fully subject to NIS2. The registration obligation under Section 33 BSIG is not among the listed exemptions and should therefore be checked separately.