CMMC Practice Number: SI.L1-3.14.4
CMMC Level: 1 CMMC Domain: System and Information Integrity (SI)
Practice Summary:
Update malicious code protection mechanisms when new releases are available.
Contents:
CMMC Practice Implementation |
Assessment Objectives
Determine if:
[a] malicious code protection mechanisms are updated when new releases are available.
Practice Clarification (DOD, CMU)
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 [a].
Example
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].
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]?
Where To Look
- 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
- system 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
Who To Talk To
- 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
Perform Test On
- 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
Additional Information
Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using steganography.
Malicious code can be transported by different means including web accesses, electronic mail, electronic mail attachments, and portable storage devices.
Malicious code insertions occur through the exploitation of information 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 company business functions.
Traditional malicious code protection mechanisms cannot always detect such code. In these situations, companies should 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 those intended. Companies may determine that in response to the detection of malicious code, different actions may be warranted. For example, companies can define actions in response to malicious code detection during periodic scans, actions in response to detection of malicious downloads, and/ or actions in response to detection of maliciousness when attempting to open or execute files.
CMMC Practice Background and References (DOD, CMU) |
Practice Discussion:
DISCUSSION FROM SOURCE: NIST SP 800-171 R2
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.
CMMC References:
· FAR Clause 52.204-21 b.1.xiv
· NIST SP 800-171 Rev 1 3.14.4
· CIS Controls v7.1 8.2
· NIST CSF v1.1 DE.CM-4
· CERT RMM v1.2 VAR:SG3.SP1
· NIST SP 800-53 Rev 4 SI-3