Recovery is the incident-response activity that returns affected systems to normal operation, usually their pre-incident state. It also includes lasting security measures to help prevent the same kind of incident from happening again. section 5.3.3 section 5.9
Recovery follows two earlier steps:
- Containment limits damage and stops the incident from spreading, sometimes by disconnecting a device or disabling an account. section 5.3.3
- Eradication removes the threat or repairs the root cause. section 5.3.3
- Recovery restores normal operation and applies measures against recurrence. section 5.3.3
Before cleaning, restoring, or rebuilding a compromised system, preserve useful evidence such as logs, malware samples, and system snapshots. An incident response plan can assign responsibilities and set out procedures for each phase. section 5.3.3 section 5.4
A malware-infected device
An incident response team might first disconnect the device to limit the infection, then remove the threat. Recovery brings the affected system back into service and adds security measures intended to prevent a similar incident. section 5.3.3
Recovery also matters after a system failure or data corruption. A disaster recovery plan may use redundant systems and backups to restore configurations and data to a last known reliable state. Recovery Time Objective and Recovery Point Objective express acceptable downtime and data loss, helping guide those choices. section 7.2 section 7.6 section 7.1









