Identify Unacceptable Code and Take Corrective Actions

LOW MODERATE HIGH

1 Overlay 0 Related Controls

Requirements NIST SOURCE

Identify [unacceptable mobile code] and take [corrective actions].

Discussion (NIST Supplemental Guidance)

Corrective actions when unacceptable mobile code is detected include blocking, quarantine, or alerting administrators. Blocking includes preventing the transmission of word processing files with embedded macros when such macros have been determined to be unacceptable mobile code.

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(1) 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

unacceptable mobile code to be identified is defined;
corrective actions to be taken when unacceptable mobile code is identified are defined;
<SC-18(01)_ODP[01] unacceptable mobile code> is identified;
<SC-18(01)_ODP[02] corrective actions> are taken if unacceptable mobile code is identified.

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 unacceptable mobile code; list of corrective actions to be taken when unacceptable mobile code is identified; system monitoring records; system audit records; 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 supporting and/or implementing mobile code detection, inspection, and corrective capabilities].

Overlays

Showing the OT/ICS overlay for the parent control SC-18 — see the SC-18(1) 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(1). 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 supporting and/or implementing mobile code detection, inspection, and corrective capabilities

Other Records

procedures addressing mobile code
mobile code usage restrictions
list of unacceptable mobile code
list of corrective actions to be taken when unacceptable mobile code is identified
system monitoring records
system audit records
other relevant documents or records