Migration Planning / Migration Verification & Closure

What this is for: Prove migration with the framework's 5-point evidence standard, log classical-key decommissioning (SP 800-88), and record program closure & BAU handover.

What a good answer looks like: Evidence that the old algorithm is gone, not just that the new one works. Both running is the normal state, and it is not done.

Worked example: Fill all five evidence fields for 'Public web TLS (edge)' but three for 'Internal mTLS service mesh', and leave the RSA-4096 root CA key unconfirmed: the badges read Verified and Unverified 3/5, the key row flags TNFL, the header says 1/2.

Runtime and privacy: This planning tool runs in your browser. Use synthetic or approved organizational data and review the site privacy terms before entering sensitive material.

Browse all Business tools · Browse PQC learning modules

For your role

Executive / Business Leader

Add each system and tick the five evidence points, observed negotiation, negative test, certificate chain under PQC, downgrade documented and evidence in the dossier: a system counts as migrated only when the old algorithm is gone.

GRC / Risk & Compliance

Attach an evidence reference to each of the five points per system, log the decommissioning of classical key material with its SP 800-88 method, and complete the closure and BAU handover: the export is the closure evidence.