Name a migration owner and adopt a cryptography policy
No owner for cryptographic change
Other industries
Healthcare, public administration, manufacturing, logistics, technology: the cryptography is the same everywhere. What changes is how long your data must stay secret, which systems are hardest to change and who asks you for proof. We weigh all three for your organisation.
Patient records, citizen data, designs and contracts copied today can be read once a quantum computer exists. What has to stay secret longest is exposed first.
Earlier cryptographic transitions took organisations a decade. Systems that are hard to change - devices, embedded controllers, legacy applications - set your real timeline.
Much of your cryptography arrives inside products and services you buy. Their roadmaps belong in yours, and your tenders should ask for them.
NIS2 asks for a cryptography policy across many sectors, national agencies have published dates, and the EU roadmap sets 2030 for high-risk use cases.
Each card is a system we inventory. Its coloured edge shows how exposed its cryptography is.
Every action in the roadmap says what to change, why - the finding behind it - who owns it, how long it takes and in which quarter. Opened up, it adds the steps, what it waits on, how done is proven and which rule it serves.
Name a migration owner and adopt a cryptography policy
No owner for cryptographic change
Complete the CBOM across the estate
27% of hosts not yet scanned
Rank systems by how long their data must stay secret
Personal data kept 10+ years
Hybrid TLS on public websites and APIs
F-002 · classical key exchange on 22 endpoints
Retire TLS 1.0 and SHA-1 certificates
F-010 · 17 legacy endpoints
Get PQC dates from top suppliers and cloud providers
14 suppliers without a published plan
Move remote-access VPN to hybrid IKEv2
F-004 · DH group 14 on the staff VPN
Upgrade to OpenSSL 3.5 and OpenSSH 10 across the fleet
F-013 · 46 hosts on libraries without ML-KEM
Pilot ML-DSA certificates from the internal CA
Issuing CA signs with RSA-2048
AES-256 and re-wrapped keys for backups
F-020 · 128-bit keys on long-term backups
Re-scan and update the CBOM
Confirm the Q2–Q3 changes
Board report and evidence pack
Annual risk review
Hybrid TLS on public websites and APIs
F-002 · 22 internet-facing endpoints offer classical key exchange only. The traffic includes personal data kept for 10+ years (HNDL).