Compromise requires more than issuing a replacement. Determine what the old key could read or authorize.
Evaluation approach
Map scope, use history and related registrations. Plan revocation, re-enrollment and user effects.
Application example
One device key and a key shared by every app copy require different response scales.
Limits and considerations
Publishing a new version does not delete keys from old copies.
Does historical data remain at risk?
Identify covered datasets and periods. Stopping future signatures does not resolve past confidentiality exposure. Describe both effects separately.
Checks and decisions
- Map impact
- Revoke old authority
- Preserve evidence
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.