CAP-2140 · Data Forensics I · Module 4

Data Acquisition

Choose what to collect, preserve access to evidence, and verify the copy before analysis.

Plan the acquisition

Data acquisition collects digital evidence from a device or other data source. In a static acquisition, the source system is offline and the examiner protects the media from writes, typically with a tested hardware write-blocker when the interface supports one. In a live acquisition, the system stays running. This can preserve access to RAM, an unlocked volume, or a service that must stay online. Live collection can change system state. Document the reason for collecting live, the order of collection, and any changes or errors you observe.

  1. Set the scope. Confirm the authority to collect, the questions to answer, and which devices, volumes, or files are in scope.
  2. Identify constraints. Record the device state, interfaces, encryption, source size, target capacity, and tools. Estimate the time for acquisition, verification, and any repeat work.
  3. Plan for interruptions and failure. Have spare destination media and a way to resume or switch methods when possible. Where practical, keep a verified master and an independently stored, verified backup. A second source read can help in some cases. Consider the cost of reading unstable media or a changing live system again. Choose image formats for compatibility, space, and recovery needs.

SWGDE · Best Practices for Computer Forensic Acquisitions (PDF)

Choose the scope, destination, and format

A physical acquisition captures the readable sectors presented by the source interface, including addressable unallocated space. A logical acquisition collects selected files or records through a file system or application. A sparse or targeted acquisition may collect selected regions or artifacts, depending on the tool. If time, authority, or capacity limits the collection, coordinate the scope with the lead attorney or supervisor as appropriate. Preserve relevant metadata and document what was excluded.

Disk to image file
Stores acquired whole-disk data in an image that can be verified, archived, and opened for analysis.
Disk to disk
Clones the source disk to a separate destination disk. Verify the corresponding data range when the destination is larger.
Partition to partition
Copies the selected partition’s sectors to a destination partition.
Partition to image file
Stores the selected partition’s sectors in a file. Other partitions and sectors outside it are outside this acquisition.

Raw images preserve the acquired byte stream directly. Keep case metadata and acquisition logs alongside the image. Open Advanced Forensic Format (AFF) supports metadata and lossless compression. Expert Witness Format (EWF), commonly encountered as E01, also supports metadata and compression and is widely supported by forensic tools. Containers can embed metadata, and tools may also produce companion logs.

Lossless compression preserves the acquired bytes when decoded. Savings depend on the data. Empty or repetitive areas often compress well, while encrypted or already compressed regions may offer little savings. Open-source software such as libewf’s ewfacquire can create compressed EWF images. Budget enough destination capacity for the uncompressed size when compression results are uncertain.

Garfinkel and colleagues · Advanced Forensic Format · libewf · ewfacquire manual

Handle encryption, hidden areas, SSDs, and RAID

SWGDE guidance on acquisition and verification (PDF) · NIST scientific foundation review of digital investigation techniques

Use tested tools and verify the acquired data

GUI tools such as FTK Imager and command-line tools such as dc3dd can support acquisition. dc3dd can hash while copying, log errors, and verify an output when configured for that purpose. Check the source and destination before starting. Practice on disposable test drives with known contents, including write-blocker and hash checks. A bootable environment such as Kali Linux Live in forensic mode can support offline acquisition. Booting it on the evidence computer replaces the prior running session, so collect any needed volatile data first.

Use SHA-256 where supported. For raw images, compare the hash of the acquired stream with the hash of the same bytes read back from the image. For a container such as E01, use the tool’s verification routine to check the decoded evidence data. Hash the container file itself separately when tracking the integrity of the stored file. On Linux, sha256sum evidence.dd hashes a raw image file. In PowerShell, Get-FileHash -Algorithm SHA256 -LiteralPath .\evidence.dd does the same.

Record the source, acquisition scope, tool version and settings, start and end times with time zone, hash algorithm and values, and any read errors. A matching hash confirms the integrity of the bytes compared. Review the acquisition log and check for the expected items to assess coverage.

Kali · dc3dd documentation · Microsoft · Get-FileHash documentation

Practice case

A running laptop with an encrypted SSD. A company laptop is powered on and its encrypted volume is unlocked. The authorized scope covers a browser profile and a project folder. You have 30 minutes, limited destination space, and no confirmed recovery key.

What would you collect before changing the laptop’s power state? How would you verify what you collected and document the acquisition’s limits?

Review a possible approach

Keep the laptop running while you confirm the scope and collect the authorized browser profile and project folder through the unlocked file system. Use a method that preserves relevant metadata, record files the tool skips or cannot read, and verify the exported files or container using the appropriate hash or verification option. Document the live actions, timestamps, source paths, and the fact that this targeted collection did not cover the entire disk or its unallocated space. If further collection is needed, coordinate access to a recovery key and a follow-up acquisition.

Read and watch