CP-7(1)—Alternate Processing Site | Separation from Primary Site
>Control Description
>DoD Impact Level Requirements
Additional Requirements and Guidance
CP-7 (1) Guidance: The service provider may determine what is considered a sufficient degree of separation between the primary and alternate processing sites, based on the types of threats that are of concern. For one particular type of threat (i.e., hostile cyber attack), the degree of separation between sites will be less relevant.
>Discussion
Threats that affect alternate processing sites are defined in organizational assessments of risk and include natural disasters, structural failures, hostile attacks, and errors of omission or commission. Organizations determine what is considered a sufficient degree of separation between primary and alternate processing sites based on the types of threats that are of concern. For threats such as hostile attacks, the degree of separation between sites is less relevant.
>Programmatic Queries
Related Services
CLI Commands
aws ec2 create-image --instance-id i-123456 --name cp-7-1-ami --no-rebootaws ec2 run-instances --image-id ami-12345678 --instance-type t3.medium --region us-west-2aws autoscaling create-auto-scaling-group --auto-scaling-group-name cp-7-1-asg --launch-template LaunchTemplateName=primary-template,Version='$Latest' --availability-zones us-west-2a us-west-2baws ec2 describe-instances --filters Name=tag:Environment,Values=production --region us-west-2 --query 'Reservations[*].Instances[*].[InstanceId,State.Name]'>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of CP-7(1) (Separation From Primary Site)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring CP-7(1)?
- •How frequently is the CP-7(1) policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures CP-7(1) requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce CP-7(1) requirements.
- •What automated tools, systems, or technologies are deployed to implement CP-7(1)?
- •How is CP-7(1) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce CP-7(1) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of CP-7(1)?
- •What audit logs, records, reports, or monitoring data validate CP-7(1) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of CP-7(1) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate CP-7(1) compliance?
Ask AI
Configure your API key to use AI features.