← Back to rule catalog
Rule R-AES-128
active

AES below 256 bits should be migrated for PQC resilience

Advisory migration rule for symmetric encryption with insufficient long-term margin.

Applies to
*
Cases
1
Evaluation order
60
Tags
aes, symmetric, pqc
Overlay-specific scope
pci-dss-4, hipaa, cmmc
Engine description
AES-128 remains usable today but should be upgraded to AES-256 for long-lived confidentiality.

Match cases

Case 1 medium · plan-2030
When
  • algorithm equals AES
  • keySize < 256
Finding title template
AES-{{asset.keySize}} — migrate to AES-256
Current crypto template
AES-{{asset.keySize}}
Severity / status
medium · advisory
Effort / deadline
medium · 2030-12-31
Recommended replacement
Where available, configure AES-256. Treat 128-bit symmetric keys as short on long-confidentiality data and align new designs, KMS defaults, and partner profiles to 256-bit strength.
Rationale
NIST SP 800-57 key-management guidance and NSA CNSA 2.0 both point high-assurance deployments toward 256-bit symmetric strength. AES-128 remains usable today, but it leaves less long-term margin once quantum search costs are considered.
Citations
  • NIST_SP_800_57_PT1 · Recommendation for Key Management: Part 1 - General
  • BSI_TR_02102_1 · Cryptographic Mechanisms: Recommendations and Key Lengths
  • ENISA_PQC_2024 · Post-Quantum Cryptography: Integration study
  • NSA_CNSA_2_0 · Commercial National Security Algorithm Suite 2.0 FAQ

This is intentionally advisory rather than immediate non-compliance, but it still belongs in the same docs-backed rule catalog as the strict prohibitions.