A.5 Organizational controls

A.5.28 Collection of evidence

Not mandatory by default – decided in your SoA

What it means in plain language

Collect and preserve evidence in a way that keeps it usable for legal or disciplinary action.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Evidence collection must preserve usability, integrity, and provenance from the first responder onward. A weak handoff, a re-imaged disk, or an undocumented export can make material unusable for disciplinary or legal action even if the incident itself was well handled. Teams should define who can collect, what to collect, how to seal it, and how to record every transfer.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Logs or device images were collected, but integrity values, time of capture, or source system details were not recorded, weakening provenance.
  • Chain-of-custody steps were skipped during handoffs between IT, HR, legal, or external specialists, creating gaps in possession history.
  • The organization waited until after re-imaging or cleanup to preserve artifacts, so volatile data, temporary files, or relevant audit logs were lost.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define evidence roles in the Evidence Collection Procedure: first responder, evidence custodian, approving manager, and external forensics contact if escalation is needed. Limit access to evidence cabinets, encrypted evidence repositories, and removable media so only authorized people can collect, copy, move, or examine items.
  • Specify collection methods for each evidence type: screenshots with metadata, log exports with hash values, disk images with write protection, cloud audit records, email headers, and physical device tagging. Use plain steps for when to isolate a machine, when to avoid power cycling, and when to document the original state before handling.
  • Require a chain-of-custody form with item description, unique identifier, date and time, collector, transferor, recipient, seal number, hash or checksum, location, and purpose of transfer. If evidence is sent externally, keep courier details, package photos, and receipt confirmation so possession is traceable.
  • Create a storage and retention rule that balances investigation needs, legal holds, privacy, and records protection. Evidence should be sealed, encrypted where appropriate, and retained only as long as needed. Test the process through tabletop scenarios involving a compromised laptop, a privileged account abuse case, and a records request.

What an auditor will ask to see

  • Chain-of-custody form with unique evidence ID, seal number, and signatures for each transfer.
  • Hash record for a disk image or log export, matched to the stored evidence copy.
  • Evidence inventory showing location, retention status, access log, and legal hold flag.
  • External forensics engagement note or call-off record naming the approved provider and contact path.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.28. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.26 — Response to information security incidents and A.5.33 — Protection of records. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.