SI.L2-3.14.4 Update Malicious Code Protection
Keep malicious code protection mechanisms current by applying new releases as they are issued.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Update configuration for signatures and engine versions · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence of remediation for out of date endpoints · Endpoint management (MDM / EDR)
governing documentDocuments that govern the control
- Reporting showing current update status across the estate · Document repository
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Signatures updated while the engine version lags
- Offline or infrequently connected devices left stale
- Update failures unmonitored
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 sheetSI.L2-3.14.3 Security Alerts & Advisories · SI.L2-3.14.5 System & File Scanning