Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The NTFS change journal records every file creation, rename, write, and deletion on a volume, which makes it the closest thing Windows has to a file system audit log.
What Is the USN Journal?
The Update Sequence Number Journal is a change log maintained by NTFS, stored as a sparse alternate data stream at $Extend\$UsnJrnl:$J. It exists so that backup software, indexing services, and replication tools can ask what has changed on a volume without scanning the whole file system. For an examiner it does something no other Windows artefact does: it records events that left no surviving file.
A file created, renamed, used, and deleted within a single minute vanishes from the Master File Table once its record is reused. The journal still carries its name, its creation, its rename, and its deletion.
Each entry is small and specific:
FILE_CREATE, DATA_EXTEND, DATA_OVERWRITE, RENAME_OLD_NAME and RENAME_NEW_NAME, FILE_DELETE, BASIC_INFO_CHANGE, SECURITY_CHANGE, and CLOSE.Those flags are what make it readable as a narrative. A sequence of FILE_CREATE, repeated DATA_EXTEND, then CLOSE describes a file being written. Thousands of RENAME_OLD_NAME and RENAME_NEW_NAME pairs within minutes, with a consistent new extension, describe ransomware encrypting a share.
MFTECmd handles the journal and produces CSV output suited to Timeline Explorer:
MFTECmd.exe -f "C:\Cases\$J" --csv C:\Cases\out --csvf usn.csv
On a live system, fsutil usn readjournal C: dumps records directly, though for evidential work the stream should be extracted from an image or a triage collection instead. Plaso ingests journal data into a super timeline, and most commercial suites parse it as standard.
The journal is a circular buffer with a maximum size, commonly around 32 MB on a system volume unless an administrator has increased it. Old records are discarded as new ones arrive. On a busy workstation that can mean only two or three days of history; on a quiet server it may stretch to months.
This is the single most important practical point about the artefact. Its value decays faster than almost anything else on disk, which argues for collecting it early in triage rather than waiting for a full image. It is also a strong argument for increasing the journal size on servers that matter, which is a one-line configuration change:
fsutil usn createjournal m=0x8000000 a=0x800000 C:
FILE_DELETE records.The journal records what happened to files, not who did it or which process was responsible. It carries no user or process attribution at all, so it must be correlated with Security event log entries, prefetch, and EDR telemetry to attach actions to actors. It can also be disabled or deleted by an administrator, and that deletion is itself evidence worth reporting.
Collected early and read alongside the Master File Table, it is one of the highest-yield artefacts available, which is why it forms part of the standard triage package in our Investigation and Incident Response Services.
It depends entirely on volume activity and the configured maximum size, which is often around 32 MB by default. A busy workstation may retain only two or three days of records, while a quiet file server can hold months. Because the window is short and unpredictable, the journal should be collected at the earliest opportunity rather than left for a later full image.
No. Journal records identify the file, the operation, and the time, but contain no user or process attribution. To establish responsibility you must correlate the journal entry with Security event log records, process execution artefacts such as prefetch and Amcache, or endpoint detection telemetry covering the same moment on the same host.
A dense sequence of rename pairs as each file is replaced with an encrypted version carrying a new extension, together with creation records for ransom note files in every directory. This provides an exact inventory of affected files and precise start and end times per volume, which is often the fastest way to scope the damage accurately.
On servers holding sensitive data, yes. Expanding the journal with fsutil is a simple configuration change that costs a modest amount of disk space and can extend retention from days to months. It is one of the cheapest forensic readiness improvements available, and the benefit is realised precisely when an intrusion is discovered weeks after it began.
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.