Azure Security Benchmark
Data Protection

Azure Security Benchmark ASBv3-DP-7: Use a secure certificate management process

Document and implement an enterprise certificate management standard covering the certificate lifecycle and certificate policies, so certificates used by critical services are tracked and renewed.

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

What else in your programme already covers this

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

FedRAMP High · 2 controls

  • IA-5(2) Public Key-Based Authentication
  • SC-17 Public Key Infrastructure Certificates

FedRAMP Moderate · 2 controls

  • IA-5(2) Public Key-Based Authentication
  • SC-17 Public Key Infrastructure Certificates

NIST SP 800-171 Rev 3 · 2 controls

  • 03.05.12 Authenticator Management
  • 03.13.10 Cryptographic Key Establishment and Management

PCI DSS 4.0 · 2 controls

  • 12.3.3 12.3.3 Cryptographic cipher suite and protocol inventory reviewed annually
  • 4.2.1.1 4.2.1.1 Inventory of trusted transmission keys and certificates
  • SEC09-BP01 Implement secure key and certificate management

C5 (Germany) · 1 control

ISO 27001:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27002:2022 · 1 control

  • 8.24 Use of cryptography

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls
  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit 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-7 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 17 it maps to, and the evidence behind each claim, over MCP and REST.