← Back to SecureAzCloud PQC Migration Resource Hub
Downloads
XLSX Assessment Template
Workbook with inventory dropdowns, formulas, risk scoring, roadmap, vendor questions, and source map.
PDF Companion
Printable companion explaining field model, scoring logic, sample redacted entries, and evidence expectations.
CSV Import Template
Lightweight CSV for importing crypto inventory fields into GRC or asset-management systems.
What this artifact covers
| Area | Coverage | Expected Evidence |
|---|---|---|
| Crypto inventory | Asset, data, exposure, business criticality, crypto function, algorithm, certificate/key store, vendor, library, firmware dependency. | Discovery export, certificate scan, library report, architecture evidence. |
| Risk scoring | Long-lived data, exposure, criticality, quantum vulnerability, supplier readiness, and migration effort scoring. | Scoring review, P1/P2/P3 backlog, risk acceptance record. |
| Migration planning | Five-phase roadmap, target quarter, owners, supplier questions, and evidence links. | Roadmap, change records, vendor responses, pilot evidence. |
Recommended use
- Download the XLSX and complete the Crypto_Inventory sheet for priority assets.
- Review the calculated risk score and P1/P2/P3 priority.
- Use the Assessment_Checklist and Vendor_Questions sheets to collect evidence and identify blockers.
- Convert P1/P2 items into a migration roadmap and pilot plan.
- Publish only redacted output externally; keep sensitive architecture evidence internal.
Standards and source alignment
Aligned to NIST's PQC standards, NIST NCCoE cryptographic discovery/inventory workstream, and NIST crypto-agility guidance.
Core references include NIST FIPS 203, NIST FIPS 204, NIST FIPS 205, NIST NCCoE Migration to PQC, NIST CSWP 39 crypto-agility guidance, CISA quantum-readiness resources, and CISA's 2026 product-category announcement for PQC adoption.
Disclaimer
This artifact is an independent planning aid. It is not a government publication and does not imply endorsement by NIST, CISA, or any public agency. Organizations should adapt it to their own architecture, operating constraints, regulatory obligations, and vendor support status.