Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The master file table holds a record for every file on an NTFS volume, including deleted ones. Parsing it produces a complete filesystem timeline from a file that is a fraction of the disk size.

What Is Master File Table Analysis?
Every file on an NTFS volume has an entry in the master file table, a system file conventionally named $MFT that sits near the start of the partition. Directories have entries, system files have entries, and the table has an entry for itself. For an investigator this concentration is a gift: a few gigabytes of metadata describes a multi-terabyte disk, and collecting it from fifty machines during triage is a matter of minutes.
Records are 1,024 bytes by default and begin with the ASCII signature FILE. Each holds a sequence of attributes rather than fixed fields, which is what makes NTFS extensible. Three matter most.
$STANDARD_INFORMATION carries the timestamps shown by Explorer and most tools, plus flags and the security identifier. $FILE_NAME carries the name, the reference to the parent directory — which is how a full path is reconstructed for a file whose folder no longer exists — and a second, separate set of timestamps. $DATA carries the content: for files below roughly 700 bytes the data is resident inside the record itself, meaning a small script, a configuration snippet, or a short note can be recovered in full from the table alone, even after the file has been deleted and the clusters reused.
Deletion does not remove the record. It clears an in-use flag and increments a sequence number, leaving the name, timestamps, parent reference, and often the cluster runs intact until the record is reallocated.
Both attributes store creation, modification, metadata change, and access times, giving eight values per file. Ordinary applications and most timestamp manipulation tools update only the standard information set, because the file name attribute is maintained by the filesystem and is not reachable through the usual programming interfaces.
That asymmetry is the most reliable timestomping detection available. A file whose standard information creation time is 2019 while its file name creation time is last Tuesday was almost certainly altered, and a web shell dropped into an application directory and backdated to match its neighbours gives itself away precisely this way. A second signal is precision: genuine Windows timestamps carry sub-second detail, so values with zeroed fractional components suggest an API call rather than ordinary file activity. See anti-forensic techniques for the broader category this belongs to.
MFTECmd parses the table and the related journals into CSV at speed, and Timeline Explorer handles the resulting volume. The Sleuth Kit offers fls and istat for the same structures. In practice the master file table is analysed alongside two companions: the change journal, $UsnJrnl, which records every create, rename, write, and delete with a reason code, and the transaction log, $LogFile, which can reconstruct operations the journal has aged out. Together they frequently establish that a file existed, what it was called, where it sat, and when it was removed — all after the content itself is unrecoverable.
Cross-check against $I30 directory index slack, which retains entries for deleted files inside their former folder and is another route to proving a file once existed in a specific location.
The table records filesystem metadata, not activity. It does not say who opened a file, whether its content was read, or whether a program executed — those questions belong to Amcache and ShimCache, Prefetch, and event logs. Timestamps can be falsified, records are reused, and a file whose record has been reallocated leaves nothing. State those limits in the report rather than implying the table is an audit log.
Used properly, it is the backbone of the timeline: it shows what an intruder staged and when, which directories they worked from, and which files disappeared afterwards. At Privia Security, we collect it from every Windows host we triage during digital forensic incident response services, because it answers more questions per megabyte than any other artefact on the system.
Their metadata usually can: name, size, parent directory, timestamps, and the cluster locations where the content was stored. If those clusters have not been reused, the file itself can be recovered. For files under roughly 700 bytes the content is resident inside the record, so the whole file can be recovered from the table alone even after the clusters are overwritten.
NTFS stores two independent sets of timestamps, one in the standard information attribute and one in the file name attribute. Tools that falsify timestamps generally update only the first, because the second is maintained by the filesystem itself. A significant discrepancy between the two, or timestamps with zeroed sub-second components, indicates manipulation.
No. The master file table, the change journal, the transaction log, and the directory indexes can be collected with triage tooling in minutes per host, producing a few gigabytes rather than terabytes. That is what makes filesystem timeline analysis practical across dozens of machines during an intrusion investigation rather than only on one.
The master file table describes the current state of each file, including deleted records that have not yet been reused. The change journal is a rolling log of operations, recording each create, rename, write, and delete with a reason code. One tells you what exists and existed; the other tells you what happened, and they are strongest read together.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.