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 Financial Market Infrastructures
High Criticality Sectors / 2026-10-11

NIS2 for Financial Market Infrastructures

NIS2 Annex I identifies operators of trading venues and central counterparties under financial market infrastructures. Their precise legal definitions determine coverage. These financial entities also need to consider DORA, which supplies sector-specific ICT risk-management and major incident reporting obligations, and NIS2 Article 4 on the relationship with equivalent sector-specific Union legislation.

Identify the two Annex I entity types

The financial market infrastructures entry covers operators of trading venues as defined in Directive 2014/65/EU and central counterparties as defined in Regulation (EU) No 648/2012. It does not automatically include every brokerage, investment platform, settlement technology supplier or market-data vendor. Determine who operates the trading venue or clearing counterparty and which legal entity holds the relevant authorisation.

Map the relationship between DORA and NIS2

DORA covers trading venues and central counterparties among its financial entities. Its ICT risk-management, incident reporting, resilience-testing and third-party-risk provisions require an obligations assessment alongside NIS2 Article 4. Where sector-specific EU legislation meets the equivalence conditions, corresponding NIS2 provisions do not apply in the same way. Avoid implying that a central counterparty must use two identical notification regimes without evaluating that legal relationship.

Assess trading and clearing continuity

Trading venues depend on order-management infrastructure, connectivity, market-data flows, time-sensitive processing and controls supporting orderly markets. Central counterparties rely on clearing operations, risk systems, participant communications and settlement dependencies. Cyber risk assessments should connect technology failure to those financial functions and identify single points of failure, critical suppliers, integrity threats and recovery tolerances.

Define incident classification and escalation

A disruption that affects market operation may require technical containment, business continuity decisions and regulatory communication. Covered entities should apply DORA's major ICT-related incident classification and reporting framework, including relevant technical standards, while separately checking any other duties that remain applicable. Preserve impact assessments, affected trading or clearing functions, incident timing and evidence of decisions. Escalation arrangements should involve operations, technology, legal and the appropriate financial authority contacts.

Demonstrate governance and tested resilience

Maintain a current service inventory, risk assessments, management decisions, resilience tests, supplier oversight and corrective-action records. Evidence should reflect the actual functions of the trading venue or central counterparty. Distinguish relevant DORA obligations from NIS2 Annex I sector classification so that control owners can identify the legal source of each requirement.

Points of clarification

What entities are listed under NIS2 financial market infrastructures?

Operators of trading venues and central counterparties.

Does DORA apply to these entities?

Trading venues and central counterparties are financial entity categories covered by DORA, subject to its applicable provisions.

Can NIS2 reporting be assessed without considering DORA?

No. NIS2 Article 4 and DORA's sector-specific provisions need to be considered together.

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.