Join our Newsletter — 33% off our NHI Course
Home› Guides› Chain of Custody Form Template: Printable Evidence Forms…
Template Incident Response & Forensics

Chain of Custody Form Template: Printable Evidence Forms from Seizure to Disposal

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 12 min read
On this page

When evidence is challenged, the question is rarely whether the analysis was right; it is whether anyone can show, signature by signature, who held each item from the moment it was found to the moment it was destroyed. Responders often have a procedure but no usable form, so custody is reconstructed afterwards from chat messages and memory. This template is a complete, printable form pack for [Organisation]: a case header, an evidence item record, an acquisition and seal record, a pre-eradication clearance, a transfer and access log, an external handover receipt, a disposal record and a custody audit. It is written for incident responders, forensic examiners, first responders in IT and cloud teams, and the legal and HR staff who rely on the result. The procedure behind it sits in the Evidence Handling and Chain of Custody Guide; this page is the paperwork.

How to use this template

  • One pack per case, one item record per item: open Form A when a case is opened, and a Form B for every physical device, image, log export, cloud snapshot or SaaS export. Number items [CASE-YYYY-NNN]-[ITEM-NN] and never reuse a number.
  • Complete it at the time: SWGDE's Best Practices for Digital Evidence Collection (version 2.0, November 2025) says custody records should be made at the time of collection and should record each item, the date and time of receipt, every transfer, and the name and signature of each person taking possession. Late entries are allowed only as marked late entries with the reason.
  • Record times in UTC: write every time as UTC with the date (YYYY-MM-DD hh:mm UTC). Note local time in brackets only where staff or police need it.
  • Ink or controlled system only: on paper use permanent ink, single line strike-through with initials for corrections, no erasures. In a case management tool use an append-only record with per-user authentication; the system audit log becomes part of the chain.
  • Section names follow the incident lifecycle: sections 1 to 8 match the phases of your incident response plan, so each playbook step can point to the form it needs. Replace every [bracketed] placeholder before adoption.
  • Treat completed forms as sensitive: they reveal suspects, systems and sometimes credentials. Store them with the evidence, under the same access controls.

1. Scope and triggers

1.1 This form pack is used for any item that [Organisation] collects as potential evidence in a security incident, internal investigation, disciplinary matter or legal proceeding, whether it is held on company devices, personal devices collected with consent or legal authority, servers, cloud accounts, SaaS tenants or third-party systems.

1.2 Open a pack when any of the following occurs: an incident is declared at [High] or [Critical] severity; legal counsel, HR, an insurer or law enforcement requests preservation; a litigation hold is issued; or a first responder believes an item may be needed later. If in doubt, open the pack: an unused pack costs nothing, a missing one cannot be recreated.

Form A: Case header (one per case)

FieldEntry
Case reference[CASE-YYYY-NNN]; linked incident ticket [INC-YYYY-NNN]
Case title[Neutral description, no names of suspects or conclusions]
Opened by and date and time (UTC)[Name], [role], [YYYY-MM-DD hh:mm UTC]
Evidential standard[Internal] / [Disciplinary or civil] / [Criminal], set by [Legal Counsel]; may be raised, never lowered
Legal privilege[Yes, under direction of counsel] / [No]
Legal hold in force[Yes, reference] / [No]
Evidence Custodian[Name], [24/7 contact]
Storage location for this case[Evidence locker ID] and [forensic storage account, bucket and retention lock setting]
Item numbers issued[ITEM-01] to [ITEM-NN], updated as items are added

2. Roles and contacts

2.1 Only people named in the register below may sign as collector, custodian or recipient. Anyone else who touches an item (for example a courier or a facilities manager opening a locker) is recorded in the transfer log as a handler.

RoleNameSignature specimenContactAuthorised to
Evidence Custodian[Name][ ][Phone, email]Receive, store, release, approve disposal
Deputy Custodian[Name][ ][Phone, email]Same as custodian when custodian unavailable
Forensic Examiner[Name or retained provider][ ][Phone, email]Acquire, verify, examine working copies
First Responder[SOC or on-call engineer][ ][Phone, email]Identify, photograph, isolate, start Form B
Cloud and SaaS Administrator[Name][ ][Phone, email]Create snapshots and exports under examiner direction
Witness[Name][ ][Phone, email]Countersign collection where the standard requires two people
Legal Counsel[Name][ ][Phone, email]Approve external release and disposal

