Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CEK-01: Encryption and Key Management Policy and Procedures

What else in your programme already covers this

This control maps to 35 controls across 18 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 · 8 controls

10.1.1 10.1.1 Requirement 10 policies and procedures maintained and in use
3.5.1.3 3.5.1.3 Disk encryption access independent of OS authentication
3.6.1.1 3.6.1.1 Service provider cryptographic architecture documented
3.7.2 3.7.2 Secure distribution of cryptographic keys
3.7.3 3.7.3 Secure storage of cryptographic keys
4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated
3.6.1 3.6.1 Procedures protect keys against disclosure and misuse
3.7.1 3.7.1 Generation of strong cryptographic keys

FedRAMP High · 4 controls

IA-5(2) Public Key-Based Authentication
SC-1 Policy and Procedures
SC-12 Cryptographic Key Establishment and Management
SC-17 Public Key Infrastructure Certificates

FedRAMP Moderate · 4 controls

IA-5(2) Public Key-Based Authentication
SC-1 Policy and Procedures
SC-12 Cryptographic Key Establishment and Management
SC-17 Public Key Infrastructure Certificates

Azure Security Benchmark · 3 controls

ASBv3-DP-5 Use customer-managed key option in data at rest encryption when required
ASBv3-DP-6 Use a secure key management process
DP-4 Enable data at rest encryption by default

NIST SP 800-53 Rev 5 · 3 controls

NIST800-SC-1 SC-1 Policy and Procedures
NIST800-SC-12 SC-12 Cryptographic Key Establishment and Management
NIST800-SC-17 SC-17 Public Key Infrastructure Certificates

AWS Well-Architected Security Pillar · 1 control

SEC08-BP01 Implement secure key management

C5 (Germany) · 1 control

C5-CRY-01 Policy for the use of encryption procedures and key management

CMMC 2.0 · 1 control

SC.L2-3.13.10 Key Management

Commercial National Security Algorithm Suite (CNSA) 2.0 · 1 control

CNSA2-SIG Digital Signatures: ML-DSA-87

DORA · 1 control

DORA-Art.9 Protection and prevention

HIPAA Security Rule · 1 control

164.312(a)(2)(iv) Encryption and Decryption (Addressable)

NIS2 Directive · 1 control

Art.21.2.h Policies and procedures on the use of cryptography and, where appropriate, encryption

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced

NIST SP 800-171 Rev 3 · 1 control

03.15.01 Policy and Procedures

NIST SP 800-66 Rev 2 · 1 control

164.312(a)(2)(iv) Encryption and Decryption (Addressable)

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.

You are reading one control. How much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CEK-01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 gaps

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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free