C5 Field Guideunofficial

CRY · Cryptography and Key Management

CRY-17 Cryptographic Key Lifecycle Management

2 sub-criteria

Changed since C5:2020 · formerly CRY-04

Basic criterion

Dissolved the former key management criterion and moved key lifecycle management into its own criterion with extended requirements.

Additional criterion

Dissolved the former key management criterion and moved key lifecycle management into its own criterion, to which the former key management additional criterion does not apply.

Wording in C5:2020

Basic criterion

Procedures and technical safeguards for secure key management in the area of responsibility of the Cloud Service Provider include at least the following aspects:

  • Generation of keys for different cryptographic systems and applications;
  • Issuing and obtaining public-key certificates;
  • Provisioning and activation of the keys;
  • Secure storage of keys (separation of key management system from application and middleware level) including description of how authorised users get access;
  • Changing or updating cryptographic keys including policies defining under which conditions and in which manner the changes and/or updates are to be realised;
  • Handling of compromised keys;
  • Withdrawal and deletion of keys; and
  • If pre-shared keys are used, the specific provisions relating to the safe use of this procedure are specified separately.

Additional criterion

Keys should be withdrawn or deleted e.g. in the event of compromise or employee changes. The Cloud Service Provider protects the keys which are created and inserted into the cloud service by the cloud customers according to the same criteria as the keys created by the Cloud Service Provider.

All changes since C5:2020

Basic criterion

CRY-17.01B

The cloud service provider has documented and implemented procedures and technical safeguards to monitor and document the lifecycle of cryptographic keys and materials.

CRY-17.02B

For all keys except for ephemeral keys, the aforementioned safeguards ensure detailed records of each key from creation to destruction, including any status changes.

BSI text from C5:2026 and its changelog: © Federal Office for Information Security 2026, reproduced unchanged under CC BY-ND 4.0. Unofficial site, not affiliated with BSI. Licence and sources