CAI Technology
Menu ☰
Annex I β€” Essential Entities Β· Digital Infrastructure

πŸ“‘NIS2 for Electronic Communications Providers β€” deadlines, obligations, fines

Electronic Communications Providers fall under NIS2 (Directive (EU) 2022/2555 + Romanian Emergency Ordinance 155/2024). See Art.21 obligations, deadlines, max fines and compliance roadmap for Annex I.

Last reviewed: Β· CAI Technology Β· echipa Lexnomia + AEGIS

🎯 Who is covered

Providers of public electronic communications networks and providers of publicly available electronic communications services are listed in Annex I to Directive (EU) 2022/2555 (NIS2), in the "Digital infrastructure" high-criticality sector [C1]. Operators that qualify as medium or large enterprises (>= 50 employees or >= EUR 10 million annual turnover / balance-sheet total) are in direct scope as essential entities; in addition, NIS2 Art. 2(2) extends applicability regardless of size to providers of public electronic communications networks / services where they meet specific criticality criteria β€” sole provider in a Member State, possible systemic impact, critical national or regional importance [C2]. In Romania, the transposition was carried out by OUG 155/2024 (the Romanian Emergency Ordinance transposing NIS2, published on 30.12.2024) and approved by Law 124/2025; DNSC (the Romanian National Cybersecurity Directorate) is the competent national authority, cooperating with ANCOM (the Romanian Electronic Communications Regulator) as sectoral regulator [C7][C15]. NIS2 repealed Articles 40-41 of the EECC (Dir. 2018/1972) with effect from 18 October 2024 β€” all integrity / availability incident-reporting obligations are consolidated under the NIS2 regime [C8]. Beyond NIS2, the telecom sector remains subject to Dir. 2018/1972 transposed in Romania by Law 198/2022 (amending OUG 111/2011) [C14], plus Law 506/2004 (ePrivacy + personal data in electronic communications) [C13] and Law 163/2021 (national 5G framework + authorised vendors) [C10].

Examples in Romania

Digi Romania (RCS&RDS) β€” integrated mobile + fixed + Internet operator, present in 5 EU countriesOrange Romania β€” mobile + fixed + Internet operator, part of Orange GroupVodafone Romania β€” mobile + fixed operator, part of Vodafone GroupTelekom Romania Mobile Communications β€” mobile operatorB2B / wholesale carrier providers and MVNOs registered with ANCOM as public providers of electronic communications networks and services

Applicability thresholds

Annex I of NIS2 includes "Providers of public electronic communications networks" and "Providers of publicly available electronic communications services" in the digital infrastructure sector [C1]. General rule: medium and large enterprises (>= 50 employees or >= EUR 10 million annual turnover / balance-sheet total) are in direct scope as essential entities. On top of that, NIS2 Art. 2(2) extends scope regardless of size to public electronic communications providers when they are the sole provider of an essential service in a Member State, when disruption would have systemic or public-safety impact, or when the entity is critical at national / regional level [C2]. Essential vs. important classification and concrete notification thresholds are applied through DNSC Orders 1/2025 and 2/2025 (criteria and disruption thresholds) [C7]. In practice, national integrated operators (Digi, Orange, Vodafone, Telekom Romania) come in as essential; MVNOs and local ISPs typically come in as important, but can be reclassified individually by DNSC.

