Incident Response Plan

✓ LOW ✓ MODERATE ✓ HIGH
1 Enhancement 1 Overlay 11 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

    1. 1.Provides the organization with a roadmap for implementing its incident response capability;
    2. 2.Describes the structure and organization of the incident response capability;
    3. 3.Provides a high-level approach for how the incident response capability fits into the overall organization;
    4. 4.Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;
    5. 5.Defines reportable incidents;
    6. 6.Provides metrics for measuring the incident response capability within the organization;
    7. 7.Defines the resources and management support needed to effectively maintain and mature an incident response capability;
    8. 8.Addresses the sharing of incident information;
    9. 9.Is reviewed and approved by [personnel or roles][frequency] ; and
    10. 10.Explicitly designates responsibility for incident response to [entities, personnel, or roles].
Discussion (NIST Supplemental Guidance)

It is important that organizations develop and implement a coordinated approach to incident response. Organizational mission and business functions determine the structure of incident response capabilities. As part of the incident response capabilities, organizations consider the coordination and sharing of information with external organizations, including external service providers and other organizations involved in the supply chain. For incidents involving personally identifiable information (i.e., breaches), include a process to determine whether notice to oversight organizations or affected individuals is appropriate and provide that notice accordingly.

Enhancements NIST SOURCE

IR-8(1) Breaches LOW MODERATE HIGH

Include the following in the Incident Response Plan for breaches involving personally identifiable information:

  1. (a) A process to determine if notice to individuals or other organizations, including oversight organizations, is needed;
  2. (b) An assessment process to determine the extent of the harm, embarrassment, inconvenience, or unfairness to affected individuals and any mechanisms to mitigate such harms; and
  3. (c) Identification of applicable privacy requirements.
Discussion

Organizations may be required by law, regulation, or policy to follow specific procedures relating to breaches, including notice to individuals, affected organizations, and oversight bodies; standards of harm; and mitigation or other specific requirements.

Open full page for IR-8(1) →

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 IR-8 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. personnel or roles that review and approve the incident response plan is/are identified;
  2. the frequency at which to review and approve the incident response plan is defined;
  3. entities, personnel, or roles with designated responsibility for incident response are defined;
  4. incident response personnel (identified by name and/or by role) to whom copies of the incident response plan are to be distributed is/are defined;
  5. organizational elements to which copies of the incident response plan are to be distributed are defined;
  6. incident response personnel (identified by name and/or by role) to whom changes to the incident response plan is/are communicated are defined;
  7. organizational elements to which changes to the incident response plan are communicated are defined;
  8. an incident response plan is developed that provides the organization with a roadmap for implementing its incident response capability;
  9. an incident response plan is developed that describes the structure and organization of the incident response capability;
  10. an incident response plan is developed that provides a high-level approach for how the incident response capability fits into the overall organization;
  11. an incident response plan is developed that meets the unique requirements of the organization with regard to mission, size, structure, and functions;
  12. an incident response plan is developed that defines reportable incidents;
  13. an incident response plan is developed that provides metrics for measuring the incident response capability within the organization;
  14. an incident response plan is developed that defines the resources and management support needed to effectively maintain and mature an incident response capability;
  15. an incident response plan is developed that addresses the sharing of incident information;
  16. an incident response plan is developed that is reviewed and approved by <IR-08_ODP[01] personnel or roles> <IR-08_ODP[02] frequency>;
  17. an incident response plan is developed that explicitly designates responsibility for incident response to <IR-08_ODP[03] entities, personnel, or roles>.
  18. copies of the incident response plan are distributed to <IR-08_ODP[04] incident response personnel>;
  19. copies of the incident response plan are distributed to <IR-08_ODP[05] organizational elements>;
  20. the incident response plan is updated to address system and organizational changes or problems encountered during plan implementation, execution, or testing;
  21. incident response plan changes are communicated to <IR-08_ODP[06] incident response personnel>;
  22. incident response plan changes are communicated to <IR-08_ODP[07] organizational elements>;
  23. the incident response plan is protected from unauthorized disclosure;
  24. the incident response plan is protected from unauthorized modification.

Examine

[SELECT FROM: Incident response policy; procedures addressing incident response planning; incident response plan; system security plan; privacy plan; records of incident response plan reviews and approvals; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with incident response planning responsibilities; organizational personnel with information security and privacy responsibilities].

Test

[SELECT FROM: Organizational incident response plan and related organizational processes].

Overlays

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)

MODERATE

  • Base control: Included (matches standard baseline)

HIGH

  • Base control: Included (matches standard baseline)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for IR-8. 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

  • Incident response policy
  • incident response plan
  • system security plan
  • privacy plan
  • records of incident response plan reviews and approvals

Testing

  • Organizational incident response plan and related organizational processes

Other Records

  • procedures addressing incident response planning
  • other relevant documents or records