Azure Security Benchmark ASBv3-DP-5: Use customer-managed key option in data at rest encryption when required

What else in your programme already covers this

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

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

CCM-CEK-01 Encryption and Key Management Policy and Procedures
CCM-CEK-08 CSC Key Management Capability
CCM-GRC-07 Information System Regulatory Mapping

FedRAMP High · 3 controls

SC-12 Cryptographic Key Establishment and Management
SC-13 Cryptographic Protection
SC-28 Protection of Information at Rest

FedRAMP Moderate · 3 controls

SC-12 Cryptographic Key Establishment and Management
SC-13 Cryptographic Protection
SC-28 Protection of Information at Rest

NIST SP 800-53 Rev 5 · 3 controls

NIST800-SC-12 SC-12 Cryptographic Key Establishment and Management
NIST800-SC-13 SC-13 Cryptographic Protection
NIST800-SC-28 SC-28 Protection of Information at Rest

PCI DSS 4.0 · 3 controls

3.5.1 3.5.1 Stored PAN rendered unreadable
3.5.1.3 3.5.1.3 Disk encryption access independent of OS authentication
3.7.9 3.7.9 Key guidance for service provider customers

C5 (Germany) · 2 controls

C5-CRY-03 Encryption of sensitive data for storage
C5-CRY-04 Secure key management

CMMC 2.0 · 2 controls

SC.L2-3.13.11 CUI Encryption
SC.L2-3.13.16 Data at Rest

ISO 27001:2022 · 2 controls

5.31 Legal, statutory, regulatory and contractual requirements
8.24 Use of cryptography

ISO 27002:2022 · 2 controls

5.31 Legal, statutory, regulatory and contractual requirements
8.24 Use of cryptography

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

NIST SP 800-171 Rev 3 · 2 controls

03.13.10 Cryptographic Key Establishment and Management
03.13.11 Cryptographic Protection

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-31 Encrypt Sensitive Data, in Particular on Equipment That May Be Lost

AWS Well-Architected Security Pillar · 1 control

SEC08-BP01 Implement secure key management

HIPAA Security Rule · 1 control

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

NIST SP 800-161 Rev 1 · 1 control

161R1-SC-28 Protection of Information at Rest

NIST SP 800-66 Rev 2 · 1 control

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

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.

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-DP-5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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