πŸ“… Regulatory timeline

  1. Adoption of Directive (EU) 2018/1972 (EECC) β€” the pre-NIS2 telecom security framework, Art. 40-41 [C14]

  2. Publication of the EU 5G Cybersecurity Toolbox by the NIS Cooperation Group [C9]

  3. Romania adopts Law 163/2021 β€” authorisation of 5G vendors; basis for excluding high-risk vendors [C10]

  4. Law 198/2022 β€” full transposition of the European Electronic Communications Code into OUG 111/2011 [C14]

  5. Adoption of Directive (EU) 2022/2555 (NIS2) [C8]

  6. Commission communication on the 5G Toolbox implementation; Huawei and ZTE confirmed as presenting materially higher risk [C9]

  7. EU deadline for transposing NIS2 (Art. 41); adoption of Comm. Impl. Reg. (EU) 2024/2690 β€” does NOT cover telecom, only DNS/cloud/CDN/MSP/MSSP etc. [C8][C16]

  8. NIS1 repealed; EECC Art. 40-41 repealed; reporting consolidated under NIS2 [C8]

  9. Romania publishes OUG 155/2024 β€” NIS2 transposition; DNSC = competent national authority [C7]

  10. Law 124/2025 β€” approval of OUG 155/2024 [C7]

  11. ENISA publishes the Telecom Security Incidents 2024 report: 188 incidents in 26 EU MS + 2 EFTA, 1 743 million lost user-hours (more than 50% decrease year-on-year) [C12]

πŸ“‹ Key obligations

ICT risk-management framework based directly on NIS2 Art. 21(2) β€” no sectoral implementing act

effort: high

Providers of public electronic communications must implement the ten minimum measures of NIS2 Art. 21(2)(a-j): risk and security policies, incident handling, continuity and recovery, supply-chain security, ICT acquisition and development (including vulnerability handling), effectiveness assessment, cyber hygiene and training, cryptography, HR security and access control, multi-factor authentication [C3]. Unlike DNS, cloud, CDN, MSP and MSSP, the telecom sector does NOT have a dedicated implementing regulation β€” Reg. (EU) 2024/2690 does NOT cover providers of public electronic communications networks / services [C16]. In practice, derived obligations come directly from NIS2 + the OUG 155/2024 transposition, supplemented for 5G by the measures of the EU Toolbox and Law 163/2021 [C9][C10]. Usual technical framework: ISO/IEC 27001:2022, ISO/IEC 27002, ETSI EN 319401, plus the telecom-specific technical controls from the ENISA EECC guide (still technically relevant after the repeal of Art. 40-41) [C8]. The management body approves and oversees implementation (NIS2 Art. 20) [C6].

Recommended controls: NIS2 Art. 21(2)(a-j)OUG 155/2024ISO/IEC 27001:2022ISO/IEC 27002:2022ETSI EN 319401ENISA Guide on Security Measures under the EECC (technical)

5G EU Toolbox + Law 163/2021 β€” control of 5G technology vendors

effort: high

The 5G EU Toolbox (January 2020) requires identification and management of equipment, software and technology vendors as a key element of 5G network resilience [C9]. In its June 2023 communication, the Commission confirmed that Member State measures restricting or excluding Huawei and ZTE are justified and consistent with the Toolbox, and that these vendors present a materially higher risk than other 5G vendors [C9]. Romania transposed this policy through Law 163/2021, which requires prior authorisation of 5G technology and equipment manufacturers; for entities in the national defence, public order and national security system, purchases from non-authorised vendors are prohibited [C10]. ANCOM may request detailed information on the technologies, equipment and software used in 5G networks, the manufacturer and the degree of outsourcing [C10]. Baseline technical framework: ENISA 5G Security Controls Matrix, aligned with 3GPP [C17].

Recommended controls: 5G EU Toolbox (Strategic + Technical Measures)Law 163/2021 (RO)ENISA 5G Security Controls Matrix3GPP TS 33.501 (5G security)

Incident reporting on a 24h / 72h / 1 month track (NIS2 Art. 23) β€” successor to Art. 40 EECC

effort: high

