QuantumShield
Q v0.2 · CLI + browser · rules-engine 2026-Q2

Post-quantum readiness for your Salesforce org. Run it locally first.

QuantumShield ships as a local qshield CLI for admins who already use the Salesforce CLI, plus a static browser app for in-tab scans and demos. Both paths scan your org's cryptographic configuration against BSI TR-02102, ENISA, NCSC-NL and the NIST PQC standards — and produce PDF, CBOM, OpenVEX, CSV, and raw JSON artifacts.

macOS · Windows · Linux CLI · Browser mode uses your own OAuth app · Source on GitHub
Recommended path
Local qshield CLI
Browser auth
Your External Client App
Cloud proxy
None
Write access
None, ever
sample report · QS-0424 · nl-acme.my.salesforce.com
Sample executive summary
47 findings across 9 categories
4
Critical
9
High
18
Medium
16
Advisory
Earliest deadline
2023-12-31 · SHA-1 disallowed · 3 findings already past due
Certificates14
Connected Apps22
Named Credentials31
Apex classes612
01
Direct-to-source rules
Every finding cites a primary document — BSI TR-02102, ENISA PQC, NCSC-NL factsheet, NIST FIPS 203/204/205 — not a third-party maturity framework. Quarterly revision tracked in the rules engine.
02
CLI first, static browser second
Use the local CLI for repeatable operational scans. The website remains a static browser UI for demos, in-tab review, and teams that prefer to own the OAuth app themselves.
03
Owned auth surface
The CLI reuses the sf session already on your machine. Browser mode uses an External Client App or Connected App you create in your own org. No shared QuantumShield Connected App.