| name | CP-9_system-backup |
| description | Conduct backups of user-level information contained in [organization-defined] [organization-defined]; |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","cp-9","cp"] |
| tech_stack | ["aws","azure","gcp"] |
| cwe_ids | [] |
| chains_with | ["CP-2","CP-6","CP-10","MP-4","MP-5","SC-8","SC-12","SC-13","SI-4","SI-13"] |
| prerequisites | [] |
| severity_boost | {"CP-2":"Chain with CP-2 for comprehensive security coverage","CP-6":"Chain with CP-6 for comprehensive security coverage","CP-10":"Chain with CP-10 for comprehensive security coverage"} |
CP-9 System Backup
High-Level Description
Family: Contingency Planning (CP)
Framework: NIST SP 800-53 Rev 5
System-level information includes system state information, operating system software, middleware, application software, and licenses. User-level information includes information other than system-level information. Mechanisms employed to protect the integrity of system backups include digital signatures and cryptographic hashes. Protection of system backup information while in transit is addressed by MP-5 and SC-8 . System backups reflect the requirements in contingency plans as well as other organizational requirements for backing up information. Organizations may be subject to laws, executive orders, directives, regulations, or policies with requirements regarding specific categories of information (e.g., personal health information). Organizational personnel consult with the senior agency official for privacy and legal counsel regarding such requirements.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for CP-9 implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
Tools
| Tool | Purpose | Usage |
|---|
| Manual Review | Documentation and interview-based | N/A |
Remediation Guide
Control Statement
Conduct backups of user-level information contained in [organization-defined] [organization-defined];
Conduct backups of system-level information contained in the system [organization-defined];
Conduct backups of system documentation, including security- and privacy-related documentation [organization-defined] ; and
Protect the confidentiality, integrity, and availability of backup information.