Until 17 October 2024, integrity / availability incidents in telecom were reported under Art. 40-41 EECC to the national authority (in Romania: ANCOM) [C8]. From 18 October 2024, NIS2 repeals Art. 40-41 and consolidates reporting under Art. 23: early warning to the CSIRT (DNSC) within 24 hours of awareness, detailed incident notification within 72 hours, final report within one month [C4][C8]. For public providers of electronic communications, the obligation to notify users when a particular or significant threat exists to the security of the network or service remains β€” derived from NIS2 Art. 23 and previous EECC practice [C4]. In the aggregated 2024 reporting to ENISA, 26 EU MS + 2 EFTA reported 188 telecom incidents; lost user-hours fell by more than 50% (1 743 million in 2024 vs. 3 906 million in 2023); 58% of incidents had impact on mobile telephony [C12]. Procedurally, Romanian operators now send a single flow to DNSC; coordination with ANCOM on continuity and availability remains through the BEREC Cybersecurity WG [C15].

Recommended controls: NIS2 Art. 23(4)OUG 155/2024 (incident reporting chapter)ENISA Guide on Incident Reporting under the EECC (technical)ENISA Single Information Sharing Point mechanism

SS7 / Diameter / 5G signalling security + routing protection (NIS2 Art. 21(2)(e))

effort: high

The SS7 (2G/3G) and Diameter (4G) signalling protocols were designed without modern security considerations and are vulnerable to interception, redirection, subscriber location tracking and fraud carried out by actors with access to interconnected networks [C11]. ENISA, in a dedicated report on signalling in telecom, classifies the risk level as medium to high and recommends active contribution from all providers [C11]. For 5G, HTTP/2 signalling + NEF API + SBA introduces a new vector (network slicing isolation, service-to-service authentication). NIS2 Art. 21(2)(e) covers security of networks and systems in acquisition / development / maintenance, which for a mobile operator translates into concrete obligations on signalling firewalls, GTP anti-spoofing, inter-PLMN anomaly monitoring and 5G slice isolation [C3][C11]. The lesson from the Salt Typhoon campaign (2024+) is that operators' backbones and edge routers are a direct target for state actors β€” router security (patching, management-plane control, segregation) is part of the NIS2 list, not an optional extra [I4][C9].

Recommended controls: NIS2 Art. 21(2)(e),(b),(j)ENISA β€” Signalling Security in Telecom SS7/Diameter/5GENISA 5G Security Controls Matrix3GPP TS 33.116 / TS 33.117 (SECAM)

Stacking NIS2 + GDPR + Law 506/2004 (ePrivacy for electronic communications)

effort: medium

Providers of public electronic communications process sensitive categories (location data, traffic data, content, identity data) β€” for which Regulation (EU) 2016/679 (GDPR) and, in Romania, Law 506/2004 on the processing of personal data and the protection of privacy in the electronic communications sector apply on top of NIS2 [C13]. In practice, for any incident affecting subscriber confidentiality, the operator must notify in parallel: DNSC under NIS2 Art. 23 (24h / 72h / 1 month) [C4], ANSPDCP (the Romanian Data Protection Authority) under GDPR Art. 33 (72 hours for notification to the authority) and subscribers directly where the risk is high. The lessons from T-Mobile US 2021 [I1], Optus 2022 [I2] and Lyca Mobile 2023 [I5] show the same pattern: an application vulnerability / a compromised account exposed hundreds of thousands to tens of millions of subscriber records. Control framework: strong encryption at rest and in transit (NIS2 Art. 21(2)(h)), granular access control (i), MFA on any administrative access (j), vulnerability handling (e), isolation of CRM and billing systems from the network.

Recommended controls: NIS2 Art. 21(2)(h),(i),(j),(e)GDPR Reg. 2016/679 Art. 32-34Law 506/2004 (RO)ePrivacy Directive 2002/58/EC (consolidated)

πŸ“° Real incidents, concrete lessons

T-Mobile US

2021 Β· United States

Type: Credential compromise + exfiltration of subscriber databases (attributed to an individual attacker identified later)

Impact: Approx. 7.8 million current postpaid customers with personal data (name, date of birth, SSN, ID) exposed; approx. 5.3 million postpaid customers on another dataset (IMEI, IMSI, phone); approx. 40 million former / prospective customers exposed. Class action settlement of USD 350 million. No financial data exposed.

