Azure Security Benchmark ASBv3-PV-3: Define and establish secure configurations for compute resources

What else in your programme already covers this

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

ASD Strategies to Mitigate Cyber Security Incidents · 5 controls

ASD37-04 User application hardening (Essential)
ASD37-09 OS generic exploit mitigation (Excellent)
ASD37-10 Server application hardening (Very Good)
ASD37-11 Operating system hardening (Very Good)
ASD37-36 System recovery capabilities (Very Good)

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 4 controls

CCM-AIS-02 Application Security Baseline Requirements
CCM-CCC-06 Change Management Baseline
CCM-IVS-04 OS Hardening and Base Controls
CCM-UEM-05 Endpoint Management

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 3 controls

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

FedRAMP High · 3 controls

CM-2 Baseline Configuration
CM-6 Configuration Settings
CM-6(1) Automated Management, Application, and Verification

FedRAMP Moderate · 3 controls

CM-2 Baseline Configuration
CM-6 Configuration Settings
CM-6(1) Automated Management, Application, and Verification

UK Cyber Essentials · 3 controls

CE-SC.1 Remove or Disable Unused Software
CE-SC.2 Change Default Passwords on Devices and Software
CE-SC.3 Disable Auto-Run Features

ACSC Essential Eight · 2 controls

E8-PATCHOS-ML3 Patch Operating Systems (ML3)
E8-UAH-ML2 User Application Hardening - Maturity Level 2

C5 (Germany) · 2 controls

C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening
C5-PSS-11 Images for Virtual Machines and Containers

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

CM.L2-3.4.1 System Baselining
CM.L2-3.4.2 Security Configuration Enforcement

NIST SP 800-161 Rev 1 · 2 controls

161R1-CM-2 Baseline Configuration
161R1-CM-6 Configuration Settings

NIST SP 800-171 Rev 3 · 2 controls

03.04.01 Baseline Configuration
03.04.02 Configuration Settings

PCI DSS 4.0 · 2 controls

2.2.1 2.2.1 System configuration standards maintained
2.2.6 2.2.6 System security parameters configured against misuse

AWS Well-Architected Security Pillar · 1 control

SEC06-BP02 Provision compute from hardened images

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-2 Secure the network and systems within the data environment

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-4 Systems Operations Category

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.PS-01 Configuration management practices are established and applied

NIST SP 800-172 · 1 control

3.14.4e Refresh Systems and Components from a Trusted Baseline

NIST SP 800-53 Rev 5 · 1 control

NIST800-CM-2 CM-2 Baseline Configuration

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.

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

Azure Security Benchmark ASBv3-PV-3 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.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 gaps

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.

See the released pairs, $299 each Browse the graph free