← Back to rule catalog
Rule R-RSA-2048
active

RSA at 2048 or 3072 bits requires PQC migration planning

Transition rule for RSA that is still acceptable today but needs scheduled replacement.

Applies to
*
Cases
2
Evaluation order
20
Tags
rsa, migration, pqc
Overlay-specific scope
nis2, dora, cmmc
Engine description
RSA-2048 and RSA-3072 remain usable today but are on the deprecation path.

Match cases

Case 1 high · plan-2030
When
  • algorithm equals RSA
  • keySize between 2048 and 3071
Finding title template
RSA-{{asset.keySize}} — plan PQC migration
Current crypto template
RSA-{{asset.keySize}}{{#if asset.signatureHash}} with {{asset.signatureHash}}{{/if}}
Severity / status
high · deprecated-by-date
Effort / deadline
medium · 2030-12-31
Recommended replacement
Plan migration at the next major rotation window. For signing uses, target ML-DSA (FIPS 204); for key-establishment uses, target ML-KEM (FIPS 203). Where partner ecosystems are not yet ready, deploy hybrid certificates or dual-stack handshakes during the transition.
Rationale
RSA-{{asset.keySize}} remains usable today, but NIST IR 8547 and NSA CNSA 2.0 treat RSA-based signatures and key establishment as transition priorities. Inventory the asset now so partner dependencies and certificate chains are ready before the PQC deadline.
Citations
  • NIST_IR_8547 · Transition to Post-Quantum Cryptography Standards
  • NSA_CNSA_2_0 · Commercial National Security Algorithm Suite 2.0 FAQ
  • NIST_FIPS_203 · Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)
  • NIST_FIPS_204 · Module-Lattice-Based Digital Signature Standard (ML-DSA)
Case 2 medium · plan-2030
When
  • algorithm equals RSA
  • keySize >= 3072
Finding title template
RSA-{{asset.keySize}} — plan PQC migration
Current crypto template
RSA-{{asset.keySize}}{{#if asset.signatureHash}} with {{asset.signatureHash}}{{/if}}
Severity / status
medium · deprecated-by-date
Effort / deadline
medium · 2030-12-31
Recommended replacement
Plan migration at the next major rotation window. For signing uses, target ML-DSA (FIPS 204); for key-establishment uses, target ML-KEM (FIPS 203). Where partner ecosystems are not yet ready, deploy hybrid certificates or dual-stack handshakes during the transition.
Rationale
RSA-{{asset.keySize}} remains usable today, but NIST IR 8547 and NSA CNSA 2.0 treat RSA-based signatures and key establishment as transition priorities. Inventory the asset now so partner dependencies and certificate chains are ready before the PQC deadline.
Citations
  • NIST_IR_8547 · Transition to Post-Quantum Cryptography Standards
  • NSA_CNSA_2_0 · Commercial National Security Algorithm Suite 2.0 FAQ
  • NIST_FIPS_203 · Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)
  • NIST_FIPS_204 · Module-Lattice-Based Digital Signature Standard (ML-DSA)

This rule captures the migration window rather than current breakage.

If the migration date or recommended interim posture changes, the update belongs in this document instead of in application code.