With the entry into force of NIS2 requirements, telecom operators have revised their approaches to digital infrastructure security. According to ENISA Threat Landscape 2025 data, approximately 27.7% of all data breaches occur in digital infrastructure and services. In this context, integration nodes—APIs and data buses—become a critical perimeter that requires a shift from the outdated concept of internal network trust to a Zero Trust strategy.
Why BSS/OSS integration nodes have become a red zone under NIS2
Many BSS/OSS systems are based on monolithic architecture, where internal components are trusted by default. When transitioning to component-based systems according to TM Forum's Open Digital Architecture (ODA) standards, legacy nodes often lack native identification, creating vulnerabilities to supply chain attacks. Global telecom fraud losses, estimated at 41.82 billion dollars in 2025 (according to CFCA), highlight the danger of unsecured integration points.
Legacy system isolation: API gateway and Zero Trust strategy
The optimal method for risk minimization is the architectural wrapping of legacy components. Instead of completely replacing systems, operators can use identity-oriented API gateways. This allows for the authentication of every request before accessing legacy billing or service modules, eliminating unauthorized interactions within the network.
The role of metadata in granular access control
Zero Trust is not a product but a strategy. Effective implementation requires granular access control based on domain metadata. This allows for defining access rights not only by user role but also by request context, which limits the possibility of lateral movement by attackers. Using metadata helps isolate sensitive data even within a single technological circuit.
Architectural approach to minimizing blast radius
To minimize the impact of incidents, it is necessary to implement service-level segmentation. Professional assistance may be required for auditing the technology stack and identifying vulnerable BSS/OSS components. Experts can provide priority recommendations for modernizing the integration layer and implementing metadata. In particular, solutions built on the UnityBase platform allow for the implementation of granular access control and integration mechanisms that comply with Zero Trust principles without the need for a complete replacement of legacy systems.
Zero Trust maturity levels for integration nodes
- Level 1: Perimeter security (traditional approach, internal network trust).
- Level 2: API gateways with basic authentication (isolation via proxy).
- Level 3: Granular access control based on metadata (Zero Trust at the service level).
- Level 4: Full security policy orchestration (automated NIS2 compliance).
FAQ
How to ensure NIS2 compliance for legacy BSS/OSS systems?
It is necessary to implement architectural wrapping of legacy systems via API gateways that require mandatory identification for every request, eliminating assumptions of internal network trust.
How to isolate legacy billing systems in an API-first architecture?
The best method is using an API gateway as a proxy layer that verifies access rights based on metadata before forwarding the request to the billing core.
Which architectural methods minimize the risks of supply chain attacks in telecom?
Key methods include transitioning to a component-based architecture (ODA), service-level segmentation, and implementing granular access control that limits lateral movement.