mirror of
https://github.com/strongdm/comply
synced 2024-11-22 15:44:55 +00:00
Initial commit of Business Continuity
This commit is contained in:
parent
91f16e4729
commit
8cb7dc7bf8
@ -8,4 +8,89 @@ majorRevisions:
|
|||||||
comment: Initial document
|
comment: Initial document
|
||||||
---
|
---
|
||||||
|
|
||||||
# Coming Soon
|
|
||||||
|
# Purpose and Scope
|
||||||
|
|
||||||
|
a. The purpose of this policy is to ensure that the organization establishes objectives, plans and, procedures such that a major disruption to the organization’s key business activities is minimized.
|
||||||
|
|
||||||
|
a. This policy applies to all infrastructure and data within the organization’s information security program.
|
||||||
|
|
||||||
|
a. This policy applies to all management, employees, and suppliers that are involved in decisions and processes affecting the organization’s business continuity. This policy must be made readily available to all whom it applies to.
|
||||||
|
|
||||||
|
# Background
|
||||||
|
|
||||||
|
a. The success of the organization is reliant upon the preservation of critical business operations and essential functions used to deliver key products and services. The purpose of this policy is to define the criteria for continuing business operations for the organization in the event of a disruption. Specifically, this document defines:
|
||||||
|
|
||||||
|
i. The structure and authority to ensure business resilience of key processes and systems.
|
||||||
|
|
||||||
|
i. The requirements for efforts to manage through a disaster or other disruptive event when the need arises.
|
||||||
|
|
||||||
|
i. The criteria to efficiently and effectively resume normal business operations after a disruption.
|
||||||
|
|
||||||
|
a. Within this document, the following definitions apply:
|
||||||
|
|
||||||
|
i. *Business impact analysis/assessment* - an exercise that determines the impact of losing the support of any resource to an enterprise, establishes the escalation of that loss over time, identifies the minimum resources needed to return to a normal level of operation, and prioritizes recovery of processes and the supporting system.
|
||||||
|
|
||||||
|
i. *Disaster recovery plan* - a set of human, physical, technical, and procedural resources to return to a normal level of operation, within a defined time and cost, when an activity is interrupted by an emergency or disaster.
|
||||||
|
|
||||||
|
i. *Recovery time objective* - the amount of time allowed for the recovery of a business function or resource to a normal level after a disaster or disruption occurs.
|
||||||
|
|
||||||
|
i. *Recovery point objective* - determined based on the acceptable data loss in the case of disruption of operations.
|
||||||
|
|
||||||
|
# Policy
|
||||||
|
|
||||||
|
a. *Business Risk Assessment and Business Impact Analysis*
|
||||||
|
|
||||||
|
i. Each manager is required to perform a business risk assessment and business impact analysis for each key business system within their area of responsibility.
|
||||||
|
|
||||||
|
i. The business risk assessment must identify and define the criticality of key business systems and the repositories that contain the relevant and necessary data for the key business system.
|
||||||
|
|
||||||
|
i. The business risk assessment must define and document the Disaster Recovery Plan (DRP) for their area of responsibility. Each DRP shall include:
|
||||||
|
|
||||||
|
1. Key business processes.
|
||||||
|
|
||||||
|
1. Applicable risk to availability.
|
||||||
|
|
||||||
|
1. Prioritization of recovery.
|
||||||
|
|
||||||
|
1. Recovery Time Objectives (RTOs).
|
||||||
|
|
||||||
|
1. Recovery Point Objectives (RPOs).
|
||||||
|
|
||||||
|
a. *Disaster Recovery Plan*
|
||||||
|
|
||||||
|
i. Each key business system must have a documented DRP to provide guidance when hardware, software, or networks become critically dysfunctional or cease to function (short and long term outages).
|
||||||
|
|
||||||
|
i. Each DRP must include an explanation of the magnitude of information or system unavailability in the event of an outage and the process that would be implemented to continue business operations during the outage. Where feasible, the DRP must consider the use of alternative, off-site computer operations (cold, warm, hot sites).
|
||||||
|
|
||||||
|
i. Each plan must be reviewed against the organization’s strategy, objectives, culture, and ethics, as well as policy, legal, statutory and regulatory requirements.
|
||||||
|
|
||||||
|
i. Each DRP must include:
|
||||||
|
|
||||||
|
1. An emergency mode operations plan for continuing operations in the event of temporary hardware, software, or network outages.
|
||||||
|
|
||||||
|
1. A recovery plan for returning business functions and services to normal on-site operations.
|
||||||
|
|
||||||
|
1. Procedures for periodic testing, review, and revisions of the DRP for all affected business systems, as a group and/or individually.
|
||||||
|
|
||||||
|
a. *Data Backup and Restoration Plans*
|
||||||
|
|
||||||
|
i. Each system owner must implement a data backup and restoration plan.
|
||||||
|
|
||||||
|
i. Each data backup and restoration plan must identify:
|
||||||
|
|
||||||
|
1. The data custodian for the system.
|
||||||
|
|
||||||
|
|
||||||
|
1. The backup schedule of each system.
|
||||||
|
|
||||||
|
|
||||||
|
1. Where backup media is to be stored and secured, as well as how access is maintained.
|
||||||
|
|
||||||
|
1. Who may remove backup media and transfer it to storage.
|
||||||
|
|
||||||
|
1. Appropriate restoration procedures to restore key business system data from backup media to the system.
|
||||||
|
|
||||||
|
1. The restoration testing plan and frequency of testing to confirm the effectiveness of the plan.
|
||||||
|
|
||||||
|
1. The method for restoring encrypted backup media.
|
||||||
|
Loading…
Reference in New Issue
Block a user