CP-2—Contingency Plan
>Control Description
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;
Distribute copies of the contingency plan to ⚙organization-defined key contingency personnel (identified by name and/or by role) and organizational elements;
Coordinate contingency planning activities with incident handling activities;
Review the contingency plan for the system ⚙organization-defined frequency;
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;
Communicate contingency plan changes to ⚙organization-defined key contingency personnel (identified by name and/or by role) and organizational elements;
Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and
Protect the contingency plan from unauthorized disclosure and modification.
>DoD Impact Level Requirements
FedRAMP Parameter Values
CP-2 (d) [at least annually]
Additional Requirements and Guidance
CP-2 Requirement: For JAB authorizations the contingency lists include designated FedRAMP personnel. CP-2 Requirement: CSPs must use the FedRAMP Information System Contingency Plan (ISCP) Template (available on the fedramp.gov: https://www.fedramp.gov/assets/resources/templates/SSP-A06-FedRAMP-ISCP-Template.docx).
>Discussion
Contingency planning for systems is part of an overall program for achieving continuity of operations for organizational mission and business functions. Contingency planning addresses system restoration and implementation of alternative mission or business processes when systems are compromised or breached. Contingency planning is considered throughout the system development life cycle and is a fundamental part of the system design.
Systems can be designed for redundancy, to provide backup capabilities, and for resilience. Contingency plans reflect the degree of restoration required for organizational systems since not all systems need to fully recover to achieve the level of continuity of operations desired. System recovery objectives reflect applicable laws, executive orders, directives, regulations, policies, standards, guidelines, organizational risk tolerance, and system impact level.
Actions addressed in contingency plans include orderly system degradation, system shutdown, fallback to a manual mode, alternate information flows, and operating in modes reserved for when systems are under attack. By coordinating contingency planning with incident handling activities, organizations ensure that the necessary planning activities are in place and activated in the event of an incident. Organizations consider whether continuity of operations during an incident conflicts with the capability to automatically disable the system, as specified in IR-4(5).
Incident response planning is part of contingency planning for organizations and is addressed in the IR (Incident Response) family.
>Programmatic Queries
Related Services
CLI Commands
aws backup list-backup-plansaws route53 list-health-checksaws drs describe-source-serversaws autoscaling describe-auto-scaling-groups>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of CP-2 (Contingency Plan)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring CP-2?
- •How frequently is the CP-2 policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures CP-2 requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce CP-2 requirements.
- •What automated tools, systems, or technologies are deployed to implement CP-2?
- •How is CP-2 integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce CP-2 requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of CP-2?
- •What audit logs, records, reports, or monitoring data validate CP-2 compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of CP-2 effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate CP-2 compliance?
Ask AI
Configure your API key to use AI features.