Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are Disk Imaging and Write Blockers?

Disk imaging copies every sector of a storage device for analysis; a write blocker guarantees the original is never modified while you do it. Together they make forensic findings repeatable.

Illustration for the cybersecurity term Disk Imaging and Write Blockers
Home / Blog / Cybersecurity Terms / What Are Disk Imaging and Write Blockers?
17 November 2026

What Are Disk Imaging and Write Blockers?

What Are Disk Imaging and Write Blockers?

A forensic image is a sector-by-sector copy of a storage device, including the areas a normal file copy ignores: unallocated space, file slack, deleted records, the page file, and partition gaps. A write blocker is the device or driver that sits between the evidence and the examination machine and refuses every write command the operating system tries to send. Neither is interesting on its own. Together they are the reason a second examiner can repeat your work five years later and reach the same conclusion.

Why a Write Blocker Is Not Optional

Connect a disk to a running Windows machine and the system will write to it before you have opened anything: a recycle bin folder, system volume information, updated access times, sometimes an offer to format a partition it does not recognise. Each write alters the hash and gives an opposing expert a free line of attack.

Hardware blockers from Tableau, CRU, and Atola handle SATA, SAS, NVMe, USB, and media cards, and are the default because they are independent of the host operating system. Software blocking exists — the Windows StorageDevicePolicies registry setting for USB devices, or blockdev --setro on Linux — but it protects only what the running kernel honours, and a Linux kernel will still replay a dirty file system journal on mount unless you are careful. Where the examination platform is a trusted forensic distribution with verified read-only mounting, software blocking is defensible; on a general-purpose workstation it is not.

Acquisition in Practice

The sequence is consistent regardless of tool. Document the device, attach it through the blocker, read the full capacity including any host-protected area or device configuration overlay, write the image to clean destination media, and calculate hashes of both the source and the resulting image. SHA-256 is the sensible default; many tools compute two algorithms in one pass, which costs little and forestalls argument.

Common tools are FTK Imager and Guymager for a graphical workflow, and dc3dd or ewfacquire on the command line. Output formats matter: raw images are universally readable but uncompressed, while the EWF family stores case metadata, compresses, and carries per-chunk checksums — covered in forensic image formats. The NIST Computer Forensics Tool Testing programme publishes test reports for write blockers and imaging tools, which is the usual answer when asked to justify a tool choice.

Where the Classical Model Breaks

Making the Decision

Ask what question the evidence must answer. A deleted file hunt or a timeline covering unallocated space needs a full physical image. Confirming which accounts ran which commands during an intrusion is answered faster by triage artefacts and memory. A great deal of time is wasted imaging 2 TB of film files on a workstation when the investigation turned on four event logs.

Whatever you acquire, record it: device identifiers, blocker model, tool version, hashes, start and end times, and the examiner’s name, all tied to the chain of custody. Our digital forensics services handle acquisition on site where devices cannot leave the building, which is frequently the constraint in regulated environments.

FAQ – Frequently Asked Questions

Is a Software Write Blocker Good Enough?

It can be, on a validated forensic platform where read-only mounting is enforced and tested. On a general-purpose workstation it is not, because the operating system may write before the block takes effect and a Linux kernel can replay a file system journal during mount. Hardware blockers remove that argument entirely, which is why they remain standard practice.

Why Do the Hashes Sometimes Not Match on an SSD?

Solid-state controllers perform garbage collection and TRIM independently of the host, so blocks containing deleted data can be zeroed between two reads even with a write blocker attached. The right response is to document the behaviour, record both hash values with timestamps, and explain the mechanism in the report rather than re-acquiring until the numbers agree.

Should I Image a Running Server or Shut It Down?

Usually capture it live. Shutting down loses memory, dismounts encrypted volumes, and may trigger clean-up routines, while an outage on a production system carries its own cost. Capture memory first, then take a snapshot or a logical acquisition of the volumes that matter. Reserve dead-box imaging for endpoints and for cases where the evidential bar is highest.

How Large Should the Destination Media Be?

Larger than the source, with room for compression metadata and a working copy. Wipe and verify the destination before use so that no residual data from a previous case can be attributed to this one, and record the wipe. Many laboratories keep a standing procedure of a single-pass zero wipe plus verification for every evidence destination drive.

Related Terms

You May Be Interested In These

What Is Path Traversal?

Cybersecurity Terms

17 November 2026

What Is Path Traversal?

Read More
What Is Secure Code Review?

Cybersecurity Terms

17 November 2026

What Is Secure Code Review?

Read More
What Is a Rainbow Table?

Cybersecurity Terms

17 November 2026

What Is a Rainbow Table?

Read More