Key Revocation and Compromise Response
What you'll learn: How to immediately invalidate compromised keys and respond to security incidents involving key exposure.
What Is Key Revocation?
Key revocation is the emergency "off switch" for cryptographic keys. When a private key is compromised, stolen, or suspected of being exposed, you must immediately invalidate it to prevent attackers from impersonating you or decrypting your data. Think of it like canceling a stolen credit card—you notify everyone the old card is no longer trustworthy and issue a new one.
When to Revoke a Key
Revoke a key immediately if:
- The private key file was exposed or stolen
- A device storing the key was lost or compromised
- An employee with key access left the organization
- You suspect malicious activity or unauthorized access
- The key reached its maximum lifetime without renewal
The Revocation Process
Immediate Actions:
- Generate and distribute a revocation certificate (for systems like PGP/GPG) or update certificate revocation lists (CRLs)
- Notify all parties who trust your key via secure channels
- Update directory services like LDAP or public key servers
- Deploy new keys using your key rotation procedures
- Monitor for misuse of the revoked key
Communication is Critical: Certificate authorities publish CRLs and operate Online Certificate Status Protocol (OCSP) responders to inform verifiers about revoked certificates in real-time. Without proper communication, others may continue trusting the compromised key.
Compromise Response
After revocation, investigate the scope: What was encrypted with that key? Who might have accessed it? Review logs, rotate related credentials, and document the incident for compliance requirements.
Key Takeaway: Key revocation is your emergency response to key compromise—act immediately, communicate revocation status widely, and deploy replacement keys following established procedures to minimize security impact.