CP-9(6)—Redundant Secondary System
>Control Description
Conduct system backup by maintaining a redundant secondary system that is not collocated with the primary system and that can be activated without loss of information or disruption to operations.
>Cross-Framework Mappings
>Supplemental Guidance
The effect of system backup can be achieved by maintaining a redundant secondary system that mirrors the primary system, including the replication of information. If this type of redundancy is in place and there is sufficient geographic separation between the two systems, the secondary system can also serve as the alternate processing site.
>Related Controls
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What formal policies and procedures govern the implementation of CP-9(6) (Redundant Secondary System)?
- •Who are the designated roles responsible for implementing, maintaining, and monitoring CP-9(6)?
- •How frequently is the CP-9(6) policy reviewed and updated, and what triggers policy changes?
- •What governance structure ensures CP-9(6) requirements are consistently applied across all systems?
Technical Implementation:
- •Describe the specific technical mechanisms or controls used to enforce CP-9(6) requirements.
- •What automated tools, systems, or technologies are deployed to implement CP-9(6)?
- •How is CP-9(6) integrated into your system architecture and overall security posture?
- •What configuration settings, parameters, or technical specifications enforce CP-9(6) requirements?
Evidence & Documentation:
- •What documentation demonstrates the complete implementation of CP-9(6)?
- •What audit logs, records, reports, or monitoring data validate CP-9(6) compliance?
- •Can you provide evidence of periodic reviews, assessments, or testing of CP-9(6) effectiveness?
- •What artifacts would you present during a FedRAMP assessment to demonstrate CP-9(6) compliance?
Ask AI
Configure your API key to use AI features.