Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Evidence custodian creating verified copies of digital files in a controlled documentation studio

Method guide · 8 min

Preserve digital evidence without altering what matters.

During fraud, impersonation or sensitive publication, an immediate reaction can erase context. Simple, dated and reproducible preservation improves analysis and professional handover.

Published Updated Publisher and method: IIS

At a glance

Four rules for a useful review.

  • Keep the original before editing.
  • Record date, time, time zone and context.
  • Log each copy and action.
  • Protect sensitive data and restrict access.

Step-by-step method

A reproducible path from question to conclusion.

  1. 1

    Stabilise the situation

    Secure threatened accounts and payments through official channels, but avoid deleting useful messages, logs or files before preserving them.

  2. A team preparing an object photograph and reviewing a notebook — AI-generated photograph
    2

    Capture the context

    Save the full address, profile, publication, relevant comments, date and time. A screenshot without URL or context is fragile.

  3. Notebook, phone and tablet on a work table — AI-generated photograph
    3

    Retain originals

    Keep emails in their original format, attachments intact and downloaded files without resaving them. Work from copies.

  4. 4

    Build a timeline

    Record what was observed, by whom and when, followed by actions and responses. Separate observation from interpretation.

  5. 5

    Transfer securely

    Share only what is necessary through an agreed channel. Never include passwords, temporary codes or complete identity documents in an initial message.

A screenshot is only one element

A screenshot shows what appeared on a screen but does not by itself prove authorship, integrity or origin. Add the URL, account, time, browsing context and original file where relevant.

For email, retain the exported message and headers. For a site, note the exact address and connected pages. For a conversation, preserve useful continuity without disclosing it to unrelated people.

Keep an understandable action trail

Name copies neutrally, retain an untouched version and log conversions. A file hash can support traceability, but does not replace context or the requirements of an authorised professional.

Store the case in a restricted, backed-up location separate from a potentially compromised system. Limit personal and sensitive data to what is needed.

Know when to hand over

Threats to a person, active compromise, extortion or fraudulent payment require prompt action by the appropriate services. OSINT may clarify public traces but cannot replace technical, judicial or medical response.

Where litigation is possible, ask counsel, an appropriate court officer or expert early about the suitable method of recording and transfer.

Separate collection from readable presentation

Conversion, annotation and cropping can change bytes and metadata. Keep collected and working files distinct. Record reference, format, origin, context and digest if calculated. A descriptive filename does not replace the link between file and observation.

Agree retention rules

Specify who may read, copy and transfer records. Keep access secrets separate from circulated inventories. Agree retention and handoff with responsible professionals, without promising a universal legal deadline or automatic admissibility from a hash alone.

Reading technical evidence

A hash compares files; it does not authenticate their story

SHA-256 produces a 256-bit digest, represented here by 64 hexadecimal characters. It is calculated from the file’s bytes.

Field or situation and its interpretation
Observed itemWhat it means
Renamed copyThe name is not part of the calculation; the content can retain its hash.
Recompressed image or resaved documentBytes may change even when the document looks identical.
Hash calculated todayIt proves neither creation date, authorship nor authenticity of the scene.

Record algorithm, digest, file and collection context. Compare against a reference retained separately.

  1. Retained file
  2. SHA-256 digest
  3. Compare with the reference

Calculate and compare a file hash locally →

NIST — FIPS 180-4

Apply the method

Preservation starts with the first retained copy

Retain the original file or capture and record URL, time, timezone, device, collection method and access conditions. A signed-in page may differ from its public version. Do not put passwords in the collection note. Work on a duplicate when annotating or cropping.

Record each transfer: recipient, time and purpose. Keep file, metadata and collection context together and restrict circulation. A hash helps compare copies but does not prove publication time or truth of the content. A screenshot may omit interactions or hidden material; describe its scope. For a serious incident, preserve the original and involve a competent specialist.

Collection
Document context, time and authorised method.
Integrity
Retain the original and work on a copy.
Transfer
Record recipient, time and purpose.

Does a screenshot preserve an entire page?

