Hamdan (@devmuhakeem) header
Hamdan (@devmuhakeem) profile picture

ChemE | WordPress Developer | CMS Expert | Social Media & Community Manager | Open to Remote & Freelance Opportunities | Web3 lover ❤️

Nigeria, Lagos
Joined November 2022
Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)
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
2
8/ Recovered files had generic, auto-generated names, not anything resembling an original filename, because carving has zero access to that information. 9/ Confirmed one carved file actually displayed real, viewable image content, not a corrupted fragment.
1
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…
1
16
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
1
1
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.
1
2
8/ Actually determining what the file really is comes later in a deeper module. This lab's job was the essential first step: noticing the mismatch exists at all.
1