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
Source: NIST CSF 2.0, RS.AN-07. 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
- Access controls and audit logs on evidence repository · SIEM / log platform
periodic reviewEvidence produced at each review
- Hash validated evidence storage · Document repository
- Independent integrity verification reports · 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
First move
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… · RS.AN-08 An incident's magnitude is estimated and validated