What this policy is
Establishes how digital and physical evidence is collected, preserved, and handled during investigations so that chain-of-custody is intact if the evidence later needs to be presented to law enforcement, a regulator, or in court.
Why every organization needs one
Evidence collected without chain-of-custody is inadmissible. Without the policy, even a well-conducted investigation can leave the org unable to prosecute.
What a competent Evidence Handling Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Chain-of-custody form and procedure
- Forensic-imaging standards
- Storage requirements
- Disclosure obligations
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_evidence_handling_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.28 | Collection of evidence | Organizational controls |
| ISO/IEC 27701:2025 | A.1.2.7 | Contracts with PII processors | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.3.25 | Logging | Security considerations |
3 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.