Skip to content
Tutorials Center
My learning

Topics

Lesson 30 of 36 ยท Reporting and Legal Aspects

Writing a Forensic Report

Learn how to write a clear forensic report: audience, structure, separating facts from opinions, precise language, evidence references and a script that checks a report draft.

The report is the product of an investigation. Everything you did (acquiring, hashing, parsing, correlating) is only useful if someone else can understand, trust and act on it. A lawyer, a manager, a judge or an opposing expert may read your report, and some of them will read it looking for mistakes. Good forensic reports are clear, accurate, complete about method and honest about limits.

Know your readers

A report usually has two kinds of readers:

  • Decision makers (executives, lawyers, judges) who need conclusions in plain language and who will not read technical detail.
  • Technical reviewers (peers, opposing experts) who need enough detail to repeat your work.

The standard answer is layers: a short executive summary on top, a readable body, and appendices with raw detail.

A report structure that works

Section Content
Title and case information Case number, author, dates, requester
Executive summary What was asked, the main findings, the conclusion, in under a page
Scope and authority What you were authorized to examine, under what instrument
Evidence examined Item list with identifiers, hashes, acquisition details
Methodology and tools Steps, tools and versions, time assumptions
Findings Numbered facts, each tied to evidence
Analysis and conclusions What the facts mean, confidence, alternatives considered
Limitations What you could not determine and why
Appendices Timelines, hash lists, tool output, glossary
flowchart TB
  A["Executive summary"] --> B["Scope and evidence"]
  B --> C["Method"]
  C --> D["Findings"]
  D --> E["Conclusions and limits"]
  E --> F["Appendices"]

Readers can stop at any layer and still have an accurate picture.

Facts, inferences and opinions

The most important writing skill is separating three things:

  1. Fact (observation): "File svc.exe has a creation time of 2026-11-12 14:03:40 UTC and SHA-256 3a7b...."
  2. Inference: "The file was probably created by the web upload at 14:03:11 UTC, because of the 29 second gap and the matching file name in the access log."
  3. Opinion/conclusion: "In my opinion, it is more likely than not that the host was compromised through the upload form."

Label each, and state how much support it has. Use consistent confidence words that you define in the report, for example certain, highly likely, likely, possible, unlikely. Do not use vague phrases ("it seems", "appears to") without saying why.

Language that stands up

  • Be precise: "10.0.0.7 sent 17 MB to 198.51.100.9" not "a lot of data left".
  • Be neutral: do not argue for a side. Report what the evidence shows, including facts that do not help the person who hired you.
  • Avoid jargon or define it on first use.
  • Do not claim identity from an IP address or account name alone (network limits).
  • Quote times in UTC with seconds and state conversions (timelines).
  • Say what you did not do or could not do.

Write the findings first, then the conclusions, then the summary. A report that begins with the conclusion tends to bend the facts toward it.

Compare: weak and strong statements

Weak Strong
The user stole the data. A USB device (serial ABC123) was connected at 14:20 UTC; 412 files from E:\payroll were opened from that device between 14:21 and 14:40 UTC under the account ana.
Malware was found. svc.exe (SHA-256 shown in Appendix B) matched no entry in the reference known-good list; its behavior was not analyzed in this engagement.
Logs were deleted. Event 1102 records the Security log being cleared at 14:09 UTC by build-bot.

Check a draft with a script

Reports should be checked for missing pieces and overclaiming. This small program scans a draft for required sections and for risky absolute words.

Python Lint a report draft

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A tool like this does not replace a review, but it catches common errors. Notice what it flags: the missing Methodology and Limitations sections, and a sentence claiming identity ("former employee") that the evidence could not support.

Present numbers carefully

Quantities should be reproducible. If you give a count, give the query or filter that produced it.

Python Report a count with its method

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Writing the method next to the number lets a reviewer repeat it.

Before you deliver

  1. Check every fact against your notes; check every hash character.
  2. Check that the report matches the scope you were given and does not exceed it.
  3. Have a colleague review it (peer review is standard practice).
  4. Keep your working notes, tool versions and drafts for the retention period.
  5. Remember the legal context: your report may become an exhibit (legal frameworks).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which sentence is an observation rather than an opinion?

    A recorded timestamp is a fact; the others are inferences or opinions.
  2. 2. Where should the summary of main findings appear?

    Decision makers read the top layer first, so provide a short, accurate summary there.
  3. 3. Why define confidence words such as 'likely'?

    Defined terms prevent misreading and make your confidence testable.
  4. 4. What should you do about facts that weaken the case of the party who hired you?

    Examiners must be impartial; selective reporting damages credibility and may be unethical.

Summary

  • A report serves both decision makers and technical reviewers through layers.
  • Use a standard structure: summary, scope, evidence, method, findings, conclusions, limitations, appendices.
  • Separate facts, inferences and opinions and state confidence.
  • Be precise, neutral and reproducible; give the method for every number.
  • Review and retain your notes; your report may become a court exhibit.

Next: Legal Frameworks and Admissibility