EvidenceSheet

5.5 Contact with authorities

Requires the organisation to establish and maintain working contact with the relevant authorities, so that security matters can be raised and received through an established channel.

5
artefacts
0
held by a system
3
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

  • Named contacts and current contact details for each, with a review date · Policy repository / GRC workspace
  • Evidence of actual contact, such as registration records, correspondence or notification records · Policy repository / GRC workspace
  • Evidence the contact list is exercised or verified so it is known to work before an incident · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • The list of relevant authorities identified, such as regulators, data protection authorities, law enforcement and national cyber security bodies · Policy repository / GRC workspace
  • The procedure describing when and how each authority is contacted, and who is authorised to do so · 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

5.4 Management responsibilities · 5.6 Contact with special interest groups