5.24 Information security incident management planning and preparation
Requires the organisation to plan and prepare for incident handling ahead of time. Incident management processes, plus the roles and responsibilities attached to them, must be defined, put in place and communicated.
5
artefacts
0
held by a system
2
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
- Evidence the process and roles were communicated to those who must act on them · Identity provider / directory
- Preparation evidence, such as playbooks for likely incident types, contact lists and readiness of forensic and communication capability · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The incident management process, defining categories, severity, escalation and the decision authority at each level · Document repository
- Documented roles and responsibilities for incident handling, including out of hours coverage and named deputies · Policy repository / GRC workspace
- Records of exercises or simulations testing the plan, and the improvements arising · 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
- Plan written by the security team and never seen by the operational staff who would execute it
- No exercise, so the first test of the plan is a real incident
- Escalation defined to a role that has no authority to make the decision required, such as taking a system offline
- Out of hours arrangements undefined, which is when most incidents are detected
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 sheet5.23 Information security for use of cloud services · 5.25 Assessment and decision on information security events