IR.L2-3.6.2 Incident Reporting
Track, document and report incidents to the designated internal officials and to external authorities where required.
3
artefacts
0
held by a system
1
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 of reports made within required timeframes · Document repository
governing documentDocuments that govern the control
- Incident register with tracking and documentation per incident · Policy repository / GRC workspace
- Defined internal officials and external reporting obligations · 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
- External reporting obligations unidentified
- Incidents handled informally and never documented
- Reporting timeframes undefined so notifications are late
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 sheetIR.L2-3.6.1 Incident Handling · IR.L2-3.6.3 Incident Response Testing