NIST SP 800-53 SA-4(5) System, Component, and Service Configurations

Requirements NIST SOURCE

Require the developer of the system, system component, or system service to:

Discussion (NIST Supplemental Guidance)

Examples of security configurations include the U.S. Government Configuration Baseline (USGCB), Security Technical Implementation Guides (STIGs), and any limitations on functions, ports, protocols, and services. Security characteristics can include requiring that default passwords have been changed.

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 SA-4(5) 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

security configurations for the system, component, or service are defined;
the developer of the system, system component, or system service is required to deliver the system, component, or service with <SA-04(05)_ODP security configurations> implemented;
the configurations are used as the default for any subsequent system, component, or service reinstallation or upgrade.

Examine

[SELECT FROM: System and services acquisition policy; procedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process; solicitation documents; acquisition documentation; acquisition contracts for the system, system component, or system service; security configurations to be implemented by the developer of the system, system component, or system service; service level agreements; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with acquisition/contracting responsibilities; organizational personnel with the responsibility to determine system security requirements; system developers or service provider; organizational personnel with information security responsibilities].

Test

[SELECT FROM: Mechanisms used to verify that the configuration of the system, component, or service is delivered as specified].

Overlays

Showing the OT/ICS overlay for the parent control SA-4 — see the SA-4(5) 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)
Included: (10)
Added: (12)

MODERATE

Base control: Included (matches standard baseline)
Included: (1) (2) (9) (10)
Added: (12)

HIGH

Base control: Included (matches standard baseline)
Included: (1) (2) (5) (9) (10)
Added: (12)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SA-4(5). 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 services acquisition policy
system security plan

Testing

Mechanisms used to verify that the configuration of the system, component, or service is delivered as specified

Other Records

procedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process
solicitation documents
acquisition documentation
acquisition contracts for the system, system component, or system service
security configurations to be implemented by the developer of the system, system component, or system service
service level agreements
other relevant documents or records