software compatibility evaluations for post-quantum algorithms,
infrastructure readiness assessments,
staff training records,
allocated resources/budget.
For protocols with published cryptographic transition roadmaps,
verify operator's readiness aligns with those timelines, per Document Protocol
Responsibilities
Key Evidence
Operational readiness assessment for cryptographic migration
Key management system capability inventory; vendor/supplier
readiness evaluations
At least one concrete readiness measure in place (testing, training,
or infrastructure preparation)
Operator can provide realistic timeline estimate for executing a
migration
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No readiness assessment has been conducted
Operator has not evaluated post-quantum capabilities of key
management infrastructure
No concrete readiness measures exist (readiness entirely
theoretical)
Operator's readiness timeline significantly exceeds known protocol
governance timelines
Justifiable Exceptions
Any failure to meet this requirement needs to be explicitly
justified
Common Failure Patterns
Operators consider cryptographic migration a distant future concern
with no preparatory action;
readiness is assessed theoretically but not validated against actual
infrastructure (e.g., HSM post-quantum support is assumed but not
verified with vendor);
key management systems locked to specific algorithms with no
migration path;
staff have not received training on post-quantum concepts;
dependencies on third-party services create unaccounted
bottlenecks.