Your PQC Migration Has a Number. You Just Don't Know It Yet.

Every cryptographic deployment has an assurance posture. A real one, grounded in the evidence of what algorithms are deployed, how they are implemented, what entropy sources feed them, and how the network exposes them. The deployment either meets a defensible assurance level or it doesn't, and by how much.

Almost no organisation running a PQC migration today can tell you what their posture is — in a structured, evidence-backed way.

They can tell you which algorithms they've selected. They can tell you which vendor they've shortlisted. They can tell you their target completion date. What they cannot tell you, in a single auditable assessment, is how much real-world cryptographic assurance they currently hold, how much they'll hold after migration, and what gap sits between them and their target. The evidence exists. It is simply not being combined.

This is not a marketing complaint. It is a structural problem with how the cybersecurity industry has talked about cryptography for forty years, and it is about to collide head-on with regulatory reality.

The compliance illusion

Cryptographic security has historically been described in binary terms. A system either uses an approved algorithm or it doesn't. It is either compliant or it isn't. "We're AES-256." "We're PQC-ready." These statements are treated as proof of security.

They are not. They are statements about which materials the bridge is made of.

If a bridge engineer told you "this bridge is made of steel," you would not consider that a safety case. You would ask: how much load can it carry? What is its safety margin? Under what conditions does it fail? You would expect a number, in a defined unit, with a margin above a defined threshold. "Made of steel" is a starting point. It is not the answer.

Yet "we use ML-KEM" is treated as the answer. The same algorithm, deployed with different entropy quality, different side-channel exposure, different network architecture, different finite-security parameters, can offer wildly different real-world protection. Compliance language hides this difference entirely. And in a quantum-vulnerable world, hiding the difference is no longer harmless.

"Made of steel" is a starting point. It is not the answer. Neither is "we use ML-KEM."

The regulatory clock has started

On 22 June 2026, President Trump signed Executive Order 14412, "Securing the Nation Against Advanced Cryptographic Attacks." The order sets a 31 December 2030 deadline for federal agencies to transition their most sensitive systems to post-quantum encryption, and a 31 December 2031 deadline for post-quantum authentication. It also directs the Department of Commerce to initiate a pilot project for PQC migration, to be completed by 31 December 2027, and directs every agency to designate a PQC migration lead. Through federal contractor obligations, the requirements extend to anyone selling into the federal supply chain.

This is not a US-only signal. France's national cybersecurity agency, ANSSI, has announced it will stop certifying products that lack quantum-safe encryption starting in 2027. The EU's DORA regulation already imposes cryptographic resilience obligations on financial entities. NIS2 extends similar duties to essential entities across critical sectors.

The regulatory direction is unanimous: migrate, and prove you have migrated. The proof is the part the industry has not solved.

The physics approach

Physics treats safety differently from compliance. In any engineering discipline derived from physics — civil, aerospace, nuclear, pharmaceutical — safety is expressed as a margin. The bridge holds three times the expected load. The pressure vessel withstands four times the operating pressure. The aircraft can lose two of three redundant systems and still fly. The unit is the same regardless of the system being assessed, and the discipline of "discount toward the worst plausible outcome" is built in.

This is the discipline cryptographic security has been missing.

The Unified Security Margin Calculator (USMC), built on the Patent Pending QRESB framework, applies that physics discipline to quantum-resilient cryptography. It assesses a deployment across six independent evidence dimensions — entropy quality, post-quantum cryptography, protocol and reconciliation leakage, side-channel resistance, architecture and network exposure, and finite-security effects — and produces a structured assessment with an overall assurance verdict, a QRESB Assurance Index, evidence confidence, and assessment coverage.

The QRESB Assurance Index is a composite decision-support metric. It is not a direct measurement of brute-force security strength in bits unless the report explicitly identifies the output as an estimated bit-security margin and states the calculation method. The assessment is designed to survive scrutiny, not to flatter the customer.

What the report delivers

A single auditable assessment containing:

The output is not a marketing number. It is a defensible position. And critically, it is something a CISO can take into a board meeting.

Why PQC professionals should care

The hardest conversation in cybersecurity right now is not technical. It is financial. CISOs and crypto architects are being asked to justify eight and nine-figure migration budgets to finance committees and audit committees who have no way to evaluate the technical claims being made to them.

"We need £40 million to migrate to PQC" is not a fundable proposition. "Our current QRESB Assurance Index is 42; this migration plan moves us to 78, with the gap closed across these specific dimensions" is.

USMC turns a technical posture into a board-grade business case. It also turns a future-state target into something measurable: not "we will be PQC-ready," but "we will reach a QRESB Assurance Index of 78 by Q4 2027." That is a commitment a board can hold a CISO to. It is a commitment an underwriter can underwrite. It is a commitment an auditor can verify.

It is also, increasingly, what the regulator is going to demand. EO 14412 names migration leads and contractor obligations; it does not yet name a measurement standard. The migration leads being designated across every federal agency this year will need one. So will the contractors selling into them. So will every regulated entity in the EU when DORA and NIS2 enforcement matures.

The shift the industry now has to make

For forty years, cryptographic security has been allowed to describe itself with labels. AES-256. RSA-2048. FIPS-compliant. PQC-ready. Those labels worked when the threat model was static and the algorithms were trusted. They do not work in a world where the threat is a quantum computer measured in qubits, where migrations cost tens of millions, where regulators demand evidence, and where boards demand outcomes.

Quantum cryptography is too serious to enter with the phrase "we are protected."

It must be entered with the phrase "we know how protected we are, based on evidence, with a defined assurance verdict and a defined index."

That is the physics standard. It is the standard every other safety-critical engineering discipline has used for a century. It is the standard PQC migration now needs.

Every PQC migration has an assurance posture. The organisations that know theirs will be the ones still standing when the regulator, the underwriter, and the board come asking.

Physivitis Ltd · physivitis.tech · Making security measurable.