← CM-7
CM-7(7) CM · Configuration Management

Code Execution in Protected Environments

LOW MODERATE HIGH
1 Overlay 2 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Allow execution of binary or machine-executable code only in confined physical or virtual machine environments and with the explicit approval of [personnel or roles] when such code is:

Discussion (NIST Supplemental Guidance)

Code execution in protected environments applies to all sources of binary or machine-executable code, including commercial software and firmware and open-source software.

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 CM-7(7) 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. personnel or roles to explicitly approve execution of binary or machine-executable code is/are defined;
  2. the execution of binary or machine-executable code is only allowed in confined physical or virtual machine environments;
  3. the execution of binary or machine-executable code obtained from sources with limited or no warranty is only allowed with the explicit approval of <CM-07(07)_ODP personnel or roles>;
  4. the execution of binary or machine-executable code without the provision of source code is only allowed with the explicit approval of <CM-07(07)_ODP personnel or roles>.

Examine

[SELECT FROM: Configuration management policy; procedures addressing least functionality in the system; configuration management plan; system design documentation; system configuration settings and associated documentation; list or record of binary or machine-executable code; system component inventory; common secure configuration checklists; system audit records; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with responsibilities for approving execution of binary or machine-executable code; organizational personnel with information security responsibilities; organizational personnel with software management responsibilities; system/network administrators; system developers].

Test

[SELECT FROM: Organizational process for approving execution of binary or machine-executable code; organizational process for confining binary or machine-executable code to physical or virtual machine environments; mechanisms supporting and/or implementing the confinement of binary or machine-executable code to physical or virtual machine environments].

Overlays

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

  • Base control: Included (matches standard baseline)

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (5)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (1) (2) (5)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for CM-7(7). 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 security plan

Configuration

  • Configuration management policy
  • configuration management plan
  • system design documentation
  • system configuration settings and associated documentation
  • system component inventory
  • common secure configuration checklists

Testing

  • Organizational process for approving execution of binary or machine-executable code
  • organizational process for confining binary or machine-executable code to physical or virtual machine environments
  • mechanisms supporting and/or implementing the confinement of binary or machine-executable code to physical or virtual machine environments

Other Records

  • procedures addressing least functionality in the system
  • list or record of binary or machine-executable code
  • system audit records
  • other relevant documents or records