Post-quantum planning
Map dependencies, ownership and supplier readiness before treating migration as a product switch.

Where is cryptography used, who owns it and what would changing it affect?
Post-quantum migration planning is a systems and dependency problem. Begin with an inventory of cryptographic uses, interfaces, data protection needs and the parties responsible for them.
Ask suppliers for evidence of their plans and the controls required to adopt a change. Treat an advertised algorithm name separately from the readiness of the application, protocol, certificate handling and operating process around it.
Prioritise investigation using the organisation's requirements and exposure. Keep unknown dependencies visible and define how the inventory will be maintained. The output is a plan for decisions and validation, not a generic score declaring a system quantum-safe.
What to take forward
- Cryptographic dependency and ownership inventory
- Supplier evidence and integration constraints
- A maintained review and migration plan
What should I bring to a conversation?
Bring the decision you need to make, the constraints you already know and a small, non-confidential example. We can then agree whether a resource, a focused review or a more detailed discussion is the right next step.
