Chapter 01

Computer Hardware & Operating Systems

Chapter 01· 10 min read

Computer Hardware & Operating Systems

Reading as a guest

Sign up free to save your progress, highlight passages, and pick up where you left off.

You'll lose your reading position and notes if you leave without an account.

Before you can investigate a crime on a computer, you need to understand what is inside it — and what each part stores. This chapter covers hardware components, the boot sequence, and the file systems every digital examiner must recognise cold.

1.1Motherboard, Processor & Memory

The motherboard is the main circuit board inside every computer. Every other component — the CPU, RAM, storage, graphics card — plugs into or sits on top of it. Think of it as the city's road network: nothing moves without it.

The CPU (Central Processing Unit) executes every instruction the computer runs. Its speed is measured in gigahertz (GHz) — a 3 GHz CPU can attempt roughly three billion basic operations per second. Modern CPUs have multiple cores, each acting as an independent processor. Each core has its own fast memory called cache (L1 is smallest and fastest; L2 and L3 are larger but slower), which holds the data the CPU is actively working on so it does not have to reach out to the slower RAM on every instruction.

RAM (Random Access Memory) is the computer's working memory — like a whiteboard. The CPU writes whatever it is actively processing to RAM. RAM is volatile: when power is cut, everything on the whiteboard is wiped instantly. For a digital examiner this is critical. If you simply pull the power plug on a running machine, you lose running processes, open network connections, encryption keys held in memory, and any data the user was working on but had not yet saved to disk. A live memory dump — capturing RAM to an image while the machine is still running — preserves that evidence before shutdown.

The ROM/BIOS chip (Read-Only Memory) holds the computer's firmware — the lowest-level software that starts the machine before any operating system loads. Unlike RAM, ROM is non-volatile: its contents survive power-off.

Volatile vs Non-Volatile Memory

Volatile memory (RAM) requires continuous power to retain data. Non-volatile memory (ROM, hard disks, SSDs, flash drives) retains data without power. The distinction determines the seizure order: capture volatile evidence first, before the machine is powered down.

MOTHERBOARDCPUL1 / L2 / L3 CacheClock · CoresRAMVolatileDDR4 / DDR5ROM / BIOSNon-VolatileFirmwareChipsetI/O ControlPCHBusBusStorageSATA / NVMe / USBHDD · SSD · FlashPCIe SlotsGPU · NICSound · CapturePowerATX 24-pinCPU 8-pin
Fig 1.1Motherboard block diagram — CPU with cache, RAM slots, ROM/BIOS chip, storage connectors, PCIe expansion slots, and chipset.

1.2Storage Devices

Storage is where persistent evidence lives. Unlike RAM, storage devices keep their data after power is removed — but not all storage is equal when it comes to forensic recovery.

Hard Disk Drives (HDD) store data on spinning magnetic platters. A read/write head floats just above the surface and magnetises tiny areas to record binary data. Data is organised into sectors (traditionally 512 bytes; modern drives use 4 096-byte "Advanced Format" sectors) and groups of sectors called clusters. When a file is too large for one cluster, the OS spreads it across multiple clusters — sometimes non-contiguous ones. This fragmentation leaves a trail: even after a file is "deleted," the clusters that held its data are not immediately overwritten. The OS simply marks them as available. Until another file overwrites them, the original data can be recovered.

Solid State Drives (SSD) store data in NAND flash cells — no moving parts. They are faster and more durable than HDDs. However, SSDs use wear levelling: the controller deliberately spreads writes across all cells so no single cell is written too often. This means data is distributed in ways the OS does not control or record. The TRIM command instructs the SSD controller to immediately erase blocks that the OS marks as freed, so future writes are faster. The forensic consequence is severe: on a TRIM-enabled SSD, deleted data may be zeroed within seconds — long before an examiner ever images the drive.

USB flash drives use the same NAND flash technology as SSDs. Most consumer flash drives do not implement TRIM aggressively, so deleted data recovery is often still possible.

TRIM Command

An ATA command (TRIM) or NVMe equivalent (Deallocate) that tells the SSD to securely erase blocks the operating system has marked as free. It improves write performance but makes post-deletion recovery significantly harder or impossible.

Write Blocker

A hardware or software device placed between the evidence drive and the examiner's workstation. It allows read operations but blocks all write commands. Essential to preserve evidential integrity and to demonstrate in court that the examiner did not alter the original media.

