--- title: What NIST’s Post-Quantum Cryptography Plan Means For... description: NIST's new report on transitioning to post-quantum cryptography (PQC) requires coordinated changes across enterprise software, hardware, identity systems and... canonical: https://daily.dev/posts/what-nist-s-post-quantum-cryptography-plan-means-for-companies-and-their-suppliers-ytujhclmb twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: What NIST’s Post-Quantum Cryptography Plan Means For Companies And Their Suppliers | daily.dev og:description: NIST's new report on transitioning to post-quantum cryptography (PQC) requires coordinated changes across enterprise software, hardware, identity systems and... og:url: https://daily.dev/posts/what-nist-s-post-quantum-cryptography-plan-means-for-companies-and-their-suppliers-ytujhclmb og:image: https://api.daily.dev/og/posts/yTUJhclmb.png og:image:alt: What NIST’s Post-Quantum Cryptography Plan Means For Companies And Their Suppliers og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # What NIST’s Post-Quantum Cryptography Plan Means For Companies And Their Suppliers **[The Quantum Insider](https://daily.dev/sources/thequantuminsider)** · 9 min read · 0 upvotes · 0 comments ## Summary NIST's new report on transitioning to post-quantum cryptography (PQC) requires coordinated changes across enterprise software, hardware, identity systems and technology suppliers. Sensitive federal systems must adopt quantum-resistant key establishment by the end of 2030 and digital signatures by the end of 2031, ahead of the broader 2035 target. NIST recommends ML-KEM-768 as the default key establishment parameter, and expects AES to remain valid post-quantum. The report warns that TLS 1.3 support alone doesn't guarantee post-quantum protection, and that hybrid cryptography adds complexity and often requires a second migration later. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the deadline for federal systems to adopt post-quantum cryptography for key establishment and digital signatures? Prioritized sensitive federal systems must adopt quantum-resistant key establishment by the end of 2030 and digital signatures by the end of 2031, according to NIST's transition report. These deadlines are ahead of the broader federal migration target of 2035. NIST also plans to deprecate quantum-vulnerable public-key algorithms after 2030 and disallow them under its standards after 2035. _Teams planning crypto migrations can track NIST's post-quantum timeline and supplier implications on daily.dev._ ### Which algorithm does NIST recommend as the default for post-quantum key establishment? NIST recommends ML-KEM-768 as the default parameter set for key establishment in its post-quantum cryptography transition report, citing its security margin and reasonable performance cost. The agency still allows alternatives where circumstances warrant them. ML-DSA and SLH-DSA are the recommended standards for digital signatures, which verify source and integrity of information. _Engineers choosing PQC algorithms for their stack can follow coverage like this on daily.dev._ ### Does supporting TLS 1.3 mean a system is protected against quantum computer attacks? No, protocol-version support alone does not establish post-quantum protection. Federal agencies must support TLS 1.3 by January 2, 2030, but the algorithms negotiated for a given connection are what actually determine whether that connection is quantum-resistant, not merely the TLS version in use. _Security teams evaluating vendor quantum-readiness claims can dig deeper via daily.dev._ ## Similar posts on daily.dev - [Why US companies must be ready for quantum by 2030: A practical roadmap](https://daily.dev/posts/why-us-companies-must-be-ready-for-quantum-by-2030-a-practical-roadmap-rvifprppd) · CSO Online · 0 upvotes · 0 comments - [The State of Post-Quantum Cryptography](https://daily.dev/posts/the-state-of-post-quantum-cryptography-hjfyungt7) · Feisty Duck · 0 upvotes · 0 comments - [Post-Quantum Cryptography for Authentication: The Enterprise Migration Guide 2026](https://daily.dev/posts/post-quantum-cryptography-for-authentication-the-enterprise-migration-guide-2026-i5hayeibm) · Security Boulevard · 0 upvotes · 0 comments - [Guest Post: Why Enterprises Need to Start Post-Quantum Migration Now](https://daily.dev/posts/guest-post-why-enterprises-need-to-start-post-quantum-migration-now-3avzdtz5p) · The Quantum Insider · 0 upvotes · 0 comments - [The post-quantum EO is an important milestone. Now it’s time to get to work](https://daily.dev/posts/the-post-quantum-eo-is-an-important-milestone-now-it-s-time-to-get-to-work-kxyigr3vm) · Cloudflare · 1 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#quantum-computing](https://daily.dev/tags/quantum-computing), [#cryptography](https://daily.dev/tags/cryptography) [View this post on daily.dev](https://daily.dev/posts/what-nist-s-post-quantum-cryptography-plan-means-for-companies-and-their-suppliers-ytujhclmb) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"What NIST’s Post-Quantum Cryptography Plan Means For Companies And Their Suppliers","url":"https://daily.dev/posts/what-nist-s-post-quantum-cryptography-plan-means-for-companies-and-their-suppliers-ytujhclmb","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/what-nist-s-post-quantum-cryptography-plan-means-for-companies-and-their-suppliers-ytujhclmb"},"datePublished":"2026-10-28T12:10:10.447Z","dateModified":"2026-10-29T23:53:40.502Z","description":"NIST's new report on transitioning to post-quantum cryptography (PQC) requires coordinated changes across enterprise software, hardware, identity systems and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1fdd2b1f72c7467df2e9ff2b9539fa61?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1fdd2b1f72c7467df2e9ff2b9539fa61?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"The Quantum Insider","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"The Quantum Insider","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/7b14a6b34c1b464c9e8a88d9a0dac951","url":"https://daily.dev/sources/thequantuminsider"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/what-nist-s-post-quantum-cryptography-plan-means-for-companies-and-their-suppliers-ytujhclmb","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,quantum-computing,cryptography","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The Quantum Insider","item":"https://daily.dev/sources/thequantuminsider"},{"@type":"ListItem","position":3,"name":"What NIST’s Post-Quantum Cryptography Plan Means For Companies And Their Suppliers"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/what-nist-s-post-quantum-cryptography-plan-means-for-companies-and-their-suppliers-ytujhclmb#faq","mainEntity":[{"@type":"Question","name":"What is the deadline for federal systems to adopt post-quantum cryptography for key establishment and digital signatures?","acceptedAnswer":{"@type":"Answer","text":"Prioritized sensitive federal systems must adopt quantum-resistant key establishment by the end of 2030 and digital signatures by the end of 2031, according to NIST's transition report. These deadlines are ahead of the broader federal migration target of 2035. NIST also plans to deprecate quantum-vulnerable public-key algorithms after 2030 and disallow them under its standards after 2035. Teams planning crypto migrations can track NIST's post-quantum timeline and supplier implications on daily.dev."}},{"@type":"Question","name":"Which algorithm does NIST recommend as the default for post-quantum key establishment?","acceptedAnswer":{"@type":"Answer","text":"NIST recommends ML-KEM-768 as the default parameter set for key establishment in its post-quantum cryptography transition report, citing its security margin and reasonable performance cost. The agency still allows alternatives where circumstances warrant them. ML-DSA and SLH-DSA are the recommended standards for digital signatures, which verify source and integrity of information. Engineers choosing PQC algorithms for their stack can follow coverage like this on daily.dev."}},{"@type":"Question","name":"Does supporting TLS 1.3 mean a system is protected against quantum computer attacks?","acceptedAnswer":{"@type":"Answer","text":"No, protocol-version support alone does not establish post-quantum protection. Federal agencies must support TLS 1.3 by January 2, 2030, but the algorithms negotiated for a given connection are what actually determine whether that connection is quantum-resistant, not merely the TLS version in use. Security teams evaluating vendor quantum-readiness claims can dig deeper via daily.dev."}}]} ```