← SA-4

Functional Properties of 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 a description of the functional properties of the controls to be implemented.

Discussion (NIST Supplemental Guidance)

Functional properties of security and privacy controls describe the functionality (i.e., security or privacy capability, functions, or mechanisms) visible at the interfaces of the controls and specifically exclude functionality and data structures internal to the operation of the controls.

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

  1. the developer of the system, system component, or system service is required to provide a description of the functional properties of the controls to be implemented.

Examine

[SELECT FROM: System and services acquisition policy; system and services acquisition procedures; procedures addressing the integration of security and privacy requirements, descriptions, and criteria into the acquisition process; solicitation documents; acquisition documentation; acquisition contracts for the system, system component, or system services; system security plan; privacy plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with acquisition/contracting responsibilities; organizational personnel with information security and privacy responsibilities; system developers].

Test

[SELECT FROM: Organizational processes for determining system security functional requirements; organizational processes for developing acquisition contracts; mechanisms supporting and/or implementing acquisitions and the inclusion of security and privacy requirements in contracts].

Overlays

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

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

Testing

  • Organizational processes for determining system security functional requirements
  • organizational processes for developing acquisition contracts
  • mechanisms supporting and/or implementing acquisitions and the inclusion of security and privacy requirements in contracts

Other Records

  • system and services acquisition procedures
  • procedures addressing the integration of security and privacy requirements, descriptions, and criteria into the acquisition process
  • solicitation documents
  • acquisition documentation
  • acquisition contracts for the system, system component, or system services
  • other relevant documents or records