SI-3 Malicious code protection
Requires malicious code protection mechanisms to be implemented at system entry and exit points, updated automatically as new releases appear under configuration management, configured to scan periodically at a defined f
5
artefacts
2
held by a system
1
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration showing scan frequency, real time scanning and the action on detection · Vulnerability scanner / patch tooling
- Alert and response records for detections · SIEM / log platform
periodic reviewEvidence produced at each review
- Assessment of false positive handling and its operational impact · Document repository
governing documentDocuments that govern the control
- Deployment coverage report for malicious code protection across the estate · Policy repository / GRC workspace
- Update status showing definitions or engines are current · Document repository
First move
Start with the 2 of 5 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Coverage gaps on servers, appliances and unmanaged systems
- Detections logged locally with nobody alerted or responding
- Real time scanning disabled on high load systems without compensating controls
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 sheet