EvidenceSheet
CMMC 2.0 · System and Information Integrity

SI.L2-3.14.5 System & File Scanning

Run periodic scans of systems and real time scans of files arriving from external sources as those files are downloaded, opened or executed.

Source: CMMC 2.0, SI.L2-3.14.5. 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
2
held by a system
0
at each review
easy
to go live
Vulnerability scanner / patch tooling
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

  • Scheduled scan configuration and completion records · Vulnerability scanner / patch tooling
  • Real time scanning configuration covering download, open and execute events · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Coverage reporting across in scope systems · Policy repository / GRC workspace

First move

Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.

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.4 Update Malicious Code Protection · SI.L2-3.14.6 Monitor Communications for Attacks