OpenControls Logo

STIG Viewer

STIGViewer Support

The Mainframe Product must block, quarantine, and/or alert system administrators when prohibited mobile code is identified.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-205514SRG-APP-000207-MFP-000278SV-205514r961086_ruleCCI-001662medium
Description
Decisions regarding the employment of mobile code within organizational information systems are based on the potential for the code to cause damage to the system if used maliciously. 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. DoD has defined the corrective actions to be taken, when prohibited mobile code is identified, in DoDI 8552.01, "Use of Mobile Code Technologies in DoD Information Systems". DoD has identified prohibited mobile code in DoDI 8552.01 as: all Category 1X mobile code, unsigned Category 1A mobile code, Category 2 mobile code that violates usage requirements, all Emerging Technologies mobile code (all mobile code technologies, systems, platforms, or languages whose capabilities and threat level have not yet undergone a risk assessment and been assigned to a risk category), and all mobile code that downloads via an email body or email attachment that executes automatically when the user opens the email body or attachment. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed, downloaded, or executed on all endpoints (e.g., servers, workstations, and smart phones). This requirement applies to applications that execute, evaluate, or otherwise process mobile code (e.g., web applications, browsers, and anti-virus applications). Corrective actions when unacceptable mobile code is detected include, for example, blocking, quarantine, or alerting administrators. Blocking includes, for example, preventing transmission of word processing files with embedded macros when such macros have been defined to be unacceptable mobile code.
STIGDate
Mainframe Product Security Requirements Guide2026-05-23

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-205514r961086_chk)

If the Mainframe Product has no function for the use of mobile code, this is not applicable. Examine installation and configuration settings. If the Mainframe Product does not block and/or alert system programmers and security administrators when prohibited mobile code is identified, this is a finding.

Fix Text (F-5780r299776_fix)

Configure the Mainframe Product to block and/or alert system programmers and security administrators when prohibited mobile code is identified.