Telecom operators routing billions of calls and messages rely on US-controlled OSS/BSS platforms, network tools, and cloud infrastructure. Under the CLOUD Act, every layer of that stack is accessible to US authorities, without notifying you.
When OSS/BSS platforms, network management consoles, and incident ticketing systems run on Azure, AWS, or Google Cloud, the entire operational intelligence of a telecom operator sits under US jurisdiction. Under the CLOUD Act (18 U.S.C. § 2713), US authorities can compel disclosure of network topology, performance data, and operational communications, with gag orders that prevent the operator from ever being notified.
CDRs are the most sensitive data a telecom operator holds, subscriber identity, call parties, timestamps, cell tower locations, IMSI numbers. When billing and mediation platforms run on US-controlled cloud, these records are permanently accessible under a CLOUD Act order. The operator is legally required to protect subscriber data under GDPR and the ePrivacy Directive. The infrastructure they run on makes that protection impossible.
5G network slicing allows operators to create dedicated virtual networks, for governments, critical infrastructure, financial institutions. The configuration, security policies, and slice management data for these sovereign deployments are often orchestrated via US-controlled cloud platforms. An adversary with access to slice metadata can map which critical entities use which logical network segments, a map of which critical entities run on which segments — now accessible via CLOUD Act compelled disclosure.
International roaming moves subscriber data across multiple operators and jurisdictions. When the platforms managing roaming agreements, fraud detection, and inter-carrier settlement run on US-hosted infrastructure, a CLOUD Act order can expose subscriber data from multiple countries simultaneously, including users who have never interacted with a US company and whose national laws explicitly prohibit this transfer. GDPR Article 48 offers no valid legal pathway for this disclosure.
Saudi telecom operators, STC, Zain, and Mobily, face a dual regulatory burden. CITC mandates that subscriber data remains within the Kingdom of Saudi Arabia. The National Cybersecurity Authority (NCA) requires sovereign cybersecurity infrastructure for all licensed operators. Under the PDPL (enforced by SDAIA since September 2024), Article 29 treats remote access to data stored in Saudi Arabia by a foreign authority as a data export, triggering maximum fines of SAR 5M per violation, doubled for repeat offences.
NIS2 Directive Article 3 explicitly classifies providers of electronic communications networks and services as essential entities, the highest category of obligation. Article 21 requires essential entities to implement ICT supply-chain risk management measures covering all platforms used in their operations, including internal communications. A telecom operator using Microsoft Teams or Zoom for their Security Operations Centre (SOC) communications must document this as a supply-chain risk, one that, practically speaking, cannot be adequately mitigated.
Every subscriber data protection obligation applies with the same force to operational infrastructure. US cloud undermines all of it.
AMVLET is purpose-built to address all five layers simultaneously, the only sovereign communications platform built for telecom operators.
Talk to our telecom team. We'll map a deployment to your actual requirements, from NOC to board level.