Context dependent. In the idealized query model, Grover search reduces exhaustive AES-128 key search from roughly 2^128 to roughly 2^64 queries, but real attack cost and policy acceptability depend on implementation and assurance requirements.
Key Takeaway: AES-128's quantum safety is uncertain. Upgrade to AES-256 for long-term quantum resistance. This is typically a configuration change, not a protocol migration.
AES-128 quantum safety is uncertain.
AES-128 is identical to AES-256 in structure — both are symmetric block ciphers operating on 128-bit blocks using the same substitution-permutation network architecture. The difference is key size: AES-128 uses a 128-bit key (16 bytes) and performs 10 rounds of transformations, compared to 14 rounds for AES-256. The smaller key size makes AES-128 faster (approximately 20-30% higher throughput) and uses less memory, making it attractive for resource-constrained environments like embedded systems and mobile devices.
AES-128 was adopted by NIST in 2001 and has been the default cipher for many applications: it is the minimum encryption standard for Wi-Fi WPA2/WPA3, the default TLS 1.3 cipher (TLS_AES_128_GCM_SHA256), commonly used for disk encryption (BitLocker, FileVault, dm-crypt), and widely deployed in VPN protocols (IPsec, OpenVPN, WireGuard).
Classically, AES-128 provides 128 bits of security — requiring 2128 operations (approximately 340 undecillion attempts) to brute force, considered computationally infeasible for any foreseeable classical computer.
In the idealized query model, Grover search lowers exhaustive AES-128 key search to on the order of 264 oracle queries. A real attack also needs reversible AES circuits, error correction, repeated runs, and key verification, so the shorthand does not equal a demonstrated 64-bit classical attack.
No verified evidence supports a universal weeks-to-months break estimate. Real cost depends on circuit depth, parallelization limits, error correction, oracle construction, key verification, and the target's operational constraints.
NSA's CNSA 2.0 profile specifies AES-256 for its NSS scope. That scoped requirement should not be restated as a universal NIST claim or as evidence that AES-128 has a known 2030-2040 failure date.
Upgrade from AES-128 to AES-256 for long-term quantum resistance. This is typically a configuration change, not a protocol replacement:
Healthcare entities should select symmetric-key strength from their actual data lifetime, threat model, applicable law, contracts, and risk analysis. HIPAA does not create a universal 50-year retention rule or prescribe AES-256.
Financial record periods and cryptographic requirements vary by record, regulator, contract, and jurisdiction. Choose AES-128 or AES-256 from the applicable control profile and measured data lifetime rather than a universal sector retention range.
CNSA 2.0 specifies AES-256 for all classification levels in its NSS scope. NSA states that these requirements do not direct entities outside NSS, though interoperability or contractual contexts may adopt them.
Enterprise data backup and archival systems often use AES-128 for encryption-at-rest due to performance advantages. Organizations with multi-decade data retention policies (legal holds, compliance archives, long-term research data) should upgrade to AES-256 to ensure adequate security margins.
Organizations should adopt AES-256 as the default symmetric cipher for new deployments, reserving AES-128 only for low-security, short-lifetime data protection where performance constraints are critical.
| Full Name | Advanced Encryption Standard with 128-bit keys |
| Category | encryption |
| Key Size | 128-bit key (idealized Grover query complexity on the order of 2^64) |
| Quantum Vulnerability | Generic quantum key search has idealized query complexity on the order of 2^64; concrete circuit and hardware costs are architecture-dependent. |
| NIST Status | AES-128 remains a NIST-standardized cipher. CNSA 2.0 specifies AES-256 within its NSS scope; application-specific policy determines acceptability elsewhere. |
| Deprecation Timeline | No universal deprecation date. CNSA 2.0 specifies AES-256 within its NSS scope; other contexts follow their applicable profiles and risk decisions. |
| Replaced By | AES-256 (configuration upgrade) |
Algorithm-level classification. Standards status and known cryptanalysis are separated from implementation, module-validation, protocol-composition, key-management, and policy evidence.
Evidence-scope review: 2026-07-10
Upgrade to AES-256 for long-term quantum resistance. This is typically a configuration change, not a protocol migration.
QScout discovers instances of AES-128 across your infrastructure within the approved engagement window — designed to minimize operational disruption. First-findings timing is set during operator scoping.