CyberKit

Handle Table

Also called Object Handles.

A process's table of open references to kernel objects.

What it is

The per-process structure that maps numeric handle values to the kernel objects a process has opened, along with the granted access rights for each. The kernel maintains it so a process can reference files, keys, events, and other objects.

Why it matters

Enumerating a process's handles reveals the files it has open, registry keys it touches, mutants it created, and other processes it has opened for injection, often the clearest evidence of intent. Handles outlive transient activity, capturing relationships that may not appear anywhere else.

In practice

Finding that a benign-looking process held an open handle to another process with full access, consistent with it injecting code into that target.

What to look for

  • Handles to other processes with full access rights.
  • Open files in temp or staging folders.
  • Registry keys tied to persistence.

Common mistake

Skipping handles. They show what a process touched while it ran.

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

  • Kernel Object: Kernel-managed structures like processes, files, and events.
  • EPROCESS: The kernel structure describing a running Windows process.
  • Code Injection: Placing and running attacker code inside another process's memory.

Sources