Free compliance framework explorer — browse controls, evidence, and implementation guidance.Subscribe for updates →
SOC 247
ITSP.10.17198
ISO 42001soon
ISO 27001soon

Browse

98 controls

03.13.10Cryptographic key establishment and managementITSP.10.171System and communications protection

Official Requirement

Establish and manage cryptographic keys in the system in accordance with the following key management requirements: [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction].

Source: Canadian Centre for Cyber Security ITSP.10.171 (2025), adapted from NIST SP 800-171 Rev. 3

In Plain English

Your organization must have a formal process for managing cryptographic keys throughout their lifecycle -- from creation through storage, distribution, rotation, and eventual destruction. Keys must be protected from unauthorized access and managed according to defined policies.

Help us build what matters.

Vote for the next framework, subscribe for updates, and let us know if you'd contribute.

The Trust Services Criteria referenced in this tool are published by the American Institute of Certified Public Accountants (AICPA) and incorporate principles from the Committee of Sponsoring Organizations of the Treadway Commission (COSO). Criteria descriptions are reproduced for reference purposes. All implementation guidance, evidence recommendations, and control language are original work by Truvo Cyber. ISO 27001 and ISO 42001 are standards published by the International Organization for Standardization (ISO). Framework and standard names are the property of their respective owners. This tool is not affiliated with, endorsed by, or certified by AICPA, COSO, or ISO.

© 2026 Truvo Cyber. All rights reserved.

On-premises implementation and evidence

Cryptographic key lifecycle management

Implementation steps

  1. Document a key management policy covering the full key lifecycle: generation, distribution, storage, access control, rotation, and destruction
  2. Generate keys using FIPS-validated cryptographic modules or hardware security modules (HSMs)
  3. Store keys in HSMs or encrypted key stores with access restricted to authorized key custodians
  4. Implement key rotation schedules and securely destroy expired or compromised keys using approved methods

Tools / systems

Evidence artifacts

Evidence frequency: Continuous enforcement; annual key rotation; annual policy review