A.5.24 Information security incident management planning and preparation
Define incident roles, processes and readiness before an incident happens.
15
artefacts
1
held by a system
6
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
- Version history with approval signatures · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Signed role delegation letters · Identity provider / directory
- Attendance logs for incident response training · SIEM / log platform
- Assessment results or competency certificates · HR system / LMS
- Records of tabletop exercises · Document repository
- Simulated breach test reports · Document repository
- Post-exercise lessons learned summary · Document repository
governing documentDocuments that govern the control
- Formal incident response policy document · Policy repository / GRC workspace
- Detailed step-by-step response playbook · Policy repository / GRC workspace
- RACI matrix linking incident roles to staff · Policy repository / GRC workspace
- List of designated incident response team members with contact details · Policy repository / GRC workspace
- Training curriculum and slide decks · HR system / LMS
- Template incident notification email · Policy repository / GRC workspace
- Media handling guidelines · Policy repository / GRC workspace
- Escalation flowchart with thresholds · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Policy repository / GRC workspace 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
- roles are defined but not formally assigned or approved
- plans are outdated and lack version control
- testing is infrequent or only documented without evidence
- communication templates are missing or not reviewed
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.23 Information security for use of cloud services · A.5.25 Assessment and decision on information security events