Prevent Automatic Execution

LOW MODERATE HIGH

1 Overlay 0 Related Controls

Requirements NIST SOURCE

Prevent the automatic execution of mobile code in [software applications] and enforce [actions] prior to executing the code.

Discussion (NIST Supplemental Guidance)

Actions enforced before executing mobile code include prompting users prior to opening email attachments or clicking on web links. Preventing the automatic execution of mobile code includes disabling auto-execute features on system components that employ portable storage devices, such as compact discs, digital versatile discs, and universal serial bus devices.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for SC-18(4) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

software applications in which the automatic execution of mobile code is to be prevented are defined;
actions to be enforced by the system prior to executing mobile code are defined;
the automatic execution of mobile code in <SC-18(04)_ODP[01] software applications> is prevented;
<SC-18(04)_ODP[02] actions> are enforced prior to executing mobile code.

Examine

[SELECT FROM: System and communications protection policy; procedures addressing mobile code; mobile code usage restrictions; mobile code implementation policy and procedures; system design documentation; system configuration settings and associated documentation; list of software applications in which the automatic execution of mobile code must be prohibited; list of actions required before execution of mobile code; system security plan; other relevant documents or records].

Interview

[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; system developer; organizational personnel with responsibilities for managing mobile code].

Test

[SELECT FROM: Mechanisms preventing the automatic execution of unacceptable mobile code; mechanisms enforcing actions to be taken prior to the execution of the mobile code].

Overlays

Showing the OT/ICS overlay for the parent control SC-18 — see the SC-18(4) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

Not applicable at this tier.

MODERATE

Base control: Included (matches standard baseline)

HIGH

Base control: Included (matches standard baseline)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SC-18(4). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

System and communications protection policy
mobile code implementation policy and procedures
system security plan

Configuration

system design documentation
system configuration settings and associated documentation

Testing

Mechanisms preventing the automatic execution of unacceptable mobile code
mechanisms enforcing actions to be taken prior to the execution of the mobile code

Other Records

procedures addressing mobile code
mobile code usage restrictions
list of software applications in which the automatic execution of mobile code must be prohibited
list of actions required before execution of mobile code
other relevant documents or records