IR-5 Incident monitoring
Requires incidents to be tracked and documented from detection through resolution, so that a durable record exists of what happened, what was done and how it ended.
4
artefacts
1
held by a system
1
at each review
moderate
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
- Sample incident records showing timeline, actions taken and resolution · Document repository
periodic reviewEvidence produced at each review
- Evidence of tracking through to closure with root cause where determined · Document repository
governing documentDocuments that govern the control
- Incident register or ticketing system holding all incidents · Policy repository / GRC workspace
- Retention arrangements for incident documentation · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Minor incidents resolved in chat and never recorded
- Records lack timelines, so response times cannot be measured
- Incidents closed without a root cause or resolution note
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 sheet