OpenControls Logo

STIG Viewer

STIGViewer Support

The IPS must block any prohibited mobile code at the enclave boundary when it is detected.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-206883SRG-NET-000229-IDPS-00163SV-206883r1137731_ruleCCI-001662medium
Description
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.
STIGDate
Intrusion Detection and Prevention Systems Security Requirements Guide2025-09-22

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

END-10Mobile Code
0.50
VPM-02Vulnerability Remediation Process
0.50
VPM-04Continuous Vulnerability Remediation Activities
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CM-7Least Functionality
1.00
SC-18(1)Identify Unacceptable Code and Take Corrective Actions
1.00
SC-18(3)Prevent Downloading and Execution
1.00
SC-18(4)Prevent Automatic Execution
1.00
CCI1 mapping
CCI-001662
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

ID.RA-08
0.50
PR.PS-02
0.50

Details

Check Text (C-206883r1137731_chk)

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.

Fix Text (F-7137r1137730_fix)

Configure the IPS to block any prohibited mobile code at the enclave boundary when it is detected.