Azure Security Benchmark ASBv3-NS-8: Detect and disable insecure services and protocols

What else in your programme already covers this

This control maps to 44 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.

PCI DSS 4.0 · 4 controls

1.2.5 1.2.5 Allowed services, protocols and ports justified
1.2.6 1.2.6 Security features for insecure services in use
2.2.4 2.2.4 Only necessary functionality enabled
2.2.5 2.2.5 Insecure services, protocols or daemons secured

ASD Strategies to Mitigate Cyber Security Incidents · 3 controls

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-7 Least Functionality
CM-7(1) Periodic Review
SA-4(9) Acquisition Process | Functions, Ports, Protocols, and Services in Use (SA-4(9))

FedRAMP Moderate · 3 controls

CM-7 Least Functionality
CM-7(1) Periodic Review
SA-4(9) Acquisition Process | Functions, Ports, Protocols, and Services in Use (SA-4(9))

ISO 27002:2022 · 3 controls

8.20 Networks security
8.21 Security of network services
8.9 Configuration management

ACSC Essential Eight · 2 controls

E8-UAH-ML1 User Application Hardening - Maturity Level 1
E8-UAH-ML3 User Application Hardening - Maturity Level 3

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

ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
ANSSI-HYG-21 Use Secure Protocols Wherever They Exist

C5 (Germany) · 2 controls

C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CIS Controls v8 · 2 controls

CIS-12.6 Use of Secure Network Management and Communication Protocols
CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

CMMC 2.0 · 2 controls

CM.L2-3.4.6 Least Functionality
CM.L2-3.4.7 Nonessential Functionality

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

CCM-IVS-03 Network Security
CCM-IVS-07 Migration to Cloud Environments

ISO 27001:2022 · 2 controls

8.20 Networks security
8.9 Configuration management

NIST SP 800-53 Rev 5 · 2 controls

NIST800-CM-7 CM-7 Least Functionality
NIST800-RA-5 RA-5 Vulnerability Monitoring and Scanning

UK Cyber Essentials · 2 controls

CE-FW.4 Approve and Document Inbound Rules
CE-SC.1 Remove or Disable Unused Software

AWS Well-Architected Security Pillar · 1 control

SEC09-BP02 Enforce encryption in transit

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

CFTC-SS-4 Systems Operations Category

HIPAA Security Rule · 1 control

164.312(e)(1) Transmission Security (Standard)

NIST Cybersecurity Framework 2.0 · 1 control

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

NIST SP 800-161 Rev 1 · 1 control

161R1-CM-7 Least Functionality

NIST SP 800-171 Rev 3 · 1 control

03.04.06 Least Functionality

NIST SP 800-172 · 1 control

3.4.2e Automated Detection and Remediation of Unauthorized Software

NIST SP 800-66 Rev 2 · 1 control

164.312(e)(1) Transmission Security (Standard)

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-NS-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.

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