SI-03 Malicious Code Protection
System and Information Integrity
Description
a. Implement [Selection (one or more): signature based; non-signature based] malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code; b. Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures; c. Configure malicious code protection mechanisms to: 1. Perform periodic scans of the system [Assignment: organization-defined frequency] and real-time scans of files from external sources at [Selection (one or more): endpoint; network entry and exit points] as the files are downloaded, opened, or executed in accordance with organizational policy; and 2. [Selection (one or more): block malicious code; quarantine malicious code; take [Assignment: organization-defined action]]; and send alert to [Assignment: organization-defined personnel or roles] in response to malicious code detection; and d. Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system.
Supplemental Guidance
System entry and exit points 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 also be encoded in various formats 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 by electronic mail, the world-wide web, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Malicious code protection mechanisms include both signature- and nonsignature-based technologies. Nonsignature-based detection mechanisms include artificial intelligence techniques that use heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide controls against such code for which signatures do not yet exist or for which existing signatures may not be effective. Malicious code for which active signatures do not yet exist or may be ineffective includes polymorphic malicious code (i.e., code that changes signatures when it replicates). Nonsignature-based mechanisms also include reputation-based technologies. In addition to the above technologies, pervasive configuration management, comprehensive software integrity controls, and anti-exploitation software may be effective in preventing the execution of unauthorized code. Malicious code may be present in commercial off-the-shelf software as well as custom-built software and could include logic bombs, backdoors, and other types of attacks that could affect organizational mission and business functions. In situations where malicious code cannot be detected by detection methods or technologies, organizations rely on other types of controls, including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to ensure that software does not perform functions other than the functions intended. Organizations may determine that, in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, the detection of malicious downloads, or the detection of maliciousness when attempting to open or execute files.
Changes from Rev 4
Parameter adds '[Selection (one or more): signature based; non-signature based]'; another parameter adds requirement to send an alert to specified personnel Parameter selection eliminates option to send an alert to specified personnel and adds option to take specified action Discussion expanded to explain signature- and non-signature-based technologies Incorporates withdrawn controls SI-03(2) and SI-03(7)
Enhancements (4)
What NIST adds to this control. Select one to read its statement.
SI-03(04) Updates Only by Privileged Users
Update malicious code protection mechanisms only when directed by a privileged user.
SI-03(06) Testing and Verification
a. Test malicious code protection mechanisms [Assignment: organization-defined frequency] by introducing known benign code into the system; and b. Verify that the detection of the code and the associated incident reporting occur.
SI-03(08) Detect Unauthorized Commands
a. Detect the following unauthorized operating system commands through the kernel application programming interface on [Assignment: organization-defined system hardware components]: [Assignment: organization-defined unauthorized operating system commands]; and b. [Selection (one or more): issue a warning; audit the command execution; prevent the execution of the command].
SI-03(10) Malicious Code Analysis
a. Employ the following tools and techniques to analyze the characteristics and behavior of malicious code: [Assignment: organization-defined tools and techniques]; and b. Incorporate the results from malicious code analysis into organizational incident response and flaw remediation processes.
Withdrawn by NIST:
Patterns that use this control (13)
Grouped by the emphasis each pattern gives it.
Critical (2)
Important (10)
- SP-001 Client Module
- SP-002 Server Module
- SP-011 Cloud Computing Pattern
- SP-016 DMZ Module
- SP-023 Industrial Control Systems
- SP-025 Advanced Monitoring and Detection
- SP-026 PCI Full Environment
- SP-027 Secure LLM Usage
- SP-028 Secure DevOps Pipeline Pattern
- SP-048 Offensive AI and Deepfake Defence (draft)
Standard (1)
MITRE ATT&CK Techniques (226)
ATT&CK v16.1Techniques mitigated by this control, mapped via CTID.