CAP-2140 · Data Forensics I · Module 1

Foundations of Digital Forensics

Plan an investigation, preserve digital evidence, and document findings another examiner can review.

What digital forensics covers

Digital forensics is the systematic collection, preservation, examination, analysis, and reporting of digital evidence. It supports criminal, civil, administrative, and organizational investigations. Early U.S. computer crime statutes date to the 1970s. Florida’s Computer Crimes Act, enacted in 1978, is one example.

Digital forensics
The broader discipline. An examiner might compare a laptop’s file history with account sign-ins to reconstruct an event.
Network forensics
A specialty focused on network activity. Evidence can include packet captures, connection records, and firewall or DNS logs.
Data recovery
Restores access to missing or damaged files. Recovery techniques can support a forensic examination when their use is documented and evidence integrity is preserved.

Know your way around several operating systems and device types. Build contacts in system administration, networking, investigations, and legal support so you can bring in the right expertise. An evidence workstation may need extra drive bays or adapters, validated forensic tools, write-blockers, and enough secured storage for images and working copies.

An insider threat involves someone with authorized access or organizational knowledge, such as an employee or contractor. Harm can be deliberate, as in industrial espionage, or unintentional, as when someone mishandles sensitive files. Internet of Things (IoT) devices such as cameras and smart locks vary in memory, storage, and security features. An event record may live on the device, in a companion app, on a hub, or in the provider’s cloud.

Florida Computer Crimes Act · CISA Insider Threat Mitigation Guide (PDF)

Authority and professional conduct

In U.S. criminal investigations, the Fourth Amendment governs government searches and seizures. A warrant is generally required to search the digital contents of a phone seized during an arrest, subject to recognized exceptions. Document the legal authority and its scope before collecting or examining data. Rules vary across jurisdictions.

Private-sector investigations often address policy violations, misuse of assets, or possible crimes. Confirm who may authorize a case, which systems and accounts are in scope, and when to involve human resources or counsel. A limited list of authorized requesters and a warning banner that communicates acceptable-use or monitoring policies can help set expectations. Applicable law, policy, and the facts determine the scope of access.

When counsel directs the work, follow their instructions for labels, recipients, and handling of potentially privileged or work-product materials. A confidentiality label alone does not establish legal protection. Apply the same care to evidence integrity and documentation in internal and criminal cases. Either type of matter can end up in court. Protect credibility by documenting findings that support or weaken an allegation and explaining the limits of your conclusions.

Riley v. California · Fifth Circuit opinion on privilege and work product (PDF)

Case checklist

  1. Open and scope the case. Record the case ID, authorized requester, allegation, questions to answer, applicable authority, time range, and approved systems or accounts.
  2. Plan the collection. Identify evidence sources, tools, storage, and specialists. Plan for encryption, unreadable media, rotating logs, cloud retention limits, and data that may disappear after shutdown. Record deviations from the plan and why they were needed.
  3. Collect and preserve. Record the device’s state and acquisition method, assign evidence IDs, verify copies where possible, and begin the custody record. Secure originals and examine verified working copies whenever practical.
  4. Examine and analyze. Extract relevant artifacts, then compare them across sources. Check time zones, clock offsets, and retention gaps. Separate observations from inferences and consider other explanations.
  5. Report and review. Explain methods, results, limitations, and the basis for conclusions. After the case, critique what worked, what could have been done differently, and what should change in the next investigation.

Keep a contemporaneous case journal with dates, times and time zones, examiner names, tool versions, actions, settings, outputs, errors, and decisions. The journal records your work. The custody form records possession, transfers, and storage.

NIST SP 800-86 · SWGDE guidance on forensic examinations

Acquisition and chain of custody

Choose the acquisition method

A bit-stream image copies the readable, addressable sectors exposed by the device, including unallocated space where remnants of deleted data may survive. A logical acquisition collects selected files, folders, or records through a file system or service. The method depends on scope, device access, encryption, and what you need to preserve. For a supported storage device, use a tested write-blocker when appropriate. On a live system, weigh the value of volatile data, such as RAM, against the changes collection can introduce. Document the decision.

Verify and preserve the copy

Use the acquisition tool’s verification process and record a cryptographic hash such as SHA-256. Compare hashes of the same data, such as the acquired data stream and the data verified from the stored image. Matching hashes support integrity. Record unreadable sectors or other acquisition errors so the report reflects what the image contains. Keep a verified master protected and use a working copy for examination.

Record every transfer

Use a standard single-evidence form for one item or a multi-evidence form for several items. Give every item a unique ID and a traceable history. Record its description, serial number if available, source, collector, collection date and time with time zone, storage location, and condition. For each transfer, log who released and received the item, when, why, and where it went, with signatures or equivalent authenticated entries.

SWGDE guidance on computer forensic acquisition · SWGDE guidance on digital evidence collection

Practice case

Suspected upload to a personal cloud account. A manager reports that someone may have uploaded a confidential file from a company laptop. The approved scope covers the laptop and company-managed logs for a two-hour window. Proxy logs rotate the following morning.

Which records would you preserve first? What could a proxy connection tell you about whether the specific file was uploaded?

Review a possible approach

Preserve the relevant company proxy logs before they rotate, including their time zone and export details. Look for corroborating evidence in endpoint telemetry, browser artifacts, identity-provider logs, and any authorized cloud audit records. A proxy entry may establish a connection to a service. Identifying the exact file or the person at the keyboard takes additional evidence. Document each export and any gaps in the timeline.

Read and watch