Skip to content
Tutorials Center
My learning

Topics

Lesson 27 of 36 ยท Timeline and Artifact Analysis

File System Timestamps and mactime

Understand modified, accessed, changed and born timestamps on NTFS and ext4, how copying and moving change them, and how to build a mactime-style bodyfile timeline.

Every file carries timestamps, and they are the backbone of most disk timelines. They tell you when something was created, edited or opened, and when it arrived on the machine. But they are easy to misread: the same action sets different timestamps on different file systems, and copying a file can change them in surprising ways. This lesson explains the four MACB times, the rules that matter, and how the classic mactime format turns them into a timeline.

The four timestamps

Letter Name Meaning (typical)
M Modified Contents last written
A Accessed Contents last read (often disabled or coarse)
C Changed Metadata (or MFT entry) last changed; on Unix, ctime
B Born Created on this file system

On NTFS each file has two sets of times: $STANDARD_INFORMATION (shown by Explorer, easy for programs to edit) and $FILE_NAME (updated by the system only, harder to alter). A mismatch between the two sets is a classic hint of timestomping, deliberately setting times to hide a file. On ext4 you have mtime, atime, ctime and a birth time (crtime) that is stored but not always shown by tools.

Rules of thumb

  • Copy: the new file's created time is the copy time, while modified usually stays the original. So a file whose modified time is earlier than its created time was probably copied (or extracted from an archive).
  • Move on the same volume: times normally stay the same; moving across volumes behaves like a copy.
  • Open without editing: may update accessed time, but modern systems delay or disable access-time updates for performance (for example relatime on Linux, and NTFS access updates are often off), so absence of an access time proves little.
  • Edit: updates modified (and changed).
  • Rename or permission change: updates changed time, not modified.
  • Download: the browser may set modified to the server's value and created to the download time.

Because rules differ by operating system, file system, mount options and application, validate your assumption on a test system with the same setup when a conclusion depends on it. Record that test in your notes.

Read-only: stat and mactime output

Illustrative tool output (not runnable here):

Terminal
$ stat report.docx
  File: report.docx
  Modify: 2026-11-10 09:12:44.000000000 +0000
  Change: 2026-11-12 14:03:40.000000000 +0000
   Birth: 2026-11-12 14:03:40.000000000 +0000

Example: modified is earlier than born, so the file was likely copied in at 14:03:40.

The Sleuth Kit's fls -m writes a bodyfile, a pipe-separated text file with one line per file, and mactime turns it into a sorted timeline.

TEXT
MD5|name|inode|mode_as_string|UID|GID|size|atime|mtime|ctime|crtime
0|/Temp/svc.exe|1234|r/rrwxrwxrwx|0|0|88064|1699797821|1699797820|1699797820|1699797820

All times are Unix seconds. This simple, open format is easy to build or parse yourself.

Build a mactime-style timeline

Python Turn a bodyfile into a MACB timeline

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.

In the output, svc.exe shows m.cb at a single second: it was created and written at once (a typical drop), with the access time one second later. report.docx shows modified on 2023-11-10 but born on 2023-11-12, which is the copy signature described above.

Detect timestomping hints

A simple heuristic: a file whose creation time is earlier than a system component it depends on, or whose $STANDARD_INFORMATION times disagree with $FILE_NAME times.

Python Compare two sets of NTFS times

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 standard-information time claims 2017, but the system-maintained file-name time says it appeared in 2023. That mismatch is a lead, not proof (some legitimate tools and installers preserve times).

Good practice

  • Always state which timestamp you used and its meaning in the report.
  • Collect timestamps from an image, not from a live system you have been browsing, since reading files can change access times. Use a write blocker or read-only mount (timelines).
  • Compare against other sources: a log, a prefetch entry or a registry key that corroborates the time (Windows artifacts).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A file's modified time is earlier than its created time. What is the most likely explanation?

    A copy gets a new creation time but typically keeps the original modified time.
  2. 2. Which NTFS attribute is harder for ordinary programs to alter?

    The $FILE_NAME times are maintained by the system, so mismatches with $STANDARD_INFORMATION can reveal timestomping.
  3. 3. Why is a missing accessed time weak evidence that a file was never opened?

    Mount options like relatime or NTFS settings often prevent access times updating on each read.
  4. 4. What does a mactime bodyfile contain?

    The bodyfile lists metadata and timestamps; mactime sorts it into a timeline.

Summary

  • MACB: modified, accessed, changed, born; meanings vary by file system.
  • Copying changes created time but usually not modified time.
  • NTFS keeps two sets of times; disagreement hints at timestomping.
  • Bodyfile plus mactime builds a simple, sortable timeline.
  • Validate assumptions on a test system and corroborate with other artifacts.

Next: Windows Artifacts Overview