EvidenceSheet

IR-8 Incident Response Plan

a. Develop an incident response plan that: 1. Provides the organization with a roadmap for implementing its incident response capability; 2. Describes the structure and organization of the incident response capability; 3. Provides a high-level approach for how the incident response capability fits into the overall organization; 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions; 5. Defines reportable incidents; 6. Provides metrics for measuring the incident response capability within the organization; 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability; 8. Addresses the sharing of incident information; 9. Is reviewed and approved by organization-defined personnel or roles organization-defined frequency; and 10. Explicitly designates responsibility for incident response to organization-defined entities, personnel, or roles. b. Distribute copies of the incident response plan to organization-defined incident response personnel (identified by name and/or by role) and organizational elements; c. Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing; d. Communicate incident response plan changes to organization-defined incident response personnel (identified by name and/or by role) and organizational elements; and e. Protect the incident response plan from unauthorized disclosure and modification.

Source: NIST SP 800-53 Rev 5, IR-8. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

7
artefacts
2
held by a system
0
at each review
moderate
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Records of incident response plan reviews and approvals · Policy repository / GRC workspace
  • Test of Organizational incident response plan and related organizational processes · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Incident response policy · Policy repository / GRC workspace
  • Procedures addressing incident response planning · Policy repository / GRC workspace
  • Incident response plan · Policy repository / GRC workspace
  • System security plan · Policy repository / GRC workspace
  • Privacy plan · Policy repository / GRC workspace

First move

Start with the 2 of 7 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

IR-7(2) Incident Response Assistance | Coordination with External Providers · IR-8(1) Incident Response Plan | Breaches