Satellite Networks and Mobile Carriers: What Could Go Wrong?

Satellite companies are knocking on the door of mobile networks, and carriers are actually opening it. After decades of running completely separate operations, satellite infrastructure is being folded into terrestrial mobile systems. On the surface, this sounds like progress. More coverage, fewer dead zones, better resilience. But I’ve spent enough time in security work to know that integration almost always creates friction—and friction is where vulnerabilities live.

The Convergence Problem

Here’s what’s happening: telecommunications providers are realizing that satellite networks can fill gaps that ground-based infrastructure can’t easily reach. Remote areas, maritime zones, disaster zones where towers are down. The business case is compelling. Adding satellite capacity as a backup layer or primary service in underserved regions makes economic sense.

But merging two historically separate systems creates a problem that doesn’t get nearly enough attention. Satellite networks were built with different assumptions about security, latency, bandwidth, and threat models. They operated in isolation. Your phone’s security architecture was designed around cell towers a few kilometers away, not hardware orbiting 20,000 kilometers up.

When you start stitching these worlds together at the infrastructure level, you inherit complexity. And complexity is the enemy of security. Each integration point becomes a potential attack surface. Authentication between ground and space networks. Handoff protocols. Cross-system traffic encryption. Signal routing decisions. These aren’t trivial problems to solve correctly.

What worries me most isn’t whether satellite connectivity itself is secure. It’s whether telecom providers—already stretched managing their core networks—have the expertise and resources to properly secure a hybrid infrastructure. One weak link in the integration and an attacker might exploit it to redirect traffic, intercept communications, or disrupt service across both systems simultaneously.

The Hidden Dependencies

Let’s think about failure modes. If a satellite network becomes part of your mobile infrastructure, what happens when something goes wrong up there? A solar flare. Debris collision. Antenna malfunction. A cyberattack targeting ground stations.

Your mobile network suddenly has a new point of failure it doesn’t fully control. Satellite operators and telecom companies are different businesses with different risk tolerances, different operational procedures, and different incident response capabilities. When something breaks, figuring out whose responsibility it is and coordinating a fix becomes a nightmare. Meanwhile, users lose service.

There’s also the supply chain dimension. Satellite operators often source components globally. Ground station equipment comes from various vendors. Integration middleware comes from yet another set of companies. The more vendors involved in making the system work, the more supply chain risk you inherit. A compromised component at any point in this chain could affect millions of mobile subscribers.

And then there’s the regulatory minefield. Satellite networks cross borders. They’re regulated by different agencies depending on orbital mechanics, frequency bands, and which countries they serve. Telecom regulations vary wildly by country. Trying to create a unified system that satisfies all these requirements while maintaining security is genuinely difficult. The temptation to cut corners or make trade-offs is real.

Who’s Actually Responsible Here?

This is where my scepticism really kicks in. When something goes wrong—when a security incident happens or service fails—who owns the problem? The satellite operator? The mobile carrier? The integration vendor? The equipment manufacturer?

Liability and responsibility become murky in hybrid systems. I’ve seen this before in other converged infrastructure projects. Everyone points fingers at everyone else while customers suffer. From a security perspective, this lack of clear ownership is dangerous. Security requires someone to be accountable for decisions, for incident response, for hardening systems.

There’s also a knowledge transfer problem. Satellite engineers and mobile network engineers speak different languages. They have different priorities. Satellite folks optimize for latency tolerance and intermittent connectivity. Mobile networks demand low latency and always-on availability. Getting these teams to actually work together, rather than just technically coexist, requires serious effort.

The integration of satellite networks into mobile infrastructure isn’t bad—it might actually solve real problems. But it’s not a simple addition to existing systems. It’s a fundamental change to how telecommunications infrastructure works, and I’m not convinced the industry is thinking carefully enough about the security, operational, and organizational implications. Until I see evidence that these concerns are being treated as seriously as the business opportunity, I’ll remain skeptical.

Source: Turning Orbit into Infrastructure: Why Satellites Are Becoming Part of the Mobile Economy