Forensic Imaging and Acquisition (How Computer Evidence Is Imaged and Verified)
Imaging + Acquisition Write Blockers • Hashing • DD/E01 • Verification • Encryption • Live vs Deadbox

Forensic Imaging and Acquisition (How Computer Evidence Is Collected and Verified)

Forensic imaging is the process of creating a forensic-quality copy of digital evidence so examiners can perform parsing and analysis on a working copy, rather than the original device or media. In computer forensics, imaging decisions affect what evidence is available, how defensible the workflow is, and how confidently findings can be reported. For the main service overview, see: computer forensics.

What this guide covers

This page explains the most common acquisition types (logical vs file-level vs full-disk), how imaging formats like DD and E01 work, how hashing and verification help validate integrity, and why write blockers matter. It also explains limits and special cases such as encryption, live imaging, and container-based evidence (e.g., encrypted volumes, virtual disks, and cloud-synced content).

  • Acquisition types: logical/file collection vs full-disk imaging, and when each is used.
  • Physical media: HDDs, SSDs, NVMe, USB flash drives, SD cards, and external drives.
  • Imaging formats: raw (DD) and evidence containers such as E01.
  • Write blockers: what they do and what “write protected” means in practice.
  • Hashing + verification: how integrity checks support defensible computer forensic reporting.
  • Encryption and live acquisition: what changes when the data is protected by BitLocker, FileVault, LUKS, or encrypted containers.

Internal navigation

If you want to start with the foundation of evidence handling first, see: evidence preservation and chain of custody. If you want the broader primer before imaging details, see: what is computer forensics.

Educational note: Imaging is not “copying files.” A defensible acquisition documents method, scope, and constraints, and validates the resulting evidence set when possible.

What “forensic imaging” means (plain-English definitions)

Computer forensic experts use the term “imaging” to mean a controlled acquisition that is documented and designed to minimize unintended changes. Depending on scope, imaging can be full-disk or limited to selected data.

Full-disk (bit-for-bit) imaging

A full-disk image attempts to capture the entire storage device at the block level. This can include allocated file data and other structures, depending on storage type and encryption state.

  • Useful when the scope requires deeper file system reconstruction
  • Can preserve partitions and structural context
  • Still constrained by encryption and storage behaviors

File-level / folder collection

Sometimes the scope is targeted: specific folders, user profiles, or export sets. This approach is faster but may omit artifacts that live outside those paths.

  • Useful for narrow questions (documents, specific app data)
  • Lower storage and time cost
  • May not capture system-level artifacts needed for timelines

Logical acquisition

“Logical” typically means collecting data through the operating system’s normal access pathways (what the OS allows at that time). It can be appropriate, but it is inherently scope-limited.

  • Often used when credentials and access are controlled
  • May not include deleted-space context
  • Should be documented precisely to avoid overstatement

Physical media types (what is being imaged)

Computer forensics can involve many evidence sources beyond a single internal drive. The media type affects imaging speed, connectors, and what “deleted data” can realistically mean.

  • HDD (spinning hard drives): older but still common in desktops, older laptops, and some external drives.
  • SSD (SATA / NVMe): common in modern systems; SSD behaviors can reduce recoverability of deleted data over time.
  • USB flash drives: often use FAT variants or exFAT and are frequently moved between systems.
  • SD / microSD cards: common in cameras and embedded devices; often exFAT/FAT-based.
  • External hard drives: can be HDD or SSD inside an enclosure; the enclosure interface can affect performance and stability.
  • Servers and storage arrays: may involve multiple disks, RAID/virtualization layers, and log-centric analysis requirements.

Practical note: “One drive” may not equal “one dataset.” Virtual disks, partitions, snapshots, and encrypted containers can create multiple logical evidence layers inside a single device.

Write blockers (why they matter)

A write blocker is a hardware or software control designed to reduce the risk of writing data to the original evidence media during acquisition. In many workflows, a hardware write blocker is used when imaging removable media (e.g., SATA/USB drives) to help prevent accidental modification.

  • Purpose: reduce inadvertent writes that could alter metadata or content.
  • Reality check: a write blocker supports defensibility, but it does not solve all problems (encryption, missing logs, and overwritten data still apply).
  • Documentation: defensible acquisition documents the method, device used (when applicable), and any observed issues/errors.

A frequent misunderstanding: plugging a drive into a normal computer can create new system artifacts or trigger background processes. That is why controlled acquisition environments are used.

Imaging formats (DD vs E01 and what they represent)

Imaging outputs are typically either a raw, bitstream-style image or an evidence container format that stores additional metadata. The defensible point is not “the format,” but documenting what was captured and validating it when possible.

DD / raw images

