CEK-14: Key Destruction

CSF v1.1 References:

Info icon.

Control is new to this version of the control set.

Control Statement

Define, implement and evaluate processes, procedures and technical measures to destroy keys stored outside a secure environment and revoke keys stored in Hardware Security Modules (HSMs) when they are no longer needed, which include provisions for legal and regulatory requirements.

Implementation Guidance

Key destruction removes all traces to prevent recovery by physical or electronic means.

  1. When a key is to be destroyed, all key copies should be destroyed.
  2. Keys should be destroyed when they are not needed to minimize compromise risks.
  3. Secret and private keys should be destroyed so they cannot be recovered by any means.
  4. Public keys may be kept or destroyed.
  5. Notify stakeholders in advance of key destruction.
  6. Consider laws, regulations, and their retention requirements for keys and/or metadata.
  7. Key recovery information (KRI) should be protected against unauthorized disclosure or destruction.
  8. All relevant transitions/activity should be recorded (logged) in the inventory management system (CKMS).

Auditing Guidance

  1. Confirm the existence of key destruction processes and procedures.
  2. Review the access permissions for the destruction and restoration of keys and confirm that only appropriate individuals have access to these capabilities.
  3. Review keys that have been destroyed and ascertain the appropriate process and procedure have been followed.
  4. Establish documented criteria that determine when it is appropriate for a cryptographic key to be stored outside a secure environment.

[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.