A Post-Quantum Cryptography Compliance Assessment Tool
Discovery, Risk Quantification, and Verifiable Evidence for the PQC Migration.
Abstract
Every federal agency and most regulated enterprises now carry a written obligation to inventory their cryptography and migrate it to post-quantum algorithms. Almost none of them can answer the first question that obligation implies: where, exactly, is the vulnerable cryptography? PQCAT is a cryptographic discovery and compliance assessment tool built to answer that question with evidence. It scans TLS endpoints, SSH services, software bills of materials, PKI stores, source code (626 detection patterns across 54 file extensions), service configurations, HSM and KMS interfaces, SCAP content, container images, firmware images, and AWS cloud services; classifies every finding against the quantum threat; and converts the results into a defensible 0–100 compliance score under any of eleven regulatory frameworks, from CNSA 2.0 and OMB M-23-02 to PCI DSS 4.0 and HIPAA. A family of twelve patent-pending techniques distinguishes it, anchored by two: a harvest-now-decrypt-later (HNDL) risk engine that scores findings by how long the data they protect must outlive the arrival of a cryptanalytically relevant quantum computer, and a Confidential Compliance Engine that lets an organization prove its compliance posture to an auditor or regulator without disclosing the location of a single vulnerable asset. Its verifiable evidence suite extends that engine: portable evidence files an auditor re-verifies on an air-gapped machine, selective disclosure of a single asset class under a sealed commitment, cryptographically bound before-and-after remediation proof, a backward-looking clock quantifying ciphertext an adversary has already been able to collect, and firmware-region verdicts re-derivable from the silicon itself. PQCAT ships as a single static binary with zero C dependencies. Every capability described in this paper works with no licence at all, bounded by a 25-host scan scope: a licence raises that bound and adds what only matters once an assessment is a programme rather than an evaluation. Two builds exist alongside that: an air-gapped Enclave build whose absence of network code is enforced by the compiler and checkable with one command, and a Pro build adding a REST API and a role-based dashboard. It is built by the team that performed one of the first production migrations of a blockchain from ECDSA to NIST FIPS 204 ML-DSA signatures.
Key points
- Inventory is the unmet obligation. Federal agencies and regulated enterprises must inventory their cryptography, and most cannot say where the vulnerable cryptography is.
- Prioritise by how long the data must stay secret. The HNDL exposure window is the data’s retention lifetime minus the years until a cryptanalytically relevant quantum computer arrives. The multiplier runs from 1.0 for data kept under two years to 6.0 for data kept 25 years or longer, and is reported per asset rather than folded into the score.
- A compliance score is relative to scope. Ten quantum-vulnerable assets assessed alone score 0, but score 90 alongside ninety quantum-safe assets and 99 alongside 990, with nothing remediated. The paper’s advice is to gate on the absolute count of vulnerable assets, not on a score threshold.
- Prove posture without revealing where the weak spots are. The Confidential Compliance Engine offers full, anonymized and aggregate-only reports, with a hash-based proof that binds the score to the finding set and an ML-DSA-44 signature over the result.
- Evidence should fail closed. Challenge Coins and the other evidence artifacts are re-verified offline by someone who does not trust the operator, and a single altered byte is a failure, not a warning.
What the paper covers
A foreword and ten sections across ten pages. Jump to any of them below, or read the whole thing in the PDF.
Foreword
Why the paper exists: a decade of building automated compliance assessment for federal environments, and a production migration of a blockchain from ECDSA to FIPS 204 ML-DSA signatures. It states two principles: findings without prioritisation are noise, and the most security-conscious customers cannot hand anyone a map of their weakest cryptography.
1. The Problem: Mandated Migration, Unknown Inventory
The mandates behind the work: Executive Order 14412, OMB M-26-15 and M-23-02, CISA BOD 23-02, NSA CNSA 2.0 and the NIST post-quantum standards (FIPS 203, 204 and 205), plus sector frameworks that already require documented cryptographic inventories. It defines harvest now, decrypt later and explains why general-purpose vulnerability scanners miss it.
2. What PQCAT Is
A Go program in four layers: discovery, intelligence, security and delivery. It ships as a single static binary with no CGO, enforces its air gap at compile time, can seal reports with ML-DSA-44 signatures, and runs on Linux, macOS and Windows.
3. Discovery: Eleven Scanners, One Inventory
The scanner modules (TLS, SSH, SBOM, PKI, source code, configuration, HSM, SCAP, container images, firmware and AWS cloud), what each inspects, and how every asset is classified into a red, yellow or green quantum-risk zone.
4. Risk Quantification: Scoring That Reasons About Time
The 0–100 compliance score and what it does and does not mean, the HNDL risk engine (patent pending), and the Confidential Compliance Engine (patent pending) for proving posture without disclosing where the vulnerable assets are.
5. The Evidence Suite: Verify It Yourself
Portable, offline-verifiable artifacts: the Challenge Coin, Prove-It Kiosk, selective disclosure, remediation proof, Harvest Clock, Quantum X-Ray, nine-item federal binding, committed CBOM and origin pinning. It also covers two derived metrics, the cryptographic agility index and the migration plan builder.
6. Compliance Frameworks and Evidence Formats
Eleven framework profiles (CNSA 2.0, NSM-10, FISMA, FedRAMP, NIST SP 800-131A, CMMC, PCI DSS 4.0, SOX, HIPAA, NYDFS 500 and SWIFT CSP) and the formats evidence leaves in: POA&M CSV for eMASS, XML for Archer, ServiceNow and Xacta, OSCAL, executive briefing PDFs, ATO support packages, a CISA BOD 23-02 inventory export and a CycloneDX 1.6 CBOM.
7. Enterprise Operations: The Connected Build
The Pro build’s REST API and dashboard with four persona views, role-based access and a hash-chained audit log, SIEM export, offline ML-DSA-65-signed licences with no activation server, and the design choice of having no SaaS backend and no telemetry.
8. Editions, Licensing, and Verifiability
The difference between which build you have (fixed at compile time) and what you are entitled to use (fixed by the licence). Licence tiers scale by scan scope: 25 hosts with no licence, 500 Professional, 10,000 Enterprise and unlimited Federal. It also gives a one-command check of the Enclave air-gap claim and draws the open-core boundary.
9. Roadmap
Stated as direction, not shipped capability: Azure and OCI cloud scanners, a succinct zero-knowledge argument over the compliance statement, published benchmarks at larger scale, Windows EV code signing and assisted remediation.
10. About Soqucoin Labs
The company behind PQCAT and its other post-quantum products, and its twelve U.S. provisional patent applications. The paper is explicit that these are applications rather than granted patents.
Key terms
- Harvest now, decrypt later (HNDL)
- An adversary records encrypted traffic and stolen ciphertext today and decrypts it once a cryptanalytically relevant quantum computer exists. The migration deadline for a given system is therefore the arrival date minus the confidentiality lifetime of the data it protects.
- CNSA 2.0
- The NSA’s algorithm-by-algorithm deadlines for National Security Systems, with a stated preference for exclusive post-quantum use as vendor support matures.
- Challenge Coin
- One portable file that bundles a transparent binding proof, the witness needed to reopen it and an ML-DSA-44 origin seal, so an auditor can re-derive the verdict on a disconnected machine.
- Cryptographic bill of materials (CBOM)
- A CycloneDX 1.6 inventory of the cryptography found in a scan, ranked by HNDL exposure.
- Cryptographic agility index
- A metric for how fast an estate could respond if an algorithm were broken tomorrow, published with the slowest occupied response tier and the share of assets that could not be classified.
See the claims run
The paper separates what can be checked against the open-source scanner code, what is proprietary, and what is roadmap. This revision describes PQCAT v2.12.3. Later releases may differ, and the download page lists the current one. The quickest way to check the rest is to run it.