SOLUTIONS / POST-QUANTUM READINESS
Start with your business questions. Build a path to PQC readiness. Discover assets, understand dependencies and align teams. Support phased decisions with traceable evidence.
Asset visibility Migration priorities Governance
01 / DISCOVER
Understand where cryptography is used. The challenge Network and software information is fragmented. A single list rarely explains how cryptography is used.
Our approach Combine multi-protocol network observations with software CBOM to establish inventories and source evidence.
What this supports
A view across network and software assets Algorithm, certificate and protocol findings Traceable sources and open questions Explore discovery ↗ An organisation preparing for PQC migration often faces a first question: where is vulnerable cryptography actually used?
Define the enterprise boundary. Confirm the available evidence. Consider network services, certificates, code, SBOMs, HSM key interfaces, containers, firmware and cloud environments. This is a scoping checklist: collection methods, tool support and evidence gaps need confirmation for each environment.
02 / PRIORITISE
Put technical risk in business context. The challenge Knowing an algorithm name is not enough. Which services and systems depend on it?
Our approach Trace dependencies through cryptographic topology and combine them with business importance and confirmed deployment context.
What this supports
Host, service and software dependencies Impact areas requiring priority review Evidence to support phased planning Explore topology ↗ HNDL / HARVEST NOW, DECRYPT LATER
HNDL: confidentiality may outlast its protection. Harvest Now, Decrypt Later means retaining encrypted data today to attempt decryption in the future.
2026 Confidentiality begins 2035 Assumed quantum-threat planning year 2046 20-year confidentiality period ends 2035–2046: under this assumption, the data remains sensitive while its existing protection may be threatened.
2035 is an illustrative planning assumption, not a prediction or guarantee of quantum decryption capability.
Assess algorithm use, asset importance and migration deadlines, then include confidentiality lifetimes to evaluate HNDL exposure. Define scoring rules and weights for the organisation’s context.
NIST: understand HNDL ↗ 03 / COMMUNICATE
Give teams a shared language. The challenge Technical findings need to be understood by leadership and teams across countries.
Our approach Put evidence in the context of applicable official guidance and communicate findings, risk and gaps through multilingual reports.
What this supports
MODA × FSC, NIST and regional guidance Traditional Chinese, English and Japanese reports Clear separation of observation, reference and confirmation Explore standards and reports ↗ 01 Discover→ 02 Understand→ 03 PrioritisePQCAT ↗ Solutions support discovery and assessment. Scope depends on available data, environment and supported product capabilities. Guidance mapping is not compliance certification.
