Azure Security Benchmark
Data Protection

Azure Security Benchmark ASBv3-DP-6: Use a secure key management process

Document and implement an enterprise cryptographic key management standard covering the key lifecycle, with keys generated, distributed and stored in a secured key vault service and rotated on a defined schedule.

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 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.

PCI DSS 4.0 · 8 controls

  • 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.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.4 3.7.4 Key changes at end of cryptoperiod
  • 3.7.5 3.7.5 Retirement, replacement or destruction of keys
  • 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 Authenticator Management
  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection
  • SC-28(1) Cryptographic Protection

FedRAMP Moderate · 4 controls

  • IA-5 Authenticator Management
  • SC-12 Cryptographic Key Establishment and Management
  • SC-13 Cryptographic Protection
  • SC-28(1) Cryptographic Protection

NIST SP 800-53 Rev 5 · 3 controls

C5 (Germany) · 2 controls

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

CMMC 2.0 · 2 controls

ISO 27001:2022 · 2 controls

  • 5.17 Authentication information
  • 8.24 Use of cryptography

ISO 27002:2022 · 2 controls

  • 5.17 Authentication information
  • 8.24 Use of cryptography

NIST SP 800-171 Rev 3 · 2 controls

  • 03.05.12 Authenticator Management
  • 03.13.10 Cryptographic Key Establishment and Management
  • ASD37-23 Protect authentication credentials (Excellent)

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

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.

Other controls in Data Protection

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

Azure Security Benchmark ASBv3-DP-6 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.

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.

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.