Read Linux file systems and links
UNIX originated as a multiuser, multitasking operating system with controls for access to shared resources. The Open Group administers the UNIX certification program for products that conform to the relevant specifications. A Linux distribution bundles the Linux kernel with utilities, a package manager, and often a desktop environment. Ubuntu, Linux Mint, Fedora, CentOS Stream, and Gentoo are examples.
Linux supports several file systems, including ext4, XFS, and Btrfs. Ext4 uses extents to describe ranges of file data and can support file systems larger than 16 TiB with appropriate features and configuration. Identify the actual file system and its features from the image before choosing a parser.
A traditional Unix file system model identifies a boot area, a superblock, inode storage, and data blocks. Layouts vary. Ext4 organizes storage into block groups with structures such as inode tables and allocation bitmaps. An inode holds metadata such as ownership, permissions, timestamps, link count, and mappings to file data. Directory entries associate names with inode numbers. An examiner reconstructs paths from those directory relationships.
- Hard link
- Another directory entry for the same inode on the same file system. Removing one name reduces the link count. Other names for the inode can still provide access to the file.
- Symbolic link
- A separate file that stores a target path. It can refer to a path on another mounted file system or network share, and it can dangle if the path no longer resolves. It leaves the target inode’s link count unchanged.
The Open Group · POSIX and UNIX standards · Linux kernel documentation · ext4 design · Linux kernel documentation · ext4 directory entries · Linux manual · Symbolic and hard links
Recognize HFS, HFS+, and APFS
Older Macs used HFS and then HFS+, also called Mac OS Extended. HFS+ continued into macOS and uses 32-bit allocation block identifiers, providing room for many more blocks than HFS. On HFS+ an allocation block consists of consecutive logical sectors. The allocation block size is set when the volume is formatted, and 4 KiB is a common choice. A clump size guides how some files grow in groups of allocation blocks to reduce fragmentation.
A Mac file can have a data fork for its main contents and a resource fork that may contain application resources or other structured data. Resource forks are optional, and other metadata can live in separate file system structures or extended attributes. Check what the acquisition or export preserves before evaluating a file’s contents and metadata.
Apple began using Apple File System (APFS) for supported Mac startup disks with macOS High Sierra. An APFS container can hold multiple volumes that share free space. APFS supports encryption, snapshots, and copy-on-write metadata. A snapshot captures a volume’s state at a particular point in time. If retained and accessible, it can provide an earlier view of a file or directory for comparison with the current volume.
Apple · HFS Plus Volume Format · Apple · HFS+ and APFS format comparison
Build a timeline from macOS artifacts
- Property lists. Plists store structured data, including application and system preferences. A user’s
~/Library/Preferencesis a starting point. Plists can be XML or binary. Preserve the original and use a compatible parser, such asplutilon macOS, to inspect a copy. Determine what each key means before treating it as evidence of an action. - Unified logs. macOS stores unified log records in a compressed binary format. Console and the
logutility can display and filter supported records. Record the time range and predicates used. Retention settings and privacy redaction can affect what you see. - Snapshots. Inventory available snapshots and compare relevant paths across them. Snapshot times establish when a state was captured. Use additional records to narrow down when a change occurred and what caused it.
Normalize timestamps to the same time zone, identify the relevant user context, and compare artifacts before attributing activity to a person.
Choose an acquisition method and verify tool support
On a Mac, identify the model, processor, storage design, encryption, and power state. Some models have removable storage. On Macs with Apple silicon or a T2 chip, integrated storage and hardware-backed encryption can make traditional disk removal and imaging impractical. Determine whether the authorized workflow can acquire an unlocked volume or selected files without losing access. Preserve relevant snapshots, forks, extended attributes, and logs where the collection method supports them. Document the scope and any limitations.
Kali Linux includes tools for penetration testing and forensic work, and its Live image offers a forensic boot mode. Booting from external media ends a running session, so make the live-versus-static acquisition decision first. dc3dd extends GNU dd with features such as hashing during acquisition, error logging, and split output. Autopsy is an open-source examination platform. Check the tool and version against the source file system and specific features you need, then verify the acquisition before analysis.
Apple Platform Security · Volume encryption with FileVault · Kali · dc3dd documentation · Autopsy · Platform and installation details
Practice cases
Two paths on a Linux image. On the same ext4 file system, work/notes.txt and archive/notes.txt refer to inode 7421. A symbolic link named latest stores the target work/notes.txt. What happens to each name if someone removes work/notes.txt?
A missing file on a Mac. An APFS snapshot taken at 08:00 UTC contains draft.txt. The path is absent from the live volume when it is collected at 10:00 UTC. An application plist lists it among recent items, and the unified log has an application entry at 09:12 UTC with no visible file path. What can you conclude, and what remains open?
Review possible answers
Linux. The archive entry can still refer to the inode and its contents. The symbolic link remains but is dangling in the observed layout because its target path is absent.
Mac. The path existed in the snapshot and was absent from the live volume at collection. A move, rename, or deletion could explain the difference. The plist supplies application context. The log entry needs corroboration before it can be tied to the file or used to establish a time or actor for the change.
Read and watch
- Review how ext4 groups blocks and organizes on-disk structures. Linux kernel documentation · ext4 High-Level Design
- Compare volume structures and features across Mac file system generations. Apple · Volume Format Comparison
- Watch a demonstration of the forensic examination platform. Embry-Riddle video · Introduction to Autopsy Forensic Platform