1/ Worked through a forensics lab on file carving. Genuinely different technique from everything else in this series, because it assumes the file system has nothing left to offer at all. Thread below.
muhakeem.hashnode.dev/file-c…
builder.aws.com/content/3Lk7…
github.com/devmuhakeem/SSD-F…
6/ Set up the case with the same documentation discipline as a full disk-image lab: dedicated base directory, examiner details, case number.
7/ Then the part worth planning around: Autopsy eats serious system resources while carving. Lab specifically said not to touch
1/ Every forensic tool I'd worked through up to this point operated on one file at a time: hash a file, check a hash, open a file to verify its format.
Worked through a forensics lab using Autopsy to analyze a full Linux disk image.
muhakeem.hashnode.dev/analyz…
6/ The Results tab went further, automatically flagged the file as password protected. A real finding surfaced without me manually opening and testing it myself.
7/ There's also a dedicated Images/Videos gallery that pulls every media file across the whole image into one view
8/ At the scale of a real disk image with potentially thousands of files, that kind of automatic categorization is what makes systematic review practical instead of just theoretically possible
builder.aws.com/content/3Lh3…
github.com/devmuhakeem/Analy…
1/ Worked through a forensics lab on viewing files of different formats. Real lesson: recognizing when a tool's failure IS the evidence, not a dead end. Thread below.
muhakeem.hashnode.dev/a-blan…
builder.aws.com/content/3LgC…
github.com/devmuhakeem/Viewi…
7/ Easy to treat that as "tool's broken, move on." The lab framed it as the opposite: the failure IS the finding. A working file needs no further attention. A file that fails to open as claimed is exactly the signal worth flagging.
