TVM-02 Malware Protection Policy and Procedures
Keep approved policies and procedures for protecting managed assets against malware, and review them at least annually.
4
artefacts
0
held by a system
2
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
- Annual review record · Document repository
- Evidence of communication and enforcement · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The approved malware protection policy · Policy repository / GRC workspace
- The asset classes in scope and the protection required for each · 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
- Policy covers endpoints and omits servers or cloud workloads
- Annual review missed
- Policy names a product rather than a control requirement, so it ages badly
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 sheetTVM-01 Threat and Vulnerability Management Policy and Procedures · TVM-03 Vulnerability Remediation Schedule