the PQC migration deadlines are closer than most people realize

Understand this faster with AI
NIST finalized the first three post-quantum standards in August 2024: FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA). the dates that follow for US national security systems (CNSA 2.0): Jan 1, 2027: new NSS acquisitions have to be CNSA 2.0 compliant 2030: gear that can’t support it gets phased out; networking equipment and firmware signing go CNSA-only 2033: OS, web, cloud and custom apps go CNSA-only 2035: all NSS quantum-resistant (NSM-10) for everyone else, NIST’s draft IR 8547 deprecates quantum-vulnerable public-key crypto after 2030 and disallows it after 2035. TLS is the easy part, since browsers and CDNs already do hybrid X25519MLKEM768. the slow parts are firmware signing, PKI roots, SSH, encrypted backups, and IoT devices that can’t be patched. the reason it matters now: harvest now, decrypt later. any session keyed with classical ECDH/RSA today can be recorded and decrypted once a CRQC exists, which matters for anything that has to stay secret 10+ years. migration takes years, so the clock started at migration, not Q-day. where are you in your stack? edit: corrected the CNSA 2.0 dates (procurement gate is 2027, not 2025) submitted by /u/Gkdeaddevil [link] [comments]
Tags
Source Information
Discussion
0 professional contributions
Sign in to join this professional discussion.
Be the first to add a constructive contribution.
