What evidence do auditors commonly ask for on 30 Endpoint detection and response (Very Good)?

EDR policy settings showing which threat indicators trigger alerts and which trigger automatic host isolation; EDR console export of active sensors compared with the full computer inventory, showing coverage percentage and stale agents; EDR telemetry forwarding configuration to the central analysis platform or SIEM; Sample of EDR detections with analyst triage records and any host isolation actions taken.

What is the most common gap auditors find on 30?

EDR licences bought for a subset of endpoints, leaving servers or contractor laptops uncovered

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

`30` Endpoint detection and response (Very Good)

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

Source: ASD Strategies to Mitigate Cyber Security Incidents, 30. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ASD Strategies to Mitigate Cyber Security Incidents in the compliance library.

artefacts

held by a system

at each review

easy

to go live

Endpoint management (MDM / EDR)

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

EDR policy settings showing which threat indicators trigger alerts and which trigger automatic host isolation · Endpoint management (MDM / EDR)
EDR console export of active sensors compared with the full computer inventory, showing coverage percentage and stale agents · Endpoint management (MDM / EDR)
EDR telemetry forwarding configuration to the central analysis platform or SIEM · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

Sample of EDR detections with analyst triage records and any host isolation actions taken · Endpoint management (MDM / EDR)

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

EDR licences bought for a subset of endpoints, leaving servers or contractor laptops uncovered
Sensors silently offline for weeks with no health alerting on disconnected agents
EDR detections reviewed only by the vendor portal with no internal reporting or follow-up

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

29 Host-based IDS/IPS (Very Good) · 31 Hunt to discover incidents (Very Good)