Lesson: Pivot incident for the telecom sector: a lax configuration on a publicly exposed non-prod environment was the entry point. NIS2 Art. 21(2)(e) and (i) require environment segregation, access control and vulnerability handling β€” measures which, had they been implemented, would have blocked the exploitation chain.

Public source β†—

Optus (Singtel Optus, Australia)

2022 Β· Australia

Type: API exposed without authentication; coding error in a legacy endpoint

Impact: Out of 9.8 million Optus customers, approx. 1.2 million with valid ID and complete personal information compromised; 900 000 with expired ID compromised. Data exposed: name, date of birth, phone, email, addresses, passport and driver's licence numbers. The attack was described as "not sophisticated" β€” trial and error on a forgotten endpoint. Dual regulatory probe (ACMA + OAIC).

Lesson: Same root cause class as Salt Typhoon and T-Mobile: asset management lacking control and forgotten / non-decommissioned APIs. NIS2 Art. 21(2)(i) (asset management) and Reg. (EU) 2024/2690 β€” even though it does not cover telecom β€” make it plain that a complete inventory of public endpoints is a minimum practice expected by DNSC under OUG 155/2024.

Public source β†—

Vodafone Portugal

2022 Β· Portugal

Type: Deliberate cyberattack that halted 4G/5G, SMS, fixed voice and TV services

Impact: The entire Vodafone Portugal base (approx. 4 million mobile subscribers + 3.4 million residential and business fixed-services customers) affected; only 3G remained operational, with limited capacity (~3 MB/s); service restoration required extended and careful action. Vodafone Portugal officially described the incident as a "deliberate and malicious attack intended to cause damage".

Lesson: Demonstration that a single incident at an integrated operator can simultaneously take mobile, fixed, TV and SMS networks offline. NIS2 Art. 21(2)(c) (continuity / crisis management) requires periodic scenario testing; for an integrated operator, the crisis plan must include per-service restoration, prioritisation of emergency services (112) and public communications coordinated with the authorities.

Public source β†—

AT&T, Verizon, Lumen, T-Mobile US (Salt Typhoon β€” PRC APT)

2024 Β· United States (global campaign, including the EU and Indo-Pacific)

Type: Persistent state espionage on operators' backbone and edge routers; long-term multi-year access

Impact: AT&T, Verizon and Lumen confirmed compromise in December 2024; the campaign was described by US officials as the "worst telecom hack in our nation's history", with the capability to geolocate millions of people and record calls. T-Mobile US announced it was monitoring the activity. CISA and international partners issued advisory AA25-239A in August 2025; the FCC opened a notice of proposed rulemaking for new cybersecurity rules for carriers.

Lesson: Backbone and provider edge / customer edge routers are priority targets. CISA calls for patching CVE-2024-21887 (Ivanti Connect Secure) and CVE-2024-3400 (Palo Alto PAN-OS GlobalProtect), plus active hunting. NIS2 Art. 21(2)(e),(f),(i) covers exactly these requirements; for EU operators, integration with the ENISA CTI mechanisms and the EU CSIRTs Network is a minimum operational baseline.

Public source β†—

Lyca Mobile (global MVNO, headquartered in the UK)

2023 Β· UK + 60 other operational markets

Type: Cyberattack (suspected ransomware-related); top-up service, national and international calls disrupted; investigation into data exfiltration

Impact: Services suspended in all 60 countries except 4; top-up portal taken down; investigation with third-party IT + law enforcement and data protection authority notification. Lyca's wording about "encrypted customer data" suggests unauthorised database access.

Lesson: A global MVNO with centralised IT propagates the incident across dozens of jurisdictions. NIS2 Art. 21(2)(d) (supply chain) + (c) (BCM / crisis management) β€” for an MVNO, per-market segregation + a parallel communications plan with each jurisdiction's authorities are already part of the minimum operational standard.

Public source β†—

⚠️ Typical threats

  • β€’ Atacuri pe SS7/Diameter
  • β€’ SIM swap fraud
  • β€’ 5G slicing security

