C5 (Germany)
C5: Cryptography and Key Management

C5 (Germany) C5-CRY-01: Policy for the use of encryption procedures and key management

Maintain and issue encryption and key management policies that mandate state-of-the-art algorithms and network protocols, tie encryption strength to the information classification scheme, cover the full key lifecycle, and reflect applicable legal obligations.

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

What else in your programme already covers this

This control maps to 44 controls across 20 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

  • 12.3.3 12.3.3 Cryptographic cipher suite and protocol inventory reviewed annually
  • 3.6.1.1 3.6.1.1 Service provider cryptographic architecture documented
  • 3.7.4 3.7.4 Key changes at end of cryptoperiod
  • 3.7.5 3.7.5 Retirement, replacement or destruction of keys
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 3.7.1 3.7.1 Generation of strong cryptographic keys

FedRAMP High · 4 controls

  • IA-7 Cryptographic Module Authentication
  • SC-1 Policy and Procedures
  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection

FedRAMP Moderate · 4 controls

  • IA-7 Cryptographic Module Authentication
  • SC-1 Policy and Procedures
  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection

NIST SP 800-53 Rev 5 · 3 controls

  • ANSSI-HYG-18 Encrypt Sensitive Data Transmitted Over the Internet
  • ANSSI-HYG-31 Encrypt Sensitive Data, in Particular on Equipment That May Be Lost
  • ASBv3-DP-6 Use a secure key management process
  • ASBv3-GS-3 Define and implement data protection strategy

CMMC 2.0 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • 03.13.10 Cryptographic Key Establishment and Management
  • 03.13.11 Cryptographic Protection

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

DORA · 1 control

HIPAA Security Rule · 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

NIST SP 800-218 · 1 control

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-01 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 44 it maps to, and the evidence behind each claim, over MCP and REST.