CMMC Requirement SI.L1-B.1.XIII – Malicious Code Protection: Provide protection from malicious code at appropriate locations within organizational information systems.
Links to Publicly Available Resources
AMTSO is the Anti-Malware Testing Standards Organization, a community of over 60 security and testing companies from around the world. This policy template is meant to supplement the CIS Controls v8. The policy statements included within this document can be used by all CIS Implementation Groups (IGs) but are specifically geared toward Safeguards in Implementation Group 1 (IG1). This document provides self-assessment guidance for conducting Cybersecurity Maturity Model Certification (CMMC) assessments for Level 1. This Ransomware Guide includes ransomware prevention best practices and a ransomware response checklist. This on demand course from CISA can assist in training users on how to ensure devices have antivirus and anti-malware protection. This guide from CISA is designed to provides high level information about protecting against malicious code. Learn about antivirus for business, why it's essential, and how it protects your small business against cyberthreats. This guide is intended to provide small and medium-sized organizations with guidance for using Microsoft 365 (M365) to satisfy the Cybersecurity Maturity Model Certification (CMMC) Level 1 requirements. Microsoft Entra ID meets identity-related practice requirements in each Cybersecurity Maturity Model Certification (CMMC) level. To be compliant with requirements in CMMC, it's the responsibility of companies performing work with, and on behalf of, the US Dept. of Defense (DoD) to complete other configurations or processes. In CMMC Level 1, there are three domains that have one or more practices related to identity: Access Control (AC), Identification and Authentication (IA), and System and Information integrity (SI) This blog speaks to the different types of malicious code and how to protect against it. NIST resource that defines the requirements for malicious code protection. This NIST Special Publication provides recommendations for improving an organization’s malware incident prevention measures. In this article, you'll learn how to install and run three different antimalware applications that can help you keep your system free of malicious irritants that make users call you at the least convenient times: chkrootkit, rkhunter, and ClamAV. This sample policy from Sam Houston State University is an example of a policy to reduce risk by protecting against malware. This SANS whitepaper discusses several common practices which, when implemented together, will greatly decrease, and perhaps almost stop malware.
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 – program designed to cause damage, steal information, change data, send email, show messages, or any combination of these things;
- Spyware – program designed to secretly gather information about a person’s activity;
- 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.