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

Incident Response Plan

LOW MODERATE HIGH
1 Overlay 1 Related Control
Graph
Export ▾

Requirements NIST SOURCE

Require the developer of the system, system component, or system service to provide, implement, and test an incident response plan.

Discussion (NIST Supplemental Guidance)

The incident response plan provided by developers may provide information not readily available to organizations and be incorporated into organizational incident response plans. Developer information may also be extremely helpful, such as when organizations respond to vulnerabilities in commercial off-the-shelf products.

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(10) 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 an incident response plan;
  2. the developer of the system, system component, or system service is required to implement an incident response plan;
  3. the developer of the system, system component, or system service is required to test an incident response plan.

Examine

[SELECT FROM: System and services acquisition policy; procedures addressing incident response, standards, and tools; solicitation documentation; acquisition documentation; service level agreements; acquisition contracts for the system, system components or services; acquisition documentation; solicitation documentation; service level agreements; developer incident response plan; system security plan; privacy plan; supply chain risk management 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; organizational personnel with supply chain risk management responsibilities].

Overlays

Showing the OT/ICS overlay for the parent control SA-15 — see the SA-15(10) 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(10). 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
  • developer incident response plan
  • system security plan
  • privacy plan
  • supply chain risk management plan

Other Records

  • procedures addressing incident response, standards, and tools
  • solicitation documentation
  • acquisition documentation
  • service level agreements
  • acquisition contracts for the system, system components or services
  • other relevant documents or records