Security Requirements for 03.14.04 Update Malicious Code Protection
Malicious code protection mechanisms include anti-virus signature definitions and reputationbased 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.
Assessment GuidanceExamine 0/12
How an assessor determines this requirement is met. Source: CMMC Assessment Guide – Level 2, Version 2.13 (NIST SP 800-171 Rev. 2).
Discussion
Malware changes on an hourly or daily basis, and it is important to update detection and protection mechanisms frequently to maintain the effectiveness of the protection.
Examples
- Example 1
You have installed anti-malware software to protect a computer 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].
Assessment Methods
Not all of the evidence listed is required to meet this requirement — check the items your organization has collected.
- 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
- 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
Potential Assessment Considerations
- Is there a defined frequency by which malicious code protection mechanisms must be updated (e.g., frequency of automatic updates or manual processes) [a]?