SI.L1-b.1.xiv
Update Malicious Code Protection [FCI Data]
Source and approval
CMMC Assessment Guide — Level 1 · Revision 2.13
Publisher approved · Complete cited source edition 2026-10-31
Read the official guideSee SI.L1-b.1.xiv in the reference catalog with its NIST cross-references
Official requirement
Update malicious code protection mechanisms when new releases are available.
Assessment objectives
a. malicious code protection mechanisms are updated when new releases are available.
Implementation guidance
Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.
In plain language
Keep malicious-code protection mechanisms current when updates are available.
Implementation example
Example from the source assessment guide (not a mandatory implementation): You have installed anti- malware software to protect a computer that stores FCI from malicious code. Knowing that malware evolves rapidly, you configure the software to automatically check for malware definition updates every day and update as needed [a].
Evidence examples
Examples suggested by the source guide (not an exhaustive or mandatory checklist): System and information integrity policy; configuration management policy and procedures; procedures addressing malicious code protection; malicious code protection mechanisms; records of malicious code protection updates; system security plan; system design documentation; system configuration settings and associated documentation; scan results from malicious code protection mechanisms; record of actions initiated by malicious code protection mechanisms in response to malicious code detection; system audit logs and records; other relevant documents or records
Common mistakes
Assuming installed antivirus automatically has current software, signatures, and detection information.