An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 for Banks
High Criticality Sectors / 2026-10-11

NIS2 for Banks

NIS2 Annex I lists credit institutions under its banking sector, but the relationship with the Digital Operational Resilience Act (DORA) is essential. For financial entities covered by DORA, its ICT risk-management, incident-reporting, resilience-testing and ICT third-party-risk provisions operate as sector-specific rules in the areas addressed by NIS2 Article 4. Banks should not treat NIS2 and DORA as two identical reporting checklists.

Which banks fall within the Annex I definition

The banking entry in Annex I identifies credit institutions as defined in Article 4(1) of Regulation (EU) No 575/2013. It is not a generic label for every company offering payment services or financial technology. First identify the licensed legal entity and its regulatory category. Then assess how the NIS2 scope and classification provisions interact with the financial-sector rules applicable to that institution.

Understand the NIS2 and DORA relationship

NIS2 Article 4 addresses sector-specific Union acts that require cybersecurity risk-management measures or incident notifications of at least equivalent effect. DORA is the principal dedicated ICT operational-resilience framework for covered financial entities. Its rules apply from 17 January 2025 and include governance, ICT risk management, major incident reporting, resilience testing and ICT third-party-risk management. The bank should establish which duties are addressed under DORA rather than duplicating equivalent NIS2 requirements without analysing Article 4.

Protect core banking services and dependencies

Banks rely on account and transaction systems, digital channels, payment connectivity, identity services and external ICT providers. A resilience programme should map these dependencies and consider availability, integrity and confidentiality consequences. DORA requires a documented ICT risk-management framework and proportionate controls, including detection, response, recovery and testing. Cybersecurity governance should connect technology findings with the banking services affected, not merely count alerts or software vulnerabilities.

Coordinate incident decisions and authorities

DORA has a specific major ICT-related incident classification and reporting regime for covered financial entities. Do not assume that the generic NIS2 Article 23 timeline is an additional parallel duty for an incident already addressed by the sector-specific equivalent framework. Identify the appropriate financial competent authority, classification criteria, reporting channel and internal decision-makers. Other obligations may still apply in particular circumstances and need separate legal assessment.

Keep a clear obligations and assurance map

Record the licensed entity, its Annex I classification rationale, DORA applicability, competent authority and relevant service inventory. Map governance and ICT risk controls to the correct legal instrument and preserve evidence of testing, supplier oversight and remediation. Review the analysis after restructuring or a change in regulated services. A compliance matrix should explain the legal basis for each obligation instead of combining all EU rules into one unqualified checklist.

Points of clarification

Does NIS2 Annex I include banks?

Yes. It identifies credit institutions defined in Regulation (EU) No 575/2013.

Does a bank need to file every ICT incident under both NIS2 and DORA?

Not automatically. NIS2 Article 4 and the sector-specific DORA reporting framework require a careful assessment.

When did DORA begin applying?

DORA has applied since 17 January 2025.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.