EvidenceSheet

6.13.1 Management of information security incidents and improvements

The organization must establish responsibilities and procedures for identifying and recording breaches of personal data and for notifying required parties, including timing, and for disclosure to authorities under applic

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

  • Evidence of the review step that decides whether an event is a notifiable breach · Document repository
  • Notification records to authorities, customers or individuals where breaches occurred · Document repository

governing documentDocuments that govern the control

  • Documented breach identification, recording and notification procedures with timings · Policy repository / GRC workspace
  • Breach record template carrying every required field, and completed records or exercise output · Document repository
  • Where the organization is a processor, contract clauses on notification content and response times · Vendor register / contract 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

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

6.12.2 Supplier service delivery management · 6.14.1 Information security continuity