6.8 Information security event reporting
Requires a mechanism through which personnel can report security events they have observed or suspect, using appropriate channels and without delay.
5
artefacts
0
held by a system
4
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
- The defined reporting mechanism and channels, and evidence they are known to personnel and to relevant third parties · Vendor register / contract repository
- Reporting records for the period, showing volume, source and the time between observation and report · Document repository
- Evidence the channel is available at all times and does not depend on a system that may itself be affected · Document repository
- Evidence of feedback to reporters, which is what sustains reporting rates · Document repository
governing documentDocuments that govern the control
- Awareness material showing what people are expected to report, including suspicions and near misses · HR system / LMS
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
- Reporting route is the service desk, which is closed when most events occur
- Reporting rates near zero and read as good news rather than as a broken channel
- No feedback to reporters, so people stop reporting after the first ignored report
- Fear of blame suppressing reports, with no evidence of a no blame position being stated or honoured
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