Why does post-quantum crypto migration matter for satellites specifically — aren't my ground systems the real risk?

Satellites are uniquely exposed because their command-and-control links, telemetry streams, and intersatellite links are broadcast across radio frequencies that any actor with a dish can record today. The harvest-now-decrypt-later threat means an adversary intercepting encrypted telemetry now can decrypt it once a cryptographically relevant quantum computer exists — potentially within 10–15 years. Ground systems can be patched continuously; a satellite on orbit for 12 years cannot. Migration must start at the architectural design phase, not as an afterthought.

Which NIST algorithms should a sovereign space programme prioritise?

For key encapsulation (protecting session keys on uplink/downlink), ML-KEM-768 or ML-KEM-1024 are the current recommendations depending on the classification level of the payload. For digital signatures on commands and firmware updates, ML-DSA-65 offers the best balance of signature size and verification speed for bandwidth-constrained links. NIST explicitly advises against waiting for further algorithms — programmes should begin design work against FIPS 203/204/205 now, with a hybrid classical overlay during the transition period.

What is 'harvest now, decrypt later' and how real is the threat to my satellite operations?

Harvest-now-decrypt-later (HNDL) refers to adversaries recording encrypted traffic today with the intent of decrypting it once quantum computing matures sufficiently to break current public-key algorithms. Classified government satellite telemetry, orbital manoeuvre commands, and intelligence imagery downlinks are prime targets because their value persists for decades. The US NSA, the UK NCSC, and France's ANSSI have all issued public advisories treating HNDL as an active, ongoing threat rather than a theoretical future risk.

Can I migrate my existing on-orbit satellite to PQC without building a new one?

Possibly, but with significant caveats. If the satellite carries a software-defined radio (SDR) payload and an onboard processor with spare compute and memory, a firmware update can introduce PQC algorithms at the link layer. However, if the cryptographic engine is implemented in dedicated hardware (ASICs or FPGAs without reconfigurability), on-orbit migration is not feasible. A thorough on-orbit software-reconfigurability assessment should be your first step; the CCSDS 352.0-B-1 framework provides a useful baseline for what can be updated in-flight.

Why should a sovereign nation own its PQC migration capability rather than buying a managed service from a commercial provider?

A commercial PQC-as-a-service provider controls the key generation, storage, and algorithm selection — precisely the components that define whether your communications are truly sovereign. If that provider operates under a foreign jurisdiction, it is legally compelled to comply with that government's intelligence access demands. Owning the full stack — HSMs, satellite command-encryption modules, ground PKI, and key distribution infrastructure — means no foreign law, no foreign court order, and no vendor acquisition can compromise your national communications without your knowledge.

How long does a full PQC migration for a national satellite constellation typically take?

Industry and government experience (drawing on the US CNSA 2.0 timeline and ESA's internal assessments) suggests 5–8 years for a full-stack migration across a mixed legacy/new-build constellation. The longest poles are: (1) HSM procurement and certification, (2) ground station firmware qualification, and (3) operator retraining. Programmes that begin architecture work immediately and prioritise hybrid-mode operation as a transitional state can achieve meaningful risk reduction within 18–24 months even before full migration is complete.

Does PQC replace quantum key distribution (QKD), or do the two work together?

They address different parts of the problem. PQC replaces classical public-key algorithms (RSA, ECC, Diffie-Hellman) with mathematically hard lattice and hash-based problems that even quantum computers cannot efficiently solve. QKD distributes symmetric keys using quantum physics guarantees, independent of computational hardness assumptions. Best-practice sovereign architecture layers both: PQC for authentication and key encapsulation across the full link budget, QKD where distance and hardware allow, with symmetric encryption (AES-256) as the final payload cipher. Neither is sufficient alone.

What international standards bodies are actively publishing guidance that a national space programme should track?

NIST (FIPS 203/204/205, plus the forthcoming FIPS 206 for FALCON/FN-DSA) is the primary algorithm authority. CCSDS Working Group 2 is updating its cryptographic standards for space link protocols. ETSI's Quantum Safe Cryptography working group publishes migration guides directly applicable to satellite systems. The ITU-T Study Group 17 is developing X-series recommendations on PQC for network security, which affects ground-segment interconnects. ESA's ECSS secretariat is revising space-link security standards to mandate PQC readiness for ESA-funded missions from 2027 onwards.

16.1.3Experimental

Post-Quantum Crypto Migration

A woman engineer at a workstation surrounded by server racks, reviewing code on multiple monitors — A data engineer configures server infrastructure to support quantum-resistant encryption across satellite communication links worldwide.

Satellite Link Post-Quantum Crypto Migration Flow

1
Satellite node
Firmware updated with CRYSTALS-Kyber KEMs
2
Encrypted downlink
Hybrid classical/PQC handshake protects channel
3
Ground processing
Key management server validates PQC certificates
4
Sovereign endpoint
Agency systems receive harvest-safe secure data

Post-quantum algorithms replace classical keys at every hop, ensuring satellite data remains secure against future quantum attacks.

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: Engineering proven; commercial, regulatory or technical gates remain. 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

16.1.2 · Previous

Quantum Repeater Networks

All in quantum & sovereign cryptographic infrastructure

16.1.4 · Next

Quantum Random Number Distribution

Bring this into your sovereign programme.

All solutions Speak with engineering