RC.RP-03 The integrity of backups and other restoration assets is verified before using them for restoration
The integrity of backups and other restoration assets is verified before using them for restoration.
5
artefacts
0
held by a system
3
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
- Pre restoration verification records · Backup / DR tooling
- Cryptographic hash validation evidence · Document repository
- Tabletop exercise on compromised backup scenarios · Backup / DR tooling
governing documentDocuments that govern the control
- Backup integrity testing standard · Policy repository / GRC workspace
- Restoration test outcomes · 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
- Integrity checks bypassed under time pressure
- Hash validation absent for some media
- Tabletop scenarios shallow
- Test outcomes not retained
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 sheetRC.RP-02 Recovery actions are selected, scoped, prioritized, and performed · RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms