SIM-01 Policy for security incident management
Document, communicate and provide an incident response policy with technical and organisational safeguards for fast and proper handling, defining classification, prioritisation and escalation rules, interfaces to inciden
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Incident management policy setting out classification and prioritisation criteria · Policy repository / GRC workspace
- Escalation matrix showing thresholds and the roles that receive each level · Policy repository / GRC workspace
- Charter, staffing roster and contact details for the emergency response team · Policy repository / GRC workspace
- Sample customer notification issued after a classified incident · Document 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
- Severity levels defined but no criterion for who assigns the level
- Response team exists on paper with no named members or on call rota
- No documented interface between incident handling and continuity activation
- Timing of customer notification left entirely to case by case judgement
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 sheetPSS-12 Locations of Data Processing and Storage · SIM-02 Processing of security incidents