RS.AN-08 An incident's magnitude is estimated and validated
An incident's magnitude is estimated and validated.
5
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
- Five whys or similar method evidence · Document repository
governing documentDocuments that govern the control
- Root cause analysis procedure · Policy repository / GRC workspace
- RCA report with contributing factors and lessons · Document repository
- Action plan from RCA with owners and due dates · Policy repository / GRC workspace
- Closure verification of RCA actions · 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
- RCA reduced to a single root cause
- Contributing factors omitted
- Action plans without owners
- Closure verification absent
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 sheetRS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved · RS.CO-02 Internal and external stakeholders are notified of incidents