πŸ’° Maximum fines

Max 10 mil. EUR sau 2% cifra afaceri

πŸ“Š Romania compliance status

Top 4 operatori RO la 80%+ conformitate. ANCOM monitorizează proactiv.

πŸ›‘οΈ How CAI Technology helps

πŸ“š Adjacent regulations with overlap

European Electronic Communications Code β€” Directive (EU) 2018/1972 Β· Transposed in Romania by Law 198/2022 (amending OUG 111/2011) [C14]

The basic regulatory framework for the electronic communications sector (authorisation, access, spectrum, universal service, user rights). Articles 40-41 (with security requirements and incident reporting) were repealed by NIS2 from 18 October 2024 [C8]; the rest of the EECC remains applicable. The ENISA Guide on Security Measures under the EECC remains technically relevant for any telecom operator seeking a verified operational baseline.

5G EU Toolbox + Law 163/2021 (Romania) Β· Toolbox: coordinated instrument of the NIS Cooperation Group, January 2020; Law 163/2021 published 11 June 2021 [C9][C10]

Combined framework for 5G network security. The EU Toolbox contains strategic measures (control of high-risk vendors) and technical measures (the ENISA 5G Security Controls Matrix catalogue) [C9][C17]. Law 163/2021 imposes in Romania prior authorisation of 5G technology manufacturers; for the defence, public order and national security system, purchases from non-authorised vendors are prohibited [C10].

GDPR (Reg. (EU) 2016/679) + Law 506/2004 (ePrivacy for electronic communications) Β· GDPR directly applicable from 25 May 2018; Law 506/2004 published 25.11.2004, amended several times (including by Law 235/2015) [C13]

Providers of electronic communications process traffic, location and identity data of subscribers β€” sensitive categories for which the GDPR + Law 506/2004 impose confidentiality, retention and subscriber rights requirements. For an incident affecting personal data, notification to DNSC under NIS2 Art. 23 does not replace notification to ANSPDCP under GDPR Art. 33 and, where applicable, to subscribers [C4]. Good practice: a single runbook feeding both flows.

Comm. Impl. Reg. (EU) 2024/2690 β€” NIS2 technical measures Β· Directly applicable from 17 October 2024 [C16]

Important for the supply chain: the regulation spells out technical requirements for DNS, TLD, cloud, data centres, CDN, MSP, MSSP and trust services [C16]. Providers of public electronic communications are NOT in direct scope, but if they use any of those providers (cloud, CDN, MSSP), their partner is bound by the same 13 technical sections β€” a key element for contractual clauses under NIS2 Art. 21(2)(d).

ENISA β€” Guide on Security Measures under the EECC + 5G Security Controls Matrix Β· Non-legal technical documents; remain the operational reference [C8][C17]

Even after the repeal of Art. 40-41 EECC, the technical baseline developed by ENISA under the previous regime remains an accepted operational standard. For 5G, the 5G Security Controls Matrix (a catalogue of controls aligned with the Toolbox + 3GPP) is the standard reference for national authorities during NIS2 + Law 163/2021 audits. DNSC will use this technical framework in audits on NIS2 Art. 21(2) for telecom, pending any future publication of a separate sectoral implementing regulation.

❓ Frequently asked

We are a provider of electronic communications networks or services in Romania β€” are we in scope of NIS2?

Very likely yes. NIS2 Annex I lists providers of public electronic communications networks and providers of publicly available electronic communications services in the "Digital infrastructure" sector [C1]. If you are a medium or large enterprise (>= 50 employees or >= EUR 10 million annual turnover / balance-sheet total), you are in direct scope as an essential entity. On top of that, NIS2 Art. 2(2) extends scope regardless of size where the service has a unique character in a Member State, where disruption would have systemic effects or where the entity is critical at national / regional level [C2]. In Romania, the regime is operated by DNSC via OUG 155/2024; registration is done through the NIS2@RO Tool and the ATHENA platform [C7].

