EvidenceSheet

5.27 Learning from information security incidents

Requires knowledge gained from information security incidents to be fed back into strengthening and improving the information security controls.

5
artefacts
0
held by a system
2
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

  • Post incident review records for incidents meeting the defined threshold, with attendees and findings · Document repository
  • Actions arising, with owner, due date and evidence of completion · Document repository

governing documentDocuments that govern the control

  • Root cause analysis distinguishing the technical cause from the process or control failure that allowed it · Document repository
  • Evidence that findings changed something concrete, such as a control strengthened, a procedure amended or a detection rule added · Policy repository / GRC workspace
  • Trend analysis across incidents, showing recurring causes are identified as recurring · 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

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 sheet

5.26 Response to information security incidents · 5.28 Collection of evidence