2.2 External contacts to keep with the pack: [Incident response retainer hotline], [Cloud provider support case route], [Police or national cyber crime reporting route], [Insurer breach line].

3. Detection and triage

3.1 At identification, the first responder completes Form B before anything is moved or copied, and photographs the item in place. SWGDE recommends recording the location, the device state (on, off, open files) and physical characteristics such as damage, marks, serial numbers and connections, and advises not to turn on a computer that is powered off and to treat a device in standby as running.

Form B: Evidence item record (one per item)

FieldPhysical itemDigital or cloud item
Item number[CASE]-[ITEM-NN][CASE]-[ITEM-NN]
DescriptionType, make, model, serial number, asset tag, colour, visible damageResource type, resource ID or ARN, account or tenant ID, region, log source, query text or export name
Location foundSite, building, room, desk; photo references [P-NN]Console path or API endpoint; screenshot references [S-NN]
State when foundPowered on, off, standby; screen content; cables and peripherals attachedRunning, stopped, deleted pending; retention remaining on the source
Found by, date and time (UTC)[Name], [time][Name], [time]
System clock checkDevice time vs trusted UTC source, offset [ ]Source time zone and log timestamp format
Owner or user of item[Name or "unknown"]; consent or authority reference if personal[Account owner or service owner]
Related identitiesAccounts logged in on the deviceService accounts, API keys, tokens or OAuth apps involved (identifiers only, never the secret)
Collector signature[ ][ ]
Witness signature[ ] (if required)[ ] (if required)

4. Containment

4.1 In this pack, containment means protecting the item from change, loss and unauthorised access. Complete Form C for every acquisition and every seal applied.

Form C: Acquisition and seal record

FieldEntry
Item number[CASE]-[ITEM-NN]
Acquisition type[Full disk image] / [Memory capture] / [Logical or triage collection] / [Cloud snapshot] / [Log or SaaS export] / [Physical seizure only]
Tool and version[Tool name, version, build]; write blocker [model and serial] or [software blocker, version]
Command, API call or method[Exact command line or API request ID; snapshot ID]
Start and end time (UTC)[ ] to [ ]
Source hash (where readable)SHA-256 [ ]; second algorithm [ ]
Acquisition hashSHA-256 [ ]; second algorithm [ ]
Verification hash and resultSHA-256 [ ]; match [Yes] / [No, see discrepancy report]
Collection notesData size, file count, file names, tool logs and screenshots attached as [refs]
Destination media or storage[Media serial, wiped and verified on date] or [bucket, object key, version ID, retention lock mode]
Seal number(s)Tamper-evident bag [number]; seal [number]; photo of sealed item [P-NN]
Faraday or isolationFor mobile and wireless devices: Faraday bag [number] or network isolation method
Acquired by and witness[Name, signature] / [Name, signature]

4.2 SWGDE recommends an acquisition hash, using multiple algorithms, during imaging and a verification hash after acquisition is complete. Use SHA-256 as the primary value; see the Hashing Guide. For cloud evidence, record the snapshot or export ID and the identity that created it; see the Cloud Forensics Guide.

5. Eradication

5.1 No system that is the source of an item in this pack may be wiped, reimaged, restored, deleted, or have its credentials rotated until the Evidence Custodian signs Form D. Incident playbooks must reference this form before their eradication step.

Form D: Pre-eradication evidence clearance

System or identityItems acquiredHashes verifiedIdentity evidence exported before resetCleared by and time (UTC)
[Hostname, resource ID or account][ITEM-NN, ITEM-NN][Yes / No][Key or token IDs, created and last-used times, audit log of use, OAuth consent records: Yes / Not applicable][Custodian name, signature, time]

5.2 Rotating a key or deleting a token can remove the last-used data that shows when it was abused. Export the identifiers and activity first; record secret values only if counsel requires them, encrypted and never on this form.

6. Recovery

6.1 RFC 3227 requires you to document who had custody of the evidence, during what period and how it was stored, and when and how custody changed, including shipping numbers. Form E is that record. Every movement and every access to the master item gets a line, including returns to the locker.

Form E: Transfer and access log (continuation sheets as needed)

#Date and time (UTC)Released by (name, signature)Received by (name, signature)PurposeSeal intact and numberLocation after
1[ ][ ][ ][Storage] / [Examination] / [Copy made] / [Courier][Yes / No], [seal no.][Locker, shelf, bucket]
2[ ][ ][ ][ ][ ][ ]

