Document the essential processes to be recovered.
Essential processes to be recovered
|
Recovery Time Objective
At what point in time do you need the process running again?
|
Name and role of individual(s) responsible for recovery
|
Recovery location
|
1
|
|
|
|
|
2
|
|
|
|
|
3
|
|
|
|
|
4
|
|
|
|
|
5
|
|
|
|
|
6
|
|
|
|
|
Document any equipment or network services that are necessary to carry out essential processes in the event of a disaster or disruption.
PRIMARY
|
BACKUP/SECONDARY
|
Equipment/Network
|
Location
|
Equipment/Network
|
Location
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Document recovery requirements and dependencies.
Using the numbers to identify your process, document the requirements for each process to be recovered (i.e., Information systems, data, applications, security access, vendor support, manuals or instruction resources). In the Dependencies column, indicate who or what other processes may be on the process recovery to be completed. This will assist in prioritizing recovery activities when planning for and responding to an incident.
Requirements
|
Dependencies
|
1
|
|
|
2
|
|
|
3
|
|
|
4
|
|
|
5
|
|
|
6
|
|
|
Document recovery action items for each process.
For each process there will be a series of actions required for the recovery. It may not be the individual normally responsible for the process who is involved in the recovery, so it is important to describe in detail the steps involved. Providing an estimated time for actions to be completed will support planning and help set realistic expectations for recovery. Expand the tables as necessary to complete the actions for each process. Following a test or actual incident, review recovery procedures and update your plan based on lessons learned
Action
|
Estimated time
|
|
|
|
|
|
|
|
|
|
|
|
|
Action
|
Estimated time
|
|
|
|
|
|
|
|
|
|
|
|
|