5.3.1 The anti-malware solution(s) is kept current via automatic updates
The anti-malware solution(s) is kept current via automatic updates.
2
artefacts
0
held by a system
1
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
- Management review minutes addressing PIMS · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Board or executive sign-off on privacy policy · 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
- No top-management statement of accountability for PII protection
- Privacy objectives not integrated with strategic business objectives
- Resources for the PIMS not formally approved or tracked
- Leadership review of privacy performance not on a fixed cadence
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 sheet5.2.3.1 Frequency of periodic evaluations per targeted risk analysis · 5.3.2 The anti-malware solution(s): • Performs periodic scans and active or real-time scans. OR • Performs continuous behavioral analysis of systems or processes