HDD — Magnetic PlatterR/W HeadTracks → Sectors (512 B / 4 096 B)SSD — NAND FlashNANDFlashNANDFlashNANDFlashNANDFlashNANDFlashNANDFlashController (TRIM)Wear levelling — data scatteredvs
Fig 1.2HDD vs SSD architecture — magnetic platter with read/write head on the left; NAND flash chip array with wear-levelling controller on the right.

The table below summarises the forensic differences between HDD and SSD:

FeatureHDDSSD
Storage mediumMagnetic plattersNAND flash cells
Deleted data recoveryHigh (until overwritten)Low if TRIM is active
Wear levellingNoYes — data location unpredictable
FragmentationYes — useful forensic trailMinimal

1.3OS Boot Process

When you press the power button, the computer does not jump straight to Windows or Linux. It follows a strict sequence of steps before the operating system is ready. Every step is also a location where malware — especially rootkits — can hide.

Step 1 — Power-On Self Test (POST). The firmware immediately runs a hardware check: is the CPU working? Is RAM present and readable? Are storage devices detected? If POST fails, the machine beeps an error code and stops.

Step 2 — BIOS or UEFI initialises hardware. The firmware scans for a bootable device (hard disk, USB, optical disc, network) in the configured priority order.

  • BIOS (Basic Input/Output System): the legacy firmware standard. It is 16-bit, runs in "real mode," and looks for the Master Boot Record (MBR) — the first 512 bytes of the disk — which contains a small bootloader and the partition table. BIOS supports disks up to 2 TB and a maximum of four primary partitions.
  • UEFI (Unified Extensible Firmware Interface): the modern replacement. It is 32/64-bit, uses the GUID Partition Table (GPT) which supports disks over 2 TB and up to 128 partitions. UEFI also supports Secure Boot — it verifies that the bootloader is digitally signed by a trusted authority, blocking unsigned rootkits from loading.

Step 3 — Bootloader loads the OS kernel.

  • On Windows (UEFI): bootmgfw.efiwinload.efi → Windows kernel (ntoskrnl.exe)
  • On Windows (BIOS): bootmgrwinload.exe → Windows kernel
  • On Linux: GRUB reads its configuration, selects the kernel image (vmlinuz), loads initramfs, then hands off to the kernel

Step 4 — Kernel and services start. The kernel initialises the file system, loads device drivers, starts system services, and creates the user login session.

Master Boot Record (MBR)

The first 512 bytes of a partitioned disk. Contains bootstrap code (446 bytes), the partition table (64 bytes — four entries of 16 bytes each), and the boot signature (0x55AA). MBR-based rootkits overwrite the bootstrap code to execute before the OS loads, making them invisible to OS-level security tools.

Secure Boot

A UEFI feature that verifies the cryptographic signature of the bootloader before executing it. If the signature is invalid or absent, the firmware refuses to boot, blocking unsigned rootkits and bootkits. On a forensic acquisition, Secure Boot status can be read from the UEFI NVRAM.

1 Power OnElectricity flows to motherboard2 POSTHardware self-test — CPU / RAM / I/O3 BIOS / UEFIFirmware finds bootable device (MBR / GPT)Rootkit targetMBR / EFI partition4 Bootloaderbootmgr / GRUB loads OS kernel5 OS KernelDrivers · services · file system mount6 User Session
Fig 1.3OS boot sequence — power-on through POST, firmware initialisation, bootloader, kernel load, and user session. Rootkits target the MBR or EFI partition.

From a forensic perspective, the MBR or EFI System Partition (ESP) are high-value artefacts. A bootkit — a rootkit that persists in the boot sector — executes before the OS and before any security software, making it very difficult to detect from within a running OS. Examiners image the entire disk including the first sectors, not just the data partitions.

1.4File System Types

A file system is the method the OS uses to organise, store, and retrieve files on a storage device. Different operating systems use different file systems, and each leaves different forensic artefacts.

FAT32 (File Allocation Table, 32-bit) is the oldest of the common file systems. Its key limitation is a maximum file size of 4 GB and a maximum volume size of 8 TB (though many implementations cap it at 2 TB). FAT32 has no access permissions, no journaling, and no metadata beyond basic timestamps. It is still found on USB drives and SD cards for cross-platform compatibility. Forensically, FAT32 is simple to parse: deleted directory entries are marked with byte value 0xE5 but remain intact in the directory table until overwritten.

NTFS (New Technology File System) is the default file system for Windows since Windows NT. NTFS is far richer than FAT32:

  • $MFT (Master File Table): Every file and directory has an entry in the MFT — 1 024 bytes per record storing the file's attributes, timestamps, and data location. When a file is deleted, its MFT record is marked as available but not immediately zeroed, so deleted-file metadata persists.
  • $LogFile: NTFS journals all metadata changes. Forensically, the journal records recent file operations even after deletion.
  • Alternate Data Streams (ADS): A single file can carry multiple named data streams beyond its primary content. Malware uses ADS to hide payloads inside innocent-looking files. Example: document.txt:hidden.exe.
  • Full access permissions (ACLs), file ownership, and MACB timestamps (Modified, Accessed, Changed, Born).

ext4 is the default Linux file system. Ext4 uses inodes — data structures that store a file's metadata (size, timestamps, permissions, data block locations) separately from the file's name. It supports extents (contiguous block ranges for large files) and a journal. Forensically, the inode table and journal are primary targets for recovering deleted file information.

APFS (Apple File System) is Apple's modern file system for macOS and iOS, introduced in 2017. Key features: copy-on-write (when a file is modified, old blocks are not immediately overwritten, enabling snapshots — point-in-time copies that preserve evidence of files the user thought they deleted), nanosecond timestamps, and native full-volume or per-file encryption. APFS snapshots are a forensic goldmine.

exFAT is a Microsoft extension of FAT32 designed for large flash drives. It removes the 4 GB file size limit but has no journaling and minimal metadata, making forensic analysis harder than NTFS.

File SystemPrimary OSMax File SizeJournalingKey Forensic Feature
FAT32Cross-platform / USB4 GBNo0xE5 deleted entries survive in directory table
NTFSWindows16 EB (practical)Yes ($LogFile)$MFT records, ADS, MACB timestamps
ext4Linux16 TBYesInode table + journal retain deleted-file info
APFSmacOS / iOS8 EBNo (copy-on-write)Snapshots preserve deleted file history
exFATCross-platform / large USB128 PBNoMinimal metadata; limited recovery

Alternate Data Streams (ADS)

An NTFS feature that allows a file to carry additional data streams beyond its primary content. The extra streams are invisible in Windows Explorer and most file listings. Malware abuses ADS to hide executable payloads inside innocent files — the file appears to have a normal size while the hidden stream contains the payload.

Master File Table ($MFT)

The heart of NTFS. Every file and directory on an NTFS volume has at least one 1 024-byte record in the $MFT, storing the file's attributes including name, timestamps, permissions, and data location. Deleted file records are marked free but remain readable until reused, making the $MFT a primary forensic target for recovering metadata about deleted files.

Memory hooks · Chapter 1

1.1 RAM = whiteboard — volatile, wiped on power-off; always capture a live memory dump before shutdown or you lose encryption keys, running processes, and network connections.

1.1 ROM = printed manual — non-volatile firmware; holds BIOS/UEFI; survives power loss.

1.1 Cache levels — L1 fastest and smallest (inside core) → L2 → L3 largest and shared across cores.

1.2 HDD sectors — 512 B (legacy) or 4 096 B (Advanced Format); clusters group sectors; fragmentation leaves trails; "deleted" = cluster marked free, data intact until overwritten.

1.2 SSD + TRIM — wear levelling scatters data unpredictably; TRIM zeroes freed blocks instantly; deleted data recovery is hard or impossible on a TRIM-enabled SSD.

1.3 Boot order — POST → BIOS/UEFI → Bootloader → Kernel → User session. BIOS reads MBR (first 512 bytes); UEFI reads GPT + checks Secure Boot signature.

1.3 Rootkit/bootkit hiding spot — MBR or EFI System Partition; runs before OS and antivirus; invisible from inside a running OS.

1.4 FAT32 — max file 4 GB, no journaling, no permissions; USB drives; deleted entries marked 0xE5.

1.4 NTFS — $MFT records survive deletion; $LogFile journals ops; ADS hides payloads; MACB timestamps.

1.4 ext4 — inode table + journal; Linux default; deleted inodes recoverable until reused.

1.4 APFS — copy-on-write snapshots may hold deleted files; nanosecond timestamps; native encryption.

Don't lose your place

Save this chapter and the rest of Cyber & Digital Forensics.

A free ForensicSpot account remembers which chapters you've read, lets you highlight passages, take notes and resume from any device.

PreviousNextCyber Crime Categories