ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
Improvements are identified from execution of operational processes, procedures, and activities.
5
artefacts
1
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
- Operations metrics dashboard with anomaly indicators · SIEM / log platform
periodic reviewEvidence produced at each review
- Quarterly improvement retro records · Document repository
governing documentDocuments that govern the control
- Incident lessons learned register · Policy repository / GRC workspace
- Near miss reporting workflow · Document repository
- Process improvement initiatives tied to operations data · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Lessons learned never close out
- Near misses not reported because no impact occurred
- Improvement initiatives lose momentum
- Retros skipped during busy periods
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 sheetID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties · ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved