Field Perspective · Public Safety

Digital evidence is more than the file

Why digital-evidence preservation depends on context around an object as well as the object itself—and what a careful record helps make reviewable.

By LeshCore TechnologiesOctober 21, 20265 min readVersion 1.0
Digital EvidencePublic Safety

Executive summary

A file can be examined as data. A defensible account also needs to make its source, handling and preservation context understandable.

A digital object rarely arrives with its full history attached. It may be a file copied from a device, material collected from a remote service, an online account, or a record generated by a system. The object matters, but so does the account of where it came from and what happened to it.

What the guidance covers

NISTIR 8387 is written for evidence-management professionals and addresses preservation considerations for several forms of digital evidence. It notes that digital data can be easy to change while also describing techniques that can prevent or detect change. The report focuses on preservation; it does not purport to cover every aspect of acquisition or every jurisdiction’s legal rules.

Preservation is a record of decisions

For a reader trying to understand a digital record, the practical questions extend beyond ‘is this the same file?’ A useful record can make the source, transfer, handling steps, integrity checks, storage and access conditions visible. Those details help a later reviewer understand the process and its limits; they do not, by themselves, establish that an interpretation is correct or that a legal standard has been met.

  • Source: what system, device, account or custodian provided the material?
  • Transfer: when and how did it move between people or systems?
  • Integrity: what checks were performed, with what tools and recorded results?
  • Handling: what transformations, exports or access events occurred?
  • Limits: what could not be collected, verified or preserved, and why?

Separate the artifact from the interpretation

An integrity check can support a statement about a particular object at particular points in a documented process. It should not be made to carry a broader claim than that. Questions about completeness, provenance, system behavior, meaning and legal admissibility require their own evidence and qualified review.

The systems-design implication is modest but important: preservation procedures, human roles and technical tools should be considered together. A workflow that captures a value but loses its context can make later review harder. Conversely, a clear record helps expose what is known, what is inferred and what remains uncertain.

Evidence and interpretation

Evidence summarized here: NISTIR 8387 identifies preservation challenges for digital evidence and discusses preservation considerations for evidence handlers. Interpretation: documenting source, transfer and handling makes the object’s path more legible to later review. This article does not report original case research, recommend a forensic procedure, or offer legal advice.

Source and limitation

This perspective is grounded in one public NIST report. It is not a systematic literature review, operational protocol or assessment of any agency’s practices. Readers should consult the full report, applicable policy and qualified practitioners for decisions about a particular matter.

References

  1. NISTIR 8387, Digital Evidence Preservation: Considerations for Evidence Handlers (opens in a new tab)
Research BriefOctober 21, 2026

Cybercrime & Digital Evidence Technology Brief

Digital evidence is not a single extraction step. Its value depends on a connected lifecycle: recognizing and preserving information, establishing lawful authority, acquiring and analyzing it with validated methods, and making the result reviewable through disclosure, presentation, retention and disposition.

LC-CJ-002 · Version 1.0

14 min read · Research & Insights

CybersecurityDigital EvidencePublic Safety
Technology ExplainerOctober 21, 2026

A trust boundary is a policy, not a line

The useful question is not where a request came from, but what is being accessed, by whom, under which policy, and with what evidence.

5 min read · Technology

CybersecuritySystems thinking
DesignOctober 21, 2026

Designing a visual language for LeshCore

A design-system note about using material, symbols and diagrams to clarify relationships—not decorate every available surface.

5 min read · Company

DesignEngineeringResponsible Technology