ASD Strategies to Mitigate Cyber Security Incidents
Detecting Cyber Security Incidents and Responding

ASD Strategies to Mitigate Cyber Security Incidents ASD37-30: Endpoint detection and response (Very Good)

Endpoint detection and response software on all computers for centralised analysis and reporting of threat indicators.

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

What else in your programme already covers this

This control maps to 51 controls across 17 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 · 5 controls

  • IR-4 Incident Handling
  • SI-3 Malicious Code Protection
  • SI-4 System Monitoring
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis
  • SI-4(23) System Monitoring | Host-based Devices (SI-4(23))

FedRAMP Moderate · 5 controls

  • IR-4 Incident Handling
  • SI-3 Malicious Code Protection
  • SI-4 System Monitoring
  • SI-4(2) Automated Tools and Mechanisms for Real-Time Analysis
  • SI-4(23) System Monitoring | Host-based Devices (SI-4(23))
  • ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling
  • ASBv3-LT-1 Enable threat detection capabilities
  • ES-1 Use Endpoint Detection and Response (EDR)
  • LT-5 Centralize security log management and analysis

CIS Controls v8 · 4 controls

  • CIS-10.6 Centrally Manage Anti-Malware Software
  • CIS-10.7 Use Behavior-Based Anti-Malware Software
  • CIS-13.2 Deploy a Host-Based Intrusion Detection Solution
  • CIS-8.9 Centralize Audit Logs

ISO 27002:2022 · 4 controls

  • 8.1 User endpoint devices
  • 8.15 Logging
  • 8.16 Monitoring activities
  • 8.7 Protection against malware

CMMC 2.0 · 3 controls

ISO 27001:2022 · 3 controls

  • 8.1 User end point devices
  • 8.15 Logging
  • 8.16 Monitoring activities

NIST SP 800-53 Rev 5 · 3 controls

PCI DSS 4.0 · 3 controls

  • 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
  • 5.2.1 5.2.1 Anti-malware deployed on all system components

HIPAA Security Rule · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.4 CC7.4 Responding to security incidents

C5 (Germany) · 1 control

  • C5-OPS-05 Protection Against Malware - Implementation

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 Detecting Cyber Security Incidents and Responding

You are reading one control. How much of ASD Strategies to Mitigate Cyber Security Incidents have you already done?

ASD Strategies to Mitigate Cyber Security Incidents ASD37-30 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ASD Strategies to Mitigate Cyber Security Incidents your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 32 of 37 ASD Strategies to Mitigate Cyber Security Incidents 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 51 it maps to, and the evidence behind each claim, over MCP and REST.