CP-7(6)—Inability To Return To Primary Site
>Control Description
Plan and prepare for circumstances that preclude returning to the primary processing site.
>Cross-Framework Mappings
>Supplemental Guidance
There may be situations that preclude an organization from returning to the primary processing site such as if a natural disaster (e.g., flood or a hurricane) damaged or destroyed a facility and it was determined that rebuilding in the same location was not prudent.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of CP-7(6) (Inability To Return To Primary Site)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring CP-7(6)?
- •How frequently is the CP-7(6) policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures CP-7(6) requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce CP-7(6) requirements.
- •What automated tools, systems, or technologies are deployed to implement CP-7(6)?
- •How is CP-7(6) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce CP-7(6) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of CP-7(6)?
- •What audit logs, records, reports, or monitoring data validate CP-7(6) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of CP-7(6) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate CP-7(6) compliance?
Ask AI
Configure your API key to use AI features.