Azure Security Benchmark
Posture and Vulnerability Management

Azure Security Benchmark ASBv3-PV-4: Audit and enforce secure configurations for compute resources

Continuously monitor compute resources for deviation from the defined configuration baseline, alert on drift and enforce the desired configuration by denying or remediating non-compliant configuration.

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

What else in your programme already covers this

This control maps to 69 controls across 24 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 · 6 controls

  • CA-7 Continuous Monitoring
  • CM-2(2) Automation Support for Accuracy and Currency
  • CM-3 Configuration Change Control
  • CM-6(1) Automated Management, Application, and Verification
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

FedRAMP Moderate · 6 controls

  • CA-7 Continuous Monitoring
  • CM-2(2) Automation Support for Accuracy and Currency
  • CM-3 Configuration Change Control
  • CM-6(1) Automated Management, Application, and Verification
  • SI-7 Software, Firmware, and Information Integrity
  • SI-7(1) Integrity Checks

PCI DSS 4.0 · 6 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 10.7.1 10.7.1 Service providers detect critical control failures (superseded)
  • 10.7.2 10.7.2 Detect and alert on critical security control failures
  • 11.5.2 11.5.2 Change detection on critical files
  • 2.2.6 2.2.6 System security parameters configured against misuse
  • 6.5.1 6.5.1 Change control procedure for production

ISO 27002:2022 · 5 controls

  • 5.36 Compliance with policies, rules and standards for information security
  • 8.16 Monitoring activities
  • 8.19 Installation of software on operational systems
  • 8.32 Change management
  • 8.9 Configuration management

NIST SP 800-53 Rev 5 · 5 controls

ISO 27001:2022 · 4 controls

  • 5.36 Compliance with policies, rules and standards for information security
  • 8.19 Installation of software on operational systems
  • 8.32 Change management
  • 8.9 Configuration management

NIST SP 800-171 Rev 3 · 4 controls

ACSC Essential Eight · 3 controls

  • E8-APP-ML1 Application Control (ML1)
  • E8-MACRO-ML1 Configure Microsoft Office Macro Settings (ML1)
  • E8-UAH-ML2 User Application Hardening - Maturity Level 2
  • ASD37-01 Application control (Essential)
  • ASD37-11 Operating system hardening (Very Good)
  • ASD37-29 Host-based IDS/IPS (Very Good)

CMMC 2.0 · 3 controls

  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.14.4e Refresh Systems and Components from a Trusted Baseline
  • 3.4.2e Automated Detection and Remediation of Unauthorized Software

APRA CPS 234 · 1 control

C5 (Germany) · 1 control

  • C5-PSS-11 Images for Virtual Machines and Containers

CIS Controls v8 · 1 control

  • CIS-4.6 Securely Manage Enterprise Assets and Software

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.15.2 Information security reviews

SOC 2 · 1 control

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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 Posture and Vulnerability Management

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

Azure Security Benchmark ASBv3-PV-4 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 69 it maps to, and the evidence behind each claim, over MCP and REST.