Back to DashboardGovernance & RiskFoundationsintermediate30 min

PQC GRC

Make the post-quantum migration governable, measurable, and auditable: the KRI cascade, risk appetite, regulatory horizon, and the GRC-SOC handoff.

Why this matters: A Key Risk Indicator that never reaches the board is just a spreadsheet — cascading KRIs from operational to governance level is what turns a SOC finding into an organizational decision.

Start here: Assign each Key Risk Indicator to the board, CISO or operational level in the KRI Cascade and set its status against the framework thresholds.

For your role

Executive / Business Leader
Assign each Key Risk Indicator to the board, the CISO or the operational level: a KRI that never reaches the board is a spreadsheet, and the cascade is what turns a SOC finding into a decision.
GRC / Risk & Compliance
Cascade the KRIs across the three levels, then triage the deferral exception register into the SOC suppression list, escalating what should not be suppressed: the GRC-to-SOC handoff, made auditable.
Practice in the Simulation

Why Quantum Risk Breaks the ERM Playbook

Where the SOC detects and responds, the function measures, reports, and governs. It produces the instruments the board uses to oversee the program, the CISO uses to manage it, and internal audit uses to verify it.

Standard enterprise risk management assumes observable precursors, historical frequency, and bounded timelines. Quantum risk has none: CRQC estimates span 10 to 30+ years, there are no historical incidents to calibrate against, and the risk straddles technology, compliance, strategic, and operational categories at once. Logging it as "Low likelihood / High impact, review annually" is risk acknowledgment, not risk management.

The fix is not a separate quantum-risk framework. It is adapting the existing ERM framework so quantum risk receives the same structured treatment — risk-appetite statement, KRIs, escalation thresholds, board cadence — as every other top-tier risk.

KRIs: The Three-Level Cascade

Key Risk Indicators make governance operational. For PQC migration they cascade across three organizational levels — each serving a different audience at a different cadence. Every KRI carries a threshold that triggers a specific action; an indicator with no trigger is a chart, not a control.

Illustrative policy template — your organization sets these values, no regulation does

Board-Level KRIs
Board of Directors / Risk Committee — Quarterly

Are we on track, compliant, exposed — and what has changed?

  • Migration Completion RateVariance > 5 percentage points from plan triggers SteerCo review and board notification.
  • HNDL Residual ExposureAny quarter where this fails to decrease triggers a risk-committee escalation.
  • Regulatory Compliance BufferBuffer < 12 months: amber. Buffer < 6 months: red — board intervention.
  • Third-Party Quantum ReadinessAny Tier 1 vendor below "planning" triggers formal engagement.
  • Material Developments FlagQualitative — produced by the CTI function, packaged by GRC for the board.
CISO-Level KRIs
CISO / Steering Committee — Monthly

Is the program executing, or has it hit a blocker?

  • Inventory CompletenessBelow 80%: the migration plan is unreliable; priority shifts back to inventorying.
  • Migration VelocityVelocity < 70% of plan for two consecutive months triggers a program review.
  • Crypto-Agility AdoptionAny month below 95% triggers an architecture-governance review.
  • Regulatory Horizon TrackerCount of pending requirements with a compliance status tracked for each.
  • Vendor Readiness ScoresAny Tier 1 vendor dropping a level triggers an engagement review.
  • Budget Consumption vs. PlanUnderspend > 15% triggers a review (usually signals blocked workstreams).
Operational KRIs
Program / SOC / Engineering — Weekly / Real-time

What is happening right now that could compound?

  • Weekly Migration ThroughputInstances migrated in the past 7 days, broken down by system tier.
  • Cryptographic Drift CountAny non-zero value investigated; persistent drift indicates a systemic issue.
  • Hybrid Downgrade AlertsBroken down by confirmed attacks, misconfigs, and false positives.
  • Certificate Transition Progress% of certificates reissued with PQC signature algorithms.
  • Open Exceptions / DeferralsAny exception > 6 months without a remediation plan triggers escalation.
  • TTR-PQCTime from PQC-vulnerability disclosure to confirmed remediation.

Risk Appetite & Tolerance

A quantum risk-appetite statement translates the board's intent into decision criteria the program can act on. Without it, every trade-off between migrating a costly legacy system and deferring it must be escalated, because no instrument defines which choice aligns with the board's intent. The statement operates at two levels.

Strategic level (board language)

“The organization will complete migration of all systems protecting data with confidentiality requirements exceeding 10 years before the earliest credible CRQC estimates, and will achieve compliance with all applicable PQC regulatory deadlines with a minimum 12-month buffer.”

Operational tolerances (program language)

Illustrative policy template — your organization sets these values, no regulation does

HNDL exposure tolerance

No more than 20% of data classified as having secrecy requirements exceeding 10 years will remain protected by quantum-vulnerable algorithms by end of 2027.

Target 0% by end of 2029.

TNFL exposure tolerance

This module’s advice: All production software and firmware signing will use quantum-resistant signatures (SP 800-208 hash-based or ML-DSA).

All CA signing keys PQC-capable, with hybrid or PQC issuance available, by end of 2029.

Regulatory compliance tolerance

The organization will achieve compliance with all PQC-related regulatory requirements at least 12 months before the applicable deadline.

Zero tolerance for deadline non-compliance.

Crypto-agility tolerance

All newly deployed systems from Q3 2026 onward must implement crypto-agile architecture as a mandatory design requirement.

No exceptions without Steering Committee approval and a remediation plan.

These thresholds are illustrative — the right values depend on sector, regulatory environment, data profile, and risk culture. The requirement is that they exist, are specific enough to drive decisions, and are reviewed annually at board level.

Regulatory Intelligence: The Quarterly Horizon Report

PQC regulation is moving faster than most GRC teams appreciate. Annual review is too infrequent; quarterly is the minimum, and monthly is more appropriate in regulated sectors. The output is a quarterly Regulatory Horizon Report to the Steering Committee and risk committee, listing each development's jurisdiction, effective date, migration-plan implications, and required action.

Confirmed

Enacted; a final rule is in force.

A new confirmed requirement affecting the migration timeline triggers an immediate Steering Committee assessment, outside the quarterly cycle.

Proposed

In the legislative or regulatory process.

Triggers an impact assessment within 30 days.

Signaled

Guidance, recommendations, or speeches by senior officials indicating direction.

Triggers a monitoring entry for the next quarterly review.

The GRC-SOC Handoff

The SOC's detection use cases depend on a queryable cryptographic-posture registry — which is a GRC asset. Beyond that registry, GRC produces four outputs the SOC consumes. The relationship is symbiotic, but only if both sides make their outputs consumable by the other; designing these data flows is a Phase 0 governance decision.

Risk appetite statement

Defines escalation thresholds. A hybrid downgrade is Medium or High depending on whether the data traversing that connection has HNDL-relevant secrecy needs.

Regulatory compliance tracker

Tells the SOC which systems are highest priority. Systems approaching a compliance deadline receive more intensive monitoring.

Vendor readiness assessments

Inform monitoring of third-party connections. A vendor with no PQC timeline warrants different treatment.

Exception and deferral register

Ingested as a dynamic suppression list. Without it, drift-detection rules alarm constantly on legitimately deferred legacy systems, drowning out real regressions.

The exception register as a suppression list. The SOC must ingest the exception and deferral register as a dynamic suppression list. Without it, cryptographic-drift detection rules generate constant alerts from legacy systems that are legitimately deferred — drowning out the genuine regressions the rules exist to catch.

Third-Party Quantum Readiness

An organization can migrate its own cryptography flawlessly and still be exposed through its vendors. GRC tiers third parties by how their readiness affects the migration.

Illustrative policy template — your organization sets these values, no regulation does

Tier 1: Migration-constraining

PQC readiness directly constrains the migration timeline.

HSM vendors, certificate authorities, cloud platforms, payment processors, MSSPs.

Detailed assessment + active engagement. Illustrative policy: ask for a CBOM (e.g. CycloneDX 1.6+) and a product-security review.

Tier 2: Cryptographic dependency

