DIGITAL FORENSICS: FOLLOW THE EVIDENCE
Acquisition · Filesystem · Windows artifacts · Memory (Volatility 3) · Timelines (Plaso) · Network & logs · Mobile & cloud · Reporting
Forensic Principles & Process
- Locard’s exchange principle is the philosophical core of forensics: every interaction leaves a trace, and your job is to find and interpret it.
- The order of volatility dictates acquisition sequence - capture RAM, network state and running processes before you ever touch disk.
- Chain of custody is a documented, unbroken record of who handled evidence, when, and why - break it and your evidence is inadmissible.
- Forensic soundness means working on verified copies, using write blockers, and proving with hashes that the original was never altered.
- Admissibility (Daubert, Frye, ISO 17025) depends on validated tools, repeatable method and a defensible documented process - not just a correct answer.
- Anti-forensics (timestomping, wiping, encryption, log tampering) is now routine; the examiner must expect it and hunt for the absence of evidence.
Think of the watchman's gate register at an estate, backed by the CCTV above it. When something goes missing, the register tells you who entered, when, and who signed them in; the camera footage shows what actually happened. Digital forensics is exactly this for computers — reconstructing who did what and when from the traces left behind. And there is one golden rule the estate learned the hard way: if a guard scribbles over the register or someone edits the footage, it is worthless in a baraza or a court. The evidence only counts if you can prove nobody tampered with it.
► What Digital Forensics Actually Is
Digital forensics is the application of scientific method to digital evidence so that findings survive scrutiny - in a courtroom, a disciplinary hearing, an insurance dispute or an internal incident review. The discipline splits into closely related sub-fields: disk (dead-box) forensics, memory forensics, mobile forensics, network forensics, cloud forensics and multimedia forensics. DFIR - Digital Forensics and Incident Response - fuses the evidentiary rigour of forensics with the speed of incident response, because in a live breach you rarely have the luxury of a pristine lab and unlimited time.
The examiner's mindset is adversarial toward their own conclusions. You do not set out to prove a theory; you set out to test every reasonable hypothesis against the artifacts and let the evidence falsify the wrong ones. A single artifact rarely proves anything on its own - Prefetch shows a program ran, but not who ran it or why. You corroborate, cross-reference and build a weight-of-evidence case where multiple independent artifacts point to the same conclusion.
► Locard's Exchange Principle
Edmond Locard, a pioneer of physical forensic science, observed that "every contact leaves a trace." In the digital world this is almost absurdly true. Running a program writes a Prefetch file, updates the Amcache registry hive, touches the filesystem $MFT, and may leave an entry in the SRUM database and the UserAssist key. Plugging in a USB device writes to the SYSTEM and software hives, the setupapi logs and the Windows event log. Opening a document creates an LNK shortcut, a JumpList entry and a Recent item. Your task is to recognise which traces a given action produces, and - just as importantly - to notice when an expected trace is missing, because absence is itself evidence of tampering.
► The Order of Volatility
RFC 3227 codifies the order in which evidence should be collected, from most to least volatile. Memory and ephemeral state vanish on power-off; disks persist. If you pull the power to "preserve" a machine you destroy every piece of volatile evidence - running malware, decryption keys, network connections, clipboard contents and injected code that exists only in RAM. Conversely, if you fumble around a live system you alter timestamps and overwrite slack. The order of volatility resolves the conflict: capture the most volatile first.
| Priority | Evidence source | Lifetime | Capture method |
|---|---|---|---|
| 1 | CPU registers, cache | Nanoseconds | Generally not captured |
| 2 | RAM (processes, keys, network, clipboard) | Until power-off | winpmem, DumpIt, LiME, AVML |
| 3 | Network state, ARP, routing, sockets | Seconds to minutes | netstat, ss, arp -a |
| 4 | Running processes, loaded modules | Until reboot | Live triage (KAPE, Velociraptor) |
| 5 | Disk (filesystem, slack, unallocated) | Persistent | dd, dc3dd, FTK Imager, E01 |
| 6 | Remote logs, archival backups | Long term | Log pull, legal request |
| 7 | Physical config, media labels | Static | Photography, notes |
► Chain of Custody
Chain of custody is the documented, continuous record of everyone who handled a piece of evidence, from seizure to presentation. Every transfer is logged: who had it, when, what they did and why. A single unexplained gap lets opposing counsel argue the evidence was altered or substituted, and a judge may exclude it entirely. Each item gets a unique exhibit number, is sealed in tamper-evident packaging, and is tracked on a custody form. For digital evidence the hash of the acquired image is recorded at seizure and re-verified at every stage, so the chain is not just a signature trail but a cryptographic one.
Exhibit: GN-2026-0042-HDD1 (Seagate 1TB, S/N 5XW3QZ8K) Seized: 2026-11-03 09:14 UTC by J. Mensah, warrant #2026-118 Acquired: 2026-11-03 11:02 UTC image GN-0042-HDD1.E01 sha256: 9f2c...e41a (verified against source) Transfers: 2026-11-03 11:40 evidence locker A-7 (seal 00318) J. Mensah 2026-11-04 08:20 examiner bench 2 (seal broken) A. Owusu 2026-11-04 17:55 evidence locker A-7 (seal 00412) A. Owusu Hash re-verified at each custody change: MATCH
► Write Blockers and Forensic Soundness
Forensic soundness is the principle that your examination must not alter the original evidence, and that you can prove it. The physical guarantee is the write blocker - a hardware or software device placed between the suspect drive and your workstation that passes read commands through but silently drops or rejects every write command. Simply mounting a disk on a modern OS can update last-access times, replay a dirty journal, or auto-run indexing services, so you never attach suspect media directly. Hardware write blockers (Tableau, WiebeTech) are preferred for court work; software blockers and read-only loopback mounts suffice for triage when documented. The proof of soundness is the hash: compute it on the source before acquisition, on the image after, and they must match.
► Legal Admissibility
A technically correct finding is worthless if a court will not hear it. In US federal practice the Daubert standard asks whether a technique is testable, peer-reviewed, has a known error rate, and is generally accepted; older Frye jurisdictions ask only about general acceptance. Internationally, ISO/IEC 17025 accreditation of the lab and ISO/IEC 27037 guidance on handling digital evidence carry weight. Practically this means you use validated tools (NIST's Computer Forensics Tool Testing program tests imagers and carvers), you document every step so the analysis is repeatable by an independent examiner, and you can explain in plain language what each artifact means and how confident you are.
► Anti-Forensics: Expecting an Adversary
Modern subjects fight back. Timestomping rewrites MACB timestamps so a malicious binary looks years old; full-disk encryption (BitLocker, LUKS, FileVault) renders a powered-off image useless without the key, which is one more reason to capture RAM while the machine is live; secure-delete tools and SSD TRIM destroy unallocated data; log cleaning (wevtutil cl, shred of auth.log) erases the obvious trail. The experienced examiner treats anti-forensics as a signal, not a dead end. A file whose $STANDARD_INFORMATION timestamps predate its $FILE_NAME timestamps is almost certainly timestomped. A conspicuously empty Security event log on a server that should be noisy is itself an indicator of compromise. You hunt for the shadow the adversary forgot to erase - a Prefetch file for the wiping tool, a USN journal entry, a VSS snapshot taken before the cleanup.
- Locard’s exchange principle is the philosophical core of forensics: every interaction leaves a trace, and your job is to find and interpret it.
- The order of volatility dictates acquisition sequence - capture RAM, network state and running processes before you ever touch disk.
- Chain of custody is a documented, unbroken record of who handled evidence, when, and why - break it and your evidence is inadmissible.
- Forensic soundness means working on verified copies, using write blockers, and proving with hashes that the original was never altered.
- Admissibility (Daubert, Frye, ISO 17025) depends on validated tools, repeatable method and a defensible documented process - not just a correct answer.
- Anti-forensics (timestomping, wiping, encryption, log tampering) is now routine; the examiner must expect it and hunt for the absence of evidence.