EvidenceSheet
NIST SP 800-171 Rev 3 · 03.14 SI (System and Information Integrity)

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.

Source: NIST SP 800-171 Rev 3, 03.14.02. 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 NIST SP 800-171 Rev 3 in the compliance library.

3
artefacts
2
held by a system
1
at each review
easy
to go live
Endpoint management (MDM / EDR)
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

  • EDR/AV deployment report · Endpoint management (MDM / EDR)
  • Scan results · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

  • Signature update evidence · Document repository

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

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

03.14.01 Flaw Remediation · 03.14.03 Security Alerts, Advisories, and Directives