CMMC 2.0 SC.L2-3.13.10: Key Management

What else in your programme already covers this

This control maps to 48 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 · 13 controls

10.1.2 10.1.2 Roles for logging and monitoring assigned and understood
2.3.2 2.3.2 Wireless encryption keys changed on triggers
3.6.1.3 3.6.1.3 Cleartext key component access limited to minimum custodians
3.6.1.4 3.6.1.4 Cryptographic keys kept in fewest locations
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.7.5 3.7.5 Retirement, replacement or destruction of keys
3.7.7 3.7.7 Prevent unauthorized substitution of keys
4.2.1.1 4.2.1.1 Inventory of trusted transmission keys and certificates
9.2.4 9.2.4 Locking of consoles in sensitive areas
3.6.1 3.6.1 Procedures protect keys against disclosure and misuse
3.7.1 3.7.1 Generation of strong cryptographic keys

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 11 controls

CCM-CEK-01 Encryption and Key Management Policy and Procedures
CCM-CEK-02 CEK Roles and Responsibilities
CCM-CEK-10 Key Generation
CCM-CEK-11 Key Purpose
CCM-CEK-12 Key Rotation
CCM-CEK-13 Key Revocation
CCM-CEK-14 Key Destruction
CCM-CEK-15 Key Activation
CCM-CEK-19 Key Compromise
CCM-CEK-20 Key Recovery
CCM-CEK-21 Key Inventory Management

SOC 2 · 6 controls

SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
SOC2-CC6.1 CC6.1 Logical access security over protected information assets
SOC2-CC6.3 CC6.3 Role-based access, least privilege and segregation of duties
SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal
SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

AWS Well-Architected Security Pillar · 2 controls

SEC08-BP01 Implement secure key management
SEC09-BP01 Implement secure key and certificate management

Azure Security Benchmark · 2 controls

ASBv3-DP-6 Use a secure key management process
ASBv3-DP-8 Ensure security of key and certificate repository

C5 (Germany) · 2 controls

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

FedRAMP High · 1 control

SC-12 Cryptographic Key Establishment and Management

FedRAMP Moderate · 1 control

SC-12 Cryptographic Key Establishment and Management

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-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected

NIST SP 800-171 Rev 3 · 1 control

03.13.10 Cryptographic Key Establishment and Management

NIST SP 800-53 Rev 5 · 1 control

NIST800-SC-12 SC-12 Cryptographic Key Establishment and Management

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 CMMC 2.0 have you already done?

CMMC 2.0 SC.L2-3.13.10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.

If you hold FedRAMP Moderate98.2% covered · 2 gaps If you hold NIST SP 800-171 Rev 394.5% covered · 6 gaps If you hold NIST SP 800-53 Rev 585.5% covered · 16 gaps If you hold ISO 27001:202279.1% covered · 23 gaps If you hold ISO 27002:202267.3% covered · 36 gaps If you hold CIS Controls v864.5% covered · 39 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. 1 were rejected on the FedRAMP Moderate pair alone.

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