MP.L2-3.8.9 Protect Backups
Protect the confidentiality of backup copies of CUI at the locations where those backups are stored.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Access controls and records for backup storage · Backup / DR tooling
governing documentDocuments that govern the control
- Backup inventory identifying which backups contain CUI · Policy repository / GRC workspace
- Protection applied at backup storage locations, encryption or physical control · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Production data protected while backups are not
- Offsite and cloud backup locations unassessed
- Backup encryption keys stored alongside the backups
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 sheetMP.L2-3.8.8 Shared Media · PE.L2-3.10.1 Limit Physical Access