RS.MA-05 The criteria for initiating incident recovery are applied
The criteria for initiating incident recovery are applied.
5
artefacts
1
held by a system
2
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 linking response to recovery handoff · SIEM / log platform
periodic reviewEvidence produced at each review
- Joint review by IR and recovery teams · Document repository
- Tabletop coverage of the response to recovery boundary · Document repository
governing documentDocuments that govern the control
- Recovery initiation criteria documented · Document repository
- Closure of recovery initiation actions · 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
- Recovery initiation criteria absent
- Handoff informal and verbal
- Joint reviews not held
- Tabletops omit recovery handoff
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 sheetRS.MA-04 Incidents are escalated or elevated as needed · RS.MI-01 Incidents are contained