RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders.
5
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Distribution evidence for recovery updates · Document repository
- Stakeholder feedback collection records · Document repository
governing documentDocuments that govern the control
- Stakeholder communication plan for recovery · Policy repository / GRC workspace
- Status update templates with cadence · Document repository
- Lessons learned on communication effectiveness · 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
- Updates technical, not business focused
- Cadence drops during long recoveries
- Distribution lists outdated
- Feedback not collected
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 sheetPR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle · RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging