Skip to content

Contingency Planning Decision Worksheet

Contingency Planning Decision Worksheet template: Every decision the Contingency Planning family of NIST SP 800-53 Rev. 5 forces, with typical values and who decides, per baseline, as a spreadsheet.

TypeProgram stageStatusTemplate versionNIST basis
Decision worksheetCoreDraft1.0.0SP 800-53 release 5.2.0

Every decision the Contingency Planning family asks your organization to make before its policy and procedures can be final: the family’s key questions, then each organization-defined parameter of every CP control in the baseline, with a typical value where the Contingency Planning Policy gives one. Download the spreadsheet, fill the “Your value” column with the people who decide, and carry the values into the policy’s highlighted fields.

Typical values are starting points, not recommendations for every system. “Who decides” defaults to the role accountable for the family policy; many organizations delegate system-level values to the system owner.

VariantSpreadsheet
LowCSV
ModerateCSV
HighCSV

42 decisions.

DecisionControlTypical valueWho decides
Who sets each system’s recovery time and recovery point objectives, and from what?CP-2, CP-10The system owner, from a business impact analysis agreed with the business owner; the authorizing official approves them with the contingency plan.System owner
Where are the alternate storage and processing sites for each system?CP-6, CP-7A second region or availability zone of the same cloud provider for cloud systems; a second data center or a recovery service for on-premises systems.Chief Information Security Officer
How are backups protected against ransomware and deliberate deletion?CP-9At least one immutable or offline copy, separate backup credentials, and encryption.Chief Information Security Officer
What kind of contingency plan test does each baseline need?CP-4A tabletop exercise each year for Low systems; a functional recovery test each year for Moderate and High systems, at the alternate site for High.Chief Information Security Officer
Personnel or roles to whom the contingency planning policy is to be disseminatedCP-1Everyone within its scope, through the policy libraryChief Information Security Officer
Personnel or roles to whom the contingency planning procedures are to be disseminatedCP-1The people who carry them out, and the system ownersChief Information Security Officer
Select one or more: organization-level; mission/business process-level; system-levelCP-1Organization-levelChief Information Security Officer
An official to manage the contingency planning policy and proceduresCP-1Chief Information Security OfficerChief Information Security Officer
The frequency at which the current contingency planning policy is reviewed and updatedCP-1AnnuallyChief Information Security Officer
Events that would require the current contingency planning policy to be reviewed and updatedCP-1Assessment or audit findings, security incidents or breaches, and changes in applicable laws, executive orders, directives, regulations, policies, standards or guidelinesChief Information Security Officer
The frequency at which the current contingency planning procedures are reviewed and updatedCP-1AnnuallyChief Information Security Officer
Events that would require procedures to be reviewed and updatedCP-1The same events as the policy, and changes to the systems, tools or services the procedures describeChief Information Security Officer
Personnel or roles to review a contingency planCP-2The system owner and the system security officerChief Information Security Officer
Personnel or roles to approve a contingency planCP-2The authorizing official, or the business owner the authorizing official namesChief Information Security Officer
Key contingency personnel (identified by name and/or by role) to whom copies of the contingency plan are distributedCP-2The contingency team members, by roleChief Information Security Officer
Key contingency organizational elements to which copies of the contingency plan are distributedCP-2The operations, facilities and communications functionsChief Information Security Officer
Frequency of contingency plan reviewCP-2AnnuallyChief Information Security Officer
Key contingency personnel (identified by name and/or by role) to communicate changes toCP-2The contingency team members, by roleChief Information Security Officer
Key contingency organizational elements to communicate changes toCP-2The operations, facilities and communications functionsChief Information Security Officer
Select one: all; essentialCP-2(3)EssentialChief Information Security Officer
The contingency plan activation time period within which to resume mission and business functionsCP-2(3)The recovery time objective set in the contingency plan from the business impact analysisChief Information Security Officer
Select one: all; essentialCP-2(8)EssentialChief Information Security Officer
The time period within which to provide contingency training after assuming a contingency role or responsibilityCP-330 daysChief Information Security Officer
Frequency at which to provide training to system users with a contingency role or responsibilityCP-3AnnuallyChief Information Security Officer
Frequency at which to review and update contingency training contentCP-3AnnuallyChief Information Security Officer
Events necessitating review and update of contingency trainingCP-3A change to the contingency plan, and lessons learned from a test or an actual contingency eventChief Information Security Officer
Frequency of testing the contingency plan for the systemCP-4AnnuallyChief Information Security Officer
Tests for determining the effectiveness of the contingency planCP-4A functional test that restores the system, or a representative part of it, from backupChief Information Security Officer
Tests for determining readiness to execute the contingency planCP-4A tabletop exercise that walks the contingency team through the planChief Information Security Officer
System operations for essential mission and business functionsCP-7The system operations that support essential mission and business functionsChief Information Security Officer
Time period consistent with recovery time and recovery point objectivesCP-7The recovery time objective set in the contingency plan from the business impact analysisChief Information Security Officer
System operations to be resumed for essential mission and business functionsCP-8The system operations that support essential mission and business functionsChief Information Security Officer
Time period within which to resume essential mission and business functions when the primary telecommunications capabilities are unavailableCP-8The recovery time objective set in the contingency plan from the business impact analysisChief Information Security Officer
System components for which to conduct backups of user-level informationCP-9All servers and cloud storage that hold user dataChief Information Security Officer
Frequency at which to conduct backups of user-level information consistent with recovery time and recovery point objectivesCP-9Daily incremental and weekly full, or more often where the recovery point objective requires itChief Information Security Officer
Frequency at which to conduct backups of system-level information consistent with recovery time and recovery point objectivesCP-9Daily incremental and weekly full, or more often where the recovery point objective requires itChief Information Security Officer
Frequency at which to conduct backups of system documentation consistent with recovery time and recovery point objectivesCP-9On each changeChief Information Security Officer
Frequency at which to test backup information for media reliabilityCP-9(1)QuarterlyChief Information Security Officer
Frequency at which to test backup information for information integrityCP-9(1)QuarterlyChief Information Security Officer
Backup information to protect against unauthorized disclosure and modificationCP-9(8)All backup informationChief Information Security Officer
Time period consistent with recovery time and recovery point objectives for the recovery of the systemCP-10The recovery time objective set in the contingency plan from the business impact analysisChief Information Security Officer
Time period consistent with recovery time and recovery point objectives for the reconstitution of the systemCP-10The reconstitution time set in the contingency planChief Information Security Officer

Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.