RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
The recovery portion of the incident response plan is executed once initiated from the incident response process.
5
artefacts
1
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
- Execution log of recovery activities · SIEM / log platform
periodic reviewEvidence produced at each review
- Post execution review records · Document repository
governing documentDocuments that govern the control
- Recovery plan with triggers and decision rights · Policy repository / GRC workspace
- Recovery team roster with on call coverage · Document repository
- Plan invocation tests and outcomes · Policy repository / GRC workspace
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
- Triggers unclear in the plan
- Execution log incomplete during incidents
- Roster outdated
- Tests omit the invocation step
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.CO-04 Public updates on incident recovery are shared using approved methods and messaging · RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed