← SA-4
SA-4(2) SA · System and Services Acquisition

Design and Implementation Information for Controls

LOW ✓ MODERATE ✓ HIGH
1 Overlay 0 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Require the developer of the system, system component, or system service to provide design and implementation information for the controls that includes: [one of: security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; ] at [level of detail].

Discussion (NIST Supplemental Guidance)

Organizations may require different levels of detail in the documentation for the design and implementation of controls in organizational systems, system components, or system services based on mission and business requirements, requirements for resiliency and trustworthiness, and requirements for analysis and testing. Systems can be partitioned into multiple subsystems. Each subsystem within the system can contain one or more modules. The high-level design for the system is expressed in terms of subsystems and the interfaces between subsystems providing security-relevant functionality. The low-level design for the system is expressed in terms of modules and the interfaces between modules providing security-relevant functionality. Design and implementation documentation can include manufacturer, version, serial number, verification hash signature, software libraries used, date of purchase or download, and the vendor or download source. Source code and hardware schematics are referred to as the implementation representation of the system.

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(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. one or more of the following PARAMETER VALUES is/are selected: {security-relevant external system interfaces; high-level design; low-level design; source code or hardware schematics; <SA-04(02)_ODP[02] design and implementation information>};
  2. design and implementation information is defined (if selected);
  3. level of detail is defined;
  4. the developer of the system, system component, or system service is required to provide design and implementation information for the controls that includes using <SA-04(02)_ODP[01] SELECTED PARAMETER VALUES> at <SA-04(02)_ODP[03] level of detail>.

Examine

[SELECT FROM: System and services acquisition policy; system and services acquisition procedures; procedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process; solicitation documents; acquisition documentation; acquisition contracts for the system, system components, or system services; design and implementation information for controls employed in the system, system component, or system service; 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: Organizational processes for determining the level of detail for system design and controls; organizational processes for developing acquisition contracts; mechanisms supporting and/or implementing the development of system design details].

Overlays

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

  • 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(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 services acquisition policy
  • system security plan

Testing

  • Organizational processes for determining the level of detail for system design and controls
  • organizational processes for developing acquisition contracts
  • mechanisms supporting and/or implementing the development of system design details

Other Records

  • system and services acquisition procedures
  • procedures addressing the integration of security requirements, descriptions, and criteria into the acquisition process
  • solicitation documents
  • acquisition documentation
  • acquisition contracts for the system, system components, or system services
  • design and implementation information for controls employed in the system, system component, or system service
  • other relevant documents or records