Azure Security Benchmark
Data Protection

Azure Security Benchmark ASBv3-DP-8: Ensure security of key and certificate repository

Harden the key vault service itself through access control, network restriction, logging, monitoring and backup so keys and certificates stay protected.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 37 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 · 6 controls

  • 10.2.1.3 10.2.1.3 Access to the audit logs is itself logged
  • 3.6.1.2 3.6.1.2 Permitted storage forms for secret and private keys
  • 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.3 3.7.3 Secure storage of cryptographic keys
  • 3.6.1 3.6.1 Procedures protect keys against disclosure and misuse

FedRAMP High · 5 controls

  • AC-3 Access Enforcement
  • AU-9 Protection of Audit Information
  • IA-5(6) Protection of Authenticators
  • IA-7 Cryptographic Module Authentication
  • SC-12 Cryptographic Key Establishment and Management

FedRAMP Moderate · 5 controls

  • AC-3 Access Enforcement
  • AU-9 Protection of Audit Information
  • IA-5(6) Protection of Authenticators
  • IA-7 Cryptographic Module Authentication
  • SC-12 Cryptographic Key Establishment and Management

NIST SP 800-53 Rev 5 · 3 controls

ISO 27002:2022 · 2 controls

  • 8.15 Logging
  • 8.3 Information access restriction

NIST SP 800-171 Rev 3 · 2 controls

  • 03.05.12 Authenticator Management
  • 03.13.10 Cryptographic Key Establishment and Management
  • E8-BACKUP-ML1 Regular Backups (ML1)

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.3 Information access restriction
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

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-8 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 37 it maps to, and the evidence behind each claim, over MCP and REST.