Read a sample: 1. What Digital Forensics Can Answer
A document is missing from a shared folder. Yesterday, a project team expected to find it there. This morning, the folder contains an older draft, but the version everyone remembers is gone.
The immediate question may be, “Who deleted it?” That question is understandable, but it carries an assumption: that someone deleted the document. The file might have been moved, renamed, saved somewhere else, replaced during synchronization, or never uploaded to the shared folder at all. It could also have been deleted, intentionally or accidentally.
Digital forensics begins by making room for those possibilities. Instead of choosing a story and looking for proof, an investigator asks what information is available, how it can be preserved, and what it actually shows. The goal is not to make every uncertainty disappear. It is to produce an account that another person can examine, understand, and assess.
This chapter introduces that way of thinking through a fictional missing-document case. Before working through it, we need a practical definition of the field and a clear view of what an investigator does.
Digital forensics is the disciplined examination of digital information to answer questions about events, data, and systems. Depending on the situation, the information might come from a computer, phone, storage device, application, online account, network system, or another source that records or holds data.
The work can support many kinds of inquiry. An organization might need to understand how a file changed, whether an account was accessed, or which systems were affected by an incident. A support team might need to establish what happened before a workstation stopped functioning. An examiner might be asked to identify records relevant to a dispute or reconstruct a sequence of activity.
These situations differ in purpose and authority, but they share a basic challenge: digital information can change easily, and its meaning is not always obvious. Opening an application, signing into an account, or allowing a device to continue operating may change the information available for later examination. A file’s displayed date may have a specific technical meaning that differs from what a reader assumes. A log entry may record an action by an account without identifying the person who used it.
Forensic work therefore involves more than finding interesting data. It includes deciding what to preserve, recording how it was handled, using suitable methods to examine it, and explaining the limits of the result. A useful finding connects a claim to identifiable sources and makes clear where observation ends and interpretation begins.
Digital forensics is not limited to criminal investigations or dramatic courtroom reveals. It can be useful whenever a responsible person needs a well-supported account of digital events. Nor does every investigation end with a complete reconstruction. Sometimes the most reliable answer is that the available information supports several explanations and cannot distinguish among them.
A beginner might imagine a forensic investigator as someone who runs a tool and reads the results. Tools matter, but the investigator’s responsibilities begin earlier and continue after the analysis.
First, the investigator is a question framer. A broad request such as “Find out everything that happened” is difficult to answer and may exceed the authority or practical resources available. A better starting point identifies the event, the relevant sources, and the decision the requester needs to make. Even then, the question may need refinement as the investigator learns more.
Second, the investigator is a custodian of information. That does not necessarily mean physically taking possession of every device. It means recognizing that evidence can be lost, changed, or mishandled, and taking appropriate steps within the investigator’s authority. It also means recording what was received, where it came from, and what happened to it.
Third, the investigator is an examiner. The examiner selects methods, reviews relevant material, and checks whether apparent findings hold up. This may involve looking at file content, metadata, logs, account records, or other traces. Different sources can describe different parts of an event; none should be treated as automatically complete simply because it appears in a tool.
Fourth, the investigator is a communicator. A finding is useful only if its audience can understand what it means and how much confidence to place in it. Communication includes describing uncertainty, identifying gaps, and avoiding words that imply more than the evidence supports.
These roles may be divided among several people. An IT employee might notice a problem and preserve initial information, while an authorized specialist performs acquisition and analysis. A manager might define the business concern without being the right person to examine employee data. Knowing when to pause and involve someone else is part of responsible forensic work.
Consider a fictional design firm called Northbridge Studio. On Tuesday morning, a project coordinator, Elena, reports that a document named Harbor Proposal.docx is missing from the team’s shared project folder. Elena says she worked on the proposal the previous afternoon and expected the current version to be available for a client meeting.
A team lead asks Marcus, an IT support professional, to “find out who deleted Elena’s file.” Marcus has experience helping staff recover documents, but he has not been assigned to conduct a broad investigation into employee activity.
The request contains a real operational need: the team wants the proposal back, and it wants to understand what happened. It also contains a conclusion too soon: the team lead has described the file as deleted and has asked Marcus to…