6.2 Examine working copies only. When a working copy is made, record it as a line in Form E with the copy's hash, and re-verify the master hash before and after each examination session. If a seal is broken for examination, record the old and new seal numbers on the same line.

6.3 Physical items returned to service (for example a laptop reissued after imaging) are recorded with "returned to [owner]" and the custodian's approval; the image remains the evidence item.

7. Communication and notification

7.1 Evidence or copies released outside [Organisation], to law enforcement, a regulator, an insurer, a retained incident response provider or opposing counsel, require approval by [Legal Counsel] and a signed Form F.

Form F: External handover receipt

FieldEntry
Items released[ITEM-NN list]; original or copy; hashes
Recipient organisation and reference[Organisation, case or crime reference]
Recipient name, role, identity check[Name], [role], [warrant card, ID or letter of authority checked by]
Legal basis and approval[Consent, court order, contract, request]; approved by [Legal Counsel], [time]
Transfer method[In person] / [Courier, tracking number] / [Secure transfer, link expiry, encryption method, key sent separately]
Conditions[Return or destruction terms, onward disclosure limits, personal data handling]
SignaturesReleased by [ ], received by [ ], date and time (UTC) [ ]

7.2 Ask law enforcement early what format and handling they need. In England and Wales, forensic science activities for the criminal justice system are subject to the Forensic Science Regulator's statutory Code of Practice (version 1 in force since October 2023; version 2 presented to Parliament in 2025), so police may need evidence in a particular form.

8. Post-incident review

8.1 When a case closes, the custodian audits the pack before retention or disposal, and records the outcome in Form G.

Form G: Custody audit, discrepancy and disposal record

Check or actionResultSigned
Every item in Form A has Forms B, C and E[Yes / exceptions listed][ ]
No gaps in Form E (every release has a matching receipt)[Yes / gaps listed][ ]
Final hash verification of masters[All match / mismatch on ITEM-NN][ ]
Discrepancies (broken seal, late entry, hash mismatch, missing signature)[Description, cause, who was informed, impact on evidential value][ ]
Retention decisionRetain until [date] under [retention schedule or hold]; reviewed by [ ][ ]
Disposal or return[Method: secure wipe standard, physical destruction, crypto erase, object deletion after lock expiry]; certificate [ref]; approved by [Legal Counsel][ ]
Lessons for the procedure[Changes to forms, tools, training][ ]

8.2 A discrepancy does not automatically make evidence worthless, but hiding one can. Record it honestly, inform counsel, and keep the explanation with the pack.

Implementation guidance

  1. Adopt and brand the forms: convert Forms A to G into your document system or case management tool, with fields mandatory and append-only. Keep a printed set and pens in every response kit, with tamper-evident bags, seal labels, a camera and Faraday bags.
  2. Pre-number seals and items: buy bags with unique serial numbers and log them on receipt so an unaccounted bag is noticed.
  3. Train first responders: the first person on scene is usually an IT or cloud engineer, not an examiner. Run a 30-minute drill on Forms B and C each year and after staff changes.
  4. Exercise it: include a custody step in tabletop and technical exercises: hand an item between two people, then audit the pack. See the Tabletop Exercise Guide.
  5. Protect the record: store electronic forms and evidence where only a small set of privileged users can reach them, with access logging, separate from the production identity plane so a compromised administrator cannot alter them.
  6. Review: [DFIR Lead] reviews this pack annually and after any case where evidence or custody was questioned.

Framework fit: the pack supports NIST CSF 2.0 RS.AN-06 (actions performed during an investigation are recorded, and the records' integrity and provenance are preserved) and RS.AN-07 (incident data and metadata are collected, and their integrity and provenance are preserved); NIST SP 800-53 Rev. 5 IR-4 Incident Handling, AU-9 Protection of Audit Information, AU-9(4) Access by Subset of Privileged Users, AU-10 Non-repudiation and AU-11 Audit Record Retention; and ISO/IEC 27001:2022 Annex A 5.28 Collection of evidence. ISO/IEC 27037:2012, last reviewed and confirmed in 2018, gives the international guidance for identification, collection, acquisition and preservation that these forms evidence.

Standards and references

Related NHI Mgmt Group resources: Evidence Handling and Chain of Custody Guide · Digital Forensics (DFIR) Guide · Incident Decision Log Template · Disk Imaging and Forensic Acquisition Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.