Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 36 ยท Disk and File System Forensics

NTFS Timestamps and Metadata

Learn how NTFS stores timestamps (FILETIME), the MACB model, the difference between $STANDARD_INFORMATION and $FILE_NAME times, alternate data streams and how timestomping shows up.

Almost every investigation asks "when?" The answer usually comes from timestamps, and NTFS, the Windows file system, records more of them than most. Reading them correctly means knowing what each one means, when it changes and where it can lie. This lesson covers the format, the MACB model, the two sets of times kept per file and the signs that someone has tampered with them.

The FILETIME format

NTFS stores a time as a 64-bit integer counting 100-nanosecond ticks since 1 January 1601, 00:00 UTC. Windows calls this a FILETIME. Times are stored in UTC, and display tools convert to local time, so you must always know which time zone a tool is showing. The tiny resolution (a ten-millionth of a second) also gives a fingerprint: a time with all trailing digits zero ("exactly 12:00:00.0000000") is suspicious, because normal activity rarely lands on a whole second.

To convert: ticks divided by 10,000,000 gives seconds since 1601. The gap between 1601 and the Unix epoch (1970) is 11,644,473,600 seconds.

Python Convert FILETIME to a readable UTC time

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The MACB model

Examiners label the four timestamps with letters:

Letter Meaning NTFS name Updated when
M Modified Last write File content changes
A Accessed Last access File is read (updates can be delayed or disabled)
C Changed MFT entry modified Metadata changes (rename, permissions, content)
B Born Created The file is created on this volume

Careful: in Windows terminology "Changed" is the MFT record change and "Created" is B. In Unix, ctime is "inode change", not creation. Mixing the vocabularies is a classic beginner trap.

How common actions affect them on a Windows 10/11 NTFS volume (typical behaviour; settings and versions vary):

Action M A C B
Create a file now now now now
Edit and save now (maybe) now unchanged
Open and read unchanged (maybe now) unchanged unchanged
Copy to another place kept from source now now now
Move on the same volume kept kept now kept
Rename kept kept now kept

The copy rule explains the "modified before created" pattern from the earlier lesson: a copy's B is the time of copying while its M is the original's. Careful use of this rule can prove that a file arrived on a computer by copying (for example from a USB stick) at a specific time.

The last-access time deserves a warning: Windows may update it with a delay of up to an hour, and recent Windows versions often disable last-access updates by default on large volumes for performance. A missing "A" change is therefore weak evidence.

Two sets: $STANDARD_INFORMATION and $FILE_NAME

Each NTFS file has two attributes holding timestamps:

  • $STANDARD_INFORMATION ($SI): the times shown in Explorer, changed freely by programs through ordinary APIs.
  • $FILE_NAME ($FN): times stored with the name, in the file's own record and in its parent directory index. Windows updates these mainly when the file is created, renamed or moved; ordinary user-level tools cannot easily edit them.

So there are up to eight times per file (four in each), and the $FN set is the harder to forge. Comparing them is a powerful check.

Timestomping

Timestomping means deliberately editing a file's timestamps, usually to make a malicious or sensitive file look old. Tools set the $SI times because the Windows API allows it. Indicators:

  1. $SI created earlier than $FN created. The $SI date can be pushed back, but $FN stays at the real creation time. This is the classic indicator.
  2. Whole-second times. $SI times with zero fractional part (.0000000) when the OS normally records full precision.
  3. Times before the OS or the volume existed, or in the future.
  4. Nonsense relationships, such as a file "created" before its parent folder, or before the volume format date.
  5. Journal evidence. The $UsnJrnl and $LogFile record the real sequence of operations and often reveal a time change.

Timestomping can happen innocently too (archive extraction and backup tools set times intentionally), so treat these as flags, not conclusions.

Python Flag possible timestomping

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

tool.exe shows both signs. photo.jpg has only whole seconds, which is a weak sign on its own, because some programs and file systems (and copying from other file systems such as FAT, which has 2-second resolution) produce rounded times.

Other useful metadata

  • File size, allocated size and attributes (read-only, hidden, system, archive, compressed, encrypted).
  • MFT record number and sequence number, and the parent record: it lets you rebuild the full path even for deleted files.
  • Owner SID and security descriptor (who owns the file and who may access it).
  • Resident data: very small files are stored inside the MFT record itself (typically under about 700 bytes), so their content survives with the record.
  • Alternate data streams (ADS): extra named $DATA attributes. They are written file.txt:hidden. Windows itself uses one called Zone.Identifier to record that a file came from the internet, with the download source (referrer URL) in some cases, which makes it valuable evidence of how a file arrived.

Reading a Zone.Identifier stream

The content of a Zone.Identifier ADS is plain text. This is sample content (not read from a real disk):

TEXT
[ZoneTransfer]
ZoneId=3
ReferrerUrl=https://downloads.example.com/tools/
HostUrl=https://downloads.example.com/tools/setup.exe

ZoneId=3 means the Internet zone. The parser below turns such text into a small summary.

Python Parse a Zone.Identifier stream

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Sample tool output (read-only)

The Sleuth Kit prints the timestamps of an MFT record with istat. Shortened sample output, not run here:

TEXT
$ istat -o 2048 image.dd 64
MFT Entry Header Values:
Entry: 64   Sequence: 3
$STANDARD_INFORMATION Attribute Values:
Created:    2025-04-02 21:14:36.9021440 (UTC)
File Modified: 2025-04-02 21:14:36.9021440 (UTC)
MFT Modified:  2025-04-02 21:14:37.0100020 (UTC)
Accessed:   2025-04-02 21:15:01.2200000 (UTC)
$FILE_NAME Attribute Values:
Name: tool.exe
Created:    2025-04-02 21:14:36.9021440 (UTC)

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A FILETIME counts 100-nanosecond ticks from which date?

    NTFS FILETIME values count from 1 January 1601 UTC.
  2. 2. A file is copied from a USB stick to the desktop. What happens to its timestamps on the copy?

    Copying creates a new file (new B) but preserves the original modified time.
  3. 3. Which finding is the classic sign of timestomping?

    $SI can be edited by tools, but $FN usually keeps the true creation time, so the mismatch stands out.
  4. 4. What does the Zone.Identifier alternate data stream record?

    Windows adds this stream to downloaded files, recording the security zone and often the source.

Summary

  • NTFS stores UTC times as 64-bit counts of 100 ns ticks since 1601; always confirm the time zone a tool displays.
  • MACB: modified, accessed, changed (MFT record), born (created); copy and move affect them differently.
  • Each file has $SI times (easy to edit) and $FN times (harder to edit); comparing them reveals timestomping.
  • Zero fractional seconds, impossible dates and journal records are further clues.
  • Alternate data streams such as Zone.Identifier add context about how a file arrived.

Next: Memory forensics fundamentals