What should we ask vendors about post-quantum readiness?

Ask questions that have verifiable answers. Which post-quantum or hybrid algorithms does the product support today, by name, such as X25519MLKEM768 for TLSTLS: Transport Layer Security. The encryption that protects most internet traffic, such as HTTPS. or ML-DSA for signatures, and from which version? If none yet, in which release and by when? Can the algorithms be changed by configuration or update, without replacing hardware? Which cryptographic library does the product use, and who maintains it? Does the hardware, such as a firewall, a hardware security module or a controller, have the capacity for larger keys, or will it need replacing? How will the vendor sign its own updates once signature algorithms change? Will the product keep working with clients that only support classical algorithms during the transition? Ask for the answers in writing, with dates. Be careful with answers that promise immunity to quantum attacks or that only talk about symmetric encryption: they avoid the real question. A vendor that cannot answer is a dependency to plan around, and its answer belongs in your inventory.

← All 33 questions on Post-quantum cryptographyAll topics