Study guide
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager
Computer Hacking Forensic Investigator CHFI 312-49
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Foundations of Digital Forensics & Cybercrime Investigation
1.1 Cybercrime Classifications, Forensic Science Principles & Legal Admissibility 1.2 RFC 3227 Order of Volatility, Live vs. Dead Acquisition & Forensic Readiness 1.3 Indicators of Compromise (IoCs), Cyber Attribution & Threat Intelligence 1.4 AI-Assisted Forensics, GitOps, Automation/Orchestration & Forensics-as-a-Service (FaaS)
2 Chapter 2: Modern Forensic Environments & Emerging Threats
2.1 Fileless Malware, In-Memory Execution & Living-off-the-Land (LotL) 2.2 IoT & Operational Technology (OT/SCADA) Forensic Fundamentals 2.3 Dark Web, Tor Network, Onion Routing & Hidden Services Forensics 2.4 Blockchain Transactions, Cryptocurrency Tracing & Digital Asset Investigations
3 Chapter 3: Legal Frameworks, Search Warrants & Evidence Rules
3.1 Federal Rules of Evidence (FRE 702, 901, 902, 1001-1003) & Daubert/Frye Standards 3.2 Fourth Amendment, Warrant Exceptions, Workplace Search & Consent Protocols 3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines 3.4 Cybercrime Statutes, Privacy Compliance, CAN-SPAM & International Cooperation
4 Chapter 4: eDiscovery, Chain of Custody & Professional Ethics
4.1 Electronic Discovery Reference Model (EDRM) & Legal Spoliation Holds 4.2 Chain of Custody Documentation, Evidence Packaging & Tamper-Evident Handling 4.3 Expert Witness Testimony, Report Writing Standards & EC-Council Code of Ethics
5 Chapter 5: Storage Architecture, Boot Sequences & Media Forensics
5.1 Storage Media Architecture: Sectors, Clusters, RAM/File Slack & Unallocated Space 5.2 Partition Tables & Boot Structures: MBR, GPT, VBR, BIOS vs. UEFI Secure Boot 5.3 RAID Reconstruction (RAID 0, 1, 5, 6, 10) & SSD Forensic Challenges (TRIM, Wear Leveling)
6 Chapter 6: Windows File Systems: NTFS & FAT
6.1 NTFS Architecture: Master File Table ($MFT) Record Structure & Attribute Headers 6.2 NTFS Artifacts: Alternate Data Streams (ADS), Volume Shadow Copies (VSS) & $LogFile 6.3 FAT12/16/32 and exFAT Architecture, Directory Entries & File Deletion Mechanics
7 Chapter 7: Non-Windows File Systems & File Signatures
7.1 Linux File Systems: ext2/ext3/ext4 Inode Architecture, Superblocks & Journaling Forensics 7.2 macOS File Systems: HFS+ and Apple File System (APFS) Architecture & Snapshots 7.3 File Signatures, Magic Bytes, Hex Headers/Footers & File Carving Techniques
8 Chapter 8: Investigation Lifecycle, Lab Setup & First Response
8.1 Forensic Laboratory Accreditation: ISO/IEC 17025 Standards & Hardware/Software Controls 8.2 First Responder Duties: Crime Scene Containment, Electronic Triage & Volatile Triage 8.3 Physical Evidence Packaging, Anti-Static/Faraday Protection & Transport Security
9 Chapter 9: Forensic Acquisition & Verification Methodology
9.1 Hardware and Software Write-Blockers: Operational Validation & Bridge Verification 9.2 Bit-Stream Disk Imaging, Physical vs. Logical vs. Targeted Acquisition Methodology 9.3 Forensic Image Formats (RAW/DD, E01, AFF) & Cryptographic Hashing Verification (MD5, SHA-256)
10 Chapter 10: Anti-Forensics Techniques & Countermeasures
10.1 Steganography Detection: Spatial/Frequency Domain Steganalysis & Hidden Carrier Extraction 10.2 Timestomping Countermeasures: Comparing $STANDARD_INFORMATION vs $FILE_NAME Timestamps 10.3 Secure Wiping, Degaussing, File Shredding Countermeasures & Residual Artifact Recovery
11 Chapter 11: Windows Operating System Forensics
11.1 Windows Registry Forensics: SYSTEM, SOFTWARE, SAM & NTUSER.DAT Hive Analysis 11.2 Execution Artifacts: Prefetch (.pf), Shimcache (AppCompatCache), Amcache.hve & UserAssist 11.3 User Activity Artifacts: ShellBags, LNK Shortcut Files, Jump Lists & Recycle Bin ($I/$R) 11.4 Windows Event Log Forensics: Security Audit IDs (4624, 4625, 4688, 4720, 7045) & EVTX Parsing
12 Chapter 12: Memory Forensics & Malware Analysis
12.1 Volatile Memory Acquisition: RAM Capture, Crash Dumps, Hiberfil.sys & Pagefile.sys 12.2 Memory Analysis with Volatility 3: pslist, pstree, malfind, netscan & Vadinfo 12.3 Static Malware Triage: Strings, PE Headers, Import Tables, Hashes & YARA Rule Matching 12.4 Dynamic Malware Analysis: Sandboxing, Process Monitor (Procmon), Regshot & Network Callouts 12.5 .NET Managed Malware Analysis & the GOOTLOADER Fileless Infection Chain
13 Chapter 13: Network, Web Application & Email Forensics
13.1 Network Forensics: PCAP Analysis, Protocol Dissection, Snort/Suricata & Flow Analysis 13.2 Web Server Forensics: Apache/IIS Access Logs, SQL Injection, XSS & Web Shell Detection 13.3 Email Forensics: RFC 5322 Headers, Authentication (SPF, DKIM, DMARC) & Mbox/PST Extraction 13.4 SIEM Event Correlation, Cross-Source Timeline Analysis & Super-Timeline Construction 13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force 13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH 13.7 Wireless Network Forensics: Rogue APs, Evil Twins, MAC Spoofing, Deauthentication & Jamming
14 Chapter 14: Mobile, Cloud & IoT Forensics
14.1 Mobile Device Forensics: Manual, Logical, File System & Physical Extraction (Android/iOS) 14.2 Mobile Artifact Analysis: Call Logs, SMS/Chat SQLite Databases, Location Data & Plists 14.3 Cloud Forensics: AWS CloudTrail, Azure Activity Logs & Multi-Tenant Evidence Collection 14.4 IoT Forensics: UART/JTAG Physical Interfaces, Firmware Extraction & Sensor Telemetry
15 Chapter 15: Commercial & Open-Source Forensic Suites
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager 15.2 Open-Source Forensic Platforms: Autopsy, The Sleuth Kit (TSK) & SIFT/CAINE Workstations 15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite
16 Chapter 16: Analysis Toolkits, Python Scripting & Tool Validation
16.1 Reverse Engineering & Password Cracking: Ghidra, IDA Pro, Hashcat & John the Ripper 16.2 Python for Digital Forensics: Parsing Raw Artifacts, Custom Scapy Scripts & Evidence Automation 16.3 Forensic Tool Testing & Validation: NIST CFTT Methodology, ISO/IEC 17025 Standards & Daubert Compliance
17 Chapter 17: Database Forensics & Web Application Firewalls
17.1 MySQL Forensics: Internal Architecture, Data Directory, Information Schema & Utility Programs 17.2 SQL Server Forensics: SSMS, ApexSQL, SQLCMD Transaction-Log Collection, Plan Cache & Trace Files 17.3 Web Application Firewall (WAF) Architecture, Audit Logs, Benefits & Limitations
18 Chapter 18: Social, Virtualized, Multimedia & Browser Investigations
18.1 Social Media, Social Engineering, Insider Threat & Identity Theft Forensics 18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications 18.3 Multimedia Forensics: Image, Audio & Video Authentication, EXIF, PRNU and Deepfake Detection 18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager
Key Takeaways Explain This Topic AI
OpenText EnCase Forensic utilizes flat-file evidence caches and proprietary .E01 (Expert Witness Compression Format) and .Ex01 formats, featuring embedded chunk CRCs, metadata headers, and acquisition hashes.
.Ex01 introduces major structural upgrades over legacy .E01, including mandatory GUID tracking, native AES-256 encryption, LZ/bzip2 compression, and SHA-256 hashing alongside MD5.
AccessData/Exterro Forensic Toolkit (FTK) is built upon a PostgreSQL relational database back-end, providing crash resilience, ACID compliance, and concurrent multi-examiner case collaboration.
FTK pre-indexes evidence at ingestion using the multi-threaded dtSearch engine, enabling sub-second keyword, fuzzy, stemming, and phonetic searches, while Distributed Processing Engines (DPE) offload heavy parsing across network nodes.
AccessData FTK Imager provides bit-stream physical and logical acquisition, live RAM capture, write-blocked virtual image mounting, and command-line execution via ftkimager for headless triage automation.
Last updated: September 2026
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK & FTK Imager
Quick Answer: Commercial digital forensics platforms represent the primary investigative workhorses in corporate, legal, and law enforcement environments. OpenText EnCase Forensic centers on the proprietary Expert Witness Format (.E01 / .Ex01) , utilizing chunk-level 32-bit CRCs, an Evidence Processor , and the C++/Java-like EnScript language for extensibility. In contrast, Exterro Forensic Toolkit (FTK) employs an enterprise-grade PostgreSQL relational database back-end to ensure crash resilience and enable concurrent multi-examiner collaboration, leveraging the multi-threaded dtSearch engine for comprehensive pre-indexing at ingestion and Distributed Processing Engines (DPE) for scalable workload clustering. Complementing both is FTK Imager , a free, standalone utility providing bit-stream disk acquisition, live RAM capture, read-only drive mounting, and command-line automation via ftkimager .
OpenText EnCase Forensic Architecture
Originally developed by Guidance Software and acquired by OpenText, EnCase Forensic has served as an industry and judicial standard for computer investigations for over two decades. Its core design philosophy prioritizes strict evidence preservation, defensible auditability, and extensive scripting extensibility.
Platform Architecture & Processing Workflow
EnCase operates through a modular client architecture centered on the Evidence Processor : [Evidence Source (.E01/.Ex01/Raw)]
- │
- ▼
- ┌───────────────────────┐
- │ Evidence Processor │ ──> Hash Calculation (MD5/SHA-1/SHA-256)
- │ (Multi-Core Worker) │ ──> File Signature & Extension Mismatch Analysis
- └───────────────────────┘ ──> Protected / Encrypted File Identification
- │ ──> Email & Compound File Extraction (PST/OST)
- ▼ ──> Artifact Parsing (Registry, Event Logs, Prefetch)
- ┌───────────────────────┐ ──> Unallocated Space Carving
- │ Case Evidence Cache │
- │ (Flat-File DB / Index)│
- └───────────────────────┘
- │
- ▼
- ┌───────────────────────┐
- │ Examiner GUI & Reports│ <── EnScript Automation & Bookmarks
- └───────────────────────┘
Evidence Acquisition & Addition: Physical media is acquired into forensically sound container files ( .E01 or .Ex01 ). When added to a case, EnCase reads the image in a strict read-only state.
Evidence Processor Pipeline: The examiner configures automated processing tasks. The Evidence Processor parses compound files (ZIP, PST, OST), generates cryptographic hashes, compares file headers against known file signatures, carves deleted files from unallocated space, and indexes searchable text.
Evidence Cache: Extracted metadata, parsed artifacts, and indexes are stored in local flat-file databases in the examiner's configured Evidence Cache directory. Unlike relational database engines, EnCase maintains dedicated proprietary cache structures per case.
Case Management: Cases are tracked using .case (legacy) or .cbkp (case backup/project) files containing pointer references, folder hierarchies, search results, tags, and bookmarks.
EnCase Evidence File Formats: .E01 vs. .Ex01
The Expert Witness Format (EWF) is the de facto standard forensic container format in modern investigations. Understanding its internal sector mapping, chunk allocation, and cryptographic safeguards is critical for CHFI certification. +-------------------------------------------------------------------------+
- | LEGACY EXPERT WITNESS FORMAT (.E01) LAYOUT |
- +-------------------------------------------------------------------------+
- | Header (Case #, Examiner, Evidence #, Acquisition Date, Drive Geometry) |
- +-------------------------------------------------------------------------+
- | Chunk 0: 64 Sectors (32 KB Data) | 32-bit CRC Checksum |
- +-------------------------------------------------------------------------+
- | Chunk 1: 64 Sectors (32 KB Data) | 32-bit CRC Checksum |
- +-------------------------------------------------------------------------+
- | ... | ... |
- +-------------------------------------------------------------------------+
- | Chunk N: 64 Sectors (32 KB Data) | 32-bit CRC Checksum |
- +-------------------------------------------------------------------------+
- | Table of Offsets (Array of Chunk Pointer Offsets in Container) |
- +-------------------------------------------------------------------------+
- | Footer: MD5 Hash of Entire Original Bitstream |
- +-------------------------------------------------------------------------+
- Detailed Technical Comparison: .E01 vs. .Ex01
- Architectural Attribute Legacy Format (.E01) Enhanced Format (.Ex01)
- Primary Purpose Standard physical/logical disk imaging High-security, enterprise-scale imaging
- Chunk Block Size 64 sectors (32 KB uncompressed) Configurable (up to 128 KB+ chunks)
- Chunk Integrity Check 32-bit Cyclic Redundancy Check (CRC) per chunk 32-bit Adler/CRC or SHA-256 block hash
- Acquisition Hashes MD5 (mandatory), optional SHA-1 MD5, SHA-1, and SHA-256 simultaneously
- Compression Algorithm Deflate / zlib Bzip2 or LZMA (faster, higher ratio)
- Native Encryption Password protection (weak XOR/Blowfish) AES-256 full container encryption
- Unique Identifier Internal case number / serial metadata Globally Unique Identifier ( GUID ) embedded
- Logical Counterpart .L01 (Logical Evidence File) .Lx01 (Logical Evidence File with AES)
Important
If an .E01 file suffers physical bit corruption during transit or storage, only the specific 64-sector chunk whose 32-bit CRC fails will report an error. The remaining chunks retain valid CRC checksums and can still be parsed. The footer MD5 hash, however, will fail overall image verification because the reconstructed bitstream no longer matches the original pre-acquisition hash.
EnScript Scripting Language
EnScript is OpenText EnCase's proprietary, object-oriented programming language. Structurally modeled after C++ and Java, EnScript empowers forensic examiners to automate repetitive analysis, build custom artifact decoders, query raw sector streams, and generate complex courtroom reports.
EnScript Object Model & Architecture
EntryClass: Represents a directory, file, or carved artifact in the evidence tree. Provides properties such as Name() , Extension() , LogicalSize() , Created() , Modified() , and Deleted() .
FileClass: Provides low-level, stream-oriented binary I/O access to the underlying sectors of an evidence item.
BookmarkClass: Programmatically creates bookmarks, assigns investigative comments, and categorizes findings into case reporting structures.
CaseClass: Represents the active case container, managing data sources, evidence processors, and global examiner settings. // Representative EnScript: Automated Search and Bookmarking
- class CustomTriageScriptClass : SceneClass {
- void Run(CaseClass c) {
- BookmarkClass rootBookmark = c.BookmarkRoot();
- ItemIteratorClass iter(c);
- while (EntryClass entry = iter.GetNextEntry()) {
- // Check for executable files located in temporary user directories
- if (entry.Extension().Compare("exe") == 0 && entry.FullPath().Contains("AppData\\Local\\Temp")) {
- BookmarkClass folder = rootBookmark.FindFolder("Suspicious Temp Binaries");
- if (!folder.IsValid()) {
- folder = rootBookmark.CreateFolder("Suspicious Temp Binaries");
- }
- folder.CreateBookmark(entry, "Executable identified in AppData Temp directory");
- }
- }
- }
- }
- Advanced EnCase Search & Analysis Features
File Signature Analysis: Matches the file header hex bytes against the file extension database (e.g., flagging a file named report.docx whose header starts with 4D 5A as an executable renamed to evade detection).
Hash Analysis (NSRL RDS): Integrates the National Software Reference Library Reference Data Set (NSRL RDS) to filter out millions of known, benign operating system files (known-good), and ingests custom threat intelligence hashes (known-bad).
Grep & Regular Expression Search: Built-in Grep engine parsing data units and unallocated space for credit card numbers, social security numbers, and email patterns using syntax such as \b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}\b .
AccessData / Exterro Forensic Toolkit (FTK)
Developed by AccessData (now Exterro), Forensic Toolkit (FTK) is an enterprise investigation suite designed for multi-examiner teams, massive datasets, and rapid automated triage. +-------------------------------------------------------------------------+
- | EXTERRO FTK DISTRIBUTED DATABASE ARCHITECTURE |
- +-------------------------------------------------------------------------+
- | |
- | ┌─────────────────────────────────────────────────────────────────┐ |
- | │ PostgreSQL Relational Database │ |
- | │ - Centralized evidence metadata, objects, and bookmarks │ |
- | │ - Multi-user concurrency, access controls, ACID transactions │ |
- | │ - Eliminates local flat-file index corruption │ |
- | └─────────────────────────────────────────────────────────────────┘ |
- | ▲ |
- | ┌─────────────────────────┼─────────────────────────┐ |
- | │ │ │ |
- | ▼ ▼ ▼ |
- | ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ |
- | │ Examiner 1 │ │ Examiner 2 │ │ Examiner 3 │ |
- | │ GUI Client │ │ GUI Client │ │ GUI Client │ |
- | └──────────────┘ └──────────────┘ └──────────────┘ |
- | │ │ │ |
- | └─────────────────────────┼─────────────────────────┘ |
- | ▼ |
- | ┌─────────────────────────────────────────────────────────────────┐ |
- | │ Distributed Processing Engines (DPE) │ |
- | │ Node 1: Carving Node 2: dtSearch Indexing Node 3: OCR │ |
- | └─────────────────────────────────────────────────────────────────┘ |
- +-------------------------------------------------------------------------+
- The PostgreSQL Database Back-End
While legacy tools rely on local flat files or memory-mapped index caches, FTK routes all case operations through an enterprise PostgreSQL relational database (formerly Microsoft SQL Server or Oracle):
Crash Resilience: Because data commits are managed by an ACID-compliant (Atomicity, Consistency, Isolation, Durability) database engine, an unexpected workstation shutdown or operating system crash does not corrupt the entire case file. Re-opening FTK restores the case state immediately.
Multi-User Collaboration: Multiple forensic examiners across a local network or WAN can connect to the same PostgreSQL back-end simultaneously. Examiner A can review email artifacts while Examiner B tags carved images and Examiner C drafts timeline bookmarks on the exact same evidence volume.
Centralized Data Storage: Object metadata, bookmark tags, processing status flags, and forensic annotations reside centrally in structured SQL tables rather than disconnected files on individual analysts' machines.
dtSearch Multi-Threaded Ingestion-Time Pre-Indexing
A defining technical differentiator of FTK is its integration of the dtSearch engine. Unlike tools that scan drive sectors during runtime searches, FTK performs complete pre-indexing at ingestion :
Every printable word, compound file string, metadata token, and carved text block is parsed, normalized, and written to a multi-threaded inverted index during initial processing.
Search Query Performance: Subsequent complex queries—including Boolean ( AND , OR , NOT , W/PARAGRAPH ), proximity, stemming, and regular expressions—execute in sub-second intervals across multi-terabyte datasets.
Stemming: Automatically identifies grammatical variations of root words (e.g., searching for embezzle matches embezzling , embezzled , and embezzlement ).
Fuzzy Searching: Uses adjustable Levenshtein distance metrics (from 1 to 9) to locate words containing minor spelling errors or OCR inaccuracies (e.g., matching contraband if OCR transcribed c0ntraband ).
Phonetic Searching: Matches words that sound alike based on Soundex algorithms (e.g., matching Smith and Smyth ).
Distributed Processing Engines (DPE)
To overcome computational bottlenecks caused by massive storage volumes, FTK supports Distributed Processing Engines (DPE) :
Standalone worker nodes are deployed across dedicated physical or virtual servers on the forensic network.
The central FTK server distributes computational tasks—such as Optical Character Recognition (OCR) , MD5/SHA-256 hashing, archive decompression (ZIP inside RAR inside ISO), photo classification, and unallocated space carving—across these worker nodes.
Workloads are parallelized, reducing evidence processing turnaround from several days to mere hours.
Visualization and Timeline Analysis
Social Network Analysis: Analyzes communication patterns across parsed email archives, SMS threads, and chat logs. Visualizes relationship matrices by generating interactive link-node graphs displaying communication frequency between individuals.
Interactive Timeline: Plots file system metadata changes (NTFS MACB timestamps), Windows Event Logs, and browser history into graphical histograms, exposing temporal clusters, intrusion timelines, and anti-forensics activity bursts.
AccessData FTK Imager & ftkimager CLI
FTK Imager is a lightweight, standalone forensic acquisition and preview tool distributed freely by Exterro. It is widely considered an indispensable first-responder utility. +-------------------------------------------------------------------------+
- | FTK IMAGER FUNCTIONAL CAPABILITIES |
- +-------------------------------------------------------------------------+
- | 1. Physical Disk Acquisition ──> Bit-stream image of entire drive |
- | 2. Logical Volume Acquisition ──> Bit-stream image of active partition |
- | 3. Custom Content Image (.AD1) ──> Targeted folders & triage metadata |
- | 4. Volatile RAM Acquisition ──> Uncompressed physical memory dump |
- | 5. Virtual Image Mounting ──> Read-only drive emulation in Windows |
- | 6. Image Format Conversion ──> RAW/DD <--> .E01 <--> .AFF |
- +-------------------------------------------------------------------------+
- Key GUI Capabilities
Physical vs. Logical Imaging:
Physical Drive: Captures the entire physical storage unit (MBR, GPT, partition tables, active volumes, unallocated space, and volume slack).
Logical Drive: Captures only the logical partition recognized by the operating system (e.g., C:\ ), omitting unallocated space outside the partition boundary.
Custom Content Image (.AD1):
AccessData's proprietary logical container format. Allows first responders to acquire specific critical directories (e.g., C:\Windows\System32\config , C:\Users\*\AppData ) while maintaining original file metadata, NTFS timestamps, and relative directory paths.
Live RAM Capture:
Safely captures volatile physical memory into a single flat binary file ( memdump.mem ).
Provides an optional checkbox to simultaneously copy the active Windows paging file ( pagefile.sys ).
Forensic Image Mounting:
Mounts forensic images ( .E01 , .raw , .vmdk ) as virtual Windows drives via an emulated software write-blocker, allowing third-party tools or analysts to explore evidence through Windows Explorer without altering source hashes.
Cryptographic Verification:
Computes MD5 and SHA-1 hashes before and after acquisition, recording sector counts and bad block counts in a generated text audit log ( image_name.txt ).
Command-Line Automation: ftkimager
In headless environments, incident response live USBs, or automated Linux triage scripts, the command-line utility ftkimager provides fast, scriptable acquisition: # Syntax for ftkimager acquisition
ftkimager <source_device> <destination_path> [options]
- # Example: Creating an E01 bit-stream image of physical drive 0 in Linux
- ftkimager /dev/sda /cases/case101/evidence/disk_sda \
- -e01 \
- -frag 2G \
- -compress 6 \
- -case-num "CHFI-2026-041" \
- -evidence-num "EV-01" \
- -description "Suspect Workstation SATA SSD" \
- -examiner "Lead_Investigator" \
- -verify :: Example: Windows batch script for automated physical acquisition
- ftkimager.exe \\.\PhysicalDrive0 D:\Evidence\Endpoint01 --e01 --frag 4G --verify --print-hash-ext
- Key ftkimager Command-Line Flags
--e01 : Instructs the utility to output into the Expert Witness Format ( .E01 ). If omitted, raw dd format is generated.
--frag <size> : Splits the image into chunks (e.g., 2G , 4G , 640M ) to prevent file size limitation errors on FAT32/exFAT destination drives.
--compress <0-9> : Sets compression level (0 = none, 9 = maximum compression; 6 is the standard default).
--verify : Mandates a post-acquisition verification pass, hashing the written chunks and comparing against the source.
--print-hash-ext : Displays raw MD5 and SHA-1 hashes directly in the console output stream upon completion.
Comparative Capabilities Matrix: EnCase vs. FTK vs. FTK Imager
Feature / Dimension OpenText EnCase Forensic Exterro FTK AccessData FTK Imager
Primary Architecture Workstation-centric / Evidence Processor Enterprise Client-Server Relational DB Lightweight Standalone Utility
Database Back-End Proprietary flat-file cache / SQLite PostgreSQL relational database None (in-memory / direct disk writes)
Text Indexing In-case indexing pass (post-processing) dtSearch pre-indexing during ingest No indexing capabilities
Multi-User Collaboration Case file locking (single active user) Concurrent multi-examiner access Single-user local utility
Scripting Extensibility EnScript (compiled C++/Java-like) Python API, Exterro Automation APIs Batch/bash scripting ( ftkimager )
Workload Distribution EnCase Enterprise / Endpoint agents Distributed Processing Engines (DPE) None (single host hardware)
Native Image Formats .E01 , .Ex01 , .L01 , .Lx01 .E01 , .Ex01 , .AD1 , Raw/DD .E01 , .AD1 , Raw/DD, SMART, AFF
Live Memory Capture Supported via EnCase Enterprise Agent Supported via FTK CLI / Agent Native GUI & CLI RAM Capture
Primary Use Case Deep evidentiary parsing, law enforcement High-volume corporate IR, multi-analyst First response, triage, disk imaging