“DD” is often used informally to describe a raw image: a direct representation of data from the source at the block level. Raw images are widely supported and straightforward, but they do not inherently carry rich case metadata unless documented separately.

  • Common in technical workflows and compatible with many tools
  • May be split into segments depending on storage and tooling
  • Requires strong documentation outside the file itself

E01 (evidence container)

E01 is a commonly used evidence container format that can store image data plus acquisition metadata (e.g., examiner notes, segmentation, and integrity-related fields), depending on the workflow and tool configuration.

  • Designed for evidentiary workflows and tool ecosystems
  • Often supports segmentation and embedded metadata
  • Still requires independent documentation and verification steps

Other “containers” you may see

In practice, you may also encounter formats associated with virtual disks, backups, or snapshots (for example, virtual drive files and system backup sets). These can be forensic-relevant, but they are not the same as a controlled forensic image unless acquired and documented with that intent.

Hashing and verification (bit-for-bit integrity in plain English)

Hashing uses a mathematical algorithm to generate a “fingerprint” of data. In computer forensics, hash values are commonly recorded during acquisition so an examiner can later verify that the image being analyzed matches what was acquired. This supports defensible reporting, especially when evidence changes hands.

  • What hashing supports: consistency checks between a source and an acquired image (or between copies of the image).
  • What hashing does not prove: it does not prove who created the data, and it does not guarantee that the source was not already altered before acquisition.
  • Verification: workflows often include a post-acquisition verification step to confirm the image is readable and consistent.

Practical takeaway: hash and verification steps strengthen defensibility, but conclusions still depend on artifact interpretation and constraints (encryption, missing logs, overwrites).

Encryption and live acquisition (what changes when data is protected)

Modern computers increasingly rely on full-disk encryption and protected containers. This can limit what a “powered-off” acquisition can access without authorized keys. In some cases, a live acquisition may be considered specifically to preserve access to decrypted content or running-state artifacts—subject to scope and authorization.

Full-disk encryption

Technologies such as BitLocker (Windows), FileVault (macOS), and LUKS (Linux) can prevent access to user data when the device is powered off or locked, unless authorized recovery material is available.

  • Access may depend on credentials, recovery keys, or escrowed enterprise keys
  • A “full-disk image” may be an image of encrypted blocks without the ability to interpret content
  • Reporting should clearly state what could and could not be accessed

Encrypted containers and “live” context

Some evidence exists inside containers that are only available when mounted or unlocked (encrypted volumes, secure vaults, or application-level encrypted stores). In these situations, “live acquisition” may be discussed specifically to capture accessible, decrypted content or confirm container existence and configuration.

  • Mounted containers may expose files that are otherwise unavailable at rest
  • Live systems can produce volatile artifacts (running processes, active connections)
  • Any live approach must be documented carefully because it can change the system

Important limitation

Encryption is a normal security feature. The defensible stance is to document the encryption state and access conditions and avoid overstating what can be recovered. When keys are not available, a computer forensic analysis may shift toward artifacts outside the encrypted scope (cloud logs, network/device management records, backups, and endpoints).

Quality controls during acquisition (what professionals typically document)

A sound imaging workflow records more than “we made a copy.” It documents what was attempted, the method used, observed errors, and the resulting evidence set. This is one of the main differences between casual data copying and work performed by computer forensic companies.

  • Scope statement: what devices/media were acquired (and what was excluded).
  • Tooling and settings: the acquisition method used and any segmentation/compression choices.
  • Integrity notes: hash values when applicable and the verification step performed.
  • Error logs: read errors, bad sectors, power events, or unstable connections.
  • Evidence handling: where the image is stored, access controls, and transfer documentation.

“No errors reported” does not always mean “perfect evidence.” Aging drives, unstable enclosures, and firmware behaviors can affect what is readable and when.

After imaging: parsing, analysis, and reporting

Imaging is the beginning, not the end. The acquired evidence is typically parsed into artifacts (file system structures, logs, application data) and then analyzed to answer the case questions. The findings are then presented in a written report that separates observed facts from interpretation and explains limitations.

If you are building foundational understanding, the “what is” primer is here: what is computer forensics.

Continue learning (hub + related pages)

For the full overview of computer forensic services (scope, process, and what outcomes are realistic), return to the main hub: computer forensics. If your priority is handling and documentation before any acquisition occurs, start with: evidence preservation and chain of custody.

Educational note: This page is informational and explains common acquisition approaches and constraints. Any real-world workflow should be scoped to the matter, devices, and authorized access conditions.

Assistant Icon Elite Digital Forensics Assistant
👋 Live Chat Now!
Free Virtual Consultation 24/7
Chat Now!

By submitting this form, you consent to be contacted by email, text, or phone. Your information is kept secure and confidential. Reply Stop to opt out at anytime. 

IMPORTANT: Please remember to check your spam or junk folder