EvidenceSheet

8.7 Protection against malware

Requires malware protection to be put in place and reinforced by suitable awareness among users.

5
artefacts
2
held by a system
2
at each review
moderate
to go live
Endpoint management (MDM / EDR)
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • Malware protection deployment records showing coverage across servers, endpoints, mobile devices, email and web gateways · Endpoint management (MDM / EDR)
  • Configuration evidence including update frequency, scanning scope, real time protection and the action taken on detection · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

  • Detection records for the period and the response taken to each · Endpoint management (MDM / EDR)
  • Awareness evidence covering user recognition and reporting of malicious content · Endpoint management (MDM / EDR)

governing documentDocuments that govern the control

  • Coverage reporting showing devices without protection or with outdated definitions, and the follow up on them · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Endpoint management (MDM / EDR)); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

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

8.6 Capacity management · 8.8 Management of technical vulnerabilities