Post-Quantum Readiness Assessment
Adversaries are harvesting encrypted traffic today to decrypt when quantum computers mature — so data with a long secrecy lifetime is already at risk. We inventory every place your organisation uses cryptography and build a pragmatic, standards-aligned migration path to post-quantum algorithms.
Verified Solvex Specialist
Verified by SolvexDirect specialist contact for Solvex engagements
What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.
Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.
What's covered
- Cryptographic inventory: protocols, certificates, libraries, hardware and embedded uses
- Data-lifetime analysis: what you hold that must stay secret past the quantum horizon
- Harvest-now-decrypt-later exposure assessment for data in transit
- Crypto-agility review: how hard each system is to migrate, and why
- NIST PQC standards mapping (ML-KEM, ML-DSA) and hybrid deployment options
- Vendor and dependency readiness: where your migration waits on someone else
What you receive
- Complete cryptographic bill of materials (CBOM) for the systems in scope
- Risk-ranked migration roadmap sequenced by data lifetime and exposure
- Crypto-agility recommendations so this migration is your last painful one
- Vendor readiness matrix with the questions to put in your contracts
- Executive briefing separating the real timeline from vendor fear-marketing
Evidence and reporting
How the work is kept honest- Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
- A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
- Written scope firstAdvisory work runs to a written scope agreed before it starts, so what you receive is what was agreed.
Anyone holding a Solvex report can verify it publicly without seeing its contents.
Our boundaries
What this engagement does not do, stated before it starts.
- Honest framing only — we won't use quantum hype to sell you urgency your data lifetime doesn't justify
- Implementation of new cryptography is a separate, scoped engagement
- We assess vendor readiness from evidence; we can't certify third-party roadmaps
- No predictions of exactly when cryptanalytically-relevant quantum computers arrive — no one honest can
How this engagement runs
- 01
Intake
Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.
- 02
Scope and authorization
Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.
- 03
Investigation or build
Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.
- 04
Evidence
Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.
- 05
Delivery
A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.
- 06
Verification and retest
Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.
Questions we are asked
- Quantum computers can't break encryption yet. Why act now?
- Because of data lifetime, not computer timelines. Traffic captured today can be stored and decrypted whenever the capability arrives — so anything that must stay secret for ten-plus years is effectively already exposed. Add multi-year enterprise migration timelines, and 'wait and see' quietly becomes 'too late' for long-lived data.
- What are ML-KEM and ML-DSA?
- The NIST-standardised post-quantum algorithms (FIPS 203 and 204): ML-KEM for key establishment, ML-DSA for signatures. Major browsers, cloud providers and TLS stacks are already deploying them, usually in hybrid mode alongside classical algorithms — which is the deployment pattern we typically recommend first.
- How disruptive is the migration?
- It varies enormously by system, which is what the crypto-agility review measures. Modern TLS termination points can move quickly; embedded devices, hardware security modules and long-lived document signatures are the hard tail. The roadmap sequences the easy, high-exposure wins first so risk drops early.
Related services
Offensive / Testing
Security Architecture Review
The cheapest vulnerabilities to fix are the ones you design out. We review your system architecture against threats and best practice to find structural weaknesses before they become expensive incidents.
Governance / Compliance
ISO 27001 Readiness & Certification Support
Get certification-ready without the guesswork. We build or align your information security management system to ISO 27001, run the gap analysis, prepare the evidence and stand beside you through the audit.
Governance / Compliance
Virtual CISO (vCISO)
Executive security leadership without a full-time hire. Our virtual CISO sets your security strategy, manages risk, guides compliance and represents security to your board — scaled to what you actually need.