CyberKit

Pagefile Analysis

Also called Swap Analysis, Pagefile.sys.

Recovering evidence from memory pages the OS swapped out to disk.

What it is

The examination of the backing store, the pagefile or swap, where the OS writes memory pages it has evicted from RAM to free physical memory. It holds data that was in memory but was not resident at capture time.

Why it matters

Because paged-out content is missing from a RAM image, the pagefile can supply the rest of a process's memory and recover secrets, strings, or code that swapping displaced. Correlating it with a memory capture mitigates the gaps that demand paging creates.

In practice

Recovering the remainder of an injected payload from the pagefile after only part of its memory region was resident in the RAM image.

What to look for

  • Strings, URLs and commands in pagefile.sys.
  • Fragments of documents or credentials.
  • Swapped pages missing from the memory image.

Common mistake

Expecting structure. Pagefile data is fragmented, so treat it as a string and carving source.

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

  • Demand Paging: Loading pages into RAM only when accessed, leaving gaps in captures.
  • Memory-Mapped File: A file whose contents are mapped into a process's address space.
  • Crash Dump: An OS-generated memory snapshot written when the system or a process fails.

Sources