EvidenceSheet

CC9.1 Identifies, selects and develops risk mitigation activities

Identifies, selects, and develops risk mitigation activities for risks arising from potential business disruptions.

5
artefacts
0
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

none for this control

periodic reviewEvidence produced at each review

  • Evidence of insurance or other risk transfer where used as part of the mitigation · Document repository

governing documentDocuments that govern the control

  • Identification of risks arising from potential business disruption, and the mitigation activities selected for each · Document repository
  • Business continuity and disaster recovery plans, with recovery objectives derived from a business impact analysis · Policy repository / GRC workspace
  • Evidence of testing of those plans in the period, with results measured against the objectives · Policy repository / GRC workspace
  • Evidence the plans are maintained and updated after significant change · 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

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 sheet

CC8.1 Change management processes are in place · CC9.2 Risk mitigation activities include assessment of vendor and business partner controls