National Vulnerability Database

National Vulnerability Database

National Vulnerability
Database

NIST Special Publication 800-53 (Rev. 4)

Security and Privacy Controls for Federal Information Systems and Organizations

CP-4 CONTINGENCY PLAN TESTING

Family:
CP - CONTINGENCY PLANNING
Class:
Priority:
P2 - Implement P2 security controls after implementation of P1 controls.
Baseline Allocation:
Low Moderate High
CP-4 CP-4 (1) CP-4 (1) (2)

Control Description

The organization:

a. Tests the contingency plan for the information system [Assignment: organization-defined frequency] using [Assignment: organization-defined tests] to determine the effectiveness of the plan and the organizational readiness to execute the plan;

b. Reviews the contingency plan test results; and

c. Initiates corrective actions, if needed.

Supplemental Guidance

Methods for testing contingency plans to determine the effectiveness of the plans and to identify potential weaknesses in the plans include, for example, walk-through and tabletop exercises, checklists, simulations (parallel, full interrupt), and comprehensive exercises. Organizations conduct testing based on the continuity requirements in contingency plans and include a determination of the effects on organizational operations, assets, and individuals arising due to contingency operations. Organizations have flexibility and discretion in the breadth, depth, and timelines of corrective actions.

Related to: CP-2CP-3IR-3

Control Enhancements

CP-4(1) CONTINGENCY PLAN TESTING | COORDINATE WITH RELATED PLANS
The organization coordinates contingency plan testing with organizational elements responsible for related plans.
Supplemental Guidance: Plans related to contingency plans for organizational information systems include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. This control enhancement does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. It does require, however, that if such organizational elements are responsible for related plans, organizations should coordinate with those elements.
Related to: IR-8PM-8
CP-4(2) CONTINGENCY PLAN TESTING | ALTERNATE PROCESSING SITE
The organization tests the contingency plan at the alternate processing site:
CP-4 (2)(a)
To familiarize contingency personnel with the facility and available resources; and
CP-4 (2)(b)
To evaluate the capabilities of the alternate processing site to support contingency operations.

Related to: CP-7
CP-4(3) CONTINGENCY PLAN TESTING | AUTOMATED TESTING
The organization employs automated mechanisms to more thoroughly and effectively test the contingency plan.
Supplemental Guidance: Automated mechanisms provide more thorough and effective testing of contingency plans, for example: (i) by providing more complete coverage of contingency issues; (ii) by selecting more realistic test scenarios and environments; and (iii) by effectively stressing the information system and supported missions.
CP-4(4) CONTINGENCY PLAN TESTING | FULL RECOVERY / RECONSTITUTION
The organization includes a full recovery and reconstitution of the information system to a known state as part of contingency plan testing.

Related to: CP-10SC-24