CP – Contingency Planning
NIST SP 800-53 Rev. 5 – CP – Contingency Planning
1.Kravtext (engelskt original)#
CP-1 – Policy and Procedures#
- a. Develop, document, and disseminate to [organization-defined personnel or roles]:
- [organization-level or mission/business process-level or system-level] contingency planning policy that:
- (a) Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- (b) Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- Procedures to facilitate the implementation of the contingency planning policy and the associated contingency planning controls;
- b. Designate an [organization-defined official] to manage the development, documentation, and dissemination of the contingency planning policy and procedures; and
- c. Review and update the current contingency planning:
- Policy [organization-defined frequency] and following [organization-defined events] ; and
- Procedures [organization-defined frequency] and following [organization-defined events].
CP-2 – Contingency Plan#
- a. Develop a contingency plan for the system that:
- Identifies essential mission and business functions and associated contingency requirements;
- Provides recovery objectives, restoration priorities, and metrics;
- Addresses contingency roles, responsibilities, assigned individuals with contact information;
- Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;
- Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;
- Addresses the sharing of contingency information; and
- Is reviewed and approved by [organization-defined personnel or roles];
- b. Distribute copies of the contingency plan to [organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
- c. Coordinate contingency planning activities with incident handling activities;
- d. Review the contingency plan for the system [organization-defined frequency];
- e. Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;
- f. Communicate contingency plan changes to [organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
- g. Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and
- h. Protect the contingency plan from unauthorized disclosure and modification.
CP-2(1) – Coordinate with Related Plans
Coordinate contingency plan development with organizational elements responsible for related plans.
CP-2(2) – Capacity Planning
Conduct capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during contingency operations.
CP-2(3) – Resume Mission and Business Functions
Plan for the resumption of [all or essential] mission and business functions within [organization-defined time period] of contingency plan activation.
CP-2(4) – Resume All Mission and Business Functions
CP-2(5) – Continue Mission and Business Functions
Plan for the continuance of [all or essential] mission and business functions with minimal or no loss of operational continuity and sustains that continuity until full system restoration at primary processing and/or storage sites.
CP-2(6) – Alternate Processing and Storage Sites
Plan for the transfer of [all or essential] mission and business functions to alternate processing and/or storage sites with minimal or no loss of operational continuity and sustain that continuity through system restoration to primary processing and/or storage sites.
CP-2(7) – Coordinate with External Service Providers
Coordinate the contingency plan with the contingency plans of external service providers to ensure that contingency requirements can be satisfied.
CP-2(8) – Identify Critical Assets
Identify critical system assets supporting [all or essential] mission and business functions.
CP-3 – Contingency Training#
- a. Provide contingency training to system users consistent with assigned roles and responsibilities:
- Within [organization-defined time period] of assuming a contingency role or responsibility;
- When required by system changes; and
- [organization-defined frequency] thereafter; and
- b. Review and update contingency training content [organization-defined frequency] and following [organization-defined events].
CP-3(1) – Simulated Events
Incorporate simulated events into contingency training to facilitate effective response by personnel in crisis situations.
CP-3(2) – Mechanisms Used in Training Environments
Employ mechanisms used in operations to provide a more thorough and realistic contingency training environment.
CP-4 – Contingency Plan Testing#
- a. Test the contingency plan for the system [organization-defined frequency] using the following tests to determine the effectiveness of the plan and the readiness to execute the plan: [organization-defined tests].
- b. Review the contingency plan test results; and
- c. Initiate corrective actions, if needed.
CP-4(1) – Coordinate with Related Plans
Coordinate contingency plan testing with organizational elements responsible for related plans.
CP-4(2) – Alternate Processing Site
Test the contingency plan at the alternate processing site:
- (a) To familiarize contingency personnel with the facility and available resources; and
- (b) To evaluate the capabilities of the alternate processing site to support contingency operations.
CP-4(3) – Automated Testing
Test the contingency plan using [organization-defined automated mechanisms].
CP-4(4) – Full Recovery and Reconstitution
Include a full recovery and reconstitution of the system to a known state as part of contingency plan testing.
CP-4(5) – Self-challenge
Employ [organization-defined mechanisms] to [organization-defined system or system component] to disrupt and adversely affect the system or system component.
CP-5 – Contingency Plan Update#
CP-6 – Alternate Storage Site#
- a. Establish an alternate storage site, including necessary agreements to permit the storage and retrieval of system backup information; and
- b. Ensure that the alternate storage site provides controls equivalent to that of the primary site.
CP-6(1) – Separation from Primary Site
Identify an alternate storage site that is sufficiently separated from the primary storage site to reduce susceptibility to the same threats.
CP-6(2) – Recovery Time and Recovery Point Objectives
Configure the alternate storage site to facilitate recovery operations in accordance with recovery time and recovery point objectives.
CP-6(3) – Accessibility
Identify potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outline explicit mitigation actions.
CP-7 – Alternate Processing Site#
- a. Establish an alternate processing site, including necessary agreements to permit the transfer and resumption of [organization-defined system operations] for essential mission and business functions within [organization-defined time period] when the primary processing capabilities are unavailable;
- b. Make available at the alternate processing site, the equipment and supplies required to transfer and resume operations or put contracts in place to support delivery to the site within the organization-defined time period for transfer and resumption; and
- c. Provide controls at the alternate processing site that are equivalent to those at the primary site.
CP-7(1) – Separation from Primary Site
Identify an alternate processing site that is sufficiently separated from the primary processing site to reduce susceptibility to the same threats.
CP-7(2) – Accessibility
Identify potential accessibility problems to alternate processing sites in the event of an area-wide disruption or disaster and outlines explicit mitigation actions.
CP-7(3) – Priority of Service
Develop alternate processing site agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives).
CP-7(4) – Preparation for Use
Prepare the alternate processing site so that the site can serve as the operational site supporting essential mission and business functions.
CP-7(5) – Equivalent Information Security Safeguards
CP-7(6) – Inability to Return to Primary Site
Plan and prepare for circumstances that preclude returning to the primary processing site.
CP-8 – Telecommunications Services#
Establish alternate telecommunications services, including necessary agreements to permit the resumption of [organization-defined system operations] for essential mission and business functions within [organization-defined time period] when the primary telecommunications capabilities are unavailable at either the primary or alternate processing or storage sites.
CP-8(1) – Priority of Service Provisions
- (a) Develop primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with availability requirements (including recovery time objectives); and
- (b) Request Telecommunications Service Priority for all telecommunications services used for national security emergency preparedness if the primary and/or alternate telecommunications services are provided by a common carrier.
CP-8(2) – Single Points of Failure
Obtain alternate telecommunications services to reduce the likelihood of sharing a single point of failure with primary telecommunications services.
CP-8(3) – Separation of Primary and Alternate Providers
Obtain alternate telecommunications services from providers that are separated from primary service providers to reduce susceptibility to the same threats.
CP-8(4) – Provider Contingency Plan
- (a) Require primary and alternate telecommunications service providers to have contingency plans;
- (b) Review provider contingency plans to ensure that the plans meet organizational contingency requirements; and
- (c) Obtain evidence of contingency testing and training by providers [organization-defined frequency].
CP-8(5) – Alternate Telecommunication Service Testing
Test alternate telecommunication services [organization-defined frequency].
CP-9 – System Backup#
- a. Conduct backups of user-level information contained in [organization-defined system components][organization-defined frequency];
- b. Conduct backups of system-level information contained in the system [organization-defined frequency];
- c. Conduct backups of system documentation, including security- and privacy-related documentation [organization-defined frequency] ; and
- d. Protect the confidentiality, integrity, and availability of backup information.
CP-9(1) – Testing for Reliability and Integrity
Test backup information [organization-defined frequency] to verify media reliability and information integrity.
CP-9(2) – Test Restoration Using Sampling
Use a sample of backup information in the restoration of selected system functions as part of contingency plan testing.
CP-9(3) – Separate Storage for Critical Information
Store backup copies of [organization-defined critical system software and other security-related information] in a separate facility or in a fire rated container that is not collocated with the operational system.
CP-9(4) – Protection from Unauthorized Modification
CP-9(5) – Transfer to Alternate Storage Site
Transfer system backup information to the alternate storage site [organization-defined time period and transfer rate consistent with the recovery time and recovery point objectives].
CP-9(6) – Redundant Secondary System
Conduct system backup by maintaining a redundant secondary system that is not collocated with the primary system and that can be activated without loss of information or disruption to operations.
CP-9(7) – Dual Authorization for Deletion or Destruction
Enforce dual authorization for the deletion or destruction of [organization-defined backup information].
CP-9(8) – Cryptographic Protection
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of [organization-defined backup information].
CP-10 – System Recovery and Reconstitution#
Provide for the recovery and reconstitution of the system to a known state within [organization-defined time period consistent with recovery time and recovery point objectives] after a disruption, compromise, or failure.
CP-10(1) – Contingency Plan Testing
CP-10(2) – Transaction Recovery
Implement transaction recovery for systems that are transaction-based.
CP-10(3) – Compensating Security Controls
Addressed through tailoring.
CP-10(4) – Restore Within Time Period
Provide the capability to restore system components within [organization-defined restoration time periods] from configuration-controlled and integrity-protected information representing a known, operational state for the components.
CP-10(5) – Failover Capability
CP-10(6) – Component Protection
Protect system components used for recovery and reconstitution.
CP-11 – Alternate Communications Protocols#
Provide the capability to employ [organization-defined alternative communications protocols] in support of maintaining continuity of operations.
CP-12 – Safe Mode#
When [organization-defined conditions] are detected, enter a safe mode of operation with [organization-defined restrictions].
CP-13 – Alternative Security Mechanisms#
Employ [organization-defined alternative or supplemental security mechanisms] for satisfying [organization-defined security functions] when the primary means of implementing the security function is unavailable or compromised.
National Institute of Standards and Technology, OSCAL release 5.2.0. Republished courtesy of the National Institute of Standards and Technology. CC0 1.0. Source.