Cryptographic transition decision system

POST-QUANTUM ENTERPRISE READINESS 2027

Executive Intelligence & Migration Decision System

A technical enterprise reference for post-quantum migration decisions, connecting cryptographic exposure, HNDL, priority, technology evidence, supplier capability, crypto agility, execution risk and governance.

103 pages · 17 Decision Assets · 3 fillable PDF forms · 24 fields

Explore Decision Assets
POST-QUANTUM ENTERPRISE READINESS 2027 cover

Enterprise problem

Post-quantum migration is a dependency and execution problem, not an algorithm-selection exercise.

Large environments need to know where quantum-vulnerable cryptography exists, which data retains long-lived confidentiality value, which systems require action first, which product and protocol combinations have credible evidence, and which supplier, validation, interoperability or change dependencies block execution.

Where is the exposure?Cryptographic function, protocol, system, data horizon and dependency context.
What is urgent?Migration priority is separated from organisational readiness and deployment eligibility.
What is evidenced?Standards, protocol maturity, product support, trust model, validation and interoperability are kept distinct.
What can move next?Preparation, pilot, remediation, controlled hold and transition remain explicit decision states.

What the publication delivers

A 103-page decision system with 17 integrated Decision Assets.

Exposure & HNDL

System-level cryptographic exposure and long-lived confidentiality assessment without relying on a speculative Q-Day date.

Priority & readiness

Migration urgency, enterprise readiness and Decision Gap are treated as separate management questions.

Technology evidence

Function, protocol, product, trust, validation, interoperability and operational gates are evaluated independently.

Supplier & procurement

Product/function/version-level evidence structures, RFP questions, conditions, evidence holds and follow-up actions.

Migration execution

Transition patterns, execution-risk states, crypto agility and change constraints for governed migration planning.

Governance & audit

Decision rights, evidence remediation, executive action, board reporting and auditable decision logging.

103 pages17 Decision Assets3 fillable forms / 24 fields20 source notes

Decision architecture

Evidence is converted into controlled states, not a single composite score.

01

Source

Identify authoritative, official, technical or product evidence and record its status and date.

02

Evidence

Extract the proposition relevant to the enterprise decision and preserve its source context.

03

Analytical rule

Apply the documented research method without elevating guidance, marketing or assumptions into authority.

04

Controlled state

Return a defined result, unresolved state or evidence gap rather than manufacture certainty.

05

Enterprise action

Translate the state into a documented action, owner, escalation or review requirement.

06

Revalidation

Recheck time-sensitive evidence and affected decisions when material facts or source status change.

Decision Assets

17 instruments for enterprise migration decisions.

Each instrument exposes the decision it supports, required enterprise inputs, documented output, ownership and key boundaries without publishing the full paid research corpus.

Inventory & exposure

Establish a controlled enterprise readiness stage while retaining a multi-domain view instead of reducing readiness to a single unsupported impression.

What you receive
A document-based Enterprise PQC Readiness Assessment inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Establish a controlled enterprise readiness stage while retaining a multi-domain view instead of reducing readiness to a single unsupported impression.
When to use it
At baseline, after a material programme change, before executive review, and before using readiness in later prioritisation or Decision Gap work.
Information your team brings
Current programme governance, inventory coverage, architecture and dependency knowledge, supplier engagement, testing/validation readiness and other organisation-owned readiness evidence.
What your team can document
A documented overall readiness state with a domain profile, including provisional or unknown treatment where evidence is not sufficient.
Who should own the output
CISO, CIO, Enterprise Architecture and the PQC programme lead.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Create a system-level record of where quantum-vulnerable cryptography is used and classify the controlled exposure state needed for later prioritisation.

What you receive
A document-based Cryptographic Exposure Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Create a system-level record of where quantum-vulnerable cryptography is used and classify the controlled exposure state needed for later prioritisation.
When to use it
For scoped systems before priority, transition or migration-path decisions are prepared.
Information your team brings
System identity and criticality, cryptographic functions, protocols, key/certificate dependencies, data flows, lifecycle facts and the evidence available for those facts.
What your team can document
A traceable system exposure record and controlled quantum-risk state that can feed priority and transition analysis.
Who should own the output
Enterprise Architecture, Cryptography/PKI and Security Architecture.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Document harvest-now-decrypt-later exposure without pretending to predict a quantum break date.