Cryptographic operations, but no direct timing constraint.

SaaS handling sensitive data, API partners, analytics platforms with encryption at rest.

Standard third-party assessment.

Tier 3: No cryptographic dependency

No cryptographic touchpoint.

Vendors with no encryption, signing, or key-handling role.

No PQC assessment required.

For Tier 1 vendors, consider making a machine-readable (for example CycloneDX 1.6+) a procurement requirement — a control you choose, not an external mandate. A vendor who cannot produce one has a level of cryptographic visibility that should itself concern the organization. Maintain a documented substitution assessment for each — concentration on a single HSM vendor, CA, or crypto library is its own risk.

Audit, Assurance & Insurance

A multi-year transformation with significant budget and risk should face the same audit oversight as any comparable enterprise program. The key audit question is whether systems are actually migrated or only marked migrated — evidenced through an auditable artifact set (inventory database with timestamps, quarterly CBOM snapshots, SteerCo minutes, the board-approved risk-appetite statement, Regulatory Horizon Reports, vendor records, and the exception register).

Illustrative policy template — your organization sets these values, no regulation does

First 6 months

Governance and inventory validation.

18-24 months

Execution against plan.

Annual thereafter

Until migration is substantially complete.

Insurance. Ask your broker whether your insurer's renewal questionnaire covers cryptographic inventories, migration plans or crypto-agility, and how the policy's cyber wording and any state-backed attack exclusion would treat a quantum-enabled attack. Keep the program's documentation presentable to underwriters either way: a documented, governed, measured program is easier to explain at renewal than an intention to "migrate when standards are ready."

Crisis Communications & Crisis Governance

A quantum cryptographic event is a confidence crisis before it is a technical incident: operational damage may take days, but trust damage begins with the first headline. The SOC playbooks own the technical response; GRC owns the external one — and it cannot be drafted during the event. Maintain pre-drafted templates, name the spokesperson and approval chain in advance, and exercise the communications leg in the same tabletop exercises that test the technical playbooks.

Customer notification

What is known, what was already migrated, what changes for them.

Regulator disclosure

Mapped to each jurisdiction’s incident-reporting deadlines from the regulatory-intelligence function.

Counterparty / partner notices

For shared connections; supplies migration status of the link.

Market / investor statement

For listed entities; the evidence dossier supplies the numbers.

Expect an attestation surge after any public quantum event — counterparties and customers demand evidence of migration status. Maintain the evidence dossier so that answering is an export, not a project.

Parts of this module are adapted from the Applied Quantum PQC Migration Framework v2.1 by Marin Ivezić / Applied Quantum, “GRC Implementation” section, pp. 176–185, licensed under CC BY 4.0. Changes: the material was condensed, reorganised and adapted for this module.

Check your understanding

12 questions on PQC GRC, each with its answer and the reason.

Take the quiz

Next step

Produce the artifact: Compliance Checklist

This module belongs to the Foundations phase; Compliance Checklist produces a deliverable of that phase in the Command Center.

Production Tool Capabilities & Verification Checklist

Capabilities to require in your production tools:

  • Control-framework harmonization mapping PQC requirements across ISO/IEC 27001:2022 (A.8.24 Use of Cryptography), NIST CSF 2.0, NIST SP 800-53 Rev. 5 (`SC-12`, `SC-13`), DORA, NIS2, and SOC 2.
  • Evidence-quality grading distinguishing policy declarations from automated configuration exports and negative-control test receipts.
  • Continuous control monitoring (CCM) alerting when certificate or cipher-suite drift violates control baselines.

How to evaluate in your environment

Perform an internal control effectiveness test on `SC-13` (Cryptographic Protection) and ISO 27001 `A.8.24` by sampling 10 production endpoints and verifying live PQC/hybrid enforcement.

Production evidence to collect

Harmonized control matrix, control-testing workpaper with live endpoint receipts, and audit-finding remediation tracker.

Completing this Hub module and its browser-based sample exercises teaches the technical and governance decision criteria for your role; it does not test, validate, or certify your deployed production systems.

Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.