RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed
Recovery actions are selected, scoped, prioritized, and performed.
5
artefacts
1
held by a system
1
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Decision log capturing scope and sequencing · SIEM / log platform
periodic reviewEvidence produced at each review
- Resource allocation records during recovery · Document repository
governing documentDocuments that govern the control
- Recovery prioritization criteria · Document repository
- Recovery sequencing diagrams for critical services · Document repository
- Stakeholder sign off on prioritization · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Criteria not used under pressure
- Sequencing diagrams outdated
- Resource decisions ad hoc
- Sign off skipped
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-01 The recovery portion of the incident response plan is executed once initiated from the incident response process · RC.RP-03 The integrity of backups and other restoration assets is verified before using them for restoration