- Atlas
- Computer Science
- Digital Forensics
Digital Forensics
Digital forensics is the practice of recovering and explaining what happened on computers, phones, networks, and online services, in a way that can stand up in a courtroom or a disciplinary hearing.
11 frameworks, from 1985 to today · Cybersecurity · Computer Science
- Computer Forensics 1985-2005
- Forensic Soundness and Chain of Custody 1995-Present
- Network Forensics 1998-Present
- Digital forensic process 2000-Present
- Malware analysis 2000-Present
- Timeline Reconstruction 2000-Present
- Live Forensics 2002-Present
- Anti–computer forensics 2005-Present
- Memory Forensics 2005-Present
- Mobile Device Forensics 2008-Present
- Cloud Forensics 2010-Present
Overview
Digital forensics is the practice of recovering and explaining what happened on computers, phones, networks, and online services, in a way that can stand up in a courtroom or a disciplinary hearing12. Its practitioners answer questions like: was this file deleted, and when? Who logged in from where? Was the machine infected, and what did the malware touch? What is at stake is evidence. A finding that cannot be shown to be accurate, complete, and unaltered is worth little when a person's liberty, a company's liability, or a nation's security depends on it. That demand—for answers that are both technically true and legally defensible—has shaped the field at every stage.
Mainframes, Time-Sharing, and the First Computer Evidence
Digital forensics grew out of ordinary computer operations1. In the 1960s and 1970s, mainframes and time-sharing systems kept logs of who used them and when, and auditors and investigators began reading those logs to reconstruct misuse. The U.S. Air Force and other large organizations developed procedures for examining magnetic tapes and disks. Early cases turned on simple artifacts: a log entry, a deleted record, a mismatch between what a system reported and what its storage held. The key realization was that a computer's own records could serve as evidence, but only if investigators could show they had not changed them.
The Personal Computer and the Birth of Computer Forensics
The 1980s changed the problem. Personal computers put storage in the hands of individuals, and crimes—fraud, theft of trade secrets, child exploitation—began to leave traces on hard drives. Investigators who had worked on mainframes now had to seize machines, image their disks, and search them. The discipline that emerged was called computer forensics: the examination of a single computer's storage12.
Two ideas defined it. The first was the forensic image: a bit-for-bit copy of a drive, made so that the original could be preserved untouched while analysis proceeded on the copy. The second was the hash value—a short mathematical fingerprint of a file or disk3. Hashing a drive before and after copying let an examiner demonstrate that the copy matched the original, and hashing individual files let examiners recognize known material without opening it. These techniques, refined through the late 1980s and 1990s, became the backbone of evidentiary integrity.
The field professionalized in the 1990s. The International Association of Computer Investigative Specialists (IACIS) formed in 1990, and the FBI established its Computer Analysis and Response Team in the mid-1990s. Early tools were largely homegrown scripts; commercial suites such as EnCase, released in the late 1990s, and later Forensic Toolkit (FTK) gave examiners a common interface for imaging, searching, and reporting. In 1995 the International Organization on Computer Evidence was founded to harmonize practice across countries, and a series of international conferences in the mid-1990s produced early principles for handling digital evidence.
Forensic Soundness and the Standards That Made It Auditable
As courts began to see digital evidence regularly, the question of forensic soundness became central: can the examiner show that the evidence was acquired, handled, and analyzed without alteration1? The answer was procedural. Investigators adopted a chain of custody—a documented record of every person who handled the evidence and every action taken on it14. They wrote write blockers, devices or software that prevent any write to the original medium during acquisition15. They hashed at every stage.
Standards bodies codified this. The Scientific Working Group on Digital Evidence (SWGDE), formed in the late 1990s under U.S. federal sponsorship, issued guidelines on imaging and handling16. The ISO/IEC 27037 standard, published in 2012, set international guidance for identifying, collecting, acquiring, and preserving digital evidence. Accreditation schemes for laboratories, modeled on forensic science generally, required documented methods and proficiency testing. The principle that emerged is often summarized as: the examiner must be able to show that what is presented is what was found.
The Process Model: From Seizure to Report
Alongside the tools came a way of describing the work itself. The digital forensic process model broke an investigation into stages—identification, preservation, acquisition, examination, analysis, and reporting—so that each could be documented, taught, and audited. Different models named the stages differently, but the logic was shared: preserve before you touch, examine before you interpret, and report what you did so another examiner could repeat it. This structure made digital forensics teachable as a discipline rather than a craft learned only on the job, and it gave courts and regulators a vocabulary for assessing whether an examination had been done properly.
Networks, Malware, and the Shift to Live Systems
Through the 1990s, forensics was mostly a matter of dead disks examined after the fact. Two developments broke that model. The first was network forensics: the examination of traffic captured as it crossed a network17. Intrusions, data exfiltration, and command-and-control communications left records in packet captures, firewall logs, and intrusion-detection alerts. Tools such as tcpdump and, later, Wireshark made it possible to reconstruct a session from captured packets. The problem network forensics solved was that a compromised machine's disk might tell you little about how an attacker entered or what they took; the network record could show both.
The second was malware forensics: the analysis of malicious code found on a system, to determine what it did and how8. Investigators moved from static inspection of files to observing malware in controlled environments—sandboxes and instrumented virtual machines—where its behavior could be recorded safely. This connected digital forensics to the separate craft of malware analysis, and it made the question "was this system compromised, and how?" answerable in technical detail8.
Both shifts pushed examiners toward live forensics: examining a running system rather than a powered-off disk1. A running machine holds encryption keys, active network connections, and processes that vanish on shutdown. The trade-off—that examining a live system alters it—forced the field to develop methods for capturing volatile state while documenting exactly what was done.
Timeline Reconstruction
A recurring task across all of these areas is timeline reconstruction: placing events in order1. Operating systems record timestamps for file creation, modification, and access; logs record logins and program launches; network captures record when packets moved. Examiners assemble these into a single chronology. The difficulty is that timestamps can be wrong, inconsistent across systems, or deliberately altered, and different sources may disagree. Building a defensible timeline means understanding each source's quirks and stating the uncertainty rather than smoothing it away. Timeline analysis became a distinct skill and a standard part of reporting, because the sequence of events is often the heart of a case.
Memory Forensics
As systems grew more complex and attackers learned to avoid leaving files on disk, examiners turned to memory forensics: the analysis of a computer's volatile memory (RAM) captured while the system was running9. Memory holds running processes, network connections, encryption keys, and fragments of malicious code that may never touch the disk—so-called fileless malware. The field's landmark tool, Volatility, released in 2007, gave examiners a framework for parsing memory images across operating systems. Memory forensics answered a problem disk forensics could not: how to find evidence of activity that existed only while the machine was on. It also raised new soundness questions, since capturing memory requires running software on the live system.
Mobile Devices
The spread of smartphones in the late 2000s created a new subfield. Mobile device forensics had to deal with devices that were locked, encrypted, constantly connected, and built on proprietary designs110. Early work focused on logical extraction—pulling data through the device's own interfaces—and on physical extraction of flash storage. Tools such as those from Cellebrite and Oxygen Forensics became standard, and the field developed its own acquisition categories (manual, logical, file system, physical) to describe how much of a device had been recovered. The central tension was between the completeness of an extraction and the risk of altering the device; unlocking and imaging a phone could change it, and examiners had to document exactly what they did.
Anti-Forensics
Every forensic method invites a counter-method. Anti-forensics is the set of techniques used to frustrate examination: overwriting files, altering timestamps, encrypting or hiding data, using tools that leave few traces, or deliberately planting misleading artifacts. The field treats anti-forensics not as a separate discipline but as a permanent adversary within forensics itself. Studying how evidence can be destroyed or faked is how examiners learn to recognize when it has been—and how to argue in court that a gap in the record is itself meaningful.
Cloud Forensics
The most recent shift is cloud forensics: investigations involving data held on remote services—email, file storage, virtual machines, and logs controlled by a provider1. The problem is jurisdictional and practical1. The evidence may sit on servers the investigator cannot seize, in another country, under a provider's terms of service, and the provider may keep logs for only a limited time. Cloud forensics developed methods for working through providers, for acquiring data from cloud APIs, and for reconstructing activity from service logs. It forced the field to confront questions that disk forensics never had to: who controls the evidence, how long does it exist, and what legal process is needed to obtain it.
The Present
Digital forensics today is a set of overlapping specialisms—disk, memory, mobile, network, cloud, and malware—unified by a common commitment to documented, reproducible method. The tools have grown more automated and the volumes of data larger, which has pushed the field toward triage (deciding quickly what matters) and toward validation of tools themselves, since a court may ask whether a automated result is reliable. The open questions are familiar in new form: how to examine encrypted devices without altering them, how to establish soundness when evidence lives on someone else's servers, how to keep pace with devices that change every year, and how to present technical findings so that judges and juries can weigh them fairly. The field's history is a record of answering each new version of the same question: what happened, and how can we prove it?
References
- Digital forensics (introduction, Digital evidence, Forensic process, 2000s: Developing standards, Network forensics, Development of forensic tools, Database forensics, Mobile device forensics, Cloud Forensics), Wikipedia
- Computer forensics, Wikipedia
- Hash function, Wikipedia
- Chain of custody, Wikipedia
- Forensic disk controller, Wikipedia
- Scientific Working Group on Digital Evidence (introduction, History), Wikipedia
- Network forensics, Wikipedia
- Malware analysis, Wikipedia
- Memory forensics, Wikipedia
- Mobile device forensics, Wikipedia
The frameworks of Digital Forensics
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1985-2005
- 1995-Present
- 1998-Present
- 2000-Present
- 2000-Present
- 2000-Present
- 2002-Present
- 2005-Present
- 2005-Present
- 2008-Present
- 2010-Present

Digital Forensics is a planet in Nousfarer
Its city has a tower for each of these 11 frameworks. Land, walk in, and climb one concept at a time.
Land on Digital ForensicsRelated fields
More in Cybersecurity
- Applied Cryptography
- Cybersecurity
- Digital Privacy
- Malware Analysis
- Network Security
- Security Economics
- Security Theory
- Software Security
- Systems Security
See where Digital Forensics sits on the Map of Human Knowledge