Define, implement and evaluate processes, procedures and technical measures to revoke and remove cryptographic keys prior to the end of its established cryptoperiod, when a key is compromised, or an entity is no longer part of the organization, which include provisions for legal and regulatory requirements.
Key revocation removes keys from operational use before their expiration dates.
- Key revocation of a “symmetric key” restricts the use of the key material.
- Key revocation of an asymmetric key specifically refers to the private key.
- Perform emergency revocation when keys are lost or compromised.
- Revocation statuses should be available to all who have relied on the key.
- Use certificate revocation lists (CRLs) or other relevant mechanisms to inform stakeholders.
- ROI: Cost to decrypt then re-encrypt large distributed databases with a significant number of key holders.
- ROI: Risk of long-term cryptoperiods versus short and the amount of data encrypted with one key.
- All relevant transitions/activity should be recorded (logged) in the inventory management system (CKMS).
- Examine the organization procedures and confirm the existence of a key revocation process.
- Identify a population of keys and confirm that they are captured within the key revocation process.
- Confirm that a list of entities no longer part of the organization is maintained.
[csf.tools Note: For more information on the Cloud Controls Matrix, visit the CSA Cloud Controls Matrix Homepage.]
Cloud Control Matrix is Copyright 2023 Cloud Security Alliance.