ID.IM-01 Improvements are identified from evaluations
Improvements are identified from evaluations.
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
- Penetration test report library with severity and status · Vulnerability scanner / patch tooling
- Red team exercise after action reviews · Document repository
- Tabletop output catalogued with improvement actions · Document repository
governing documentDocuments that govern the control
- Improvement backlog with owners and due dates · Document repository
- Trend analysis across testing programs · 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
- Improvements actioned only after the next test
- Tabletop outputs lost in chat logs
- Trend analysis not performed
- Tests scoped to easy wins
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.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles · ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties