OPS-05 Protection Against Malware - Implementation
Configure production system components with malware protection as the policy prescribes, and where signature and behaviour based detection software is used, update its detection content at least once every day.
4
artefacts
2
held by a system
0
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
system holds itEvidence a system already holds
- Protection console export showing signature age for every managed host · Endpoint management (MDM / EDR)
- Production image baseline containing the scan schedule and exclusion set · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Coverage reconciliation between the asset register and protected hosts · Policy repository / GRC workspace
- Detection and quarantine event sample with the follow up action recorded · Policy repository / GRC workspace
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
- A tail of hosts running signatures days or weeks old with no exception recorded
- Coverage measured by agents installed rather than against the full asset inventory
- Resident scanning switched off on database and hypervisor hosts for performance, with nothing in its place
- New instances left unprotected until the next scheduled enrolment run
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 sheetOPS-04 Protection Against Malware - Concept · OPS-06 Data Backup and Recovery - Concept