RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging
Public updates on incident recovery are shared using approved methods and messaging.
5
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Approved spokesperson list and training records · HR system / LMS
governing documentDocuments that govern the control
- Public communications policy with approval workflow · Policy repository / GRC workspace
- Holding statement templates for recovery · Document repository
- Crisis communications drill outcomes · Document repository
- Sample public updates issued during incidents · Document repository
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
- Spokespeople untrained
- Templates lack regulatory specifics
- Drills omit recovery phase
- Updates inconsistent across channels
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-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders · RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process