FedRAMP High SC-12: Cryptographic Key Establishment and Management

What else in your programme already covers this

This control maps to 45 controls across 15 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 · 15 controls

10.1.2 Requirement 10 roles and responsibilities documented and assigned
12.3.3 Cryptographic cipher suites and protocols inventory
2.3.2 Wireless encryption keys rotated
3.5.1.3 Disk-level encryption key management
3.6.1.1 Documented description of cryptographic architecture
3.6.1.2 Secret and private keys restricted to fewest custodians
3.6.1.4 Cryptographic keys stored in fewest possible locations
3.7.2 Secure key distribution
3.7.3 Secure key storage
3.7.4 Cryptoperiod and key changes
3.7.5 Retirement or replacement of keys
3.7.7 Prevent unauthorised substitution of keys
4.2.1.1 Inventory of trusted keys and certificates
3.6.1 Procedures are defined and implemented to protect cryptographic keys used to protect stored account data against disclosure and misuse that include: • Access to keys is restricted to the fewest number of custodians necessary.
3.7.1 Key-management policies and procedures are implemented to include generation of strong cryptographic keys used to protect stored account data

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

CCM-CEK-01 Encryption and Key Management Policy and Procedures
CCM-CEK-02 CEK Roles and Responsibilities
CCM-CEK-08 CSC Key Management Capability
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

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
ASBv3-DP-8 Ensure security of key and certificate repository

SOC 2 · 3 controls

SOC2-CC5.2 COSO principle 11: Selects and develops general controls over technology
SOC2-CC6.1 Implements logical access security software, infrastructure and architectures over protected information assets
SOC2-CC6.7 Transmission of data is restricted to authorized users

C5 (Germany) · 2 controls

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

AWS Well-Architected Security Pillar · 1 control

SEC08-BP01 Implement secure key management

CMMC 2.0 · 1 control

SC.L2-3.13.10 Key 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 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 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 FedRAMP High have you already done?

FedRAMP High SC-12 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

If you hold C5 (Germany)29% covered · 291 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. 6 were rejected on the C5 (Germany) pair alone.

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