skip to content

FTK Imager

FTK Imager captures memory and makes verified disk images in E01 or raw format, mounts images read-only and exports files. Interviewers ask how you would prove an image matches its source.

on this pageshow

explore

questions

6

After FTK Imager creates a disk image, what does its Drive/Image Verify Results window report, and what does a match prove?

level: juniorimportance: must knowfreq 45%

answer

  1. computed versus stored
  2. E01 carries its own hash
  3. raw file carries nothing
  4. the bad-sector line
  5. all segments in one folder

basics

~20 s

It lists the sector count, the MD5 and SHA-1 computed now, the hash stored inside an E01 or SMART image and whether it matches, and bad sectors. A match proves the image still holds exactly what was read at acquisition.

solid answer

~40 s

With `Verify images after they are created` ticked, or with **Verify Drive/Image** run later, FTK Imager re-reads the whole image and opens **Drive/Image Verify Results**: the name, the number of sectors, the MD5 and SHA-1 it computed, and, for an image that stores its own hash such as E01 or SMART, that stored value and whether the two match, plus the number of bad sectors. A match proves the image file still holds exactly the data that was read and hashed at acquisition. It does not prove the read was complete: a non-zero bad-sector count is data that was never captured and belongs in the report. A raw (dd) image carries no hash of its own, so its computed values have to be compared with the hashes recorded when it was made.

go deeper

for a junior

Name what the Drive/Image Verify Results window shows: sector count, MD5, SHA-1, the stored hash for E01 or SMART and whether it matches, and bad sectors. Say a match means the image still holds what was read.

for a middle

Explain why a raw (dd) image shows computed hashes but no match line, and where the comparison value then comes from. Mention that split segments must sit in one folder before verifying.

for a senior

Separate what a match proves from what it does not: unread bad sectors, writes before or during acquisition without a write blocker, the drive today. Show how you record the values so another examiner can repeat the check.

for a principal

Decide what the lab records as its verification evidence for every image: which values are copied, where, and who re-verifies on receipt. Formats that carry their own hash make that record simpler to defend.

## What the verify step is for A **forensic image** is a bit-for-bit copy of a drive or volume, written to files the examiner can work on while the original is stored away. Its value rests on one claim: the copy holds what the source held when it was read. FTK Imager backs that claim with two hash functions, **MD5** and **SHA-1**, computed over the data as it is acquired. A **hash** is a short fingerprint of the content; any change to the content gives a different fingerprint. FTK Imager runs verification in two places: - the **`Verify images after they are created`** check box in the Create Image dialog, which re-reads the finished image straight after acquisition; - **File > Verify Drive/Image** (also a toolbar button), which re-reads any drive or image in the Evidence Tree at any later time, by you or by whoever receives the image. ## What the results window shows The guide lists the contents of **Drive/Image Verify Results**: 1. the name of the drive or image that was verified; 2. the number of sectors in it; 3. the MD5 hash computed for it; 4. for an image that contains its own hash, such as `.S01` (SMART) or `.E01`, the hash stored inside the image, and whether that stored value matches the one just computed; 5. the SHA-1 hash computed for it; 6. the number of bad sectors found. Any line can be copied (right-click, **Copy**) into your notes, which is how the values reach the report without retyping. ## Stored hash against computed hash What the window can compare depends on the image type you chose: | Image type | Hash stored inside the image | What the verify can conclude on its own | |---|---|---| | **E01** | yes | stored and computed values match, or they do not | | **SMART** (`.S01`) | yes | the same as E01 | | **Raw (dd)** | no, the file is only the bytes | computes MD5 and SHA-1; you compare them with the acquisition record | | **CD or DVD source** | no hashes are generated | nothing; the guide says these images are not verified | The raw case catches people out. The computed values are correct, but nothing inside a raw file says what they should be, so the comparison is against the hashes recorded when the image was made: the Image Summary, the copied verify lines, the case notes. ## What a match proves, and what it does not A match is narrow and strong. It shows the image file has not changed since its hash was taken at acquisition. It does **not** show: - **that every sector was read.** A failing source can produce a clean match and a non-zero bad-sector count at the same time; the hash covers what was read, and the unread sectors are a limit you report. - **that the source was untouched before or during the read.** FTK Imager does not stop an operating system writing to a drive attached without a hardware write blocker; the guide requires one. - **that the image equals the drive today.** For that, run Verify Drive/Image on the drive itself as well; the guide describes using FTK Imager's hash to show that the image hash and the drive hash match after the image is created. ## When verification fails or cannot run Common product-side causes before anyone concludes the evidence is bad: 1. **Segments in different folders.** If a destination fills, FTK Imager asks for a new folder and continues there. The guide says all segments must then be placed together in one folder before the image is verified or added to a case. 2. **Damage in a later copy.** A segment truncated or altered while being copied gives a different hash; verify the copy at the original destination, or re-copy and verify again, before treating the image as changed. 3. **A converted AD1.** A v4 AD1 converted to v3 gets different verification hashes, because v4 hashes its GUID tables; record the conversion instead of treating the change as tampering. 4. **A format with no hashes.** CD and DVD images are not hashed, so there is nothing to verify; hash the resulting files yourself and say when you did it. ## Making it re-checkable by someone else Hand over the image, the copied Verify Results lines and the Evidence Item Information text file written beside it. A second examiner can repeat **Verify Drive/Image**, or start FTK Imager with the `/VerifyImage` switch and the image path, and must get the same MD5 and SHA-1. That repeatability, not the green match itself, is what the hashes are for.

  • FTK Imager verifies your raw (dd) image and shows MD5 and SHA-1 but no match line. Is the image unverified?
    Not necessarily. A raw file is only the bytes and stores no hash, so the window has nothing inside the image to compare against. Compare the computed MD5 and SHA-1 with the hashes recorded when the image was made: the Image Summary, the verify lines you copied at acquisition, the evidence form. Equal values verify it; record that the comparison was made against the record, not inside the file.
  • Your E01 was written across two destination drives because the first one filled up. How do you verify it?
    FTK Imager prompts for a new destination folder when the first runs out of space and continues writing there. Before verifying, copy every segment into one folder, as the guide requires before an image is verified or added to a case, then run Verify Drive/Image on the first segment. Note in your records where each segment was first written.
  • How can a second examiner re-check your FTK Imager image without trusting your screenshots?
    They load the image and run Verify Drive/Image themselves, or launch FTK Imager with the `/VerifyImage` switch and the image path. They should obtain the same MD5 and SHA-1 you recorded; for an E01 or SMART image the window also shows whether the stored hash matches. Their result, not yours, is the independent check.

  • A matching verify proves the original drive was never altered.
  • FTK Imager's verification also reports a SHA-256 value.
  • A raw (dd) image stores its own hash inside the file.
  • Bad sectors do not matter once the hashes match.
  • Every image FTK Imager makes, CD and DVD included, is hashed and verified.
  • The verify step write-protects the source drive while it reads.
open as a page

When FTK Imager's Create Disk Image wizard asks for an image type, how do you choose between Raw (dd), SMART, E01 and AFF?

level: middleimportance: must knowfreq 40%

basics

~20 s

E01 is the usual choice: it compresses, splits into fragments and stores its own hash. Raw (dd) is uncompressed, needs full source space and carries no hash. SMART caps segments near 2 GB; AFF is the type FTK Imager can password-encrypt with AFF Encryption.

open as a page

What is an AD1 custom content image in FTK Imager, and when is it the wrong evidence to collect?

level: middleimportance: should knowfreq 28%

basics

~20 s

An AD1 is FTK Imager's logical image of files you selected, by hand or with wild-card filters, with their paths and metadata. It holds no partition layout or unselected space, so it is wrong whenever later questions may reach beyond the selection.

open as a page

When you mount an evidence image with FTK Imager's Image Mounting, what do the mount types and mount methods change?

level: middleimportance: should knowfreq 24%

basics

~20 s

Mount type sets how the image appears: physically as a PhysicalDrive device, logically as drive letters, or both. Mount method sets access: Block Device/Read Only, File System/Read Only, or Block Device/Writable, whose writes go to a cache file, never the image.

open as a page

With FTK Imager, how do you capture a running workstation's memory and then its disk, and what does the tool not protect?

level: seniorimportance: should knowfreq 35%

basics

~20 s

Run FTK Imager from portable media instead of installing it, write Capture Memory's output to external media, then image the disk with verification on. The tool leaves a footprint and is not a write blocker: an attached drive still needs a hardware one.

open as a page

For a team standardising on free FTK Imager, what should the acquisition standard fix, and when must it require something more?

level: principalimportance: should knowfreq 18%

basics

~20 s

Fix the defaults: E01, post-creation verify, Evidence Item Information, a hardware write blocker, and MD5 plus SHA-1 as the only verification hashes. Require more for decryption or targeted collection (Pro at 8.3), phones, failing drives, or a SHA-256 mandate.

open as a page