Tools:Memory Imaging

From ForensicsWiki
Revision as of 15:25, 27 June 2008 by Moyix (Talk | contribs)

Jump to: navigation, search

The physical memory of computers can be imaged and analyzed using a variety of tools. Because the procedure for accessing physical memory varies between operating systems, these tools are listed by operating system. Usually memory images are used as part of memory analysis.

One of the most vexing problems for memory imaging is verifying that the data has been imaged correctly. Because the procedure cannot be repeated (i.e. the memory changes during the process), it is impossible to do the acquisition again and compare the results. At this time the structures involved are not known well enough to determine the integrity of the image.

dd
On *nix systems, the program dd can be used to capture the contents of physical memory using a device file. On Linux, this file is /dev/mem. On Microsoft Windows systems, a version of dd by George Garner allows an Administrator user to image memory using the \Device\Physicalmemory object. Userland access to this object is denied starting in Windows 2003 Service Pack 1 and Windows Vista.
hibernation files
Windows 98, 2000, XP, 2003, and Vista support a feature called hibernation that saves the machine's state to the disk when the computer is powered off. When the machine is turned on again, the state is restored and the user can return to the exact point where they left off. The machine's state, including a compressed image of physical memory, is written to the disk on the system drive, usually C:, as hiberfil.sys. This file can be parsed and decompressed to obtain the memory image.

Imaging with Firewire

It is possible for Firewire or IEEE1394 devices to directly access the memory of a computer. Using this capability has been suggested as a method for acquiring memory images for forensic analysis. Unfortunately, the method is not safe enough to be widely used yet. There are some published papers and tools, listed below, but they are not yet forensically sound. These tools do not work with all Firewire controllers and on other can cause system crashes. The technology holds promise for future development, in general should be avoided for now.

At CanSec West 05, Michael Becher, Maximillian Dornseif, and Christian N. Klein discussed an exploit which uses DMA to read arbitrary memory locations of a firewire-enabled system. The paper lists more details. The exploit is run on an iPod running Linux. This can be used to grab screen contents.

This technique has been turned into a tool that you can download from: http://www.storm.net.nz/projects/16

Memory Imaging Tools

Firewire
http://www.storm.net.nz/projects/16
Tribble PCI Card
http://www.digital-evidence.org/papers/tribble-preprint.pdf
CoPilot
http://www.komoku.com/forensics/forensics.html
Windows Memory Forensic Toolkit (WMFT) and Idetect (Linux)
http://forensic.seccure.net/
http://www.blackhat.com/presentations/bh-usa-06/BH-US-06-Burdach.pdf
Kntdd
http://www.gmgsystemsinc.com/knttools/
Nigilant32
http://www.agilerm.net/publications_4.html
winen.exe (part of Encase)
http://forensiczone.blogspot.com/2008/06/winenexe-ram-imaging-tool-included-in.html
Win32dd
http://www.msuiche.net/2008/06/14/capture-memory-under-win2k3-or-vista-with-win32dd/
mdd.exe (Mantech)
http://sourceforge.net/projects/mdd

Memory Imaging Techniques

Create a Crash Dump
http://computer.forensikblog.de/en/2005/10/acquisition_2_crashdump.html
Dump memory with livekd
Once livekd is started, use .dump -f [output file]
Use the hibernation file
Once hiberfil.sys has been obtained, [Sandman] can be used to convert it to a dd image.

External Links

Windows Memory Analysis (Sample Chapter)
http://www.syngress.com/book_catalog/sample_159749156X.PDF