SIM-05 Evaluation and learning process
Operate mechanisms that measure and monitor the type and volume of security incidents and report them to support bodies, then use the resulting analysis to identify recurring or significant incidents and decide where fur
4
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
- Decision records where that analysis led to new or strengthened safeguards · Document repository
governing documentDocuments that govern the control
- Trend statistics on incident volume and category across consecutive periods · Document repository
- Submissions made to national or sector support bodies · Document repository
- Analysis identifying repeat patterns across separate incidents · 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
- Incident counts produced but never analysed for repetition
- Categorisation too coarse to reveal a recurring underlying cause
- No reporting route to external support bodies established
- Analysis findings never converted into protection improvements
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-04 Duty of the users to report security incidents to a central body · SP-01 Documentation, communication and provision of policies and instructions