Citizen records outlive the systems that hold them.
Inventory the cryptography across agencies, counties and campuses without new hardware, meet CJIS, IRS 1075 and HIPAA encryption requirements on legacy systems as they are, and buy it through the contracts you already hold.
Q-day is uncertain. The requirements for state and local government are not.
Nobody knows when a cryptographically relevant quantum computer will arrive (Q-day), but your cryptography requirements do not depend on that date. Four reasons to start now:
AI is already finding weaknesses in algorithms
Anthropic’s Claude Mythos preview found serious weaknesses in candidate algorithms without a quantum computer. Cryptography can fail before Q-day arrives.
Adversaries are harvesting encrypted data now
They are collecting vital, tax and criminal-justice records which stay sensitive for a lifetime, to decrypt when Q-day arrives: harvest now, decrypt later.
Regulators already require PQC migration
For a state or local agency that means FIPS-validated encryption for criminal justice information in transit under the CJIS Security Policy, the safeguards on federal tax information IRS Publication 1075 requires, and HIPAA’s protections for the health agencies.
Estimates for Q-day keep shrinking
Google has set 2029 as the target for its own migration. If yours is not finished in time, the foundation of agency, county and federal data links is at risk.
Google’s 2029 target and resource estimates: QuSecure, April 2026. NIST IR 8547, initial public draft, November 2024. Anthropic, Claude Mythos preview, 2026.
Why use QuProtect?
Cryptography belongs in a layer you control and configure, not in application code.
No rewrite, no rip-and-replace
QuProtect moves critical and legacy systems to PQC in a fraction of the time and cost.
Discovery and remediation in one platform
Many PQC solutions stop at discovery and leave the fix to you.
Built for large, complex organizations with highly sensitive traffic
Developed with the U.S. Army and U.S. Air Force.
Nothing is re-coded
An agency cannot take public services down to re-code them, so QuProtect does not ask for it.
The next migration is a configuration change
It is made from an Orchestrator you control, not run as another program.
Proven in production
Banco Sabadell validated post-quantum TLS in four months.
Use case in action
Your network, from the cryptography it runs today to the policy change that keeps it current. Move through the five steps, or click a number on the drawing.
-
Counties and campuses
- County offices cannot be upgraded
- Public safety and 911
- Campus systems cannot be upgraded
-
State shared services
- DMV, tax and vital records cannot be upgraded
- Health agency systems
- Courts and CJIS-connected systems
-
Federal data links (not yours to change)
- FBI CJIS
- IRS (FTI)
- CMS and HHS
Legacy cryptography, and what Q-day does to it
County offices and campus systems reach the state’s shared services on TLS 1.0, and those services reach FBI CJIS, the IRS and CMS on TLS 1.2 with RSA key exchange. Traffic recorded today can be stored until a quantum computer running Shor’s algorithm recovers those keys, and vital, tax and criminal-justice records stay sensitive for a lifetime.
Sensors find the legacy negotiations and rank the violations
Reconnaissance sensors read what is on the wire and record the cipher suites, protocols, certificates and keys in use, without touching a system or adding hardware. Each policy violation is ranked by severity: the county and campus hops first, RSA key exchange on the federal data links next.
Encryptors remediate at the network layer
A gateway at each county and campus site and sidecars beside the shared DMV, tax, health and court systems carry each hop over TLS 1.3 with NIST post-quantum key exchange, X25519MLKEM768, in a FIPS 140-3 mode. No application rewrite, and no vendor reopening a decades-old system.
Data in transit is secured, and the CBOM proves it
Citizen records recorded in transit from now on are not readable by a future quantum computer. The CBOM lists each connection’s protocol, algorithm and certificate with no open violations, with owner and criticality, as the evidence each federal program audits.
Crypto-agility: the next algorithm is a policy change
When a standard moves, the Orchestrator pushes the new policy to each encryptor and the connections renegotiate, here from ML-KEM-768 to ML-KEM-1024, while services keep running. It is a policy change, not a new appropriation.
Other use cases
Inventory across agencies, counties and campuses
A CBOM of what state and local systems negotiate, without new hardware.
Federal tax information (IRS 1075)
FTI links protected in transit on legacy systems as they are.
Legacy county systems protected in place
Vital records, DMV, tax and court systems sit behind gateway encryptors rather than being replaced.
Evidence per federal program
Logged handshakes and a CBOM with owner and criticality for each audit.
CJIS links on FIPS-validated cryptography
Criminal justice information carried over post-quantum TLS in a FIPS 140-3 mode.
Health agency ePHI
HIPAA encryption in transit for county and state health systems.
Certificate lifecycle
Automated provisioning and rotation for small teams.
Bought through vehicles you already hold
Priced to a fiscal year and a grant cycle; the next standard is a policy change, not a new appropriation.
Bought through the vehicles you already use
QuProtect R3 is available to state and local government through NASPO ValuePoint and OMNIA Partners, and on Carahsoft's GSA Multiple Award Schedule under contract 47QSWA18D008F.
Software only. Nothing to rack, and no hardware line on the requisition.