1 Artefacts are side effects
A file system tells you which files exist and when they changed. It does not tell you that a program ran, that
a user opened a document from a USB stick, or that someone logged in over SSH at night. The operating system
does record such things, as a side effect of its normal work: Windows keeps prefetch files to start programs
faster, Explorer counts program starts to sort the Start menu, Linux logs logins for last, macOS
remembers where a download came from in order to warn the user.
None of these records were made for investigators. Their formats are often undocumented, they are overwritten on a schedule, and they differ between OS versions. But together they answer the questions an examiner gets asked:
All examples come from invented sample files of one user, robin, who has a Windows laptop
(ASH-LT07), a Linux workstation (build-07) and a Mac. The binary formats were written
from their public descriptions, the databases with Python's sqlite3, the property list with
plistlib.
2 The pages
As on the other Learn pages, every hex view is interactive: click a field to see its bytes, click a byte to see its field, and follow the → rows.
3 Where to look, per question
| Question | Windows | Linux | macOS |
|---|---|---|---|
| Program execution | Prefetch, UserAssist, BAM, Amcache, ShimCache, event 4688 | shell history, auth log (sudo), audit log, journal | Unified log, KnowledgeC/Biome, login items (sfltool dumpbtm) |
| Files and folders opened | LNK files, Jump Lists, RecentDocs, ShellBags | recently-used.xbel, editor histories (.viminfo) | app plists (recent documents), FSEvents, .DS_Store, quarantine database (downloads) |
| Logons | Security event log (4624, 4625, 4634) | wtmp, btmp, lastlog, auth.log/secure | utmpx records in the ASL store (read by last), unified log |
| External devices | USBSTOR, MountedDevices, setupapi.dev.log, LNK volume serials | kernel log (dmesg, journal): usb … SerialNumber | Unified log, FSEvents mount events, /Volumes |
| Persistence | Run keys, services (7045), scheduled tasks | cron, systemd units, .bashrc, authorized_keys | LaunchAgents/Daemons, login items |
| Deleted files | Recycle Bin ($I/$R), $MFT, $UsnJrnl | Trash (~/.local/share/Trash), ext4 journal | Trash (~/.Trash), FSEvents, APFS snapshots |
| Web activity | Browser profiles (same formats on every OS): see Browsers | ||
Paths and formats change between versions. Treat the table as a list of places to check, then verify on the version in front of you.
4 Six clocks
Every OS family counts time differently, and one examination usually meets all of them. They are normally UTC, so the local time zone is not part of the value. Exceptions exist: classic HFS and the HFS+ volume creation date store local time, and some programs write local time into a FILETIME. Check per source.
| Format | Unit and start | Where you meet it | Typical size in 2026 |
|---|---|---|---|
| FILETIME | 100 ns since 1601-01-01 | NTFS, registry, LNK, prefetch, Recycle Bin, event logs | 18 digits (≈ 1.34 × 1017) |
| WebKit / Chrome | µs since 1601-01-01 | Chrome, Edge and other Chromium browsers | 17 digits (≈ 1.34 × 1016) |
| PRTime | µs since 1970-01-01 | Firefox databases | 16 digits (≈ 1.79 × 1015) |
| Unix | s (or ms) since 1970-01-01 | Linux logs and file systems, Android, JavaScript | 10 digits (13 in ms) |
| Cocoa (Mac absolute) | s since 2001-01-01, often a float | macOS and iOS databases, plist dates | 9 digits (≈ 8.1 × 108) |
| HFS+ | s since 1904-01-01 | HFS+ volumes, old Mac formats | 10 digits (≈ 3.87 × 109) |
Timestamp converter
The preset bytes are the deletion time from the Recycle Bin sample, copied from the hex view: 8 bytes, little-endian. Paste any 8 bytes you find to see what they could mean.
5 One timeline
Single artefacts give single facts. The story appears when you put every timestamp from every source into one
sorted list: a super-timeline (tools: log2timeline/plaso, Timeline Explorer). Below is every
timestamp from the samples on these pages. Switch the time zone to see why you always report the zone with a
time, and why you sort in UTC.
Read it as an examiner would. On the Windows laptop: a visit that was later deleted from the Chrome history, a download,
regedit started, the Run key changed two minutes later. Then a shortcut to a zip file on a USB stick,
a CSV in the Recycle Bin, and a wiping tool run three times. None of these alone proves intent; the sequence is
what you write in the report, with every step tied to its source.
SYSTEM\…\TimeZoneInformation; Linux: /etc/localtime; macOS:
/etc/localtime link), check for clock drift against an outside source, and remember that some
logs (classic syslog) store local time without a year or zone.6 Ground rules
- Live or dead? A running system holds data that disappears at shutdown (memory, network connections, unsaved logs), but every command you run changes it. Decide deliberately and write the decision down.
- Locked files. On a running Windows system the registry hives and event logs are open. Copy them with
tools that read the raw volume (or from a shadow copy), never by opening them in
regedit. - Collect the companions. Hives come with
.LOG1/.LOG2transaction logs, SQLite databases with-waland-journalfiles. The newest changes may only be there. - Deleted is not gone. Registry cells, SQLite pages and log files keep old content until it is overwritten. Look before the system keeps writing.
- Absence is evidence too. A cleared event log writes event 1102; a wiped
wtmpshows a gap; an empty bash history next to a long uptime is suspicious.
7 Warm-up
Two quick checks before the deep-dive pages.
A browser database stores the visit time 13433874002000000. Which format is it most
likely?
Count the digits and compare with the last column of the table in section 4, or paste the number into the converter.
17 digits, about 1.34 × 1016: WebKit/Chrome time. Read that way it is 2026-09-14 15:40:02 UTC, the first visit in the Chrome sample. As FILETIME it would be a date in 1643, as PRTime one in the year 2395.
You examine a running Windows PC. What is the right way to get the user's
NTUSER.DAT?
See the ground rules in section 6.
The hive is locked while the user is logged in, so Explorer cannot copy it, and a regedit export is a text dump that loses cell structure, deleted cells and LastWrite times. Copy the raw file and its transaction logs with a tool that reads the volume directly (or from a volume shadow copy), then hash everything.