5.2.3.1 Frequency of periodic evaluations per targeted risk analysis
The frequency of periodic evaluations of system components identified as not at risk for malware is defined in the entity's targeted risk analysis.
5
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Evidence of evaluations at chosen cadence · Document repository
governing documentDocuments that govern the control
- Targeted risk analysis document for 5.2.3 · Document repository
- Defined frequency with rationale · Document repository
- Approval by management · Document repository
- Linkage to 12.3.1 process · Document repository
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 targeted risk analysis
- Frequency undefined
- Frequency not justified
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 Any system components that are not at risk for malware are evaluated periodically to include the following: • A documented list of all system components not at risk for malware. • Identification and evaluation · 5.3.1 The anti-malware solution(s) is kept current via automatic updates