Azure Security Benchmark
Governance and Strategy

Azure Security Benchmark ASBv3-GS-9: Define and implement endpoint security strategy

Define and implement an endpoint security strategy covering endpoint detection and response, anti-malware capability and integration with threat detection and security operations.

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

What else in your programme already covers this

This control maps to 28 controls across 19 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-14 Apply a Minimum Security Level Across the Whole Estate
  • ANSSI-HYG-17 Enable and Configure the Local Firewall on Workstations
  • ANSSI-HYG-33 Adopt Security Policies Dedicated to Mobile Terminals

CIS Controls v8 · 3 controls

  • CIS-10.1 Deploy and Maintain Anti-Malware Software
  • CIS-10.6 Centrally Manage Anti-Malware Software
  • CIS-13.2 Deploy a Host-Based Intrusion Detection Solution
  • CCM-TVM-02 Malware Protection Policy and Procedures
  • CCM-UEM-01 Endpoint Devices Policy and Procedures

HIPAA Security Rule · 2 controls

ISO 27002:2022 · 2 controls

  • 8.1 User endpoint devices
  • 8.7 Protection against malware

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

C5 (Germany) · 1 control

  • C5-OPS-04 Protection Against Malware - Concept

CMMC 2.0 · 1 control

FedRAMP High · 1 control

  • SI-1 Policy and Procedures

FedRAMP Moderate · 1 control

  • SI-1 Policy and Procedures

ISO 27001:2022 · 1 control

  • 8.1 User end point devices
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

PCI DSS 4.0 · 1 control

  • 5.1.1 5.1.1 Requirement 5 policies and procedures maintained and communicated

SOC 2 · 1 control

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software

UK Cyber Essentials · 1 control

  • CE-MP.1 Anti-Malware Software Deployed

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 Governance and Strategy

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

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