Standards are final
The three post-quantum FIPS standards are no longer drafts. Regulators, auditors and customers will increasingly expect a documented migration posture — not an intention to start one.
The post-quantum transition is no longer a research topic — it is a compliance clock. Veriqa turns a cryptographic inventory into a phased, NIST-mapped migration plan: every asset scored by shelf life and harvest-now exposure, every memo gated by a mandatory reviewer step before it ships as board-ready. Evidence-first. No vendor pitch.
NIST finalized FIPS 203 (ML-KEM), 204 (ML-DSA) and 205 (SLH-DSA) in August 2024. "Harvest-now, decrypt-later" is live: adversaries archive encrypted traffic today and decrypt it once a cryptographically relevant quantum computer exists. Any secret with a shelf life beyond roughly 5–10 years is already exposed. Waiting is a risk decision — not a neutral one.
The three post-quantum FIPS standards are no longer drafts. Regulators, auditors and customers will increasingly expect a documented migration posture — not an intention to start one.
Traffic captured today can be decrypted later. For long-lived secrets — health records, financial data, state secrets, root keys — the breach window opened before the migration began.
SHA-1 and MD5 are broken now, not in some quantum future. They surface in legacy systems, embedded firmware and third-party libraries that no one has fully inventoried.
Most security teams lack the in-house cryptography depth to inventory every algorithm, map it to a NIST target, and defend the priority order to a board on a deadline.
Standards facts cited from NIST FIPS 203 (ML-KEM), 204 (ML-DSA) and 205 (SLH-DSA), finalized August 2024. The shelf-life threshold is an illustrative planning heuristic, not a regulatory figure. Illustrative
Veriqa takes what your systems actually use today and returns a migration plan mapped to the NIST standards — prioritized by urgency, exportable, and held in draft until a reviewer approves it. The agent does not touch your keys or systems; it reasons over the inventory you provide.
Four steps turn a raw inventory into a defensible decision record. Each step is structured so the output can be audited line by line.
Catalogue every system: its role (key exchange, signature, encryption, hash), its current algorithm, its data shelf life, and any regulatory deadline that applies.
RSA / ECDH → ML-KEM (FIPS 203). ECDSA / RSA-sig → ML-DSA (FIPS 204). High-assurance and firmware signing → SLH-DSA (FIPS 205). SHA-1 / MD5 → flagged broken, P1.
P1 (now) = broken primitives or long-shelf-life key exchange. P2 (12–36 mo) = standard asymmetric migration. P3 (36+ mo) = symmetric review — confirm AES-256 and SHA-256+ are already in use, extending key or hash lengths only where a non-quantum policy requires it.
The plan compiles into a board-ready Markdown memo. It stays in draft until an internal reviewer approves it — the software enforces the gate; no memo ships as final without that sign-off.
Phase windows are planning guidance, not regulatory deadlines or guarantees; sequence and timing depend on your environment and obligations. Algorithm mappings reflect the NIST FIPS 203/204/205 target families. Illustrative
Every engagement produces the same structured artifacts — auditable, exportable, and held in draft until the reviewer gate clears.
If the data you protect today still matters in a decade, harvest-now-decrypt-later already applies to you.
Banks, insurers and market infrastructure with long-retention records, PKI estates and supervisory expectations that increasingly reference post-quantum readiness.
Patient records, genomic data and trial data carry decades-long confidentiality obligations — the definition of a long-lived secret.
Energy, transport, telecoms and industrial control systems with embedded firmware and long device lifecycles that are hard to re-key in the field.
Government, defense, legal and any enterprise with root keys, IP or state secrets whose value outlasts the migration timeline.
A plan. Veriqa is not a network scanner or an automated discovery tool — it reasons over the cryptographic inventory you provide and returns a prioritized, NIST-mapped migration plan with a board-ready memo. Discovery tooling can feed the inventory; Veriqa turns that inventory into a defensible decision.
No. Veriqa operates on the inventory and metadata you supply. It does not connect to your systems, hold your keys, or execute any cryptographic change. Implementation stays entirely within your environment and your control.
Every plan is held in draft until an internal reviewer approves it — a gate the software enforces. We do not claim staffed expert sign-off; we recommend independent cryptographic review before you act on any plan.
That depends on the size and completeness of your inventory. The agent produces a draft plan quickly once the inventory is structured; the timeline to a reviewed, board-ready memo depends on inventory quality and the reviewer step. Phase windows in the plan are planning guidance, not guarantees.
The first migration is the expensive one. The roadmap recommends algorithm-swappable infrastructure so that when standards evolve again, you replace algorithms by configuration rather than by re-engineering. Crypto-agility is treated as the durable outcome, not a one-time swap.
Tell us the size of your estate and the deadlines you face. We respond with a scope and a fixed price — and a plan held in draft until the reviewer gate clears. Forward-looking timelines on this page are guidance, not guarantees.