NCSC's PQC migration workshop report stresses that no organisation can handle the shift alone. Review their takeaways if you rely on public-key crypto for long-term data, whether running enterprise estates or smaller teams working through vendors.Cyber Resilience desk
Sources (1)
- ncsc_uk · ncsc_uk
What this means for you — CISO:Use the NCSC workshop takeaways to start a crypto inventory and a multi-year PQC migration plan—prioritize long-lived data, TLS termination points, and vendor dependencies that cannot wait for a drop-in algorithm swap.
What this means for you — Lean IT orgs:You do not need to run a PQC project yourself: ask your cloud, email, VPN, and backup vendors for their post-quantum roadmaps and timelines, and prefer products that already publish one.
What this means for you — MSP:Track PQC readiness across the client stack (identity, VPN, email, backup, line-of-business SaaS); add a standard vendor question on migration plans and flag clients with long data-retention or on-prem PKI that will need earlier help.
What this means for you — Researcher:Read the NCSC workshop report for migration sequencing, inventory scope, and inter-org coordination gaps—the practical blockers, not the algorithm choices, are the useful signal.