RS.AN-08 An incident's magnitude is estimated and validated
An incident's magnitude is estimated and validated
Source: NIST CSF 2.0, RS.AN-08. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
- RCA report with contributing factors and lessons · Document repository
governing documentDocuments that govern the control
- Root cause analysis procedure · Policy repository / GRC workspace
- Action plan from RCA with owners and due dates · Policy repository / GRC workspace
- Closure verification of RCA actions · Document repository
First move
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