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

RSA below 2048 bits is already non-compliant

Immediate failure rule for RSA keys below the minimum modern baseline.

Applies to
*
Cases
1
Evaluation order
10
Tags
rsa, key-size, current-failure
Overlay-specific scope
pci-dss-4, nis2, dora, eidas2
Engine description
RSA with key size below 2048 bits is already non-compliant today.

Match cases

Case 1 critical · replace-now
When
  • algorithm equals RSA
  • keySize < 2048
Finding title template
RSA-{{asset.keySize}} in active use — already non-compliant
Current crypto template
RSA-{{asset.keySize}}{{#if asset.signatureHash}} with {{asset.signatureHash}}{{/if}}
Severity / status
critical · already-non-compliant
Effort / deadline
low · 2020-12-31
Recommended replacement
Rotate immediately to ML-DSA (FIPS 204) for signing or ML-KEM (FIPS 203) for key transport. If interoperability blocks PQC adoption, RSA-3072 with SHA-256 is the minimum acceptable interim step.
Rationale
RSA key lengths below 2048 bits are disallowed under NIST SP 800-131A Rev 3 and excluded from BSI TR-02102 approved parameters. Use is a current compliance failure, independent of the post-quantum timeline.
Citations
  • NIST_SP_800_131A · Transitioning the Use of Cryptographic Algorithms and Key Lengths
  • BSI_TR_02102_1 · Cryptographic Mechanisms: Recommendations and Key Lengths
  • NIST_FIPS_204 · Module-Lattice-Based Digital Signature Standard (ML-DSA)

This rule is intentionally strict and date-independent: if the platform still exposes RSA below 2048 bits, the scanner should emit an immediate non-compliance finding without needing a code release.

Keep remediation text and cited sources here so review of the rule logic happens in the same document as the rationale.