← SA-15
SA-15(1) SA · System and Services Acquisition

Quality Metrics

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:

Discussion (NIST Supplemental Guidance)

Organizations use quality metrics to establish acceptable levels of system quality. Metrics can include quality gates, which are collections of completion criteria or sufficiency standards that represent the satisfactory execution of specific phases of the system development project. For example, a quality gate may require the elimination of all compiler warnings or a determination that such warnings have no impact on the effectiveness of required security or privacy capabilities. During the execution phases of development projects, quality gates provide clear, unambiguous indications of progress. Other metrics apply to the entire development project. Metrics can include defining the severity thresholds of vulnerabilities in accordance with organizational risk tolerance, such as requiring no known vulnerabilities in the delivered system with a Common Vulnerability Scoring System (CVSS) severity of medium or high.

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-15(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. one or more of the following PARAMETER VALUES is/are selected: { <SA-15(01)_ODP[02] frequency>; <SA-15(01)_ODP[03] program review>; upon delivery};
  2. frequency at which to provide evidence of meeting the quality metrics is defined (if selected);
  3. program review milestones are defined (if selected);
  4. the developer of the system, system component, or system service is required to define quality metrics at the beginning of the development process;
  5. the developer of the system, system component, or system service is required to provide evidence of meeting the quality metrics <SA-15(01)_ODP[01] SELECTED PARAMETER VALUES>.

Examine

[SELECT FROM: System and services acquisition policy; procedures addressing development process, standards, and tools; procedures addressing the integration of security requirements into the acquisition process; solicitation documentation; acquisition documentation; service level agreements; acquisition contracts for the system, system component, or system service; list of quality metrics; documentation evidence of meeting quality metrics; system security plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with system and service acquisition responsibilities; organizational personnel with information security responsibilities; system developer].

Overlays

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

Not applicable at this tier.

MODERATE

  • Base control: Included (matches standard baseline)
  • Included: (3)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (3)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SA-15(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

Other Records

  • procedures addressing development process, standards, and tools
  • procedures addressing the integration of security requirements into the acquisition process
  • solicitation documentation
  • acquisition documentation
  • service level agreements
  • acquisition contracts for the system, system component, or system service
  • list of quality metrics
  • documentation evidence of meeting quality metrics
  • other relevant documents or records