Key rotation involves more than generating a replacement. Plan access to old data, older-client behavior and rejection of revoked authority together.
Evaluation approach
Track key identifiers, purpose, validity and revocation server-side. Handle lost devices and reinstalls as separate flows.
Application example
After registering a new transaction key, specify which operations may still use the old key and for how long.
Limits and considerations
Revoking too early can lock users out; indefinite acceptance reduces the security value of rotation.
Test the transition period
Older application versions, pending evidence and caches affect rotation. Define acceptance windows, revocation conditions and registration identifiers for old and new keys.
Verify rejection of the old key as well as success with the new one. Rollback must not require reactivating a compromised key. Hardware storage, server verification and distribution signing may each have different lifecycles.
Checks and decisions
- Carry key versions
- Test revocation
- Verify recovery
Manage rotation alongside RASP and attestation registration lifecycles.
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.