RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident
Analysis is performed to establish what has taken place during an incident and the root cause of the incident.
5
artefacts
1
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
- Tooling evidence list (memory captures, disk images, log exports) · SIEM / log platform
periodic reviewEvidence produced at each review
- Analyst peer review records · Document repository
governing documentDocuments that govern the control
- Incident investigation procedure · Policy repository / GRC workspace
- Forensic analysis reports with timeline reconstruction · Document repository
- Quality assurance findings on investigation outputs · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Procedure assumes on premise scenarios only
- Timelines rely on system clocks not synchronized
- Memory captures absent for cloud workloads
- Peer review skipped under time pressure
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 sheetRC.RP-06 The end of incident recovery is declared based on criteria, and incident-related documentation is completed · RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved