CP-9 System backup
Requires backups of user-level information, system-level information and system documentation including security and privacy documentation, each at an organization-defined frequency, and requires the confidentiality, int
4
artefacts
1
held by a system
2
at each review
moderate
to go live
Backup / DR tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Encryption and access control configuration protecting backup data · Backup / DR tooling
periodic reviewEvidence produced at each review
- Restore test records proving backups are usable · Backup / DR tooling
- Defined backup frequencies and evidence they are met · Backup / DR tooling
governing documentDocuments that govern the control
- Backup schedule and success reports covering user-level, system-level and documentation backups · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Backup / DR tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Documentation and configuration backed up nowhere, only application data
- Backups unencrypted or reachable with the same credentials as production, so ransomware takes both
- Backup success monitored while restore capability is never tested
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetCP-8 Telecommunications services · CP-10 System recovery and reconstitution