Organisations are urged to begin preparing for the move to post-quantum cryptography straight away, because a full transition is likely to take more than five years and the arrival of a machine able to break today's public-key methods cannot be dated. For each asset the timing follows from three quantities: how long it must stay protected (X), how long its migration will take (Y) and how long remains before public-key methods can be broken (Z); the migration is in time when X plus Y stays below Z, and the closer the sum comes to Z the more urgent it is. Where an asset's risk impact is at the top level because intercepted data would still be sensitive later, migration should start as soon as possible. The organisation places each asset in one of three scenarios by the availability milestone it can wait for (standards published, production-quality libraries, certified libraries), knowing that moving before certified libraries exist brings certification and code-quality drawbacks, and eventually moves every system to production-quality or certified implementations of the standards. As a general order, outdated protocols are first brought to versions the Dutch NCSC currently recommends, which also exercises asset management and agility, before the PQC move itself.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.