--- title: Quantum-Secure Cryptography | RGM® url: https://realgrowthmatters.com/learn/privacy/quantum-secure-cryptography/ updated: 2026-06-10 source_html: https://realgrowthmatters.com/learn/privacy/quantum-secure-cryptography/ --- # Quantum-Secure Cryptography — NIST PQC Standards and the Migration Marketers Should Plan For Quantum-secure cryptography (post-quantum cryptography, PQC) is encryption that remains secure against attacks by future quantum computers. NIST finalized the first PQC standards in 2024: CRYSTALS-Kyber for key encapsulation, CRYSTALS-Dilithium for digital signatures, plus Falcon and SPHINCS+. Marketing teams should care because customer data with long shelf life is at risk under harvest-now-decrypt-later attacks. Public-key cryptography underlies almost every secure communication on the internet — HTTPS, VPN, email encryption, code signing, blockchain. RSA and elliptic-curve cryptography (ECC) both rely on mathematical problems (factoring large numbers, discrete logarithms) that classical computers cannot solve efficiently. Shor's algorithm running on a sufficiently large quantum computer can solve both efficiently. The cryptographic foundation of the modern internet is on the clock. ## NIST Post-Quantum Cryptography standards (finalized 2024) - **CRYSTALS-Kyber (ML-KEM, FIPS 203)** — module-lattice-based key encapsulation; replaces RSA and ECC for key exchange - **CRYSTALS-Dilithium (ML-DSA, FIPS 204)** — module-lattice-based digital signatures; replaces RSA and ECC for signatures - **Falcon (FN-DSA, FIPS 206)** — NTRU lattice-based signatures; smaller signature size than Dilithium, more complex to implement - **SPHINCS+ (SLH-DSA, FIPS 205)** — hash-based signatures; conservative fallback option not based on lattice assumptions - Additional standards in pipeline: code-based, isogeny-based alternatives for diversification ## Why now matters even though large quantum computers don't exist yet Three forces push the migration timeline earlier than 'quantum computers exist': - **Harvest-now-decrypt-later (HNDL)** — adversaries collect encrypted traffic today, store it, decrypt when quantum capability arrives. Data with shelf life longer than the quantum timeline is already at risk. - **Crypto-agility takes years** — replacing cryptographic primitives across a large system is multi-year work: identification, vendor coordination, certificate rotation, testing, deployment. - **Compliance and procurement pressure** — NIST mandates federal systems migrate; private-sector vendors selling to federal customers must follow; trickle-down affects marketing tech vendors who handle customer data. ## Marketing-relevant data at HNDL risk - **Customer PII with long shelf life** — names, addresses, DOBs, SSNs (where stored) remain valuable decades from now - **Health and financial data** — HIPAA-covered data, payment information - **Email archives** — sensitive business correspondence - **Account credentials** — passwords (hashed correctly are safer), authentication tokens - **Encryption keys themselves** — keys stored in HSMs or cloud KMS protected by RSA/ECC are vulnerable - **Long-term contracts and IP** — legal documents, M&A diligence materials, patent filings #### RGM Experts Say We have audited the cryptographic stacks of dozens of marketing platforms. Most are running TLS 1.2 or 1.3 with RSA or ECC. None had a documented PQC migration plan as of 2025. The marketers leading their organizations on this are talking to their security and procurement teams now — not because urgent action is required tomorrow, but because the cycle to migrate is multi-year and the threat to long-shelf-life data is real. ## Migration roadmap for marketing operations - **Inventory cryptographic use** — where does the marketing stack use cryptography? TLS, JWT signing, data-at-rest encryption, password hashing, code signing - **Identify vendor exposure** — what PQC roadmaps do CDPs, ESPs, ad platforms, MMPs publish? - **Prefer hybrid migration approach** — combine classical (RSA/ECC) with PQC (Kyber/Dilithium) during transition; offers backward compatibility plus forward security - **Rotate keys that secure long-shelf-life data** — even if PQC migration is years away, key rotation reduces the window of HNDL exposure - **Update procurement requirements** — new vendor contracts include PQC readiness clauses - **Plan for performance impact** — PQC signatures and keys are larger than classical (Kyber-1024 public key is 1.5KB vs RSA-3072 at 384 bytes); affects bandwidth and storage at scale - **Engage with standards bodies** — IETF, W3C, browser vendors are still finalizing TLS-PQC, signed-HTTP-exchanges, and similar ## Hybrid cryptography during transition The IETF and major implementations (OpenSSL, BoringSSL, AWS, Cloudflare) are deploying hybrid modes: a TLS handshake uses both classical (ECDH) and post-quantum (Kyber) key exchange. Either provides security; an attacker needs to break both. This is the safest migration path during the years where PQC algorithms are being battle-tested in production. Cloudflare reported deploying hybrid TLS in 2023; AWS, Google, and others followed in 2024. ## Related guides - See [harvest-now-decrypt-later threat](/learn/privacy/harvest-now-decrypt-later-threat/) - See [quantum computers](/learn/concepts/quantum-computers-marketing-implications/) - See [data classification](/learn/governance/data-classification-frameworks/) ## Sources 1. [1]NIST Post-Quantum Cryptography standardization (FIPS 203, 204, 205, 206); Cloudflare and AWS PQC deployment posts ### Related guides - [Harvest-now-decrypt-later](/learn/privacy/harvest-now-decrypt-later-threat/) - [Quantum computers](/learn/concepts/quantum-computers-marketing-implications/) - [Data classification frameworks](/learn/governance/data-classification-frameworks/)