Readiness Pack Module 05
Cryptographic Inventory / Post-Quantum Cryptography (PQC) Readiness Pack
File In. Crypto Inventory Out.
Email a redacted, unclassified listing of TLS, certificates, PKI, VPN, SSH, code-signing, HSM or KMS product versions, and application crypto libraries — or run the Encipher Evidence Pack on your box. The Encipher Readiness Pack inventories each row and returns a Cryptographic Bill Of Materials, an exposure register, a refuse list, and a cover hash. Encipher Systems does not receive live keys.
Sources We Inventory
- TLS Endpoints And Cipher Suites
- Certificate And PKI Inventories
- VPN / SSH / IKE Configurations
- Code-Signing And Firmware-Signing Stores
- HSM / KMS Product Versions (Not Key Material)
- Application Crypto Libraries
- NIST FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA
- LMS / XMSS For Firmware Signing; NSS Sets ML-KEM-1024 And ML-DSA-87
What You Send And Get
Send: A redacted, unclassified listing of protocols, libraries, certificates, HSM/KMS product versions, VPN/SSH, and code-signing. No live keys. No private key material. No unredacted CUI. If the file cannot leave the source, use the Encipher Evidence Pack.
Get: CBOM workbook, exposure register, refuse list, cover hash, and a 2030 / 2031 / 2035 sequence — packaged as a Readiness Pack.
Portable — Already FIPS 203 / 204 / 205 Or CNSA 2.0-Capable.
Rewrite — RSA / ECC That Must Move.
Blocked — Cannot Migrate From This Export.
Encipher Systems Does Not Receive Live Keys.
Default Path When The File Cannot Leave Their Box: Encipher Evidence Pack.
The Readiness Pack Will Not Host The File Beyond The Same Path Used Today.
Encipher Systems Does Not Build A Custom NSS Crypto Module.
Encipher Systems Does Not Claim Quantum Speedup On A Customer Workload.
Do Not Send CUI, Live Keys, Private Key Material, Or Unmarked Program Files. If The File Cannot Be Redacted, Use The Encipher Evidence Pack. Encipher Systems Does Not Receive An Evidence Pack.