Azure Security Benchmark
Posture and Vulnerability Management

Azure Security Benchmark ASBv3-PV-1: Define and establish secure configurations

Define secure configuration baselines for each resource type in the cloud, or establish them automatically through configuration management before or during deployment so environments are compliant by default.

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

What else in your programme already covers this

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

  • ANSSI-HYG-12 Change Default Authentication Elements on Equipment and Services
  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
  • ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies
  • ASD37-04 User application hardening (Essential)
  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)

FedRAMP High · 3 controls

  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • PL-10 Baseline Selection. Select a control baseline for the system

FedRAMP Moderate · 3 controls

  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • PL-10 Baseline Selection. Select a control baseline for the system

NIST SP 800-53 Rev 5 · 3 controls

ACSC Essential Eight · 2 controls

  • E8-UAH-ML1 User Application Hardening - Maturity Level 1
  • E8-UAH-ML2 User Application Hardening - Maturity Level 2

CIS Controls v8 · 2 controls

  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-4.1 Establish and Maintain a Secure Configuration Process

CMMC 2.0 · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-218 · 2 controls

PCI DSS 4.0 · 2 controls

  • 1.2.1 1.2.1 Ruleset configuration standards for NSCs
  • 2.2.1 2.2.1 System configuration standards maintained

SOC 2 · 2 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

UK Cyber Essentials · 2 controls

  • CE-FW.2 Change Default Firewall Passwords
  • CE-SC.2 Change Default Passwords on Devices and Software
  • CPS230-24 Design and Embedding of Internal Controls

APRA CPS 234 · 1 control

  • CPS234-21 Implementation of Information Security Controls
  • SEC01-BP06 Automate deployment of standard security controls
  • AUCDR-IS-2 Secure the network and systems within the data environment

C5 (Germany) · 1 control

  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

ISO 27001:2022 · 1 control

  • 8.9 Configuration management

ISO 27002:2022 · 1 control

  • 8.9 Configuration management

ISO 27701:2019 · 1 control

  • 6.9.1 Operational procedures and responsibilities

NIST SP 800-172 · 1 control

  • 3.4.2e Automated Detection and Remediation of Unauthorized Software

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