UEM-09 Anti-Malware Detection and Prevention
The organisation equips managed endpoints with anti-malware technology and services that both detect and block malicious code.
Source: CSA CCM v4.1, UEM-09. 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 CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
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
- Endpoint protection deployment report with coverage percentage · Endpoint management (MDM / EDR)
- Policy settings showing prevention mode enabled · Endpoint management (MDM / EDR)
- Alert and quarantine logs · Endpoint management (MDM / EDR)
periodic reviewEvidence produced at each review
- Health report of agents not checking in · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
none for this control
First move
Common gaps auditors find
- Agents in detect-only mode
- Coverage gaps on servers or Linux hosts
- Silent agents not followed 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