Platform overview PQC Shield
PQC / CBOM scanning · PQC Gate
Find the cryptography a quantum computer will break, and plan its replacement.
PQC Shield scans your code for quantum-vulnerable cryptography, builds a CycloneDX CBOM, tracks remediation and gives migration designs to ML-KEM and ML-DSA.
What it does
Data and signatures recorded today can be attacked once a large enough quantum computer exists, so anything that must stay secret or authentic for years is already exposed. The first step of any migration is knowing where the vulnerable cryptography is.
PQC Shield gives you that inventory: a cryptography bill of materials (CBOM) in the CycloneDX format, built by scanning your repositories. Each finding is tracked to remediation, with a migration design to ML-KEM and ML-DSA, and reports you can export.
ApexAI uses the same algorithms itself: licences are signed with ML-DSA-87, key exchange uses ML-KEM-1024 and SOC decision policies are signed with ML-DSA-65.
Key capabilities
CBOM scanning
A CycloneDX cryptography bill of materials for your repositories.
Risk per finding
Findings classified by their exposure to harvest-now, decrypt-later.
Remediation tracking
Each finding tracked until it is fixed.
Migration designs
Designs for moving to ML-KEM and ML-DSA.
Exportable reports
Reports to share with engineering, risk and auditors.
Feeds governance
Govern checks that the latest scan shows no broken cryptography and that the inventory is fresh.
How it works
01
Assess
Scan repositories and build the CBOM.
02
Remediate
Track each finding to a fix.
03
Design
Get a migration design to ML-KEM / ML-DSA.
04
Report
Export the result.
The human approval gate
PQC Shield changes nothing by itself: a migration becomes work for your team, not an automatic configuration change.
Licence
- Included in
- PQC Shield module licence, Platform, Sovereign
- Licence feature
- module.pqc_gate
PQC Shield can be licensed on its own. Every licence includes the Core.
See pricing and licencesWhere it stands today
The CBOM scanner matches patterns in source code rather than parsing it fully, so treat its inventory as a strong starting point, not a proof of absence.
Start your post-quantum inventory.
We scan a repository of your choice with you and walk through the CBOM and the migration design.