What it actually is
Digital forensics is the discipline of recovering, preserving, analyzing, and presenting digital evidence in a way that survives legal scrutiny.
It applies to computers, phones, cloud accounts, network logs, surveillance video, and increasingly to vehicles and IoT devices.
The deliverable is not "I looked at it."
The deliverable is a written report that records what was done to each device and when, so the court can decide what to admit.
The phases of an actual case
1. Intake and preservation
Before anyone touches the device, we document its state with photos, its location, who handed it over, when, and in what condition.
The device is then imaged where it is, in person or remotely, or transported under sealed evidence custody. A drive imaged on-site goes through a forensic write blocker, which prevents any modification.
The original device is preserved untouched; all subsequent work happens against the forensic image.
2. Hashing
Before and after imaging, we calculate cryptographic hashes (SHA-256, MD5) of the device and the image.
Matching hashes prove the image is bit-for-bit identical to the original.
This is the foundation of admissibility. Without it, opposing counsel can argue the evidence was altered.
3. Artifact analysis
We parse the image with forensic tools (Autopsy, custom tooling, and, when a matter calls for it, Cellebrite, Magnet Axiom, and FTK through our licensed partner network) to extract:
- Deleted files and free-space remnants
- Browser history, including private/incognito sessions where artifacts persist
- Application data such as messages, photos, location history, and transaction logs
- System logs such as power events, USB connections, and network associations
- Cloud sync artifacts showing what synced when, and from which device
- Anti-forensic activity such as wipers, secure-delete usage, and timestomping
4. Timeline reconstruction
Most cases hinge on timeline.
Did message X arrive before file Y was deleted?
Was the device in location Z at time T?
We assemble a master timeline correlating events across multiple artifact sources, surfacing inconsistencies that suggest user behavior or suggest evidence has been tampered with.
5. Reporting
The report is written for the audience: a court, an attorney, a regulator, or in consumer cases, the client themselves.
It includes:
- Statement of qualifications (the certifications behind the examiner's opinion)
- Methodology, with what tools, what versions, and what configurations
- Chain of custody, with every hand-off documented
- Findings stated factually, with citations to specific artifacts
- Limitations, covering what we could not determine and why
- Exhibits such as screenshots, hash records, and raw data references
6. Testimony (when needed)
For matters going to deposition or trial, the investigator becomes a qualified expert witness, voir dired, cross-examined, and expected to defend every methodology choice.
Reports written without that eventual scrutiny in mind do not survive it.
What separates real forensics from "tech consulting"
- Write blockers. Imaging a drive without one risks changing the original. A phone usually cannot be write-blocked, so the extraction method is documented instead.
- Documented chain of custody. Names, signatures, timestamps for every hand-off.
- Tool licensing. Widely used, independently tested forensic tools are expensive, and what the court weighs is whether the method was reliable and reliably applied.
- Practitioner credentials. GCFE, GCFA, EnCE, CCE, CFCE. They help show the knowledge, skill and training the court weighs when it qualifies an expert.
- Honest scope. A real forensic practice will tell you what they cannot determine. Anyone who promises certainty before looking at the evidence is selling something else.
Common case types we run
- Personal forensics for stalkerware, account compromise, and evidence preservation in protective-order matters
- Attorney-led litigation support for divorce, custody, IP theft, and employment disputes
- Incident investigation for ransomware, BEC, and insider data theft, establishing what happened and preserving the evidence
- Insider threat and fraud for financial crimes, sabotage, and exfiltration
Sources
- National Institute of Standards and Technology, SP 800-86, Guide to Integrating Forensic Techniques into Incident Response, 2006. https://csrc.nist.gov/pubs/sp/800/86/final
- Scientific Working Group on Digital Evidence (SWGDE), Best Practices for Digital Evidence Collection (18-F-002-2.0), 2025. https://www.swgde.org/documents/published-complete-listing/18-f-002-2-0/
- National Institute of Standards and Technology, NIST IR 8354, Digital Investigation Techniques: A NIST Scientific Foundation Review, 2022. https://nvlpubs.nist.gov/nistpubs/ir/2022/NIST.IR.8354.pdf
- Cornell LII, Federal Rules of Evidence, Rule 901. https://www.law.cornell.edu/rules/fre/rule_901
- Cornell LII, Federal Rules of Evidence, Rule 902. https://www.law.cornell.edu/rules/fre/rule_902
- Cornell LII, Federal Rules of Evidence, Rule 702. https://www.law.cornell.edu/rules/fre/rule_702















