Requirement
Provide protection from malicious code at appropriate locations within organizational information systems.
Assessment Objectives
- Designated locations for malicious code protection are identified
- Protection from malicious code at designated locations is provided
Potential Assessment Methods and Objects [NIST SP 800-171A]
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
Discussion [NIST SP 800-171 REV. 2]
Designated [appropriate] 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.
Further Discussion
- Malicious code purposely performs unauthorized activity that undermines the security of an information system. 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 \u2013 program designed to cause damage, steal information, change data, send email, show messages, or any combination of these things;
- Spyware \u2013 program designed to secretly gather information about a person's activity;
- Trojan Horse \u2013 type of malware made to look like legitimate software and used by cyber criminals to get access to a company's systems; and
- Ransomware \u2013 type of malware that threatens to publish the victim's data or perpetually block access to it unless a ransom is paid.
- Consider use of anti-malware tools to stop or lessen the impact of malicious code.
Examples
Example 1
Your company's IT team is buying new computers and wants to protect your company's information from viruses and spyware. The computers will be used to process, store, and transmit FCI. They research anti-malware products, select an appropriate solution, and deploy antivirus software on all hosts for which satisfactory antivirus software is available [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]?
References
- FAR Clause 52.204-21 b.1.xiii
- NIST SP 800-171 Rev. 2 3.14.2
