Rule ID
SV-206883r1137731_rule
Version
V3R4
CCIs
Mobile code is defined as software modules obtained from remote systems, transferred across a network, and then downloaded and executed on a local system without explicit installation or execution by the recipient. Examples of mobile code include JavaScript, VBScript, Java applets, ActiveX controls, Flash animations, Shockwave videos, and macros embedded within Microsoft Office documents. Mobile code can be exploited to attack a host. It can be sent as an e-mail attachment or embedded in other file formats not traditionally associated with executable code. While the IPS cannot replace the antivirus and host-based IDS (HIDS) protection installed on the network's endpoints, vendor or locally created sensor rules can be implemented that provide preemptive defense against both known and zero-day vulnerabilities. Many of the protections may provide defenses before vulnerabilities are discovered and rules or blacklist updates are distributed by antivirus or malicious code solution vendors. To block known prohibited mobile code or approved mobile code that violates permitted usage requirements, the IPS must implement policy filters, rules, signatures, and anomaly analysis.
If the device being reviewed is an IDS, this is not applicable. Verify the IPS blocks any prohibited mobile code at the enclave boundary when it is detected. If the IPS does not block any prohibited mobile code at the enclave boundary when it is detected, this is a finding.
Configure the IPS to block any prohibited mobile code at the enclave boundary when it is detected.