What you receive
A document-based HNDL Exposure Assessment inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Document harvest-now-decrypt-later exposure without pretending to predict a quantum break date.
When to use it
Where confidentiality relies on quantum-vulnerable public-key mechanisms and retained sensitivity may outlast current protection.
Information your team brings
Data sensitivity and required confidentiality duration, relevant cryptographic protection, retention or interception exposure, and the quality of supporting evidence.
What your team can document
A documented HNDL exposure state with reason and action implication, including an unknown state when material facts are missing.
Who should own the output
Risk, the Data Owner and Security Architecture.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Priority & applicability

Separate migration action urgency from readiness and execution difficulty so that leadership can decide which systems need attention first.

What you receive
A document-based System Migration Priority Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Separate migration action urgency from readiness and execution difficulty so that leadership can decide which systems need attention first.
When to use it
After exposure/HNDL and applicability inputs are sufficiently established and before Decision Gap analysis.
Information your team brings
Controlled risk/exposure information, confidentiality considerations, business/system criticality, timing constraints and applicable policy or programme context.
What your team can document
A documented migration-priority state or provisional hold where evidence does not support a final priority.
Who should own the output
CISO, Enterprise Architecture and the PQC programme lead.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Show the management gap between action urgency and enterprise execution readiness without turning that relationship into a probability or quantum-risk score.

What you receive
A document-based PQC Decision Gap Matrix™ inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Show the management gap between action urgency and enterprise execution readiness without turning that relationship into a probability or quantum-risk score.
When to use it
Only when both the relevant priority and enterprise readiness states are final enough for the report's controlled comparison.
Information your team brings
The established migration priority and enterprise readiness outputs, plus evidence of whether those upstream states are final or provisional.
What your team can document
A documented Decision Gap state, or a clear not-computed status when an upstream state is non-final.
Who should own the output
Executive Sponsor, CISO and CIO.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation. The controlled classification logic is applied within the publication and should be used with current enterprise evidence and the stated research boundary.

Determine which standards, policy, regulatory, contractual or programme milestones are relevant to a system decision while keeping guidance, targets and binding obligations distinct.

What you receive
A document-based Standards & Deadline Applicability Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Determine which standards, policy, regulatory, contractual or programme milestones are relevant to a system decision while keeping guidance, targets and binding obligations distinct.
When to use it
Whenever an external or internal instrument could influence timing, architecture, procurement or validation decisions.
Information your team brings
Jurisdiction and organisational context, system/use-case facts, the exact instrument/version and its status, plus relevant contractual or policy commitments.
What your team can document
A documented applicability state or applicability hold with the source context that must be rechecked when the instrument changes.
Who should own the output
Legal/Compliance, CISO and Enterprise Architecture.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Technology & supplier evidence

Prepare a technology-path decision using separate evidence for function, algorithm/standard maturity, protocol status, product support, trust model, validation and interoperability.

What you receive
A document-based Technology Decision Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Prepare a technology-path decision using separate evidence for function, algorithm/standard maturity, protocol status, product support, trust model, validation and interoperability.
When to use it
When evaluating a concrete migration technology or deployment path after the use case and required cryptographic functions are known.
Information your team brings
Use-case requirements, protocol and product/version evidence, key-establishment versus authentication needs, trust model, validation requirements, interoperability/test evidence and operating constraints.
What your team can document
A documented technology-eligibility/evidence state that makes missing prerequisites visible before production evaluation is justified.
Who should own the output
Enterprise Architecture, Cryptography/PKI and Security Engineering.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Record supplier and product evidence at function-and-version level so claims can be compared without creating an unsupported vendor ranking.

