6.9.2 Protection from malware
Controls against malware apply as the base guidance requires, read as protecting the personal data that a compromise would expose.
3
artefacts
0
held by a system
2
at each review
hard
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
none for this control
periodic reviewEvidence produced at each review
- Detection and response records · Endpoint management (MDM / EDR)
- Evidence of coverage on endpoints that hold local copies · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Malware protection coverage across systems holding personal data · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Coverage measured against the asset inventory, which omits systems holding personal data
- Detections handled without considering whether personal data was exposed
- Servers excluded on performance grounds with no compensating control
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 sheet6.9.1 Operational procedures and responsibilities · 6.9.3 Backup