Post-Quantum-Cryptography

tag: Post-Quantum-Cryptography · 2 items

Platform/SRE — Plan: AWS KMS now GA with all three ML-KEM key specs, backed by FIPS 140-3 HSMs — evaluate adopting ML-KEM for workloads handling long-lived sensitive data as part of a PQC migration plan this quarter; no forced deadline, but the NIST IR 8547 roadmap signals classical key-exchange schemes will be phased out.
CI/CD — Skip
Leader — Learn: AWS KMS adding ML-KEM signals cloud providers are operationalizing NIST’s PQC standards; useful context for shaping a post-quantum cryptography roadmap, but no licensing change, cost impact, or deadline requires a decision now.

Platform/SRE — Plan: Apigee X instances below 1-17-0-apigee-10 with maintenance windows configured will be auto-updated within 7–21 days of July 16; verify now that your instances don’t carry the DNS misconfiguration (known issue 445936920) or a dependency on the removed Apigee Java Library, as either will block the automatic update. Cloud KMS ML-DSA and SLH-DSA post-quantum signing algorithms are now GA — add PQC key-management evaluation to this quarter’s platform roadmap.
CI/CD — Skip
Leader — Learn: Google Cloud KMS now offers post-quantum signing algorithms (ML-DSA, SLH-DSA families) in GA — a signal that PQC migration timelines are becoming concrete and worth factoring into the org’s long-term cryptographic standards and compliance planning.
Signals: GA announcement