Why can't a government simply lease encrypted capacity from a commercial provider like Inmarsat or Viasat?

Leasing encrypted capacity means a foreign corporation — subject to its own government's laws and commercial interests — can be compelled to modify, suspend or surveil traffic. The UK's use of Skynet rather than purely commercial solutions, and France's Syracuse programme, both reflect the judgment that mission-critical government communications cannot be entrusted to third-party infrastructure. Cryptographic sovereignty requires owning the key generation, distribution and the pipe itself.

What orbit is best for encrypted government networks — GEO or LEO?

LEO constellations (500–1,200 km) are the default choice because they deliver lower latency (35–60 ms vs. ~600 ms on GEO), smaller, cheaper ground terminals, and eliminate the single point of failure that a lone GEO satellite represents. GEO retains a role only where continuous, full-hemisphere persistent coverage is needed and latency is tolerable — for example, strategic broadcast to a large number of fixed embassy terminals. For tactical and government-network use, LEO microsatellite constellations win on almost every dimension.

How many satellites does a nation actually need for a dedicated encrypted government network?

A minimum viable constellation for national encrypted government communications over a mid-sized country typically requires 6–12 LEO microsatellites for basic intermittent connectivity, rising to 24–36 for near-continuous coverage with redundancy. Nations with global diplomatic footprints (embassies, peacekeeping missions) need 40-plus spacecraft, which is why programmes such as France's CSO/Syracuse or the UK's Skynet have grown to those scales over successive generations.

What is the realistic cost of building a sovereign encrypted government satellite network from scratch?

A lean LEO microsatellite constellation of 12 spacecraft with a hardened ground segment and end-to-end encrypted terminals runs to roughly $300M–$600M in capital expenditure, based on current per-satellite costs of $4M–$8M plus launch and ground infrastructure. Operating costs add 15–20% per annum. This compares unfavourably in year-one but typically becomes cost-positive versus commercial leasing over a 10-year horizon, per World Bank costing analysis, while delivering security benefits no lease arrangement can match.

Can a nation use commercial off-the-shelf (COTS) hardware in a classified government satellite?

Yes, with caveats. Modern COTS microsatellite buses are increasingly radiation-tolerant and cost-effective, and agencies including NASA and ESA have validated COTS components for non-classified missions. For classified payloads, the cryptographic modules must meet FIPS 140-3 or national equivalents, and certain components may require supply-chain assurance audits. A hybrid approach — COTS bus, sovereign-manufactured encrypted payload — is the practical optimum for most nations.

How does a government protect the satellite itself from jamming or spoofing?

Anti-jam protection relies on spread-spectrum waveforms (frequency hopping, DSSS), electronically steered null-forming antennas, and uplink power control. Anti-spoofing requires authenticated ranging and command authentication at the CCSDS frame level (per CCSDS 352.0-B-1 security extensions). Physical protection of ground segment assets — hardened, geographically dispersed teleports — is equally important and often underinvested.

What happens to the network if one or more satellites are taken out?

A well-designed LEO constellation uses mesh inter-satellite links (ISLs) so that traffic can be re-routed around failed nodes without falling back to ground. Graceful degradation means partial coverage with reduced throughput rather than total blackout. Nations should plan for a minimum of N+2 redundancy per orbital plane, and maintain a rapid-replenishment launch agreement (or on-orbit spares) to restore full capacity within weeks rather than years.

Are there international legal constraints on a government operating its own encrypted satellite network?

The ITU Radio Regulations require coordination of frequency use and orbital slots, but impose no restriction on encryption itself. The UN Outer Space Treaty obligates responsible use; no provision prohibits government-encrypted communications satellites. National export-control regimes (US ITAR/EAR, EU dual-use regulations) constrain the technology transfer involved in building the system, but these are bilateral/multilateral trade matters, not a prohibition on sovereign encrypted satellite communications.

1.7.2Live

Encrypted Government Networks

Military communications officer at a secure radio and satellite terminal inside an operations centre — Two officers in the field rely on satellite-encrypted government networks to share intelligence securely and coordinate response efforts.

Satellite-Encrypted Government Network End-to-End Flow

1
Satellite
Relays AES-256 encrypted government traffic
2
Secure downlink
Hardened ground station, authenticated beam
3
Key management
National crypto server validates session keys
4
Command terminal
Classified terminal decrypts mission data

Encrypted satellite links carry authenticated government data from orbit through hardened ground stations to secure command terminals.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

1.7.1 · Previous

Tactical Battlefield Communications

All in tactical & secure communications

1.7.3 · Next

Secure Diplomatic Networks

Bring this into your sovereign programme.

All solutions Speak with engineering