Tessera PQC
PX-04
How an engagement runs
Four weeks to the first answer a regulator will ask for.
Where is our vulnerable cryptography, and who owns it? A pilot answers that on your own estate. A first full engagement takes about eight weeks to a complete, prioritised plan; after that the platform keeps the inventory current and the evidence ready.
01
03
The pilot
01
Week 1
Install on one host in your network. Agree authorisation and scope with your CISO office.
02
Weeks 2–3
Scan an agreed set of applications, one vendor delivery and the internet-facing TLS estate.
03
Week 4
Readiness report, CBOM, DST and RBI mapping, a prioritised migration plan, and a review with your team.
02
03
What we need from you
A sponsor | In the CISO office |
A host | 8 cores, 16 GB RAM, Linux or Docker |
Read access | To the agreed repositories and artefacts |
Scope | The list of endpoints you authorise us to probe |
← Swipe for the rest of the table →
← Drag for the rest of the table →
Delivered as a licensed product installed on your own host, with Par2 Labs running the first engagement alongside your team. Contact enterprise@par2labs.com.
03
03
What buyers ask first.
Why start now, when no quantum computer can break RSA yet?
Because data recorded today can be decrypted later — harvest now, decrypt later — and because migration takes years. Large institutions have found that the inventory alone takes 12 to 24 months, and it is exactly the first milestone the DST roadmap sets for December 2027.
Does any of our data leave the bank?
No. Tessera PQC is installed on your own server, can run air-gapped, sends no telemetry and makes no cloud AI calls. Par2 Labs has no access unless you grant it.
Most of our cryptography is inside vendor products. Can you see it?
Yes. It reads compiled applications and container images without source, imports and verifies signed vendor CBOMs, and names the vendor as the owner of what it finds.
Will it touch production systems?
Only hosts you name, and only after a second person approves. Endpoint checks send a single hello — no login, no data read — and everything is recorded in the audit trail.
Does it fix the cryptography too?
It plans, tracks and verifies the fix. Safe automatic fixes cover weak key sizes, and the platform helps your engineers adopt hybrid ML-KEM and ML-DSA; the change itself goes through your own process.