SEF-02 Service Management Policy and Procedures
Keep approved procedures that get security incidents handled within defined timeframes, and review them at least annually.
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
- Evidence timeframes are measured against actual incidents · Document repository
- Annual review record · Document repository
governing documentDocuments that govern the control
- The incident management procedure with timeframes by severity · Policy repository / GRC workspace
- Severity definitions the timeframes attach to · 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
- Timeframes defined but never measured, so adherence is unknown
- Severity definitions vague enough that anything can be downgraded
- Annual review missed
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-01 Security Incident Management Policy and Procedures · SEF-03 Incident Response Plans