Under active development Content is continuously updated and improved

CP-2(3)Contingency Plan | Resume Mission and Business Functions

IL4 Mod
IL4 High
IL5
IL6

>Control Description

Plan for the resumption of all; essential mission and business functions within organization-defined time period of contingency plan activation.

>DoD Impact Level Requirements

FedRAMP Parameter Values

CP-2 (3)-1 [all] CP-2 (3)-2 [time period defined in service provider and organization SLA]

>Discussion

Organizations may choose to conduct contingency planning activities to resume mission and business functions as part of business continuity planning or as part of business impact analyses. Organizations prioritize the resumption of mission and business functions. The time period for resuming mission and business functions may be dependent on the severity and extent of the disruptions to the system and its supporting infrastructure.

>Programmatic Queries

Beta

Related Services

AWS DynamoDB
AWS RDS
AWS Lambda

CLI Commands

List DynamoDB backups for function restoration
aws dynamodb list-backups
Create RDS restore point for mission-critical data
aws rds create-db-snapshot --db-instance-identifier prod-db --db-snapshot-identifier cp-2-3-snapshot
List Lambda function versions for quick restoration
aws lambda list-versions-by-function --function-name mission-critical
Get RDS automated backup retention
aws rds describe-db-instances --query 'DBInstances[*].[DBInstanceIdentifier,BackupRetentionPeriod]'

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

  • What formal policies and procedures govern the implementation of CP-2(3) (Resume Mission And Business Functions)?
  • Who are the designated roles responsible for implementing, maintaining, and monitoring CP-2(3)?
  • How frequently is the CP-2(3) policy reviewed and updated, and what triggers policy changes?
  • What governance structure ensures CP-2(3) requirements are consistently applied across all systems?

Technical Implementation:

  • Describe the specific technical mechanisms or controls used to enforce CP-2(3) requirements.
  • What automated tools, systems, or technologies are deployed to implement CP-2(3)?
  • How is CP-2(3) integrated into your system architecture and overall security posture?
  • What configuration settings, parameters, or technical specifications enforce CP-2(3) requirements?

Evidence & Documentation:

  • What documentation demonstrates the complete implementation of CP-2(3)?
  • What audit logs, records, reports, or monitoring data validate CP-2(3) compliance?
  • Can you provide evidence of periodic reviews, assessments, or testing of CP-2(3) effectiveness?
  • What artifacts would you present during a FedRAMP assessment to demonstrate CP-2(3) compliance?

Ask AI

Configure your API key to use AI features.