
Inside the warehouse, every file and directory is stored in equal-sized cardboard boxes (MFT records). It went something like this: The MFT is like a warehouse.

Step 3- Parse the Artifact byte-by-byteĪctive Disk Editor showing the MFT record of a fileĪfter spending some time with Active Disk Editor (and the linux-ntfs documentation), I had my own mental model for the MFT.Step 2- Learn to use the existing tools.In each of these steps I have added a My Experience section to mention what I actually did and the outcomes. Instead of writing it as a story, I thought it might be easier to consume as “The 5-step process I used to learn an artifact”. How do I make these statements? To answer that, I’ll share my experience of understanding an artifact. In my experience, however, learning a few artifacts deeply have created new learning paths and provided a much better understanding of the tools. So it’s pretty obvious, right? Just learn the tools and leave figuring out the artifacts to the tool writers. You don’t need to know that entries in the eventlog are stored as binary-encoded XML inside 64 kB Elf Chunks.
#010 EDITOR TEMPLATE ENDIAN WINDOWS#
Even if you learn, how much will it help in your daily job? For example, to determine if a user logged on to a Windows host, you only want to verify if there are any event ID 4624 in the eventlog.

First, there are too many artifacts to learn. In fact, making counterarguments is easier. Learning artifacts deeply on the other hand isn’t easy to justify. We spend our time using them, learning their APIs/commandline switches, chaining them together, raising bugs, and suggesting improvements. A security analyst’s job is built around tools. Making an argument for learning tools is straightforward. Why learning a Forensic Artifact matters?ĥ-steps to learning an artifact and how I used it to learn a thing or two about NTFS.Īs security analysts, I am sure some of us have had this question - what’s the best way to improve my host forensics skills? Should I learn more about tools or should I learn more about the artifacts themselves?
