Key concepts
The guide shows how ranking critical resources supports realistic recovery plans and tests, how to turn lessons from your own and others' events into improvements, and how to build playbooks. It references CSF 1.1-era categories and SP 800-53 Rev. 4 controls, but the method still applies.
How it is organized
- Planning for cyber event recovery
- Continuous improvement
- Recovery metrics
- Building the playbook
- Example: data breach recovery
- Example: destructive malware recovery
- Appendix: playbook elements checklist
What a school district should take from it
- Recovery communications (staff, families, board, media) need owners and drafts before an event.
- Each incident or exercise should produce at least one improvement.
How to use it in your district
- Use the playbook checklist to draft recovery steps for your most critical system.
- Prepare template messages for families and staff for an outage or data breach.
- After each exercise or incident, record lessons and assign improvements in the Improvement plan.
Common misconceptions
- Recovery ends when systems are back online.
- It also includes restoring trust, communicating and fixing the weaknesses that allowed the event.
Rubric categories and K12 Cyber Forward tools
Cybersecurity Rubric 2.0 categories
- RC.RPIncident Recovery Plan Execution
- RC.COIncident Recovery Communication
- ID.IMImprovement
Tools in the program portal
- Tabletop exercisesRun a scenario and capture after-action improvements
- Improvement planGive each gap an owner, a date and a first step
- Incident DeskDeclare an incident and track reporting clocks
- Guide: Ransomware tabletop checklist for a school dayPublic guide
Related publications
- SP 800-61 Rev. 3Incident response
- SP 800-34 Rev. 1Contingency planning
Citation and source
SP 800-184, Guide for Cybersecurity Event Recovery. National Institute of Standards and Technology. 2016. https://doi.org/10.6028/NIST.SP.800-184.
Topics: Recovery and continuity, Incident response. This summary was written by the K12 Cyber Forward program team in its own words. NIST is not affiliated with the program and has not reviewed it. The official publication on csrc.nist.gov controls.