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)