CMMC Practice SI.1.211
Provide protection from malicious code at appropriate locations within organizational information systems.
Bold Coast Security Guidance
This practice is a basic cyber-security hygiene activity. It is also very simple to comply: select and install an anti-malware software package, write a policy for deploying anti-malware to your devices including how often it should update and scan devices, and have a plan outlining which product you are using and who is responsible for monitoring it.
To measure its effectiveness for Maturity Level 4, your anti-malware software should report to a central console for monitoring and reporting. Some key metrics you can report include keeping up-to-date definitions and recording attacks blocked.
Larger organizations must scan for malware within email and at the network perimeter. Checking for malware at multiple places within the network increases the chance of catching malicious activity.
DRAFT NIST SP 800-171 R2
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 practices to help ensure that software does not perform functions other than the functions intended. NIST SP 800-83 provides guidance on malware incident prevention.