Independent PQC Assurance: Why Evidence Must Replace Assumption in Post-Quantum Migration

NIST published FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) in August 2024. NIST IR 8547, finalised on 27 October 2026, sets deprecation of RSA, ECDSA, EdDSA and Diffie-Hellman after 2030 and disallowance after 2035. Executive Order 14412, signed on 22 June 2026, and OMB Memorandum M-26-15 direct federal agencies to prioritise migration of high-value assets and high-impact systems.

The algorithms exist. The deadlines are published. The question that remains unanswered is whether the implementations deploying these algorithms actually work as claimed, and whether anyone independent has examined them.

The Migration Gap is Structural, Not Technical

Transitioning from quantum-vulnerable to quantum-safe cryptography is not a software update. It is an architectural transformation touching key management, certificate lifecycle, protocol negotiation, firmware signing, entropy generation and supply chain dependencies.

An organisation may select ML-KEM for key encapsulation and ML-DSA for digital signatures, satisfying emerging requirements on paper. Whether those algorithms are correctly integrated into the protocol stack, whether entropy sources meet independence requirements, whether key lifecycle governance supports rotation without disruption: these are questions algorithm selection leaves unanswered.

Procurement teams receive vendor attestations. Boards receive assurance statements. Regulators receive compliance declarations. The evidence supporting those claims is rarely examined by a party independent of the entity making them.

Self-Assessment Is Not Independent PQC Assurance

Self-assessed PQC compliance conflates the roles of implementer and evaluator. The entity with the strongest commercial interest in a positive outcome is the entity producing the evidence.

The harvest-now-decrypt-later threat model sharpens the urgency. Data captured today under vulnerable protocols will become readable when capable quantum computers arrive. The exposure is occurring now; decryption follows later. The window between the two is the window in which independent PQC assurance can identify and close the gap.

Independent assurance separates validation from implementation. It subjects claims to forensic examination: verifying protocol behaviour against specification, identifying wrapper implementations where a PQC header conceals a classical algorithm, characterising entropy sources, and confirming that governance artefacts support the controls.

What Independent PQC Assurance Examines

A structured validation covers four domains.

Protocol and Implementation Correctness

Validation begins with whether deployed protocols genuinely implement the post-quantum algorithms they claim to use. Wrapper implementations, where a PQC configuration label conceals classical key exchange, are a documented risk. Forensic validation tests actual protocol behaviour, not the configuration dashboard.

Crypto-Agility and Entropy Assurance

Algorithm agility is a regulatory expectation. If a deployed algorithm is compromised or deprecated, the architecture must support replacement without a full rebuild. Crypto-agility assessment evaluates whether the organisation can execute algorithm replacement without operational disruption. Entropy assurance evaluates whether random number generation meets the quality thresholds that post-quantum security demands.

Vendor and Product Claim Validation

Procurement teams selecting PQC-enabled products need an objective basis for their decisions. Independent product validation subjects vendor claims to black-box testing, separating marketing narrative from operational reality.

Third-Party and Supply Chain Risk

An organisation's PQC implementation is only as secure as the weakest cryptographic dependency in its supply chain. Third-party libraries, embedded firmware, cloud key management and certificate authority practices introduce quantum-vulnerable surface area that internal assessment will not examine.

Technical validation without governance validation is incomplete. A cryptographic control that exists in code but has no ownership in the operating model, no audit trail and no documented lifecycle governance cannot be evidenced to a regulator.

This examination covers documentation quality, SDLC integration, configuration management and audit trail integrity. The output is a validation verdict classified as Validated, Conditional or Not Validated, issued under the Quantum Cryptographic Assurance Standard (QCAS), which codifies what constitutes sufficient evidence across both technical and governance dimensions.