CyberKit

Page Table

Also called Page Tables, Page Table Entry, PTE.

The hardware mapping from virtual pages to physical frames.

What it is

The multi-level structures the CPU and OS use to translate a process's virtual addresses into physical memory frames, with each page-table entry recording the backing frame plus present, writable, and no-execute bits. Each process has its own top-level table.

Why it matters

Memory analysis depends on these tables to reconstruct what each process actually sees, and the per-page protection bits help flag executable writable regions typical of injected code. Page-table state also explains why parts of an address space may be paged out and absent from a RAM capture.

In practice

Following a process's page tables to translate a suspicious virtual address into a physical offset, then reading the bytes that turned out to be staged shellcode.

What to look for

  • Pages mapped executable that should not be.
  • Mappings that differ between processes for shared code.
  • Kernel memory mapped into user space.

Common mistake

Reading raw offsets as virtual addresses. Use the analysis tool to translate through the page tables.

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

Sources