3.14.4
SI.L1-3.14.4 · Level 1 + 2
Update malicious code protection mechanisms when new releases are available.
NIST SP 800-171 Rev 2 · §3.14.4
Update malicious code protection mechanisms when new releases are available.
Assessment objectives
From NIST SP 800-171A · 1 objective must be met to satisfy this control
Examine
[SELECT FROM: 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; 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].
Interview
[SELECT FROM: System or network administrators; personnel with information security responsibilities; personnel installing, configuring, and maintaining the system; personnel with responsibility for malicious code protection; personnel with configuration management responsibility].
Test
[SELECT FROM: Organizational processes for employing, updating, and configuring malicious code protection mechanisms; organizational process for addressing false positives and resulting potential impact; mechanisms supporting or implementing malicious code protection mechanisms (including updates and configurations); mechanisms supporting or implementing malicious code scanning and subsequent actions].
What we look for in practice
The following are placeholder notes that should be refined based on practice experience.
What assessors look for in practice. Documented evidence that this control is implemented across all CUI-handling systems within scope. Specific artifacts vary, but expect requests for written procedures, system configurations, and operational records demonstrating the control is active.
Common failure patterns. Typical issues include incomplete documentation, inconsistent implementation across systems, and missing periodic review records. Refine this section as your practice accumulates direct assessment experience.
Strong evidence looks like. Formal policy referencing this control, technical configurations demonstrating enforcement, periodic review logs with sign-off, and procedures for handling exceptions.
Scoring and POA&M context. 5-point control under the DoD Assessment Methodology. Highest scoring impact — treat as a foundational requirement. Not POA&M-eligible — must be implemented at assessment time.