EvidenceSheet

A.5.25 Assessment and decision on information security events

Triage security events and decide which become incidents.

12
artefacts
0
held by a system
4
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

  • Ticketing system screenshots showing triage steps · Document repository
  • Meeting minutes where events were reviewed · SIEM / log platform
  • Risk assessment worksheet used for classification · Data governance / DLP tooling
  • Training records for staff on escalation steps · HR system / LMS

governing documentDocuments that govern the control

  • Flowchart of initial event handling · Document repository
  • Standard operating procedure for security event triage · Policy repository / GRC workspace
  • Recorded decisions in incident management tool · Policy repository / GRC workspace
  • Decision register with timestamps and responsible persons · Policy repository / GRC workspace
  • Matrix mapping event types to severity levels · Policy repository / GRC workspace
  • Policy document defining incident vs event thresholds · Policy repository / GRC workspace
  • Escalation matrix with contact lists · Policy repository / GRC workspace
  • Email examples of escalated events · 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

A.5.24 Information security incident management planning and preparation · A.5.26 Response to information security incidents