What you receive
A document-based Vendor Capability Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Record supplier and product evidence at function-and-version level so claims can be compared without creating an unsupported vendor ranking.
When to use it
During product evidence collection, RFP review, renewal, architecture selection or material product-version change.
Information your team brings
Supplier claims, exact product/module/version, supported cryptographic functions, protocol context, trust/PKI scope, validation evidence, interoperability/test evidence and evidence dates.
What your team can document
A structured vendor/product evidence record plus a procurement or technical follow-up action; it does not output a vendor score.
Who should own the output
Procurement, Vendor Risk and Enterprise Architecture.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Collect decision-grade supplier evidence and route incomplete or conditional responses into an explicit procurement action rather than assuming support from marketing language.

What you receive
A document-based Procurement / RFP Questionnaire inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Collect decision-grade supplier evidence and route incomplete or conditional responses into an explicit procurement action rather than assuming support from marketing language.
When to use it
For RFP/RFI, product evaluation, contract renewal, material upgrade or evidence refresh.
Information your team brings
The organisation's intended use case and assurance needs together with supplier responses tied to product/version, technical function, validation, support and evidence provenance.
What your team can document
A documented evidence disposition such as accept documented evidence, request more evidence, require a pilot/commitment, hold the decision, or mark an item not applicable.
Who should own the output
Procurement and Vendor Risk, with Architecture/Security input where needed.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation. The public website describes the questionnaire's purpose but does not publish the reusable question set.

Governance & agility

Assign decision rights, escalation, override, exception and reassessment responsibility for material PQC decisions.

What you receive
A document-based PQC Governance & Decision Rights Matrix inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Assign decision rights, escalation, override, exception and reassessment responsibility for material PQC decisions.
When to use it
When establishing programme governance, assigning accountability or clarifying who may approve, challenge or revisit a decision.
Information your team brings
Enterprise roles/functions, decision types, escalation expectations, exception handling and the organisation's governance model.
What your team can document
A documented decision-right mapping with escalation, override, exception and reassessment ownership.
Who should own the output
Executive Sponsor, CISO and Programme Management.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Assess the organisation's capability to replace and govern cryptographic mechanisms across multiple operational domains.

What you receive
A document-based Crypto Agility Assessment inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Assess the organisation's capability to replace and govern cryptographic mechanisms across multiple operational domains.
When to use it
When architecture and programme leaders need to understand whether future cryptographic changes can be executed and controlled, independently of current quantum-risk urgency.
Information your team brings
Architecture modularity, cryptographic inventory and abstraction, certificate/key lifecycle, testing, deployment/change practices, supplier dependencies, governance and other organisation-owned agility evidence.
What your team can document
A documented overall crypto-agility stage with a domain profile, or an unknown state where a critical domain cannot be classified.
Who should own the output
Enterprise Architecture and Cryptography/PKI.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Translate controlled triggers and blockers into an organisation-owned 0-30 / 31-60 / 61-90 day sequencing template.

What you receive
A document-based First-90-Days Executive Action Plan inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Translate controlled triggers and blockers into an organisation-owned 0-30 / 31-60 / 61-90 day sequencing template.
When to use it
At programme initiation or when high-priority/blocking conditions require coordinated executive action.
Information your team brings
Confirmed priorities, readiness gaps, evidence-remediation needs, owners, dependencies and organisation-set target dates.
What your team can document
A documented, owner-based action sequence with dates set by the organisation rather than promised by the report.
Who should own the output
Executive Sponsor, CISO and CIO.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Present concise governance metrics and unresolved states with controlled denominators and explicit unknown counts.

What you receive
A document-based Board PQC Dashboard inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Present concise governance metrics and unresolved states with controlled denominators and explicit unknown counts.
When to use it
For periodic board or executive reporting after the underlying controlled outputs have been produced.
Information your team brings
Verified portfolio counts and states, inventory coverage, priority/gap/execution states, evidence gaps, exceptions and last-verified dates.
What your team can document
A static board-reporting metric set that can be incorporated into the organisation's own governance process.
Who should own the output
Board/Board Risk Committee and Executive Sponsor.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation. It is a document template, not a live dashboard, monitoring service or automatically refreshed application.

Transition & decision control

Document which transition-pattern families are eligible, excluded or conditional for a use case and what transition action remains appropriate.

