Overview
Traffic protected by RSA or elliptic-curve key exchange can be recorded today and decrypted once a cryptographically relevant quantum computer exists. NIST names this "harvest now, decrypt later" threat as one of the main reasons the transition is urgent, and warns that, measured against how long past cryptographic transitions have taken, the current deadlines leave little margin. Data that must stay confidential for years is already exposed if it crosses a network on classical key exchange.
The deadlines are now set. NIST published ML-KEM, ML-DSA, and SLH-DSA in August 2024, and its final transition plan, NIST IR 8547, published October 27, 2026, deprecates quantum-vulnerable public-key algorithms after 2030 and disallows them after 2035. Executive Order 14412 requires the most sensitive federal systems to use post-quantum key establishment by December 31, 2030 and post-quantum signatures by December 31, 2031, and directs a proposed rule that would require covered federal contractors to meet the FIPS standards, including post-quantum ones, by December 31, 2030. The European Union roadmap asks Member States to begin the transition by the end of 2026 and to protect high-risk use cases by the end of 2030. Each of these starts with a cryptographic inventory. For a CISO in a regulated industry, the question is where vulnerable cryptography lives and what to fix first.
Most organizations cannot answer that today. Cryptography sits in AWS service settings, in load balancer and API TLS policies, in certificates and keys, and deep inside application code, open source libraries, and container images. Avahi builds a full inventory across all of these layers, then ranks each finding by how long the data it protects must stay confidential, whether it crosses public networks, and whether it anchors long-lived trust.
The work can start now, because much of the capability already exists on AWS. The roadmap separates what AWS already handles, such as hybrid post-quantum TLS on AWS KMS, AWS Certificate Manager, and AWS Secrets Manager endpoints and on viewer connections to Amazon CloudFront, from what the customer must change: post-quantum TLS policies on load balancers and APIs, guardrails that block downgrade, SDK and client upgrades, ML-DSA for signing and private PKI, and crypto-agile design for custom applications. Scope and timing are set with each customer.
Highlights
- A full cryptographic inventory across AWS resources and settings, application code, open source dependencies, and container images.
- Every finding ranked by quantum risk: how long the data must stay confidential, exposure to record-now, decrypt-later collection, and long-lived roots of trust.
- A sequenced roadmap aligned to NIST FIPS 203, 204, and 205 and to the post-quantum capabilities AWS offers today.
Details
Pricing
Custom pricing options
How can we make this page better?
Legal
Content disclaimer
Resources
Vendor resources
Support
Vendor support
Support is provided during the engagement. A named Avahi lead runs regular working sessions with the customer's security team, with cadence agreed in scoping, and answers questions throughout. The engagement closes with delivery of the remediation roadmap and the security leadership readout.
Contact sales@avahi.ai for support.