+SI-03 Malicious Code Protection
---+SI-03(04) Updates Only by Privileged Users
---+SI-03(06) Testing and Verification
---+SI-03(08) Detect Unauthorized Commands
---+SI-03(10) Malicious Code Analysis
|
SI-03 Malicious Code Protection
Control
- 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;
- Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures;
- Configure malicious code protection mechanisms to:
- Perform periodic scans of the system [Assignement: 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
- [Selection(one-or-more): block malicious code; quarantine malicious code; take {{ insert: param, si-03_odp.05 }} ] ; and send alert to [Assignement: personnel or roles] in response to malicious code detection; and
- Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system.
Discussion
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.
Assessment Objective
- [Selection(one-or-more): signature-based; non-signature-based] malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code;
- [Selection(one-or-more): signature-based; non-signature-based] malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code;
- malicious code protection mechanisms are updated automatically as new releases are available in accordance with organizational configuration management policy and procedures;
- malicious code protection mechanisms are configured to perform periodic scans of the system [Assignement: frequency];
- malicious code protection mechanisms are configured to perform 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;
- malicious code protection mechanisms are configured to [Selection(one-or-more): block malicious code; quarantine malicious code; take {{ insert: param, si-03_odp.05 }} ] in response to malicious code detection;
- malicious code protection mechanisms are configured to send alerts to [Assignement: personnel or roles] in response to malicious code detection;
- the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system are addressed.
Assessment Method
Examine
System and information integrity policy
system and information integrity procedures
configuration management policy and procedures
procedures addressing malicious code protection
malicious code protection mechanisms
records of malicious code protection updates
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 records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel responsible for malicious code protection
organizational personnel with configuration management responsibilities
1. Přehled
| Název |
Standard |
|
SI-03(04) Updates Only by Privileged Users
|
Control
Update malicious code protection mechanisms only when directed by a privileged user.
Discussion
Protection mechanisms for malicious code are typically categorized as security-related software and, as such, are only updated by organizational personnel with appropriate access privileges.
Assessment Objective
malicious code protection mechanisms are updated only when directed by a privileged user.
Assessment Method
Examine
System and information integrity policy
system and information integrity procedures
procedures addressing malicious code protection
list of privileged users on system
system design documentation
malicious code protection mechanisms
records of malicious code protection updates
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developers
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel responsible for malicious code protection
|
|
SI-03(06) Testing and Verification
|
Control
- Test malicious code protection mechanisms [Assignement: frequency] by introducing known benign code into the system; and
- Verify that the detection of the code and the associated incident reporting occur.
Discussion
None.
Assessment Objective
- malicious code protection mechanisms are tested [Assignement: frequency] by introducing known benign code into the system;
- the detection of (benign test) code occurs;
- the associated incident reporting occurs.
Assessment Method
Examine
System and information integrity policy
system and information integrity procedures
procedures addressing malicious code protection
system design documentation
system configuration settings and associated documentation
test cases
records providing evidence of test cases executed on malicious code protection mechanisms
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel responsible for malicious code protection
|
|
SI-03(08) Detect Unauthorized Commands
|
Control
- Detect the following unauthorized operating system commands through the kernel application programming interface on [Assignement: system hardware components]: [Assignement: unauthorized operating system commands] ; and
- [Selection(one-or-more): issue a warning; audit the command execution; prevent the execution of the command].
Discussion
Detecting unauthorized commands can be applied to critical interfaces other than kernel-based interfaces, including interfaces with virtual machines and privileged applications. Unauthorized operating system commands include commands for kernel functions from system processes that are not trusted to initiate such commands as well as commands for kernel functions that are suspicious even though commands of that type are reasonable for processes to initiate. Organizations can define the malicious commands to be detected by a combination of command types, command classes, or specific instances of commands. Organizations can also define hardware components by component type, component, component location in the network, or a combination thereof. Organizations may select different actions for different types, classes, or instances of malicious commands.
Assessment Objective
- [Assignement: unauthorized operating system commands] are detected through the kernel application programming interface on [Assignement: system hardware components];
- [Selection(one-or-more): issue a warning; audit the command execution; prevent the execution of the command] is/are performed.
Assessment Method
Examine
System and information integrity policy
system and information integrity procedures
procedures addressing malicious code protection
system design documentation
malicious code protection mechanisms
warning messages sent upon the detection of unauthorized operating system command execution
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developers
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel responsible for malicious code protection
|
|
SI-03(10) Malicious Code Analysis
|
Control
- Employ the following tools and techniques to analyze the characteristics and behavior of malicious code: [Assignement: tools and techniques] ; and
- Incorporate the results from malicious code analysis into organizational incident response and flaw remediation processes.
Discussion
The use of malicious code analysis tools provides organizations with a more in-depth understanding of adversary tradecraft (i.e., tactics, techniques, and procedures) and the functionality and purpose of specific instances of malicious code. Understanding the characteristics of malicious code facilitates effective organizational responses to current and future threats. Organizations can conduct malicious code analyses by employing reverse engineering techniques or by monitoring the behavior of executing code.
Assessment Objective
- [Assignement: tools and techniques] are employed to analyze the characteristics and behavior of malicious code;
- the results from malicious code analysis are incorporated into organizational incident response processes;
- the results from malicious code analysis are incorporated into organizational flaw remediation processes.
Assessment Method
Examine
System and information integrity policy
system and information integrity procedures
procedures addressing malicious code protection
procedures addressing incident response
procedures addressing flaw remediation
system design documentation
malicious code protection mechanisms, tools, and techniques
system configuration settings and associated documentation
results from malicious code analyses
records of flaw remediation events resulting from malicious code analyses
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel responsible for malicious code protection
organizational personnel responsible for flaw remediation
organizational personnel responsible for incident response/management
|
1.1 Odkazy
1.2 Identifikované požadavky
1.3 Související regulace
2. Identifikované požadavky
Požadavky
| Zdroj |
Požadavek |
3. Související regulace
Propojené úkoly
|