Skip to main content
Commerce Security logo, "All 12 PCI DSS Requirements in Plain English," "Get it now for free," "Complete Survival Guide" and a button toclick to get it
Post-Quantum Guidance Is Final. Is Your Program Ready?Cryptography & Encryption
4 min readFor Program Managers

Post-Quantum Guidance Is Final. Is Your Program Ready?

NIST has finalized its post-quantum cryptography guidance, and a new GAO report indicates federal agencies are behind on building defenses. The source article says emerging technology will soon break the encryption protecting sensitive data. No timeline accompanies that warning, so treat the pace as an open planning variable.

The questions below are ones we hear from program managers when this topic hits a team channel. None of the answers depend on a deadline, because you shouldn't wait for one before assigning an owner.

Q1: NIST finalized the guidance. Doesn't that mean we just follow it?

Reading the guidance is step zero. It tells you the destination; it doesn't tell you which of your systems use vulnerable cryptography, who owns them, or what a vendor can deliver. The GAO finding that agencies are behind does not establish why.

Treat this as a program, not a document review. A program has a named accountable owner, a scope, a funded backlog, and a reporting cadence. If none of those exist yet for cryptographic transition, that's your first deliverable.

Q2: What do I do first on Monday morning?

Name an accountable owner and write a one-page charter. Keep it short:

  • Scope: which enclaves, system boundaries, and data types are in play (CUI Basic, export-controlled data, classified under the National Industrial Security Program, or other).
  • Decision rights: who can approve a cryptographic change, accept risk, or defer work.
  • Reporting line: who gets status and escalations.

Then fold the work into governance you already run. If your systems operate under the Risk Management Framework, the Program Management (PM) Controls in NIST SP 800-53 Rev 5 give you a natural home for enterprise-level planning and risk strategy, and SA and SR family controls cover acquisition and supply chain. Don't build a parallel bureaucracy.

Q3: How do we find where we're actually using crypto?

You probably can't answer this from memory, and that's the point. Build a cryptographic inventory the same way you'd build a hardware or software asset list, then enrich it. Capture, per system:

  • Where cryptography is used: data at rest, data in transit, authentication, signing, key management.
  • Which algorithms and key sizes are in use.
  • Which components provide it: application code, libraries, hardware, cloud services, network appliances.
  • Whether it relies on X.509 certificates and your Public Key Infrastructure, since certificate chains tend to hide dependencies.

Existing artifacts help. Your system security plans, Software Bill of Materials data where you have it, and the cryptographic controls you've already documented for NIST SP 800-171 (3.13.11 requires FIPS-validated cryptography when protecting CUI confidentiality) are good starting points. Validated modules under the Cryptographic Module Validation Program are a useful lens: if a system depends on a FIPS 140-2 validated module, find out who maintains it and how it will change.

Q4: How do we deal with suppliers and cloud providers?

Start by asking, not assuming. For each critical dependency, send the same short questionnaire: Do you have a cryptographic transition plan? Who owns it? What can you tell us about timing for products and services we consume? Record the answers, including "we don't know."

Then check where your obligations flow down. Under DFARS 252.204-7012, subcontractors handling covered defense information carry requirements through Flow-Down Requirements, so your prime and sub relationships are part of the inventory, not a side topic. For cloud services, the Shared Responsibility Model and the provider's Customer Responsibility Matrix tell you who controls cryptographic choices. Where a FedRAMP authorization or DoD Cloud Computing Security Requirements Guide Impact Level applies, you can't assume your provider's roadmap matches yours. Put it in writing.

Q5: We don't have a deadline. How do we prioritize?

Use risk, not a calendar. Because the report doesn't specify when quantum computers could threaten cryptography in current use, avoid any plan that hinges on a guessed date. Rank systems with factors you can defend:

  • Data longevity: information that must stay confidential for many years deserves earlier attention than short-lived data.
  • Mission criticality: use your Criticality Analysis Process Model results, or your existing mission impact ratings, to separate systems that can't fail from systems that can.
  • Replacement difficulty: long-lived hardware, embedded systems, and vendor-locked platforms have long lead times, so surface them early.
  • Exposure: externally reachable and widely shared data paths come before isolated ones.

Sequence by combining those factors, and document the reasoning. A defensible rationale beats a precise-looking schedule built on assumptions.

Q6: How do we report readiness without a standard checklist or required controls?

Don't invent a compliance claim. No framework you're assessed against today, whether CMMC under 32 CFR Part 170 or a FedRAMP Moderate Baseline, should be described as meeting a post-quantum requirement unless the specific control language says so. Never overstate what an assessor or authorizing official has accepted.

Instead, report internal readiness indicators you control:

  • Percentage of in-scope systems with a completed cryptographic inventory entry.
  • Number of critical suppliers who've responded to your questionnaire.
  • Open decisions awaiting an owner or funding.
  • Items on the migration backlog by priority tier.

Track these in your existing risk register or plan of action and milestones, and label them as program-management measures, not control evidence. When funding conversations arrive, you'll have defensible counts instead of anecdotes.

Next Steps: Turn Guidance Into a Program

Read NIST's finalized post-quantum guidance directly and have your cryptography and architecture leads summarize implications for your environment. Pull the GAO report to understand the agency readiness findings behind the headline. Cross-check NIST SP 800-53 Rev 5 (PM, SA, SC, SR families), NIST SP 800-37 for Risk Management Framework integration, and the Cryptographic Module Validation Program listings for your current modules. Then schedule the charter conversation from Q2. Guidance is final; ownership is still up to you.

Application Security Isn’t Optional Anymore.

You Might Also Like