Compliance & Cryptographic-Inventory Assistance
Build the inventory your migration plan and your auditors both need, mapped to the standards and deadlines that govern PQC adoption.
Cryptographic inventory template
Track at least these fields for every system that touches cryptography:
- •System / application name
- •Algorithm(s) in use (e.g., RSA-2048, ECDSA P-256, AES-256-GCM)
- •Key establishment method (e.g., TLS 1.2 ECDHE, static RSA)
- •Certificate authority & expiry
- •Library / SDK & version
- •Data classification & confidentiality horizon
- •Owner / team
- •PQC migration status (not started / planned / piloting / migrated)
- •Vendor dependency (yes/no) & vendor PQC timeline
Relevant frameworks & guidance
Transition to Post-Quantum Cryptography Standards -- sets the 2035 federal migration horizon and guidance for prioritizing systems.
Recommendation for key-derivation methods in key-establishment schemes -- covers the composite/hybrid techniques used to combine classical and PQC key exchange.
Security requirements for cryptographic modules -- PQC algorithms are being incorporated into CMVP validation testing (CAVP for algorithm-level testing).
Practical reference architectures, tooling, and interoperability guidance for organizations executing a migration, run by the National Cybersecurity Center of Excellence.
How ChatPQC helps
Ask the copilot to turn a spreadsheet export, an SBOM, or a list of TLS endpoints into a structured cryptographic inventory, flag entries that map to quantum-vulnerable primitives, and draft the audit narrative tying your migration plan back to NIST IR 8547 milestones.