Difference between revisions of "Volatility Framework"

From Forensics Wiki
Jump to: navigation, search
(Update website links.)
 
(15 intermediate revisions by one user not shown)
Line 3: Line 3:
 
   maintainer = [[AAron Walters]] |
 
   maintainer = [[AAron Walters]] |
 
   os = {{Cross-platform}} |
 
   os = {{Cross-platform}} |
   genre = [[Memory analysis]] |
+
   genre = {{Memory analysis}} |
 
   license = {{GPL}} |
 
   license = {{GPL}} |
   website = [https://www.volatilesystems.com/default/volatility https://www.volatilesystems.com/] |
+
   website = [https://code.google.com/p/volatility/ https://code.google.com/p/volatility/] |
 
}}
 
}}
  
The '''Volatility Framework''' is a completely open collection of tools, implemented in Python under the GNU General Public License, for the extraction of digital artifacts from volatile memory (RAM) samples. The extraction techniques are performed completely independent of the system being investigated but offer unprecedented visibility into the runtime state of the system. The framework is intended to introduce people to the techniques and complexities associated with extracting digital artifacts from volatile memory samples and provide a platform for further work into this exciting area of research.  
+
The '''Volatility Framework''' is a completely open collection of tools, implemented in Python under the GNU General Public License (GPL v2), for the extraction of digital artifacts from volatile memory (RAM) samples. The extraction techniques are performed completely independent of the system being investigated but offer unprecedented visibility into the runtime state of the system. The framework is intended to introduce people to the techniques and complexities associated with extracting digital artifacts from volatile memory samples and provide a platform for further work into this exciting area of research.
  
 
The project was originally developed by and is now headed up by [[AAron Walters]] of [[Volatile Systems]].
 
The project was originally developed by and is now headed up by [[AAron Walters]] of [[Volatile Systems]].
Line 17: Line 17:
 
== Memory acquisition drivers ==
 
== Memory acquisition drivers ==
  
In 2012 [[Michael Cohen]] contributed both a Linux and a Windows Open Source memory (acquisition) driver to the volatility project.
+
In 2012 [[Michael Cohen]] contributed both a Linux and a Windows Open Source memory (acquisition) driver to the Volatility project as part of the Technology Preview (TP) version, aka scudette branch.
 
+
Since the scudette branch of Volatility has moved on as a separate project, the drivers can now be found as part of the [[rekall]] project.
These drivers are currently available in the volatility scudette branch and soon to be released as a separate download. To obtain this branch run:
+
<pre>
+
svn checkout http://volatility.googlecode.com/svn/branches/scudette/ volatility
+
</pre>
+
 
+
In the scudette branch the drivers can be found under:
+
<pre>
+
volatility/tools/linux and volatility/tools/
+
</pre>
+
 
+
=== Linux ===
+
 
+
To build the kernel module for the current kernel version, make sure you have a working build environment and the kernel headers installed. Change into this directory and run make:
+
<pre>
+
cd volatility/tools/linux/
+
make
+
</pre>
+
 
+
The acquisition driver is named pmem.ko.
+
 
+
To load the driver:
+
<pre>
+
sudo insmod pmem.ko
+
</pre>
+
 
+
To check if the driver is running:
+
<pre>
+
sudo lsmod
+
</pre>
+
 
+
The driver create a device file named:
+
<pre>
+
/dev/pmem
+
</pre>
+
 
+
To unload the driver:
+
<pre>
+
sudo rmmod pmem
+
</pre>
+
 
+
To read acquire the memory just read from the device file. e.g.
+
<pre>
+
dd if=/dev/pmem of=image.raw
+
</pre>
+
 
+
For more information see:
+
<pre>
+
volatility/tools/linux/README
+
</pre>
+
 
+
=== Windows ===
+
Since recent versions of 64 bit Windows require a signed driver the volatility scudette branch comes with both pre-built (binary) and source versions of the driver. The prebuilt binary is signed.
+
 
+
Both the i386 and amd64 binary version of the driver can be found on the downloads part of the [http://code.google.com/p/volatility/ Volatility code repository] as winpmem or in the scudette branch under:
+
<pre>
+
volatility/tools/winpmem/binaries/
+
</pre>
+
 
+
E.g.
+
<pre>
+
volatility/tools/winpmem/binaries/amd64/winpmem.sys
+
</pre>
+
 
+
A standalone tool for imaging memory that uses an embedded copy of the pmem driver can be found as winpmem.exe in:
+
<pre>
+
volatility/tools/winpmem/executables/Release/
+
</pre>
+
 
+
To load the driver:
+
<pre>
+
winpmem.exe -l
+
</pre>
+
 
+
The device filename is (This can not be changed without recompiling):
+
<pre>
+
\\.\pmem
+
</pre>
+
 
+
To read and acquire the physical memory and write it to image.raw:
+
<pre>
+
winpmem.exe image.raw
+
</pre>
+
 
+
To unload the driver:
+
<pre>
+
winpmem.exe -u
+
</pre>
+
 
+
For more information see:
+
<pre>
+
volatility/tools/windows/README
+
</pre>
+
  
 
== See Also ==
 
== See Also ==
Line 116: Line 24:
  
 
== External Links ==
 
== External Links ==
* [https://www.volatilesystems.com/default/volatility Official web site]
+
* [https://code.google.com/p/volatility/ Official web site]
* [http://code.google.com/p/volatility/ Code repository]
+
* [http://code.google.com/p/volatility/source/checkout Code repository], direct link to [http://code.google.com/p/volatility/source/browse/ source]
 
* [http://code.google.com/p/volatility/w/list Volatility Documentation]
 
* [http://code.google.com/p/volatility/w/list Volatility Documentation]

Latest revision as of 20:02, 29 January 2014

Volatility
Maintainer: AAron Walters
OS: Cross-platform
Genre: Memory Analysis
License: GPL
Website: https://code.google.com/p/volatility/

The Volatility Framework is a completely open collection of tools, implemented in Python under the GNU General Public License (GPL v2), for the extraction of digital artifacts from volatile memory (RAM) samples. The extraction techniques are performed completely independent of the system being investigated but offer unprecedented visibility into the runtime state of the system. The framework is intended to introduce people to the techniques and complexities associated with extracting digital artifacts from volatile memory samples and provide a platform for further work into this exciting area of research.

The project was originally developed by and is now headed up by AAron Walters of Volatile Systems.

Contents

Plugins

See: List of Volatility Plugins

Memory acquisition drivers

In 2012 Michael Cohen contributed both a Linux and a Windows Open Source memory (acquisition) driver to the Volatility project as part of the Technology Preview (TP) version, aka scudette branch. Since the scudette branch of Volatility has moved on as a separate project, the drivers can now be found as part of the rekall project.

See Also

External Links