Policy Register

Evidence collection and forensics procedure

How evidence of an incident is identified, collected, preserved and handed over so that it can be relied on later.

How the register reads it

Also calledevidence handling, chain of custody
FamilyResilience and incidents
Document typeProcedure. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted.
Folds intoThe regimes accept it folded into the incident response plan; when neither is listed, the gap is counted once, under the parent.
Expected ownerThe information security lead (CISO or ISMS manager).
Review cadenceAnnual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period).
On the gap list whennever on its own: the register recognises it and names the clauses, but no ticked regime lists it as a separate document (its parent, incident response plan, is).
TemplateDigital forensics policy.

Which standards require it, and what each expects it to contain

1 requiring clauses, 1 regimes

Shown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text drawn from a human-verified compliance corpus under licence: the corpus statement of each clause, not the instrument verbatim.

ISO/IEC 27001:2022

ISO 27001 5.28 Collection of evidence

Have procedures to identify, collect, acquire and preserve evidence related to security events.

What the ISO 27002 guidance expects the document to say: Requires procedures to be established and used for identifying evidence relating to information security events, then collecting, acquiring and preserving it.

Evidence an auditor accepts: Procedures for identification, collection, acquisition and preservation of evidence, covering the media types the organisation holds; chain of custody records for evidence collected in the period, showing who held it and when; evidence of the method used to acquire data in a way that preserves integrity, such as hashing and write protection
Common gap: Procedures not aligned with legal requirements
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022

Do this for every document on your list

Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.

Build a register

Disaster recovery plan · Exercise and test programme