CyberKit

Memory Acquisition

Capturing a live system's RAM into an image for analysis.

What it is

The process of copying the contents of volatile memory (RAM) from a running system into a forensic image. Capture can be software-based from within the OS, or hardware- and hypervisor-assisted.

Why it matters

Memory holds artifacts that never touch disk: injected code, decrypted payloads, command history, and network state. Everything in memory forensics depends on a sound acquisition, which must change the target as little as possible.

In practice

Imaging RAM from a suspected-compromised host, then parsing it for hidden processes and injected code with a memory-analysis framework.

What to look for

  • A memory image whose size matches installed RAM.
  • The acquisition tool's own process and driver in the image, which is expected.
  • Hashes recorded at capture time.

Common mistake

Copying the acquisition tool onto the suspect disk or running it from a share the attacker can see. Run it from trusted external media and write the image elsewhere.

Use it in CyberKit

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.

ATT&CK techniques

Tools practitioners use

  • WinPmem: Windows physical-memory acquisition
  • AVML: Acquire Linux memory to an image
  • LiME: Linux Memory Extractor (kernel module)

Read next

  • Order of Volatility: Collect the most fleeting evidence first, before it disappears.
  • Process Hollowing: Malware starts a legit process, then swaps its guts for malicious code.
  • Rootkit: Stealth malware that hides itself deep in the OS.

Sources