What you receive
A document-based Transition Pattern Selector inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Document which transition-pattern families are eligible, excluded or conditional for a use case and what transition action remains appropriate.
When to use it
After technology eligibility, execution-risk and crypto-agility evidence are available.
Information your team brings
Use-case architecture, technology evidence, protocol/product constraints, execution-risk findings, agility capability and operational requirements.
What your team can document
Documented eligible/excluded pattern families, constraints and a transition action state for later architecture and programme decisions.
Who should own the output
Enterprise Architecture and Security Engineering.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Assess implementation difficulty and uncertainty separately from quantum exposure so a high-risk system is not automatically treated as easy or safe to migrate.

What you receive
A document-based Migration Execution Risk Assessment inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Assess implementation difficulty and uncertainty separately from quantum exposure so a high-risk system is not automatically treated as easy or safe to migrate.
When to use it
For candidate migration paths after relevant product, protocol, architecture and dependency constraints are understood.
Information your team brings
Architecture complexity, interoperability/testing requirements, dependencies, rollback/change constraints, supplier readiness, validation needs and programme capacity.
What your team can document
A documented migration-execution-risk state, including unknown treatment when key execution evidence is missing.
Who should own the output
Enterprise Architecture, Programme Management and Security Engineering.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Turn material evidence gaps into auditable remediation items and show whether a gap blocks a downstream decision.

What you receive
A document-based Evidence Remediation Register inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Turn material evidence gaps into auditable remediation items and show whether a gap blocks a downstream decision.
When to use it
Whenever a required input is low-confidence, unknown, missing, stale or otherwise insufficient for a material decision.
Information your team brings
The affected decision, missing/weak evidence, responsible source or owner, impact on the decision, remediation action and required review context.
What your team can document
A controlled remediation record with severity/action state and visibility of whether the gap is decision-blocking.
Who should own the output
PQC Programme Management, Risk and Internal Audit.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Preserve the auditable record of a material decision, its provenance, output, exception/override treatment and reassessment state.

What you receive
A document-based PQC Decision Log inside the report, with defined purpose, evidence expectations and a recordable output.
The decision it supports
Preserve the auditable record of a material decision, its provenance, output, exception/override treatment and reassessment state.
When to use it
For every material decision generated through the framework and whenever that decision is reviewed or changed.
Information your team brings
Decision context, upstream evidence references, responsible roles, the documented output, exceptions/overrides and the trigger/date for reassessment.
What your team can document
A decision record with completeness and reassessment status that helps later reviewers understand what was decided and why.
Who should own the output
Internal Audit, Risk and PQC Programme Management.
Boundaries and dependencies
This is a document-based decision aid, not executable software. It depends on current enterprise evidence and the report's stated research boundary; material changes in systems, products, protocols, validation status or supplier evidence can require revalidation.

Organisation-specific inputs

The system becomes operational when current enterprise evidence is applied.

Systems & crypto functions

Applications, protocols, PKI, algorithms, data flows, dependencies and current implementation context.

Data horizon & criticality

Sensitivity, retention, consequence, business criticality and HNDL-relevant confidentiality requirements.

Products & suppliers

Exact product/module/version, support evidence, protocol context, trust model, validation and interoperability.

Governance & change capacity

Decision owners, approval routes, test capacity, architecture constraints, exceptions and migration windows.

Outputs teams can use

Documented priorities, evidence states, blockers and transition actions.

Migration priority

Controlled P0–P3 / hold logic distinguishes action urgency from deployment readiness.

Decision Gap

Priority and enterprise readiness are combined only when both inputs are final, preserving uncertainty when they are not.

Technology eligibility

Preparation, pilot, conditional production evaluation, production evaluation and evidence-hold states remain distinct.

Supplier conditions

Evidence acceptance, additional evidence, contractual commitment, pilot and decision-hold outcomes can be documented.

Execution risk

Migration difficulty and uncertainty remain separate from quantum exposure so programme constraints are visible.

Audit trail

Inputs, outputs, exceptions, overrides, approvals and reassessment conditions are retained in the decision record.