SIM-02 Processing of security incidents
Have qualified internal specialists, drawing on external security providers where useful, triage each event that might be a security incident by classifying it, assigning priority and carrying out a root cause analysis.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Ticket records showing triage decisions and assigned priority for suspected incidents · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Skills or qualification records for the analysts performing triage · Document repository
governing documentDocuments that govern the control
- Root cause analysis write ups for a sample of closed incidents · Policy repository / GRC workspace
- Engagement terms with any external security provider assisting analysis · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Ticketing / ITSM); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Tickets closed as resolved with no cause identified beyond the symptom
- Priority assigned by the reporter and never reviewed by an analyst
- Events dismissed as false positives with no analysis recorded
- External specialist help arranged only mid incident, with no standing agreement
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 sheetSIM-01 Policy for security incident management · SIM-03 Documentation and reporting of security incidents