SEF-06 Event Triage Processes
Triage security-related events through a defined process so real incidents are separated from noise and routed to the right response.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Triage records for recent events · Document repository
- Evidence of the process operating within its expected time · Document repository
governing documentDocuments that govern the control
- The documented triage process with severity and routing criteria · Document repository
- Evaluation of triage accuracy, such as reopened or misrouted cases · 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
- Triage performed on analyst judgement with no documented criteria
- High event volume causing silent dropping rather than deliberate closure
- No feedback loop measuring whether triage decisions were right
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 sheetSEF-05 Incident Response Metrics · SEF-07 Security Breach Notification