{"asset": "nist-cryptographic-algorithm-deprecation-schedule", "asset_type": "deprecation-schedule", "body": "Per-algorithm status under NIST guidance for the post-quantum cryptographic transition. Each record is one algorithm or key-length configuration with its current approval status (approved, acceptable, deprecated, restricted, disallowed, legacy use), the date at which the status changes, and the recommended replacement. Drawn from three NIST publications: IR 8547 (post-quantum transition timeline), SP 800-131A Rev 2 (current algorithm status rules) and Rev 3 draft (upcoming changes), and FIPS 203/204/205 (the post-quantum replacement standards). The key deadlines: quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) deprecated after 2030, disallowed after 2035; SHA-1 and 224-bit hashes deprecated through 2030, disallowed thereafter. AES-256 and SHA-2/SHA-3 are NOT on the deprecation schedule. Answers 'when is RSA deprecated?', 'is AES-256 affected by the post-quantum transition?', 'what replaces ECDSA?', and 'what is the current NIST status of 3DES?'\n", "description": "Per-algorithm status under NIST guidance for the post-quantum cryptographic transition. Each record is one algorithm or key-length configuration with its current approval status (approved, acceptable, deprecated, restricted, disallowed, legacy use), the date at which the status changes, and the recommended replacement. Drawn from three NIST publications: IR 8547 (post-quantum transition timeline), SP 800-131A Rev 2 (current algorithm status rules) and Rev 3 draft (upcoming changes), and FIPS 203/204/205 (the post-quantum replacement standards). The key deadlines: quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) deprecated after 2030, disallowed after 2035; SHA-1 and 224-bit hashes deprecated through 2030, disallowed thereafter. AES-256 and SHA-2/SHA-3 are NOT on the deprecation schedule. Answers 'when is RSA deprecated?', 'is AES-256 affected by the post-quantum transition?', 'what replaces ECDSA?', and 'what is the current NIST status of 3DES?'", "file": "index.md", "generated": true, "harvested": "2026-08-15", "key_field": "algorithm", "licence": "US government publication \u2014 public domain", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/", "https://csrc.nist.gov/pubs/sp/800/131/a/r2/final", "https://csrc.nist.gov/projects/post-quantum-cryptography", "https://csrc.nist.gov/pubs/ir/8547/ipd"], "stale_after": "2027-02-11", "title": "NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "type": "dataset", "verified": false}
{"algorithm": "224-bit hash functions", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** 224-bit hash functions\n\n**Purpose:** hashing\n\n**Current status:** Acceptable\n\n**Planned status:** Scheduled for retirement (SP 800-131A Rev 3 draft)\n\n**Replacement:** SHA-256 or higher\n\n**Source document:** SP 800-131A Rev 3 draft (via EncryptionConsulting summary)\n\n> SHA-1 and 224-bit hashes are being retired, but for classical-strength reasons unrelated to the quantum public-key transition.\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Acceptable", "file": "224-bit-hash-functions.md", "generated": true, "harvested": "2026-08-15", "id": "224-bit-hash-functions", "nist_document": "SP 800-131A Rev 3 draft (via EncryptionConsulting summary)", "purpose": "hashing", "replacement": "SHA-256 or higher", "source_quote": "SHA-1 and 224-bit hashes are being retired, but for classical-strength reasons unrelated to the quantum public-key transition.", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "224-bit hash functions \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Scheduled for retirement (SP 800-131A Rev 3 draft)", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "AES-256", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** AES-256\n\n**Purpose:** encryption\n\n**Current status:** Approved\n\n**Planned status:** No change planned\n\n**Replacement:** N/A\n\n**Source document:** IR 8547 (not on deprecation schedule, per EncryptionConsulting summary)\n\n> It defines the formal approval status (approved, acceptable, deprecated, restricted, disallowed, or legacy use) of specific algorithms and key lengths, and it is the document a FIPS-validated implementation is measured against. The current finalized version is SP 800-131A Revision 2, published in March 2019. NIST released an initial public draft of Revision 3 in October 2024. Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030, retires ECB confidentiality mode and DSA signature generation, and schedules the retirement of SHA-1 and 224-bit hash functions. To avoid forcing organizations through two separate transitions, NIST plans to fold the asymmetric-algorithm transition into the post-quantum transition rather than enforcing a separate 128-bit step for public-key algorithms. As of mid-2026, Revision 3 remains a draft, so Revision 2 is the version currently in force. What Is Not on the Schedule A common misreading is that everything cryptographic must change. It does not. The deprecation and disallowance timeline targets public-key cryptography specifically. AES-256 is not on the schedule: Grover&#8217;s algorithm offers only a quadratic speedup against symmetric ciphers, leaving AES-256 with roughly 128 bits of effective quantum security, which is acceptable for the foreseeable future. SHA-2 and SHA-3 are not on the public-key schedule: These hash families remain secure against quantum attacks at appropriate output sizes. (SHA-1 and 224-bit hashes are being retired for unrelated classical-strength reasons.) The exposure is public-key: <https://www.encryptionconsulting.com/education-center/what-is-rsa/>\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "aes-256.md", "generated": true, "harvested": "2026-08-15", "id": "aes-256", "nist_document": "IR 8547 (not on deprecation schedule, per EncryptionConsulting summary)", "purpose": "encryption", "replacement": "N/A", "source_quote": "It defines the formal approval status (approved, acceptable, deprecated, restricted, disallowed, or legacy use) of specific algorithms and key lengths, and it is the document a FIPS-validated implementation is measured against. The current finalized version is SP 800-131A Revision 2, published in March 2019. NIST released an initial public draft of Revision 3 in October 2024. Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030, retires ECB confidentiality mode and DSA signature generation, and schedules the retirement of SHA-1 and 224-bit hash functions. To avoid forcing organizations through two separate transitions, NIST plans to fold the asymmetric-algorithm transition into the post-quantum transition rather than enforcing a separate 128-bit step for public-key algorithms. As of mid-2026, Revision 3 remains a draft, so Revision 2 is the version currently in force. What Is Not on the Schedule A common misreading is that everything cryptographic must change. It does not. The deprecation and disallowance timeline targets public-key cryptography specifically. AES-256 is not on the schedule: Grover&#8217;s algorithm offers only a quadratic speedup against symmetric ciphers, leaving AES-256 with roughly 128 bits of effective quantum security, which is acceptable for the foreseeable future. SHA-2 and SHA-3 are not on the public-key schedule: These hash families remain secure against quantum attacks at appropriate output sizes. (SHA-1 and 224-bit hashes are being retired for unrelated classical-strength reasons.) The exposure is public-key: <https://www.encryptionconsulting.com/education-center/what-is-rsa/>", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "AES-256 \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "No change planned", "type": "deprecation-schedule", "unverified_fields": "nist_document, replacement, transition_status", "verified": true}
{"algorithm": "Classical algorithms below 112-bit security strength", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** Classical algorithms below 112-bit security strength\n\n**Purpose:** all cryptographic purposes\n\n**Current status:** Disallowed\n\n**Planned status:** No change planned (already disallowed under Rev 2)\n\n**Replacement:** Algorithms meeting minimum 112-bit security strength\n\n**Source document:** SP 800-131A Rev 2 (March 2019)\n\n> provides more specific guidance for transitions to the use of stronger cryptographic keys and more robust algorithms\n\nSource: <https://csrc.nist.gov/pubs/sp/800/131/a/r2/final>\n", "current_status": "Disallowed", "file": "classical-algorithms-below-112-bit-security-strength.md", "generated": true, "harvested": "2026-08-15", "id": "classical-algorithms-below-112-bit-security-strength", "nist_document": "SP 800-131A Rev 2 (March 2019)", "purpose": "all cryptographic purposes", "replacement": "Algorithms meeting minimum 112-bit security strength", "source_quote": "provides more specific guidance for transitions to the use of stronger cryptographic keys and more robust algorithms", "sources": ["https://csrc.nist.gov/pubs/sp/800/131/a/r2/final"], "stale_after": "2027-02-11", "title": "Classical algorithms below 112-bit security strength \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "No change planned (already disallowed under Rev 2)", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "DSA (signature generation)", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** DSA (signature generation)\n\n**Purpose:** digital signature\n\n**Current status:** Deprecated\n\n**Planned status:** Disallowed (SP 800-131A Rev 3 draft proposes retirement)\n\n**Replacement:** ML-DSA (FIPS 204)\n\n**Source document:** SP 800-131A Rev 3 draft (via EncryptionConsulting summary)\n\n> Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030, retires ECB confidentiality mode and DSA signature generation, and schedules the retirement of SHA-1 and 224-bit hash functions.\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Deprecated", "file": "dsa-signature-generation.md", "generated": true, "harvested": "2026-08-15", "id": "dsa-signature-generation", "nist_document": "SP 800-131A Rev 3 draft (via EncryptionConsulting summary)", "purpose": "digital signature", "replacement": "ML-DSA (FIPS 204)", "source_quote": "Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030, retires ECB confidentiality mode and DSA signature generation, and schedules the retirement of SHA-1 and 224-bit hash functions.", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "DSA (signature generation) \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Disallowed (SP 800-131A Rev 3 draft proposes retirement)", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "ECB mode", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** ECB mode\n\n**Purpose:** encryption\n\n**Current status:** Acceptable\n\n**Planned status:** Disallowed (SP 800-131A Rev 3 draft proposes retirement)\n\n**Replacement:** CBC, CTR, GCM, or other approved modes\n\n**Source document:** SP 800-131A Rev 3 draft (via EncryptionConsulting summary)\n\n> Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030, retires ECB confidentiality mode and DSA signature generation, and schedules the retirement of SHA-1 and 224-bit hash functions.\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Acceptable", "file": "ecb-mode.md", "generated": true, "harvested": "2026-08-15", "id": "ecb-mode", "nist_document": "SP 800-131A Rev 3 draft (via EncryptionConsulting summary)", "purpose": "encryption", "replacement": "CBC, CTR, GCM, or other approved modes", "source_quote": "Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030, retires ECB confidentiality mode and DSA signature generation, and schedules the retirement of SHA-1 and 224-bit hash functions.", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "ECB mode \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Disallowed (SP 800-131A Rev 3 draft proposes retirement)", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "ECDH", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** ECDH\n\n**Purpose:** key establishment\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-KEM (FIPS 203)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "ecdh.md", "generated": true, "harvested": "2026-08-15", "id": "ecdh", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "key establishment", "replacement": "ML-KEM (FIPS 203)", "source_quote": "quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "ECDH \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "current_status, nist_document, purpose, replacement, transition_status", "verified": true}
{"algorithm": "ECDSA", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** ECDSA\n\n**Purpose:** digital signature\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-DSA (FIPS 204)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "ecdsa.md", "generated": true, "harvested": "2026-08-15", "id": "ecdsa", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "digital signature", "replacement": "ML-DSA (FIPS 204)", "source_quote": "quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "ECDSA \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "current_status, nist_document, purpose, replacement, transition_status", "verified": true}
{"algorithm": "EdDSA", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** EdDSA\n\n**Purpose:** digital signature\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-DSA (FIPS 204)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> ECDSA , EdDSA, RSA-PSS, RSA PKCS#1 v1.5), and key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman. All are broken by Shor\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "eddsa.md", "generated": true, "harvested": "2026-08-15", "id": "eddsa", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "digital signature", "replacement": "ML-DSA (FIPS 204)", "source_quote": "ECDSA , EdDSA, RSA-PSS, RSA PKCS#1 v1.5), and key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman. All are broken by Shor", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "EdDSA \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "current_status, nist_document, purpose, replacement, transition_status", "verified": true}
{"algorithm": "Falcon", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** Falcon\n\n**Purpose:** digital signature\n\n**Current status:** Selected for standardization\n\n**Planned status:** Pending FIPS standard\n\n**Replacement:** N/A\n\n**Source document:** PQC project page\n\n> Falcon digital signature algorithm and <https://csrc.nist.gov/news/2025/hqc-announced-as-a-4th-round-selection> HQC key encapsulation mechanism were selected for ongoing standardization; that process is underway. This process continues with a longer-term effort that solicited additional algorithms for digital signature schemes that could serve as a backup to ML-DSA or that could address unique use cases. Learn more on the <https://csrc.nist.gov/projects/pqc-dig-sig> Additional Digital Signature Schemes page. HQC was selected for standardization on March 11, 2025.\n\nSource: <https://csrc.nist.gov/projects/post-quantum-cryptography>\n", "current_status": "Selected for standardization", "file": "falcon.md", "generated": true, "harvested": "2026-08-15", "id": "falcon", "nist_document": "PQC project page", "purpose": "digital signature", "replacement": "N/A", "source_quote": "Falcon digital signature algorithm and <https://csrc.nist.gov/news/2025/hqc-announced-as-a-4th-round-selection> HQC key encapsulation mechanism were selected for ongoing standardization; that process is underway. This process continues with a longer-term effort that solicited additional algorithms for digital signature schemes that could serve as a backup to ML-DSA or that could address unique use cases. Learn more on the <https://csrc.nist.gov/projects/pqc-dig-sig> Additional Digital Signature Schemes page. HQC was selected for standardization on March 11, 2025.", "sources": ["https://csrc.nist.gov/projects/post-quantum-cryptography"], "stale_after": "2027-02-11", "title": "Falcon \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Pending FIPS standard", "type": "deprecation-schedule", "unverified_fields": "nist_document, replacement, transition_status", "verified": true}
{"algorithm": "Finite-field Diffie-Hellman", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** Finite-field Diffie-Hellman\n\n**Purpose:** key establishment\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-KEM (FIPS 203)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "finite-field-diffie-hellman.md", "generated": true, "harvested": "2026-08-15", "id": "finite-field-diffie-hellman", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "key establishment", "replacement": "ML-KEM (FIPS 203)", "source_quote": "quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "Finite-field Diffie-Hellman \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "HQC", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** HQC\n\n**Purpose:** key establishment\n\n**Current status:** Selected for standardization\n\n**Planned status:** Pending FIPS standard\n\n**Replacement:** N/A\n\n**Source document:** PQC project page (selected March 2025)\n\n> HQC was selected for standardization on March 11, 2025.\n\nSource: <https://csrc.nist.gov/projects/post-quantum-cryptography>\n", "current_status": "Selected for standardization", "file": "hqc.md", "generated": true, "harvested": "2026-08-15", "id": "hqc", "nist_document": "PQC project page (selected March 2025)", "purpose": "key establishment", "replacement": "N/A", "source_quote": "HQC was selected for standardization on March 11, 2025.", "sources": ["https://csrc.nist.gov/projects/post-quantum-cryptography"], "stale_after": "2027-02-11", "title": "HQC \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Pending FIPS standard", "type": "deprecation-schedule", "unverified_fields": "nist_document, purpose, replacement, transition_status", "verified": true}
{"algorithm": "ML-DSA (FIPS 204)", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** ML-DSA (FIPS 204)\n\n**Purpose:** digital signature\n\n**Current status:** Approved\n\n**Planned status:** No change planned\n\n**Replacement:** N/A\n\n**Source document:** FIPS 204 (August 2024)\n\n> Module-Lattice-Based Digital Signature Standard (ML-DSA)\n\nSource: <https://csrc.nist.gov/projects/post-quantum-cryptography>\n", "current_status": "Approved", "file": "ml-dsa-fips-204.md", "generated": true, "harvested": "2026-08-15", "id": "ml-dsa-fips-204", "nist_document": "FIPS 204 (August 2024)", "purpose": "digital signature", "replacement": "N/A", "source_quote": "Module-Lattice-Based Digital Signature Standard (ML-DSA)", "sources": ["https://csrc.nist.gov/projects/post-quantum-cryptography"], "stale_after": "2027-02-11", "title": "ML-DSA (FIPS 204) \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "No change planned", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, replacement, transition_status", "verified": false}
{"algorithm": "ML-KEM (FIPS 203)", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** ML-KEM (FIPS 203)\n\n**Purpose:** key establishment\n\n**Current status:** Approved\n\n**Planned status:** No change planned\n\n**Replacement:** N/A\n\n**Source document:** FIPS 203 (August 2024)\n\n> Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM)\n\nSource: <https://csrc.nist.gov/projects/post-quantum-cryptography>\n", "current_status": "Approved", "file": "ml-kem-fips-203.md", "generated": true, "harvested": "2026-08-15", "id": "ml-kem-fips-203", "nist_document": "FIPS 203 (August 2024)", "purpose": "key establishment", "replacement": "N/A", "source_quote": "Module-Lattice-Based Key-Encapsulation Mechanism Standard (ML-KEM)", "sources": ["https://csrc.nist.gov/projects/post-quantum-cryptography"], "stale_after": "2027-02-11", "title": "ML-KEM (FIPS 203) \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "No change planned", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "Quantum-vulnerable public-key algorithms (general)", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** Quantum-vulnerable public-key algorithms (general)\n\n**Purpose:** digital signature and key establishment\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** Post-quantum standards (FIPS 203, 204, 205)\n\n**Source document:** IR 8547 (Initial Public Draft, November 12, 2024)\n\n> This report describes NIST\u2019s expected approach to transitioning from quantum-vulnerable cryptographic algorithms to post-quantum digital signature algorithms and key-establishment schemes.\n\nSource: <https://csrc.nist.gov/pubs/ir/8547/ipd>\n", "current_status": "Approved", "file": "quantum-vulnerable-public-key-algorithms-general.md", "generated": true, "harvested": "2026-08-15", "id": "quantum-vulnerable-public-key-algorithms-general", "nist_document": "IR 8547 (Initial Public Draft, November 12, 2024)", "purpose": "digital signature and key establishment", "replacement": "Post-quantum standards (FIPS 203, 204, 205)", "source_quote": "This report describes NIST\u2019s expected approach to transitioning from quantum-vulnerable cryptographic algorithms to post-quantum digital signature algorithms and key-establishment schemes.", "sources": ["https://csrc.nist.gov/pubs/ir/8547/ipd"], "stale_after": "2027-02-11", "title": "Quantum-vulnerable public-key algorithms (general) \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "RSA key transport", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** RSA key transport\n\n**Purpose:** key establishment\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-KEM (FIPS 203)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "rsa-key-transport.md", "generated": true, "harvested": "2026-08-15", "id": "rsa-key-transport", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "key establishment", "replacement": "ML-KEM (FIPS 203)", "source_quote": "key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "RSA key transport \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "current_status, nist_document, purpose, replacement, transition_status", "verified": true}
{"algorithm": "RSA PKCS#1 v1.5 (signatures)", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** RSA PKCS#1 v1.5 (signatures)\n\n**Purpose:** digital signature\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-DSA (FIPS 204)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> ECDSA , EdDSA, RSA-PSS, RSA PKCS#1 v1.5), and key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman. All are broken by Shor\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "rsa-pkcs-1-v1-5-signatures.md", "generated": true, "harvested": "2026-08-15", "id": "rsa-pkcs-1-v1-5-signatures", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "digital signature", "replacement": "ML-DSA (FIPS 204)", "source_quote": "ECDSA , EdDSA, RSA-PSS, RSA PKCS#1 v1.5), and key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman. All are broken by Shor", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "RSA PKCS#1 v1.5 (signatures) \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "RSA-PSS", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** RSA-PSS\n\n**Purpose:** digital signature\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-DSA (FIPS 204)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> ECDSA , EdDSA, RSA-PSS, RSA PKCS#1 v1.5), and key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman. All are broken by Shor\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "rsa-pss.md", "generated": true, "harvested": "2026-08-15", "id": "rsa-pss", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "digital signature", "replacement": "ML-DSA (FIPS 204)", "source_quote": "ECDSA , EdDSA, RSA-PSS, RSA PKCS#1 v1.5), and key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman. All are broken by Shor", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "RSA-PSS \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "current_status, nist_document, purpose, replacement, transition_status", "verified": true}
{"algorithm": "RSA (signatures)", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** RSA (signatures)\n\n**Purpose:** digital signature\n\n**Current status:** Approved\n\n**Planned status:** Deprecated after 2030, Disallowed after 2035\n\n**Replacement:** ML-DSA (FIPS 204)\n\n**Source document:** IR 8547, Section 3 (via EncryptionConsulting summary)\n\n> quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "rsa-signatures.md", "generated": true, "harvested": "2026-08-15", "id": "rsa-signatures", "nist_document": "IR 8547, Section 3 (via EncryptionConsulting summary)", "purpose": "digital signature", "replacement": "ML-DSA (FIPS 204)", "source_quote": "quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "RSA (signatures) \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Deprecated after 2030, Disallowed after 2035", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "SHA-1", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** SHA-1\n\n**Purpose:** hashing\n\n**Current status:** Deprecated\n\n**Planned status:** Disallowed (SP 800-131A Rev 3 draft proposes retirement)\n\n**Replacement:** SHA-2 or SHA-3\n\n**Source document:** SP 800-131A Rev 2 / Rev 3 draft (via EncryptionConsulting summary)\n\n> SHA-1 and 224-bit hashes are being retired, but for classical-strength reasons unrelated to the quantum public-key transition.\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Deprecated", "file": "sha-1.md", "generated": true, "harvested": "2026-08-15", "id": "sha-1", "nist_document": "SP 800-131A Rev 2 / Rev 3 draft (via EncryptionConsulting summary)", "purpose": "hashing", "replacement": "SHA-2 or SHA-3", "source_quote": "SHA-1 and 224-bit hashes are being retired, but for classical-strength reasons unrelated to the quantum public-key transition.", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "SHA-1 \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "Disallowed (SP 800-131A Rev 3 draft proposes retirement)", "type": "deprecation-schedule", "unverified_fields": "current_status, nist_document, purpose, replacement, transition_status", "verified": true}
{"algorithm": "SHA-2 family", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** SHA-2 family\n\n**Purpose:** hashing\n\n**Current status:** Approved\n\n**Planned status:** No change planned\n\n**Replacement:** N/A\n\n**Source document:** IR 8547 (not on deprecation schedule, per EncryptionConsulting summary)\n\n> SHA-2 and SHA-3 are not on the public-key schedule: These hash families remain secure against quantum attacks at appropriate output sizes.\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "sha-2-family.md", "generated": true, "harvested": "2026-08-15", "id": "sha-2-family", "nist_document": "IR 8547 (not on deprecation schedule, per EncryptionConsulting summary)", "purpose": "hashing", "replacement": "N/A", "source_quote": "SHA-2 and SHA-3 are not on the public-key schedule: These hash families remain secure against quantum attacks at appropriate output sizes.", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "SHA-2 family \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "No change planned", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "SHA-3 family", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** SHA-3 family\n\n**Purpose:** hashing\n\n**Current status:** Approved\n\n**Planned status:** No change planned\n\n**Replacement:** N/A\n\n**Source document:** IR 8547 (not on deprecation schedule, per EncryptionConsulting summary)\n\n> SHA-2 and SHA-3 are not on the public-key schedule: These hash families remain secure against quantum attacks at appropriate output sizes.\n\nSource: <https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/>\n", "current_status": "Approved", "file": "sha-3-family.md", "generated": true, "harvested": "2026-08-15", "id": "sha-3-family", "nist_document": "IR 8547 (not on deprecation schedule, per EncryptionConsulting summary)", "purpose": "hashing", "replacement": "N/A", "source_quote": "SHA-2 and SHA-3 are not on the public-key schedule: These hash families remain secure against quantum attacks at appropriate output sizes.", "sources": ["https://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/"], "stale_after": "2027-02-11", "title": "SHA-3 family \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "No change planned", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, purpose, replacement, transition_status", "verified": false}
{"algorithm": "SLH-DSA (FIPS 205)", "asset": "nist-cryptographic-algorithm-deprecation-schedule", "body": "**Algorithm:** SLH-DSA (FIPS 205)\n\n**Purpose:** digital signature\n\n**Current status:** Approved\n\n**Planned status:** No change planned\n\n**Replacement:** N/A\n\n**Source document:** FIPS 205 (August 2024)\n\n> Stateless Hash-Based Digital Signature Standard (SLH-DSA)\n\nSource: <https://csrc.nist.gov/projects/post-quantum-cryptography>\n", "current_status": "Approved", "file": "slh-dsa-fips-205.md", "generated": true, "harvested": "2026-08-15", "id": "slh-dsa-fips-205", "nist_document": "FIPS 205 (August 2024)", "purpose": "digital signature", "replacement": "N/A", "source_quote": "Stateless Hash-Based Digital Signature Standard (SLH-DSA)", "sources": ["https://csrc.nist.gov/projects/post-quantum-cryptography"], "stale_after": "2027-02-11", "title": "SLH-DSA (FIPS 205) \u2014 NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when", "transition_status": "No change planned", "type": "deprecation-schedule", "unverified_fields": "algorithm, current_status, nist_document, replacement, transition_status", "verified": false}