Memory Acquisition Techniques
What you'll learn: How to capture live memory from a running system using hardware-based, software-based, and crash dump methods during incident response.
Why Memory Acquisition Matters
When investigating a security incident, a system's RAM contains volatile evidence that disappears the moment power is lost—active malware processes, decryption keys, network connections, and command histories. Capturing this evidence requires specialized techniques that minimize impact to the running system while preserving forensic integrity.
Three Primary Acquisition Methods
Software-Based Acquisition
The most common approach uses tools that run directly on the target system. These programs (like FTK Imager, WinPmem, or LiME for Linux) read memory contents through the operating system's APIs or kernel-level drivers and write them to a file.
Trade-off: While convenient, this method slightly alters the memory state by running the acquisition tool itself—like using a cup to measure water that's already in the cup.
Hardware-Based Acquisition
Physical devices connect directly to memory interfaces (FireWire, Thunderbolt, or specialized PCI cards) to read RAM contents without executing code on the target system. This approach provides the cleanest, least intrusive capture.
Trade-off: Requires physical access and compatible hardware ports, making it impractical for remote investigations or modern systems that lack legacy interfaces.
Crash Dump Acquisition
Operating systems can be forced to generate crash dumps (Windows Blue Screen dumps, Linux kernel dumps) that include memory snapshots. Some tools trigger controlled crashes or leverage existing hibernation files (hiberfil.sys) which contain complete memory images.
Trade-off: May cause system downtime and can miss certain memory regions depending on dump configuration.
Selection Criteria
Choose your method based on system state (can you reboot?), access level (physical vs. remote), legal requirements, and how much memory alteration is acceptable. Each technique balances evidence preservation against operational impact.
Key Takeaway: Memory acquisition requires choosing between software convenience, hardware purity, or crash-triggered completeness—each method trades forensic cleanliness for practical accessibility in live incident response scenarios.