Are we an essential or an important entity?

It depends on the DNSC criteria in Order 2/2025 (criteria and disruption thresholds). For public telecom providers, the usual indicators are geographic coverage, number of subscribers, role in universal service and in emergency services (112). Major operators (Digi, Orange, Vodafone, Telekom Romania) are natural candidates for essential status; local ISPs and MVNOs are typically important, but can be reclassified where DNSC considers that disruption of the service would have systemic effects [C7].

Do we still report to ANCOM after NIS2?

For cybersecurity incidents (integrity / availability / confidentiality), the primary notification is now to DNSC under NIS2 Art. 23, on a 24h / 72h / 1 month track [C4]. Articles 40-41 of the EECC were repealed from 18 October 2024 [C8]. ANCOM remains the sectoral regulator for licensing, spectrum, quality of service and tariffs β€” a major incident remains relevant to ANCOM through coordination via the BEREC Cybersecurity WG and through contractual obligations towards the authority (universal-service continuity, 112 access) [C15].

What technical instrument do we prepare NIS2 audits against, since there is no Reg. 2024/2690 for telecom?

Directly against NIS2 Art. 21(2)(a-j) + OUG 155/2024 [C3][C7]. For operationalisation: the ENISA technical guide on the NIS2 Implementing Act (published 2025) is the practical reference, even though it covers DNS/cloud/MSP β€” many controls transfer directly [C3]. For 5G, ENISA 5G Security Controls Matrix + 3GPP TS 33.501 [C17]. For signalling, the ENISA guide on SS7/Diameter/5G [C11]. For BCM and continuity, ISO/IEC 27031 + ISO 22301. The absence of a sectoral implementing regulation does not reduce the level of stringency β€” it shifts it into the obligation to demonstrate alignment with "European and international standards" (Art. 21(2) NIS2).

What is the maximum fine ceiling for an essential telecom operator?

Under NIS2 Art. 34: for essential entities, at least EUR 10 000 000 or 2% of total worldwide annual turnover, whichever is higher [C5]. For important entities: EUR 7 000 000 or 1.4% [C5]. The exact amounts transposed in lei are set by OUG 155/2024 and may also include fines for failure to register. Where the incident also affects personal data, NIS2 sanctions stack with those under GDPR Art. 83 (up to EUR 20 million or 4% of turnover).

How do we integrate the 5G EU Toolbox requirements into NIS2 compliance?

The EU 5G Toolbox (January 2020) + Law 163/2021 are complementary to NIS2, not a substitute [C9][C10]. In practice: (a) identification of 5G vendors + prior authorisation of manufacturers β€” Law 163/2021; (b) restriction of vendors presenting materially higher risk (Huawei, ZTE) to the extent Romania has adopted specific measures β€” Commission communication June 2023 [C9]; (c) application of the technical controls in the ENISA 5G Security Controls Matrix [C17]. All of these can be presented as evidence of compliance with NIS2 Art. 21(2)(d),(e).

What should we focus on operationally this year β€” top 3 priorities?

Based on the 2021-2024 incidents [I1-I5] and the ENISA Telecom 2024 report [C12]: (1) Asset management and API security β€” Optus 2022 and T-Mobile 2021 were caused by forgotten endpoints / lax configurations on publicly exposed environments; complete inventory + regular external scanning (Art. 21(2)(i),(e)). (2) Security of backbone and edge routers β€” Salt Typhoon 2024 confirms that state actors target this layer directly; aggressive patching of published CVEs (Ivanti, Palo Alto), MFA on the management plane, segregation. (3) Crisis plan tested on multi-service scenarios β€” Vodafone Portugal 2022 showed that an integrated operator can lose every service at once; mandatory annual testing under Art. 21(2)(c).

πŸ”— Official sources

Are you in the electronic communications providers sector?

Free NIS2 audit for companies with 50+ employees. We reply within 24 business hours.

Request audit β†’