03.14.02 Malicious Code Protection
Implement malicious code protection at system entry and exit points; update protection mechanisms; configure to perform periodic scans and real-time scans of files; address receipt of false positives.
3
artefacts
1
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
- Scan results · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Signature update evidence · Document repository
governing documentDocuments that govern the control
- EDR/AV deployment report · Policy repository / GRC workspace
First move
Start with the 1 of 3 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
- EDR not on Linux servers
- exclusions overly broad
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 sheet03.14.01 Flaw Remediation · 03.14.03 Security Alerts, Advisories, and Directives