← SC-18

Acquisition, Development, and Use

LOW MODERATE HIGH
1 Overlay 0 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

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

Discussion (NIST Supplemental Guidance)

None.

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

  1. mobile code requirements for the acquisition, development, and use of mobile code to be deployed in the system are defined;
  2. the acquisition of mobile code to be deployed in the system meets <SC-18(02)_ODP mobile code requirements>;
  3. the development of mobile code to be deployed in the system meets <SC-18(02)_ODP mobile code requirements>;
  4. the use of mobile code to be deployed in the system meets <SC-18(02)_ODP mobile code requirements>.

Examine

[SELECT FROM: System and communications protection policy; procedures addressing mobile code; mobile code requirements; mobile code usage restrictions; mobile code implementation policy and procedures; acquisition documentation; acquisition contracts for system, system component, or system service; system development life cycle documentation; system security plan; other relevant documents or records].

Interview

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

Test

[SELECT FROM: Organizational processes for the acquisition, development, and use of mobile code].

Overlays

Showing the OT/ICS overlay for the parent control SC-18 — see the SC-18(2) 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(2). 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

Testing

  • Organizational processes for the acquisition, development, and use of mobile code

Other Records

  • procedures addressing mobile code
  • mobile code requirements
  • mobile code usage restrictions
  • acquisition documentation
  • acquisition contracts for system, system component, or system service
  • system development life cycle documentation
  • other relevant documents or records