SC-18: Mobile Code

CSF v1.1 References:

Baselines:

  • Low

    N/A

  • Moderate
    • SC-18
  • High
    • SC-18
  • Privacy

    N/A

Previous Version:

Control Statement

  1. Define acceptable and unacceptable mobile code and mobile code technologies; and
  2. Authorize, monitor, and control the use of mobile code within the system.

Supplemental Guidance

Mobile code includes any program, application, or content that can be transmitted across a network (e.g., embedded in an email, document, or website) and executed on a remote system. Decisions regarding the use of mobile code within organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include Java applets, JavaScript, HTML5, WebGL, and VBScript. Usage restrictions and implementation guidelines apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices, including notebook computers and smart phones. Mobile code policy and procedures address specific actions taken to prevent the development, acquisition, and introduction of unacceptable mobile code within organizational systems, including requiring mobile code to be digitally signed by a trusted source.

Control Enhancements

SC-18(2): Acquisition, Development, and Use

Baseline(s):

(Not part of any baseline)

Verify that the acquisition, development, and use of mobile code to be deployed in the system meets [Assignment: organization-defined mobile code requirements].

SC-18(4): Prevent Automatic Execution

Baseline(s):

(Not part of any baseline)

Prevent the automatic execution of mobile code in [Assignment: organization-defined software applications] and enforce [Assignment: organization-defined actions] prior to executing the code.