SI.L2-3.14.2 Malicious Code Protection
Provide malicious code protection at the points in the system where such code is likely to enter or execute.
3
artefacts
1
held by a system
0
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
- Configuration showing protection is active · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Identification of designated protection locations, endpoints and gateways · Policy repository / GRC workspace
- Malicious code protection deployment and coverage reporting · Policy repository / GRC workspace
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
- Endpoints covered while email and web gateways are not
- Coverage gaps on servers and non standard platforms
- Protection installed but disabled or in passive mode
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.1 Flaw Remediation · SI.L2-3.14.3 Security Alerts & Advisories