Share

Sign In

Lose something?

Enter Username or Email to reset.

Sign Up

Painted Brain | Disaster Recovery Policy and Plan
We're bridging communities and changing the conversation about mental illness using arts and media.
page-template-default page page-id-9185 page-child parent-pageid-118 _masterslider _msp_version_3.2.2 woocommerce-no-js logo_left full-width full-width cp_hero_visible disaster-recovery-policy-and-plan cp_fixed none cpcustomizer_off megamenu no-header no-header unknown_browser cp_breadcrumbs_hidden opensignal dark_menu_background wpb-js-composer js-comp-ver-5.7 vc_responsive
Disaster Recovery Policy and Plan

Free Use Disclaimer: This policy was created by or for the SANS Institute for the Internet community. All or parts of this policy can be freely used for your organization. There is no prior approval required. If you would like to contribute a new policy or updated version of this policy, please send email to policy-resources@sans.org.

Last Update Status: Updated August 14, 2019

1. Overview Since disasters happen so rarely, management often ignores the disaster recovery planning process. It is important to realize that having a contingency plan in the event of a disaster gives a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions. Any event that could likely cause an extended delay of service should be considered. The Disaster Recovery Plan is often part of the Business Continuity Plan.

  1. Purpose

This policy defines the requirement for a baseline disaster recovery plan to be developed and implemented by that will describe the process to recover IT Systems, Applications and Data from any type of disaster that causes a major outage.

3. Scope This policy is directed to the IT Management Staff who is accountable to ensure the plan is developed, tested and kept up-to-date. This policy is solely to state the requirement to have a disaster recovery plan, it does not provide requirement around what goes into the plan or sub plans. 

Contingency Plans 

The following contingency plans must be created: 

Computer Emergency Response Plan:

Who is to be contacted, when, and how?

What immediate actions must be taken in the event of certain occurrences?

Succession Plan:

Describe the flow of responsibility when normal staff is unavailable to perform their duties. 

Data Study:

Detail the data stored on the systems, its criticality, and its confidentiality. 

Criticality of Service List:

List all the services provided and their order of importance. It also explains the order of recovery in both short-term and long-term timeframes.

Data Backup and Restoration Plan:

Detail which data is backed up, the media to which it is saved, where that media is stored, and how often the backup is done. It should also describe how that data could be recovered.

Equipment Replacement Plan:

Describe what equipment is required to begin to provide services, list the order in which it is necessary, and note where to purchase the equipment.

Mass Media Management: 

Who is in charge of giving information to the mass media?

The plan, at a minimum, should be reviewed an updated on an annual basis.

Also provide some guidelines on what data is appropriate to be provided.

After creating the plans, it is important to practice them to the extent possible.

Management should set aside time to test implementation of the disaster recovery plan.

Tabletop exercises should be conducted annually. During these tests, issues that may cause the plan to fail can be discovered and corrected in an environment that has few consequences.

Policy Compliance: 

Compliance Measurement:

The Infosec team will verify compliance to this policy through various methods, including but not limited to, periodic walk-thrus, video monitoring, business tool reports, internal and external audits, and feedback to the policy owner. 

Exceptions

Any exception to the policy must be approved by the Admin and Infosec Team in advance

Non-Compliance

An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment