Know your quantum risk. Plan your post-quantum move.
QShield finds the cryptography a quantum computer will break, scores the risk across your estate, and turns it into a migration roadmap to NIST's post-quantum standards.
Read-only, agentless scanning · TLS and SSH · CycloneDX CBOM export
Readiness score
Example data62
/ 100 · 4 endpoints
- api.example-bank.myTLS 1.3 · X25519MLKEM768Ready
- portal.example-bank.myTLS 1.3 · X25519Harvest risk
- sftp.example-bank.mySSH · sntrup761x25519Ready
- legacy.example-bank.myTLS 1.0 acceptedCritical
The data you send today can be read tomorrow
Most encrypted traffic is protected by RSA or elliptic-curve key exchange. A large enough quantum computer running Shor's algorithm breaks both. Adversaries can record traffic now and decrypt it later, so long-lived secrets are already exposed.
NIST published its first post-quantum standards in August 2024: ML-KEM (FIPS 203) for key exchange, and ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) for signatures. Its draft transition guidance (NIST IR 8547) proposes deprecating today's vulnerable algorithms after 2030 and disallowing them after 2035.
Inventory
You can't migrate what you can't see. Most organisations have no list of where RSA and ECC are used.
Harvest now
Recorded TLS and SSH sessions using classical key exchange are a liability for every secret with a long shelf life.
Long lead time
Upgrading libraries, load balancers, CAs and partners takes years. 2030 is close.
Proof
Regulators and boards ask for evidence of progress, not intentions.
How QShield works
Six modules take you from an unknown estate to an evidenced migration programme.
Discover
Add domains, hosts and ports, or import a list. QShield inventories every TLS and SSH endpoint you're authorised to assess.
Assess
Passive handshakes reveal protocol, key exchange, cipher, certificate chain and whether hybrid ML-KEM is offered.
Prioritise
Each finding gets a severity, a quantum-vulnerability flag and a phase, weighted by asset criticality and data sensitivity.
Plan
A migration roadmap groups the work into Now, Next and Later, aligned with published NIST transition timelines.
Prove
Export a CycloneDX cryptographic bill of materials (CBOM) and executive reports, stored securely in Cloudflare R2.
Govern
Roles, two-factor sign-in, an append-only audit trail and instant alerts keep the programme accountable.
Why QShield
Detects real post-quantum TLS
QShield negotiates hybrid X25519MLKEM768 itself, so it can tell you which endpoints already protect traffic against “harvest now, decrypt later”, and which only claim to.
Agentless and read-only
No agents, no credentials, no exploits. A scan is a handful of standard handshakes per endpoint, and every scan is logged with the person who started it.
From findings to a funded plan
Scores, phases and a CBOM give engineering a to-do list and give leadership a timeline they can budget against.
3
NIST post-quantum standards checked against: FIPS 203, 204 and 205
0
agents or credentials needed to scan an endpoint
≤4
standard handshakes per TLS endpoint, nothing more
Built to be trusted with your estate map
A list of your endpoints and their weaknesses is sensitive. QShield treats it that way.
- Scans reach only public addresses you authorise; private and reserved ranges are blocked.
- Two-factor sign-in with an authenticator app or email code, and organisation-wide 2FA policy.
- Role-based access enforced on the server for every request.
- Append-only audit trail of every sign-in, scan, export and setting change.
- Instant alerts to owners for lockouts, new admin sign-ins and policy changes.
- Reports and CBOM files stored in Cloudflare R2 with short-lived signed links.
See your quantum risk in a 30-minute demo
Tell us a little about your environment. We'll scan a public endpoint of your choice live during the call.