ES-3 Ensure anti-malware software and signatures are updated
Ensure anti-malware signatures and the anti-malware solution itself are updated rapidly and consistently across the endpoint estate.
4
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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
none for this control
governing documentDocuments that govern the control
- Signature version reporting across endpoints · Policy repository / GRC workspace
- Update schedule and its enforcement mechanism · Policy repository / GRC workspace
- Alerting on endpoints whose signatures are stale · Policy repository / GRC workspace
- Exception register for endpoints that cannot auto-update · 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
- signature age never reported so stale endpoints go unnoticed
- updates blocked by network restrictions on isolated subnets
- exceptions granted 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 sheetES-2 Use modern anti-malware software · GS-1 Align organization roles, responsibilities and accountabilities