Everyone else is selling a platform to manage the migration. We do the part that has to happen first: read what is actually on the wire, and hand back an inventory you can act on. VPQ Audit runs on your own infrastructure, offline if it has to be, so captures and keys stay inside your network.
Harvest-now-decrypt-later attacks your key exchange today, not your certificates. VPQ Audit shows which endpoints still negotiate classical key exchange, gives you the configuration to switch them to hybrid ML-KEM (nginx, Apache, HAProxy, Envoy, OpenSSH and strongSwan, each with a rollback), and proves the change with a before/after Remediation Effectiveness Report comparing two assessments. It needs OpenSSL 3.5 or later on the server; recent Caddy versions already negotiate it by default.
What it is for: the cipher and protocol inventory PCI DSS 12.3.3 asks for every year, a CBOM for your customers' security questionnaires, and a dated plan against the CNSA 2.0 and NIST IR 8547 timelines.
Cipher suites and protocols in use must be documented and reviewed at least once every 12 months: an up-to-date inventory, monitoring of their continued viability, and a strategy for expected changes. It does not require post-quantum algorithms; it requires knowing what you run. PCI SSC document library
New acquisitions for US National Security Systems must support the CNSA 2.0 suite from that date, unless an exception is noted. It binds NSS owners and their vendors, and it is the date the rest of the market is reading. NSA post-quantum resources
Swiss supervised institutions are expected to have a post-quantum roadmap by mid-2027, built on a cryptographic inventory. In FINMA's survey of 60 institutions, 8% had one. FINMA, 9 July 2026
Member States start the transition by the end of 2026, including inventories, and move high-risk systems to post-quantum cryptography by 2030 at the latest; NIST's draft IR 8547 deprecates 112-bit keys such as RSA-2048 after 2030 and disallows all quantum-vulnerable algorithms after 2035. European Commission · NIST IR 8547 (draft)
Reads a packet capture, parses the handshakes and scores what an adversary recording today could decrypt later. "Endpoint uses RSA, therefore HIGH" is a crude answer — risk is the vulnerability multiplied by how sensitive the data is, how long you are legally required to keep it, and how exposed the path is.
Rebuilds the trust chain from root through intermediates to leaf certificates and ranks the migration impact of each node. Migrating a mid-tier CA while the leaves below it stay classical is the failure nobody plans for, because nobody drew the tree first.
Classical against hybrid against pure post-quantum, measured on the machines you actually run, so the latency and key-size trade-off is a number in your environment rather than a claim in a vendor deck.
expected: no public CA can issue one yet
On 1 September 2026 we ran a single TLS handshake against 40 public web front doors and read both sides of it. 31 of the 40 negotiated hybrid post-quantum key exchange. None of the 40 presented a post-quantum signature at any position in the chain, which is expected, since no public CA can issue one yet.
Twelve of those hosts were chosen to be as unfavourable to a "they are simply behind" reading as we could make them — organisations whose public identity is built on getting cryptography right, including three projects that maintain the libraries implementers use to run this very measurement. Eight of the twelve had already moved their key exchange. All twelve were still at zero on signatures.
Key exchange you can switch on by yourself. A signature has to be issued to you. At the time of measurement no publicly trusted CA issued certificates carrying post-quantum signatures, so no subscriber could obtain one however much they wanted to. This is why "our TLS already negotiates X25519MLKEM768" reads correct and still leaves half the question open.
n = 40 hosts across 37 organisations, one point in time, one vantage point. Where the client did not report a group we counted it as not observed, never as declining post-quantum key exchange — the first figure is "31 confirmed", not "9 refused". The method and the host groups are in the position paper.
You run the readiness engagement. VPQ Audit produces the on-wire inventory inside it, on your client's infrastructure, and the relationship stays yours.
Post-quantum readiness is being written into mandates faster than the tooling layer can staff for it. Advisory firms are winning the engagements and then discovering that the inventory step needs instrumentation nobody on the team owns. That step is what we do, as a subcontracted measurement, delivered under your report.
Open, because you have to be able to check it: what we measure — the standards covered, the scoring formula, the output fields, the protocols parsed. Closed, because it is the only thing we cannot hire twice: how the analysis engine is built.
atkvn.com, vct.atkvn.com and vpqaudit.atkvn.com all negotiate the hybrid X25519MLKEM768 key exchange. Their certificates are ECDSA, rated HIGH as a planning item: no public CA issues post-quantum web certificates yet, so there is nothing to change until they do.
Sample report (PDF, 11 pages) · CBOM (CycloneDX 1.7)
Every customer report carries an "internal" banner by default; this one is published as it came out.
Enter up to 5 hostnames you own or are authorised to assess. We read each one’s TLS handshake on port 443 — key exchange, protocol versions, certificate chain — and grade it A–F against what harvest-now-decrypt-later can attack today. Nothing to install, and it doesn’t touch anything beyond the handshake a browser already receives.
We scan up to 10 of your public hostnames from outside: key exchange, certificate chain and protocol versions, rated and explained, with a CycloneDX CBOM. Nothing to install. Hostnames you own or are authorised to test only.
A 30-day VPQ Audit licence you install on your own network, plus one review of the resulting report by an ATK analyst. You keep the report, the CBOM and the HNDL scoring. If you move to Team or Business within 60 days, the full Audit fee is credited.
Founding customers: the first three Audits are USD 2,900 with code FOUNDING3 at
checkout, in exchange for an anonymised quote we can publish. Ends when three are sold or on 30 November 2026.
Self-hosted VPQ Audit for one organisation: up to 5 users and 250 hosts, updates included.
Offline installation bundle for networks with no internet access, larger host counts, invoiced.
The full product with a watermark on every report.
Trial without a licence: 1 user, read-only.
Prices include applicable taxes. Card checkout is handled by Paddle.com, our merchant of record; your licence and download link arrive by email within one business day of payment. Prefer an invoice (bank transfer) or PayPal? Write to support@atkvn.com with the plan you want; software licence terms are here.
VPQ Audit installs with Docker Compose, or from an offline bundle on networks with no internet access. Captures, configurations and reports are stored on your side.
The licence is a signed file checked on your server, with no call to us. It caps users and hosts and stops working when it expires; moving the system clock back does not extend it.
The delivered images contain compiled code, not source.
This one runs on our side, from outside, against public hostnames you give us. It reads only what any browser receives in a TLS handshake.
VPQ Audit is defensive and compliance-oriented — the same category as an SBOM scanner. It reads configuration and traffic you already own. It does not break, harvest or exploit anything.
Network, transport, certificates, PKI and source are covered. Endpoint binaries, mainframe, infrastructure-as-code and cloud KMS are not — we would rather name the gap than let you find it halfway through an engagement.
We hold no national certification and we do not claim one. Community edition v0.4.0 is public under MIT; Enterprise is in pilot and pre-production.
The output is built to sit inside work governed by NIST and CNSA 2.0. Interpreting those for your institution remains your counsel's job.
Send a representative capture or point us at one segment. You get the inventory, the HNDL scoring and the CBOM back as a report you can put in front of a client or a regulator — under your name if that is the arrangement.