SIM-04 Duty of the users to report security incidents to a central body
Inform employees and external business partners of their agreed or contractually imposed duty to report promptly, to one previously designated central office, any security event they learn of that relates to the cloud se
4
artefacts
0
held by a system
1
at each review
hard
to go live
HR system / LMS
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
- Acknowledgement records confirming staff received the reporting instruction · HR system / LMS
governing documentDocuments that govern the control
- Internal communication naming the central reporting point and the reporting duty · Policy repository / GRC workspace
- Partner agreement clause imposing the same reporting obligation externally · Vendor register / contract repository
- Awareness material stating that unfounded reports are not penalised · 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 duty covers employees only and omits contractors and business partners
- Several parallel reporting channels exist with no single designated office
- The no penalty message is never communicated, which suppresses early reporting
- Instruction given once at hire and never repeated or refreshed
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 sheetSIM-03 Documentation and reporting of security incidents · SIM-05 Evaluation and learning process