Under active development Content is continuously updated and improved

CP-4(1)Contingency Plan Testing | Coordinate with Related Plans

IL4 Mod
IL4 High
IL5
IL6

>Control Description

Coordinate contingency plan testing with organizational elements responsible for related plans.

>DoD Impact Level Requirements

No specific parameter values or requirements for this impact level.

>Discussion

Plans related to contingency planning for organizational systems include Business Continuity Plans, Disaster Recovery Plans, Continuity of Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber Incident Response Plans, and Occupant Emergency Plans. Coordination of contingency plan testing does not require organizations to create organizational elements to handle related plans or to align such elements with specific plans. However, it does require that if such organizational elements are responsible for related plans, organizations coordinate with those elements.

>Programmatic Queries

Beta

Related Services

AWS Fault Injection Simulator
AWS CloudWatch
AWS Systems Manager

CLI Commands

List all FIS experiment templates
aws fis list-experiment-templates
Create FIS experiment for contingency testing
aws fis create-experiment-template --description cp-4-1-test --actions '{"Stop":{"actionId":"aws:ec2:stop-instances"}}' --stop-conditions '[{"source":"aws:cloudwatch"}]'
Start a contingency plan test experiment
aws fis start-experiment --experiment-template-id eft-12345678
Get CloudWatch metrics for test coordination
aws cloudwatch get-metric-statistics --namespace AWS/EC2 --metric-name CPUUtilization --dimensions Name=InstanceId,Value=i-123456 --statistics Average

>Related Controls

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

  • What formal policies and procedures govern the implementation of CP-4(1) (Coordinate With Related Plans)?
  • Who are the designated roles responsible for implementing, maintaining, and monitoring CP-4(1)?
  • How frequently is the CP-4(1) policy reviewed and updated, and what triggers policy changes?
  • What governance structure ensures CP-4(1) requirements are consistently applied across all systems?

Technical Implementation:

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

Evidence & Documentation:

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

Ask AI

Configure your API key to use AI features.