Glossary
$STANDARD_INFORMATION vs $FILE_NAME
The two NTFS attributes that each hold a set of MACB timestamps; comparing them is a core technique for detecting timestomping.
Every file record in the $MFT carries two independent sets of MACB timestamps: one in the $STANDARD_INFORMATION attribute (often shortened to $SI) and one in each $FILE_NAME attribute ($FN). Both use the FILETIME format in UTC.
The difference lies in who updates them. $SI holds the times that Explorer, dir and most APIs display, and a user-mode program can rewrite them with a standard call such as SetFileTime. $FN times are maintained by the file system driver and change mainly when a file is created, renamed or moved; normal applications have no direct API to set them. A file can also have more than one $FN attribute, for example a long name and a short 8.3 name.
That asymmetry makes the comparison valuable:
- An
$SIcreation time earlier than the$FNcreation time is a classic sign of timestomping. $SIvalues with a zero sub-second part, while$FNvalues carry full precision, point the same way.- Because
$FNoften reflects when a file arrived in its current location, it can help date copies and moves.
Treat these as indicators, not proof. Legitimate operations such as extracting archives or some installers can also set older $SI times, and tools with kernel access can alter $FN too. Corroborate with the $UsnJrnl and other sources.
Related artifacts
- $I30 index attributes$I30 cheat sheet: NTFS directory indexes ($INDEX_ROOT, $INDEX_ALLOCATION), INDX records, timestamps, slack entries of deleted files and parsers.
- $LogFile (NTFS transaction log)$LogFile cheat sheet: NTFS metadata journal (MFT record 2), 64 MB default, redo/undo operations, restart area, short retention and parsers.
- Master File Table ($MFT)$MFT cheat sheet: FILE records, $SI vs $FN timestamps, resident data, deleted records, sequence numbers, timestomping checks and MFTECmd parsing.