CyberKit

Write Blocking

Also called write blocker, forensic bridge.

Hardware or software that prevents any writes to evidence media during acquisition.

What it is

A control, implemented in hardware as an inline bridge or in software via OS settings, that allows reading from a storage device while blocking all write commands, so the act of acquiring or examining the media cannot alter it.

Why it matters

It guarantees the source drive is not modified during imaging, which is central to evidence integrity and admissibility. Even mounting a disk read-only without enforced blocking can silently change timestamps, so a write blocker removes that risk.

In practice

The drive was attached through a hardware write blocker, and the post-acquisition hash matched the source, proving nothing was written.

What to look for

  • Hardware or software blocker used and recorded.
  • Drive hash unchanged after acquisition.
  • Notes on any device that could not be blocked.

Common mistake

Plugging evidence into a normal workstation. Windows can write to a volume just by mounting it.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Autopsy Open source

    A graphical forensics platform that parses file systems and common artifacts. Our notes.

  • Eric Zimmerman's tools Free

    Command line parsers for Windows artifacts such as the MFT, Prefetch and the Registry. Our notes.

  • Plaso Open source

    Builds a super timeline from many artifacts in one image. Our notes.

  • Velociraptor Open source

    Collects the same artifacts remotely, without pulling a full disk image. Our notes.

Read next

Sources