The Post-Quantum Cryptographic Expiration Date on Every Satellite You're Launching

There are approximately 14,000 satellites in orbit right now. US Congress just introduced the Satellite Cybersecurity Act. Fewer than 5% of enterprises around the world have a post-quantum transition plan, and Google recently moved its internal post-quantum deadline forward to 2029.

Every organization needs a post-quantum readiness plan for “Q-Day,” the point at which a sufficiently powerful quantum computer can break today's public-key cryptography. But if you're building in space, there's an extra layer of preparedness compared to the ground-based organizations.When Google's 2029 quantum deadline arrives, the satellites launching this year will still be operational. The cryptographic decisions integrated into their hardware will therefore govern their entire mission lifespan.

Post-Quantum Cryptography in 60 Seconds, and Why Space Is Different

The urgent need for Post-Quantum Cryptography (PQC) stems from a specific but critical vulnerability: the public-key cryptography currently used to secure nearly everything (such as RSA, ECC, and ECDSA) relies on mathematical problems that a sufficiently large quantum computer can solve using Shor's algorithm. The National Institute of Standards and Technology (NIST) has already standardized the replacements: ML-KEM for key exchange, ML-DSA and SLH-DSA for signatures.

The main PQC threat is referred to as Harvest now, decrypt later (HNDL). Adversaries are already collecting encrypted traffic today, planning to decrypt it once quantum hardware has matured. For satellite transmissions in low Earth orbit (LEO), that exposure window is already open.

What’s different about hardware in orbit? You can't swap the silicon chips in orbit. A satellite launched in 2027 will still be operational well past any realistic Q-Day estimate, with most credible forecasts landing between 2029 and 2035. Terrestrial data centers can be re-keyed, contrastingly, anything in LEO cannot be updated. 

PQC Beyond Harvest Now Decrypt Later Adversaries

The PQC conversation is dominated by HNDL: record encrypted traffic today, crack it when quantum lands, read every secret the key protected. That's the confidentiality version of retroactive compromise, and it's scary because there's nothing you can do about traffic that was already captured.

There's a second adversary that gets far less airtime as it requires post quantum to exist to execute, and it targets verifiability instead of confidentiality. When a quantum computer eventually breaks today's attestation root keys, every attestation ever issued under that Public Key Infrastructure (PKI) becomes forgeable. An attacker can mint a valid-looking quote claiming any code ran on any hardware at any past moment, and the verifier has no way to tell a real attestation from a fabricated one. HNDL steals your past secrets, attestation forgery steals your past verifiability.

That turns a migration problem into a historical record problem. Attestations carry weight because they outlive the handshake that produced them: telemetry logs, command provenance, model provenance, regulatory audit trails, and settlement artifacts. All of it has to stay verifiable years after it was produced. The moment the root key falls, the entire historical record built on it falls with it.

The timeline for fixing this is realistically a decade. Every major confidential computing platform, Intel SGX and TDX, NVIDIA H100 confidential compute, AMD SEV-SNP, roots its trust in elliptic curve cryptography (ECC). The provisioning keys are fused into the silicon chips at fabrication, so rotating them requires new CPUs, GPUs, silicon masks, and PKI. Organizations generating long-lived attestations today are still writing evidence for attackers, and this won’t survive the transition.

Hash-based constructions, the family ZK-STARKs live in, sidestep this failure mode. Their security reduces to hash functions, which quantum computers only weakly affect. A proof generated in 2026 is expected to still be verifiable in 2040 regardless if quantum hardware arrives in the meantime. For space, where evidence has to outlive the hardware that produced it, that durability is the whole argument.

Three Questions Every Satellite Operator Should Be Asking Right Now

If you're evaluating security vendors for a constellation, or auditing your existing stack, these are the three questions that separate serious PQC readiness from theater:

1. Are your algorithms NIST PQC compliant?
2. Can your system swap crypto algorithms without a hardware change? (Crypto-agility is the single biggest design decision that determines whether you can migrate at all.)
3. What's your migration timeline if Q-Day is 2029 instead of 2035?

Any satellite or space vendor you’re working with should be able to answer these, as you'll be living with the hardware decisions today for the entire mission lifetime.

How We're Thinking About PQC at SpaceComputer

We've designed the Space Fabric protocol to be algorithm-agnostic from the start. The attestation, endorsement, and verification layers all support pluggable cryptographic backends, so migrating to NIST PQC primitives doesn't require rebuilding the architecture.

Because Harvest Now Decrypt Later is the real near-term threat, we're planning for hybrid classical/PQC deployments that use the satellite's TPM as an independent root of trust to layer a quantum-resistant signature (such as ML-DSA) over the classical one.

The full design, including the trade-offs behind each choice, is laid out in our Space Fabric paper.

What Satellite Operators Should Do Now

If you're launching anything that will still be in orbit in 2029, or whose telemetry, command chain, or provenance records will still need to be trusted then, the decisions you make this year are the ones you'll live with.

Read our full approach to post-quantum readiness in the Space Fabric paper.

If you're thinking through the same questions, we'd love to hear from you.

Follow SpaceComputer on X (Twitter) and LinkedIn
Visit the SpaceComputer Website

Discover your next read:

SpaceComputer’s Satellite Security Services

SpaceComputer delivers satellite security services from low Earth orbit: confidential compute, key management, and verifiable randomness, all accessible through a single API on Orbitport.

SpaceComputer BlogTara Jean