Cryptographic inventory and exposure
Discover where conventional systems depend on public-key cryptography and who owns change.

The situation.
An organisation needs to understand its cryptographic dependencies before planning a post-quantum transition. Discovery spans applications, protocols, certificates, libraries, devices and suppliers, with attention to how long protected information must remain confidential.
A practical approach.
- 01
Discover dependencies
Identify where cryptography is used, the data it protects and the owners of each system.
- 02
Assess exposure
Review information lifetime, external dependencies and the practical ability to replace algorithms.
- 03
Prioritise action
Create a maintained inventory with supplier questions, evidence gaps and remediation owners.
What to validate
- Treat this as a conventional security planning activity, separate from quantum-computing experiments.
- Validate discovered dependencies with system owners and supplier evidence.
Typical outputs
- Cryptographic dependency inventory
- Data-lifetime and exposure assessment
- Prioritised discovery and supplier actions
Example measures
- Systems with verified inventory
- Dependencies with named owners
- High-priority gaps with agreed actions
Agree a baseline and acceptance criteria for the specific project.
Illustrative scenario and conceptual imagery. Scope, deliverables and acceptance evidence are agreed for each engagement; example measures are not achieved results.
