C5 (Germany)
C5: Cryptography and Key Management

C5 (Germany) C5-CRY-04: Secure key management

Operate key management spanning generation, certificate issuance, activation, storage isolated from application and middleware layers, authorised retrieval, rekeying, compromise handling, withdrawal and deletion, with separate rules stated where pre-shared keys are used.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 36 controls across 17 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 6 controls

  • 3.6.1.2 3.6.1.2 Permitted storage forms for secret and private keys
  • 3.6.1.3 3.6.1.3 Cleartext key component access limited to minimum custodians
  • 3.7.2 3.7.2 Secure distribution of cryptographic keys
  • 3.7.3 3.7.3 Secure storage of cryptographic keys
  • 3.7.4 3.7.4 Key changes at end of cryptoperiod
  • 3.6.1 3.6.1 Procedures protect keys against disclosure and misuse
  • ASBv3-DP-5 Use customer-managed key option in data at rest encryption when required
  • ASBv3-DP-6 Use a secure key management process
  • ASBv3-DP-7 Use a secure certificate management process
  • ASBv3-DP-8 Ensure security of key and certificate repository
  • ASBv3-IM-8 Restrict the exposure of credential and secrets

FedRAMP High · 2 controls

  • SC-12 Cryptographic Key Establishment and Management
  • SC-17 Public Key Infrastructure Certificates

FedRAMP Moderate · 2 controls

  • SC-12 Cryptographic Key Establishment and Management
  • SC-17 Public Key Infrastructure Certificates

NIST SP 800-53 Rev 5 · 2 controls

APPI · 1 control

  • APPI-A41 Preparation and Handling of Pseudonymized Personal Information

CMMC 2.0 · 1 control

DORA · 1 control

ISO 27001:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27002:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls

NIS2 Directive · 1 control

  • Art.21.2.h Policies and procedures on the use of cryptography and, where appropriate, encryption
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • 03.13.10 Cryptographic Key Establishment and Management

SOC 2 · 1 control

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in C5: Cryptography and Key Management

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-CRY-04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

The graph holds this control, the 36 it maps to, and the evidence behind each claim, over MCP and REST.