EvidenceSheet
CMMC 2.0 · System and Information Integrity

SI.L2-3.14.4 Update Malicious Code Protection

Keep malicious code protection mechanisms current by applying new releases as they are issued.

Source: CMMC 2.0, SI.L2-3.14.4. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CMMC 2.0 in the compliance library.

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

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

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

SI.L2-3.14.3 Security Alerts & Advisories · SI.L2-3.14.5 System & File Scanning