A.5.26 Response to information security incidents
Respond to incidents according to the documented procedures.
12
artefacts
1
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
- Incident ticketing system logs with timestamps · SIEM / log platform
periodic reviewEvidence produced at each review
- Evidence collection reports detailing seized artifacts · Document repository
- Post‑incident review report summarizing findings · Document repository
- Management briefing minutes documenting decision outcomes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Documented incident response policy · Policy repository / GRC workspace
- Incident response playbooks for common attack vectors · Policy repository / GRC workspace
- Roles and responsibilities matrix for response team members · Policy repository / GRC workspace
- Root cause analysis worksheets used during investigation · Document repository
- Lessons learned register tracking identified gaps · Policy repository / GRC workspace
- Corrective action plan with assigned owners and deadlines · Policy repository / GRC workspace
- Internal notification emails to management and IT staff · Policy repository / GRC workspace
- External breach notification letters sent to regulators or customers · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Plans not tested regularly
- Incident logs incomplete or inconsistent
- No formal post‑incident review process
- Communication with affected parties delayed
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 sheetA.5.25 Assessment and decision on information security events · A.5.27 Learning from information security incidents