ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties.
5
artefacts
0
held by a system
3
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
- Risk and control assessment findings tracker · Document repository
- Closure verification evidence per finding · Document repository
- Trend report across assessment cycles · Document repository
governing documentDocuments that govern the control
- Internal audit cyber findings with management responses · Policy repository / GRC workspace
- External assessment reports with action plans · Policy repository / GRC workspace
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
- Closure declared without retest
- Findings aggregated and forgotten
- Management responses lack measurable actions
- Trends not surfaced to leadership
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-01 Improvements are identified from evaluations · ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities