CyberKit

Demand Paging

Also called Paging, On-Demand Paging.

Loading pages into RAM only when accessed, leaving gaps in captures.

What it is

The memory-management scheme that brings a page into physical memory only when it is first touched and evicts inactive pages to the backing store under pressure. As a result, only a subset of a process's address space is resident at any moment.

Why it matters

Demand paging is why a RAM capture is incomplete: pages never touched or since evicted are absent, so analysts must turn to the pagefile or hibernation file to fill the gaps. Understanding it sets realistic expectations for what a memory image can and cannot contain.

In practice

A process region appearing empty in the RAM image because those pages were never faulted in, with the data instead reconstructed from the pagefile.

What to look for

  • Pages missing from a process because they were never loaded.
  • Paged out data that sits in the pagefile.
  • Gaps that make plugins return partial results.

Common mistake

Reading a missing page as deleted data. It may simply have never been in RAM.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Volatility 3 Open source

    A widely used open source framework for analyzing memory images with plugins. Our notes.

  • Velociraptor Open source

    Can collect memory and query live process memory across many hosts. Our notes.

  • CrowdStrike Falcon Commercial

    EDR agents watch memory activity on the host, such as injection and unbacked code.

Read next

  • Pagefile Analysis: Recovering evidence from memory pages the OS swapped out to disk.
  • Page Table: The hardware mapping from virtual pages to physical frames.
  • Page Cache: File data kept resident in RAM that can be recovered from a capture.

Sources