Disaster Recovery Policy

March 2019 Contents

1. Background
2. Policy
3. Appendix A: Relevant Points of Contact
4. Appendix B: Recovery Steps for Information Systems Infrastructure & Services

Table 1: Control satisfaction

Table 2: Document history

1. The purpose of this policy is to define the organization’s procedures to recover Information Technology (IT) infrastructure and IT services within set deadlines in the case of a disaster or other disruptive incident. The objective of this plan is to complete the recovery of IT infrastructure and IT services within a set Recovery Time Objective (RTO).
2. This policy includes all resources and processes necessary for service and data recovery, and covers all information security aspects of business continuity management.
3. This policy applies to all management, employees and suppliers that are involved in the recovery of IT infrastructure and services within the organization. This policy must be made readily available to all whom it applies to.

1. This policy defines the overall disaster recovery strategy for the organization. The strategy describes the organization’s Recovery Time Objective (RTO), which is defined as the duration of time and service level for critical business processes to be restored after a disaster or other disruptive event, as well as the procedures, responsibility and technical guidance required to meet the RTO. This policy also lists the contact information for personnel and service providers that may be needed during a disaster recovery event.
2. The following conditions must be met for this plan to be viable:
   1. All equipment, software and data (or their backups/failovers) are available in some manner.
   2. If an incident takes place at the organization’s physical location, all resources involved in recovery efforts are able to be transferred to an alternate work site (such as their home office) to complete their duties.
   3. The Information Security Officer is responsible for coordinating and conducting a bi-annual (at least) rehearsal of this continuity plan.
3. This plan does not cover the following types of incidents:
   1. Incidents that affect customers or partners but have no effect on the organization’s systems; in this case, the customer must employ their own continuity processes to make sure that they can continue to interact with the organization and its systems.
   2. Incidents that affect cloud infrastructure suppliers at the core infrastructure level, including but not limited to Google, Heroku, and Amazon Web Services. The organization depends on such suppliers to employ their own continuity processes.

1. Relocation
   1. If the organization’s primary work site is unavailable, an alternate work site shall be used by designated personnel. The organization’s alternate work site is located at [list the address of the alternate work site that the organization will use].
   2. The personnel required to report to the alternate work site during a disaster includes [list the personnel titles responsible for reporting to the alternate work site].
2. Critical Services, Key Tasks and, Service Level Agreements (SLAs)
   1. The following services and technologies are considered to be critical for business operations, and must immediately be restored (in priority order):
      1. [list the critical services and technologies that must remain running during a disaster]
   2. The following key tasks and SLAs must be considered during a disaster recovery event, in accordance with the organization’s objectives, agreements, and legal, contractual or regulatory obligations:
      1. [list of key tasks / SLAs that must be kept operational, with respective deadlines]
3. The organization’s Recovery Time Objective (RTO) is [set the maximum amount of time before critical processes must be restored, to include relocation and getting critical services/technologies back online]. Relocation and restoration of critical services and technologies must be completed within this time period.
4. Notification of Plan Initiation
   1. The following personnel must be notified when this plan is initiated:
      1. [list all personnel (including titles) that must be notified of plan initiation ]
   2. [person responsible for notifications, including title] is responsible for notifying the personnel listed above.
5. Plan Deactivation
   1. This plan must only be deactivated by [person or persons with authority to deactivate the plan, including job title].
   2. In order for this plan to be deactivated, all relocation activities and critical service / technology tasks as detailed above must be fully completed and/or restored. If the organization is still operating in an impaired scenario, the plan may still be kept active at the discretion of [person or persons with authority to deactivate the plan, including job title].
   3. The following personnel must be notified when this plan is deactivated:
      1. [list all personnel (including titles) that must be notified of plan activation]
6. The organization must endeavor to restore its normal level of business operations as soon as possible.
7. A list of relevant points of contact both internal and external to the organization is enclosed in Appendix A.
8. During a crisis, it is vital for certain recovery tasks to be performed right away. The following actions are pre-authorized in the event of a disaster recovery event:
   1. [job title] must take all steps specified in this disaster recovery plan in order to recover the organization’s information technology infrastructure and services.
   2. [job title] is authorized to make urgent purchases of equipment and services up to [amount].
   3. [job title] is authorized to communicate with clients.
   4. [job title] is authorized to communicate with the public.
   5. [job title] is authorized to communicate with public authorities such as state and local governments and law enforcement.
   6. [job title] is authorized to cooperate with [name of supplier/ outsourcing partner].
   7. [add/modify/remove authorizations in this section as necessary]
9. Specific recovery steps for information systems infrastructure and services are provided in Appendix B.

Internal Contacts

External Contacts

Systems Infrastructure & Services

Specific recovery procedures are described in detail below: