RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved
Incident data and metadata are collected, and their integrity and provenance are preserved.
5
artefacts
1
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Access controls and audit logs on evidence repository · SIEM / log platform
periodic reviewEvidence produced at each review
- Hash validated evidence storage · Document repository
governing documentDocuments that govern the control
- Evidence collection standard with integrity controls · Policy repository / GRC workspace
- Retention schedule for incident evidence · Policy repository / GRC workspace
- Independent integrity verification reports · 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
- Evidence stored on shared drives
- Hashes computed but not validated later
- Access logs not reviewed
- Retention undefined
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-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved · RS.AN-08 An incident's magnitude is estimated and validated