collecting volatile data from a running system.
Assists in building a timeline of events and identifying possible users.
Usually followed by dead/static acquisition.
Captures system data: config, date/time, uptime, processes, command history, open files, clipboard, DLLs, registers, CPU.
Captures network data: routing tables, ARP cache, connections, configuration.
Useful for:
| 1 | Registers, cache |
| 2 | Routing table, ARP cache, processes, memory |
| 3 | Temporary file systems |
| 4 | Disk |
| 5 | Remote logging/monitoring data |
| 6 | Physical configuration, network topology |
| 7 | Archived data |
collecting data from a powered-off system.
Involves imaging storage devices such as hard drives, DVDs, USBs, flash cards, smartphones.
Common data recovered: emails, documents, web activity, spreadsheets, slack space, unallocated space, deleted files.
| Temporary files |
| System registries |
| Event / system logs |
| Boot sectors |
| Web cache & cookies |
| Hidden files |
5 minsYou are called to a scene where investigators found these systems:
Discuss in a group:
Bit-stream acquisition: creates a bit-by-bit copy of the entire suspect drive (all sectors, clusters, ambient data).
| 1. Disk-to-Image File | Most common method. Creates one or more image files that are exact replicas of the suspect drive. | ProDiscover, EnCase, FTK, Sleuth Kit, X-Ways |
| 2. Disk-to-Disk | Used when disk-to-image is not possible. Clones suspect drive directly to another disk (aligning cylinders/tracks). | EnCase, Tableau Forensic Imager |
Logical Acquisition
Sparse Acquisition

| Format | Key Features | Pros | Cons |
|---|---|---|---|
| 1. RAW | Bit-by-bit copy, no compression | Fast, widely supported | Large file size, no metadata |
| 2. Proprietary | Tool-specific (e.g., EnCase, FTK) | Compression, segmentation, metadata support | Not always compatible across tools, slower searches |
| 3. AFF (Advanced Forensics Format) | Open-source, customisable, supports metadata | Cross-platform, supported by many tools (Xmount, SleuthKit, FTK) | Less common than RAW/Proprietary |
![]()
According to ACPO
|
|
|
|
DON’T: shut down the system before collecting live evidence
DON’T: trust tools on the suspect system - use your own
DO:
Volatile evidence disappears once power is lost.
Hardware Write Blocker
Software Write Blocker
|
|
dd Example:
dd if=/dev/hda of=/dev/image.dd
if = input (e.g., /dev/hda)of = output (e.g., image.dd)conv=noerror - ignore errorsconv=notrunc - don’t truncate outputdcfldd: improved dd with hashing + progress display.
|
|
When the hardware or software does not work, or a failure occurs during the acquisition

Take hash values before and after the investigation to confirm no alteration.
You must image evidence from three different cases. Research or recall which method and format you would use - and why.
| Case | Recommended Method | Format | Reason |
|---|---|---|---|
| 1. 500 GB laptop HDD (Windows) | ? | ? | ? |
| 2. 64 GB USB drive (Linux) | ? | ? | ? |
| 3. Cloud storage snapshot | ? | ? | ? |
Hints:
dd, dcfldd, FTK Imager, or X-Ways.Once the image is collected, the next task is to prepare it for examination.
Investigators typically use the following combinations:
dd image - examined on Linux with tools like dd, dcfldd, Sleuth Kit
E01 (EnCase) image - examined on Windows with tools like FTK, EnCase, X-Ways
APFS image - examined on Mac with forensic tools supporting APFS
- **Forensic process model**
- Identification - Preservation - Collection - Examination - Analysis - Reporting - Presentation.
- Alert if source > destination.
