In last years, the way that operating systems are developed, deployed, and maintained evolved quickly.
Similarly, the skillsets of memory analysts and their preferred work flows have changed to meet a world with increasingly large volumes of complex data.
In order to address these challenges, the Volatility development team has developed an entirely new version of the framework.
Let’s try to take a look at new features of Volatility 3.
In this episode, we’ll take a look at the first public beta of Volatility 3. We’ll start by covering all of the significant changes and improvements this major new version will bring. Then, we’ll spin up a virtual machine and take it for a test drive.
Starting from this video, adding my own opinion, I’ve collected a list of highlights:
- Entire framework (backend and plugins) was completely rewritten and redesigned in Python 3.
- Much simpler integration into other libraries and user interfaces
- Natively supports multi-processing and memory caches
- Automatic detection of profiles for all supported OSs (about time!)
- 32bit apps on 64bit kernels natively supported
- Automated evaluation of in-memory code
- Plugins are versioned and can directly call other plugins
- Automating operating system and application support and automatic analysis of multiple samples at once
- No longer released under GPL: the new license is the “Volatility Software License 1.0” .
How to try Volatility 3?
Two simple steps!
First, clone the latest version of Volatility 3 from GitHub :
git clone https://github.com/volatilityfoundation/volatility3.git
Then download symbol table packs for the operating systems you need to analyze:
Symbol tables zip files must be placed, as named, into the
For example, to get information on a Windows memory sample, run
python3 vol.py -f <imagepath> windows.info:
In this example, I’ve used a Stuxnet memory sample .