Ravindra BagaleCourses & study guides मराठी Track your progress

28. Introduction to Digital Forensics

28.5 Autopsy and The Sleuth Kit

By Last updated:

In short: The Sleuth Kit (TSK) is a set of command-line forensic tools; Autopsy is its graphical front-end (both ship with Kali).

The Sleuth Kit (TSK) is a set of command-line forensic tools; Autopsy is its graphical front-end (both ship with Kali). They open a disk image and let you browse files, recover deleted ones, view timelines and search.

autopsy        # start the GUI (older Kali) ; newer versions: a desktop app
# some Sleuth Kit CLI tools:
mmls evidence.dd            # show the partition layout
fls -r -m / evidence.dd     # list files (including deleted) as a timeline
icat evidence.dd 12345      # extract a file by its inode number

In Autopsy you create a case, add the disk image as a data source, and it automatically: lists files and deleted files, extracts pictures, web history, and documents, builds a timeline, and lets you keyword-search. You tag findings and generate a report.

Ravindra Bagale's Tip

In Autopsy, always create a new "Case" and enter the case number and your name – a professional habit. And when adding the image, keep the "hash verify" option on; it proves the evidence is intact. The tool is easy, but the process demands discipline.

Lab

Open your USB image from 28.4 in Autopsy as a new case. Recover at least one deleted file, look at the file timeline, and generate a report. In your notes, write the steps you took (this is your chain-of-custody practice).

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.