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 vs European Electronic Communications Code
Eu Regulations / 2026-10-11

NIS2 vs European Electronic Communications Code

NIS2 covers cybersecurity obligations for certain digital infrastructure and communications entities, while the European Electronic Communications Code, Directive (EU) 2018/1972, governs the broader framework for electronic communications networks and services. Security, availability and authority responsibilities should be mapped using both instruments and current national implementation.

Establish the regulated communications service

Identify whether the legal entity provides public electronic communications networks or publicly available electronic communications services, and how that status interacts with NIS2 sector coverage and classification.

A company purchasing connectivity is not automatically regulated in the same way as the provider of the network. Confirm the exact service, licence or authorisation position and Member State rules.

Separate the primary regulatory subjects

The EECC covers regulatory matters such as market access, user rights and aspects of network security and integrity. NIS2 centres on cybersecurity risk management, significant incidents and supervisory arrangements for entities within scope.

The overlap does not convert every EECC consumer protection provision into a NIS2 cybersecurity duty. Map obligations by the applicable provision and responsible authority.

Understand the evolving security regime

NIS2 amended the relationship with existing electronic communications security and incident notification provisions, including removal of the former EECC Article 40 and Article 41 framework through its legislative changes.

Use a current consolidated legal text and national transposition, rather than copying legacy guides that describe the previous EECC security notification system as unchanged.

Evaluate service and infrastructure dependencies

Communications providers should consider management planes, routing, interconnection, privileged operations, power, physical facilities, outsourced maintenance and cyber incident response in light of applicable duties.

The operational network can depend on non-cyber infrastructure. Cybersecurity and service availability planning should clarify responsibilities across technical and business teams.

Maintain accurate incident reporting routes

NIS2 Article 23 concerns significant incidents for covered entities; other communications reporting obligations may apply under separate legal instruments or national rules. Determine the correct trigger and recipient in advance.

Do not assume one incident notice to a telecommunications regulator automatically satisfies CSIRT, personal data breach or other requirements.

Prepare supervisory evidence

Retain scope decisions, assessments of covered services, risk management controls, incident records and authority correspondence. Track legislative updates and guidance affecting public network and communications providers.

Where uncertainty exists about sector rules or competent authorities, obtain advice under the Member State's implementing framework rather than inventing an EU-wide filing procedure.

Points of clarification

Did NIS2 leave the EECC security articles entirely unchanged?

No. NIS2 made consequential changes to the EECC security framework; current consolidated texts and national laws should be reviewed.

Is every business that uses telecommunications subject to the same provider obligations?

No. Legal scope depends on providing regulated networks or services, rather than merely using them.

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.