SI.L2-3.14.2 · NIST SP 800-171 3.14.2

Malicious Code Protection

Provide protection from malicious code at designated locations within organizational systems.

5 points if not metMust be fully met, cannot POA&M2 assessment objectives

What an assessor scores, the objectives

SI.L2-3.14.2 is met only when every one of these 2 objectives, from NIST SP 800-171A, is satisfied. A single missed objective makes the whole requirement not met.

  • a.designated locations for malicious code protection are identified
  • b.protection from malicious code at designated locations is provided

How a C3PAO checks it

NIST SP 800-171A defines three assessment methods. For SI.L2-3.14.2, an assessor uses these:

Examine

System and information integrity policy; configuration management policy and procedures; procedures addressing malicious code protection; records of malicious code protection updates; malicious code protection mechanisms; system security plan; system configuration settings and associated documentation; record of actions initiated by malicious code protection mechanisms in response to malicious code detection; scan results from malicious code protection mechanisms; system design documentation; system audit logs and records; other relevant documents or records

Interview

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

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 employing, updating, and configuring malicious code protection mechanisms; mechanisms supporting or implementing malicious code scanning and subsequent actions

What it means, in context

Designated locations include system entry and exit points which may include firewalls, remote access servers, workstations , electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. Malicious code protection mechanisms include anti- virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom -built software. This could include logic bombs, back doors, and other types of cyber -attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring technologies to help ensure that software does not perform functions oth er than the functions intended. NIST SP 800-83 provides guidance on malware incident prevention.

A designated location may be a network device such as a firewall or an end user’s computer. Malicious code, which can be delivered by a range of means (e.g., email, removable media, or websites), includes the following: • virus – program designed to damage, steal information, change data, send email, show messages, or any combination of these things; • spyware – program designed to gather information about a person ’s activity in secret when they click on a link, usually installed without the person knowing ; • trojan horse – type of malware made to look like legitimate software and used by cyber criminals to get access to a company’s systems; and • ransomware – type of malware that threatens to publish the victim’s data or perpetually block access to it unless a ransom is paid. Use anti-malware tools to stop or lessen the impact of malicious code. Example You are buying a new computer and want to protect your company ’s information from viruses, spyware, etc. You buy and install anti-malware software [a,b]. Potential Assessment Considerations • Are system components (e.g., workstations, servers, email gateways, mobile devices) for which malicious code protection must be provided identified and documented [a]?

What passing evidence looks like

Malicious code protection at the designated locations: antivirus active on every endpoint and the mail filtering at the gateway, shown from the management console.

Common ways contractors fail SI.L2-3.14.2

  • !Designated locations means you name where protection sits (endpoints, email, boundary). Defender on endpoints plus Exchange Online Protection on mail covers the classic pair; show both.

The step by step walkthrough for Microsoft 365 GCC High, Google Workspace, and on premises setups, plus the exact evidence to capture, lives inside the Level 2 Accelerator.

Prove SI.L2-3.14.2, and the other 109

The Level 2 Accelerator walks all 110 requirements with you, generates your SSP, POA&M, and Audit Room from real evidence, includes the full Level 1 platform, and puts a credentialed officer alongside you for 180 days. Filed in 180 days, or we work free until you are.

No credit card. Phase 2 begins Nov 10, 2026, when applicable DoD solicitations start requiring a current Level 2 status to win the award.

SI.L2-3.14.2 questions, answered

How many points is CMMC requirement SI.L2-3.14.2 worth?+

SI.L2-3.14.2 is worth 5 points in the CMMC Level 2 score under 32 CFR 170.24. If it is not met, you lose 5 from your total of 110.

Can SI.L2-3.14.2 be placed on a POA&M?+

No. SI.L2-3.14.2 must be fully met before you can file. It cannot be deferred to a POA&M, so it is a gate on your assessment.

What family does SI.L2-3.14.2 belong to?+

SI.L2-3.14.2 is in the System & Information Integrity (SI) family, one of the 14 families of NIST SP 800-171 that make up CMMC Level 2.

Key references
  • NIST SP 800-171 Rev. 2 3.14.2
  • FAR Clause 52.204-21 b.1.xiii