It records the visible view, but can omit the URL, interactions and hidden content. State its scope and preserve other available material without altering the original.

Try the reasoning

A copy receives a different filename. Does this establish changed content?

Reasoning: No. Filename and content are separate. Document operations and hashes without attributing unsupported meaning to the name.

NIST — Guide to Integrating Forensic Techniques into Incident Response

Worked example

A cropped screenshot circulates without the original message

Fictional teaching case, not a client investigation.

Which material permits context review without altering the available original?

Observation, interpretation and limit
ObservationWhat it establishesWhat remains unproven
A screenshot shows a sentence without an address or earlier conversation.An image contains that sentence within the received crop.The crop does not attribute the author or show full context.
The recipient still retains the message in their application.A fuller source can be preserved with context.An export may omit elements; check what it actually includes.
An original copy and an annotated copy are retained separately.The distinction between source copy and annotation is documented.This arrangement does not certify the conversation’s truth.

Conclusion to record

Preserve the full message and available context; keep annotations separate. Record each item’s provenance and transformations made before sharing.

What would change the conclusion?

Review with the native export, linked material and available time markers; disclose what cannot be obtained.

Check your reasoning

A hash calculated after cropping protects the stability of which version? It does not reconstruct removed pixels.

· Open the verification log

Your working sheet

Turn the method into a documented review.

For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.

  1. Define the question
  2. Record the source
  3. Test the observation
  4. State the limits

Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.

1. Email

Native export with headers, untouched attachment and receipt time.

Limit: Forwarding can remove useful headers.

2. Changing page

Full URL, zoned time, contextual capture and signed-in or public state.

Limit: A capture records an observation; it does not certify authorship.

3. Hash

Algorithm, hash, filename and calculation time.

Limit: A hash supports later stability, not initial authenticity.

How to write a useful conclusion
Editorial examples, not findings about your case
MaterialUseful wordingNext check
One dated sourceThe consulted source stated X on the recorded date.Check its origin and whether it still applies.
Multiple copies of one claimSeveral pages repeat X; independent corroboration is missing.Find the original and a source with independent evidence.
Conflicting sourcesA states X while B states Y; the difference is unresolved.Compare dates, scope, identifiers and definitions.
No matching resultNo result was found in the recorded scope.Describe queries, coverage and access limitations.

What to check and what to record

Use this grid to turn the method into a reviewable case file. A missing item remains an open question. The interpretation limit prevents a finding from becoming an unsupported conclusion.

Topic-specific checks
CheckUseful recordInterpretation limit
EmailNative export with headers, untouched attachment and receipt time.Forwarding can remove useful headers.
Changing pageFull URL, zoned time, contextual capture and signed-in or public state.A capture records an observation; it does not certify authorship.
HashAlgorithm, hash, filename and calculation time.A hash supports later stability, not initial authenticity.

Common pitfalls

Four shortcuts that weaken the result.

A person examining a photograph before describing it — AI-generated photograph

Cropping the only copy

Always keep the complete original before annotating or obscuring data.

Renaming without a log

Simple version control preserves order and provenance.

Two colleagues preparing content at an accessible table — AI-generated photograph

Replying publicly

A response can amplify content, reveal strategy or cause deletion.

Two volunteers handing over an organisational folder — AI-generated photograph

Sending everything

Useful collection stays targeted; over-collection exposes third parties.

Practical questions

Frequently asked questions.

Should every screenshot be printed?

No. The digital file, context and traceability are often essential. Printing may supplement but not replace the original.

Is a file hash enough?

No. It can show that a file has not changed since hashing, but does not alone prove its origin or truth.

How long should the file be retained?

That depends on the risk, applicable duties and possible proceedings. Keep it only as necessary and obtain tailored advice for legal matters.

Public references

These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.

HRC Berkeley / OHCHR — Berkeley Protocol. Framework for collecting, preserving and verifying digital open-source material. It was developed for human-rights and international investigations; using its documentation principles does not establish admissibility in a particular proceeding.

Editorial scope

Published by Internet Intelligence Service on 15 September 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.

Find primary portals and their limitations

Editorial responsibility, examples and corrections