<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><description>Volatile memory analysis research </description><title>Volatility</title><generator>Tumblr (3.0; @volatility)</generator><link>http://volatility.tumblr.com/</link><item><title>Volatility 1.1.2: Bug Fixes</title><description>&lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility 1.1.2: Bug Fixes&lt;/a&gt;: With the recent increase in acquisition tools, there are obviously more people  capturing samples of physical memory. As a result, we decided to back port the bug fixes from the upcoming 1.3 release into the 1.1 branch.  This release will also support samples taken from SP3 systems.  Let us know if you have any issues! We will keep you posted on the status of 1.3! If you have any questions, feel free to post them to the &lt;a href="https://www.volatilesystems.com/mailman/listinfo"&gt;Volatility mailing list&lt;/a&gt;.</description><link>http://volatility.tumblr.com/post/39159472</link><guid>http://volatility.tumblr.com/post/39159472</guid><pubDate>Fri, 20 Jun 2008 10:01:00 -0400</pubDate></item><item><title>Bait and Switch in Video</title><description>&lt;a href="http://treepages2.sytes.net:8080/wordpress/?p=26"&gt;Bait and Switch in Video&lt;/a&gt;: Despite the infamous drug dealer, &lt;a href="http://volatilesystems.blogspot.com/2008/01/they-are-playing-you-for-fool.html"&gt;BSHary&lt;/a&gt;, attempts to to censor him, Sippy has an interesting blog post.  In particular, I found &lt;a href="http://windowsir.blogspot.com/"&gt;keydet89&lt;/a&gt;’s comment interesting: “Having sat with the vendor, seen the videos and worked with their tool…&lt;a href="http://en.wiktionary.org/wiki/ugh"&gt;ugh&lt;/a&gt;.  That’s all I can say.” I guess this is to be expected from the same people who create and sell rootkits, including the one used by the &lt;a href="http://dvlabs.tippingpoint.com/blog/2008/06/13/recon08-day-one"&gt;Storm bot net&lt;/a&gt;.</description><link>http://volatility.tumblr.com/post/38921887</link><guid>http://volatility.tumblr.com/post/38921887</guid><pubDate>Wed, 18 Jun 2008 14:32:00 -0400</pubDate></item><item><title>Update: MDD released under the GPL</title><description>&lt;a href="https://sourceforge.net/projects/mdd/"&gt;Update: MDD released under the GPL&lt;/a&gt;: The latest version of the mdd acquisition tool was released yesterday. I’m glad they fixed the compiling issue and finally decided to release all aspects under the GPL! (They may have had &lt;a href="http://win32dd.msuiche.net/"&gt;help&lt;/a&gt; in making that decision!). I’m sure they would appreciate any testing and feedback you can provide. Until it has been tested more, my normal caveats apply about running it in a production environment. Over the last five years collecting memory samples, we have seen unexpected things happen in production environments, especially on critical servers. Make sure you know what you are doing and have the proper &lt;a href="https://www.volatilesystems.com/default/education"&gt;memory forensics training&lt;/a&gt;!</description><link>http://volatility.tumblr.com/post/38885903</link><guid>http://volatility.tumblr.com/post/38885903</guid><pubDate>Wed, 18 Jun 2008 09:28:16 -0400</pubDate></item><item><title>Open Source Memory Acquisition</title><description>&lt;p&gt;In case any of you may have missed it, there were a number of developments this weekend on the “open source” memory acquisition front.  On Friday, Ben Stotts of ManTech International Corporation released &lt;a href="http://www.mantech.com/msma/MDD.asp"&gt;MDD&lt;/a&gt; a physical memory acquisition tool for Windows computers.  &lt;a href="http://jessekornblum.com/"&gt;Jesse&lt;/a&gt; also discussed details about the tool in two recent blog posts.  The first announcing the &lt;a href="http://jessekornblum.livejournal.com/243498.html"&gt;initial release&lt;/a&gt; (Thanks for the &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility&lt;/a&gt; reference!) and the second &lt;a href="http://jessekornblum.livejournal.com/243748.html"&gt;addressing feedback&lt;/a&gt;.  There still seems to be a great deal of confusion as to how this tool will be licensed.  Both the &lt;a href="http://www.mantech.com/msma/MDD.asp"&gt;website&lt;/a&gt; and the &lt;a href="https://sourceforge.net/projects/mdd/"&gt;project page&lt;/a&gt; claim it will be GPL’d but they have failed to include the code for the driver, which would seem to be at odds with the GPL.  Unfortunately, it also appears that the initial release of the tool does not work as distributed. Hopefully these issues will be cleared up shortly! After a few modifications, the tool can be coerced into working and we were able to successfully analyze the acquired samples with Volatility.&lt;br/&gt;&lt;br/&gt;In related developments, Volatility friend and contributor &lt;a href="http://www.msuiche.net/_resume_/"&gt;Matthieu Suiche&lt;/a&gt;, the creator of &lt;a href="http://sandman.msuiche.net/"&gt;Sandman&lt;/a&gt;, decided he wanted to be the first person to release a “truly” open source memory acquisition driver.  Thus he released an independently developed open source memory acquisition driver this weekend,&lt;a href="http://www.msuiche.net/tools/win32dd.v1.0.20080614.zip"&gt; win32dd&lt;/a&gt;.  Details can be found in his &lt;a href="http://www.msuiche.net/2008/06/14/capture-memory-under-win2k3-or-vista-with-win32dd/"&gt;blog&lt;/a&gt;.  As with mdd, we have also been able to successfully analyze samples collected with win32dd using Volatility.  You have to admit that this is very impressive for 3 days of programming by a high school student preparing for exams.  Good luck Matthieu!&lt;br/&gt;&lt;br/&gt;While neither tool is probably ready, at this point, to replace your commercial acquisition tools, they are promising developments for the open memory forensics community.  I know both projects would highly appreciate any auditing or testing you are able to provide.  Hopefully through the help of the community and these two projects we will be able to develop a robust open source acquisition solution.&lt;/p&gt;&lt;p&gt;This has also motivated us to finally announce the &lt;a href="http://volatilesystems.blogspot.com/2008/06/memory-forensics-tool-testing.html"&gt;Memory Forensics Tool Testing Initiative&lt;/a&gt;.&lt;/p&gt;</description><link>http://volatility.tumblr.com/post/38563003</link><guid>http://volatility.tumblr.com/post/38563003</guid><pubDate>Sun, 15 Jun 2008 23:34:32 -0400</pubDate></item><item><title>Libewf offers improved support for memory samples</title><description>&lt;a href="http://www.uitwisselplatform.nl/frs/download.php/537/libewf-beta-20080609.tar.gz"&gt;Libewf offers improved support for memory samples&lt;/a&gt;: The latest version of &lt;a href="http://www.uitwisselplatform.nl/projects/libewf/"&gt;libewf&lt;/a&gt;, libewf-beta-20080609, has been updated to offer improved support for memory samples stored in ewf.  In case, a vendor may want to store samples in that format. The samples can now be converted back to raw samples which you can process with your favorite analysis tools (including &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility&lt;/a&gt;!). They can also be handled natively by &lt;a href="http://www.pyflag.net/"&gt;PyFlag&lt;/a&gt;! Thanks to Joachim Metz and  Robert-Jan  Mora for all their great work! So next time you get a sample with an E01 extension, you know what to do…</description><link>http://volatility.tumblr.com/post/38269552</link><guid>http://volatility.tumblr.com/post/38269552</guid><pubDate>Fri, 13 Jun 2008 09:59:00 -0400</pubDate></item><item><title>Recovery of Encryption Keys from Memory Using a Linear Scan</title><description>&lt;a href="http://doi.ieeecomputersociety.org/10.1109/ARES.2008.109"&gt;Recovery of Encryption Keys from Memory Using a Linear Scan&lt;/a&gt;: This paper discusses how encryption keys can be extracted from samples of physical memory using a linear scanning technique that attempts to find key patterns.  The techniques were demonstrated using &lt;a href="http://www.truecrypt.org/"&gt;TrueCryp&lt;/a&gt;&lt;a href="http://www.truecrypt.org/"&gt;t&lt;/a&gt; running on Windows XP. The paper is written well and an easy read for those interested in the topic. The paper does not mention the related work performed by the Princeton team, as part of the &lt;a href="http://citp.princeton.edu/memory/"&gt;“cold boot”&lt;/a&gt; paper, but it is possible that this paper may have been submitted before the Princeton paper was released. They also make the argument that the method we presented in the &lt;a href="http://www.blackhat.com/presentations/bh-dc-07/Walters/Paper/bh-dc-07-Walters-WP.pdf"&gt;VolaTools&lt;/a&gt; paper would not work because the source code is not available but the source code is available and &lt;b&gt;our technique does work&lt;/b&gt;! Maybe they could have found a more compelling example.  Thanks to &lt;a href="http://jessekornblum.livejournal.com/"&gt;Jesse&lt;/a&gt; for pointing me to the paper!</description><link>http://volatility.tumblr.com/post/37168671</link><guid>http://volatility.tumblr.com/post/37168671</guid><pubDate>Wed, 04 Jun 2008 13:14:00 -0400</pubDate></item><item><title>OMFW Update</title><description>&lt;p&gt;Thanks to all those who contacted me over the weekend, &lt;b&gt;half &lt;/b&gt;of the available seats are now reserved for the Open Memory Forensics Workshop (OMFW)!  I also wanted to take this opportunity to address some of the questions we have received:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;OMFW participants are not required to register for &lt;a href="http://www.dfrws.org/"&gt;DFRWS&lt;/a&gt;, but we would recommend it.  There are a number of exciting talks about memory forensics being presented at DFRWS this year. &lt;/li&gt;&lt;li&gt;We have also received a number of questions about the cost of OMFW.  There is no registration fee for OMFW. We want OMFW to be open to all people interested in contributing to the open source memory forensics community.  &lt;/li&gt;&lt;/ul&gt;</description><link>http://volatility.tumblr.com/post/36932919</link><guid>http://volatility.tumblr.com/post/36932919</guid><pubDate>Mon, 02 Jun 2008 17:07:27 -0400</pubDate></item><item><title>Open Memory Forensics Workshop (OMFW)</title><description>&lt;p&gt;Volatile memory forensics (ie., RAM forensics) is becoming an extremely important topic to the future of digital investigations. It has the potential to dramatically transform the way we currently perform digital investigations and help address many of the challenges currently facing the digital forensics community.&lt;br/&gt;&lt;br/&gt;We are pleased to announce the first ever workshop focused on open source volatile memory analysis. This workshop will bring together digital investigation researchers and practitioners to discuss the latest advancements in volatile memory analysis. You will also learn how memory analysis is currently being used to augment digital investigations. Through a series of invited talks and panel discussions you will have the opportunity to engage this exciting community.&lt;br/&gt;&lt;br/&gt;This half-day workshop will be co-located with &lt;a href="http://www.dfrws.org/2008/"&gt;Digital Forensics Research Workshop (DFRWS) 2008&lt;/a&gt; in Baltimore, Maryland, USA, on August 10, 2008. Pre-registration is required and space is limited, so register early. Please note that it will not be possible to register at the door. Reserve your seat by contacting: AAron Walters (awalters [at] 4tphi [dot] net). We are also still seeking individuals with interesting insights who would like to participate as a speaker or panelist.&lt;br/&gt;&lt;br/&gt;Join with industry leaders to discuss the latest advancements in memory forensics and the importance of open source initiatives. This is your opportunity to help shape the future of memory forensics!&lt;br/&gt;&lt;br/&gt;Invited speakers and panelists include:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Dr. Brian Carrier (Basis Technology) &lt;/li&gt;&lt;li&gt;Eoghan Casey (ONKC)&lt;/li&gt;&lt;li&gt;Dr. Michael Cohen (Australian Federal Police)&lt;/li&gt;&lt;li&gt;Brian Dykstra (Jones Dykstra &amp; Associates)&lt;/li&gt;&lt;li&gt;Brendan Dolan-Gavitt (Georgia Institute of Technology)&lt;/li&gt;&lt;li&gt;Matthew Geiger (CERT)&lt;/li&gt;&lt;li&gt;Keith Jones (Jones Dykstra &amp; Associates)&lt;/li&gt;&lt;li&gt;Jesse Kornblum (ManTech)&lt;/li&gt;&lt;li&gt;Andreas Schuster (Deutsche Telekom AG)&lt;/li&gt;&lt;li&gt;AAron Walters (Volatile Systems, LLC)&lt;/li&gt;&lt;li&gt;More to be announced……&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Brought to you by the &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility Team: Open Source Memory Forensics.&lt;/a&gt;&lt;br/&gt;&lt;/p&gt;</description><link>http://volatility.tumblr.com/post/36611137</link><guid>http://volatility.tumblr.com/post/36611137</guid><pubDate>Fri, 30 May 2008 16:13:00 -0400</pubDate></item><item><title>"Firms that hire “reformed” hackers to audit or guard their systems are not acting prudently any more..."</title><description>“Firms that hire “reformed” hackers to audit or guard their systems are not acting prudently any more than if they hired a “reformed” pedophile to babysit their kids. First of all, the ability to hack into a system involves a skill set that is not identical to that required to design a secure system or to perform an audit. Considering how weak many systems are, and how many attack tools are available, “hackers” have not necessarily been particularly skilled. (The same is true of “experts” who discover attacks and weaknesses in existing systems and then publish exploits, by the way — that behavior does not establish the bona fides for real expertise. If anything, it establishes a disregard for the community it endangers.)”&lt;br/&gt;&lt;br/&gt; - &lt;em&gt;Excerpt from &lt;a href="http://www.cerias.purdue.edu/weblogs/spaf/general/post-120/what-did-you-really-expect/"&gt;CERIAS Weblog&lt;/a&gt;. Prof. Eugene Spafford, Executive Director of the Purdue &lt;a href="http://www.cerias.purdue.edu/"&gt; CERIAS &lt;/a&gt; (Center for Education and Research in Information Assurance and Security). I know I have referenced this quote &lt;a href="http://volatilesystems.blogspot.com/2008/01/they-are-playing-you-for-fool.html"&gt;before&lt;/a&gt; but after reading &lt;a href="http://taosecurity.blogspot.com/2008/05/response-to-is-vulnerability-research.html"&gt;Bejtlich’s post&lt;/a&gt; I figured it was worth highlighting again.  Thanks for everything &lt;a href="http://spaf.cerias.purdue.edu/"&gt;Spaf&lt;/a&gt;!&lt;/em&gt;</description><link>http://volatility.tumblr.com/post/35904331</link><guid>http://volatility.tumblr.com/post/35904331</guid><pubDate>Sat, 24 May 2008 10:42:00 -0400</pubDate></item><item><title>PTK Memory Dump Keyword Search</title><description>&lt;a href="http://iritaly.blogspot.com/2008/05/ptk-memory-dump-keyword-search.html"&gt;PTK Memory Dump Keyword Search&lt;/a&gt;: Yes, I know it is written in Italian but you can find a translated version &lt;a href="http://ptk.dflabs.com/news.html"&gt;here&lt;/a&gt;. PTK has recently added the ability to do keyword searching on the data found within an memory images. As we previously mentioned, they have also recently &lt;a href="http://www.dflabs.com/dfblog/?p=82"&gt;announced&lt;/a&gt; the inclusion of &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility 1.1.1&lt;/a&gt; in their upcoming release! Shouts to the &lt;a href="http://ptk.dflabs.com/index.html"&gt;PTK team&lt;/a&gt;!</description><link>http://volatility.tumblr.com/post/35131586</link><guid>http://volatility.tumblr.com/post/35131586</guid><pubDate>Sat, 17 May 2008 11:32:13 -0400</pubDate></item><item><title>UserDump Memory Forensics</title><description>&lt;a href="http://moyix.blogspot.com/2008/05/parsing-windows-minidumps.html"&gt;UserDump Memory Forensics&lt;/a&gt;: Often during engagements, we run across people who collect Win32 process memory images using &lt;a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=E089CA41-6A87-40C8-BF69-28AC08570B7E&amp;displaylang=en"&gt;Microsoft’s userdump&lt;/a&gt; utility.  We will now be able to process those images natively within &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility&lt;/a&gt;.  Shouts to &lt;a href="http://moyix.blogspot.com/"&gt;Brendan Dolan-Gavitt&lt;/a&gt;!</description><link>http://volatility.tumblr.com/post/34920006</link><guid>http://volatility.tumblr.com/post/34920006</guid><pubDate>Thu, 15 May 2008 12:43:41 -0400</pubDate></item><item><title>The GPL Wins Again</title><description>&lt;a href="http://www.groklaw.net/article.php?story=20080508212535665"&gt;The GPL Wins Again&lt;/a&gt;: “To all those who don’t like the license: you don’t have to use it. Just write your own code.” Shouts to guys at &lt;a href="http://gpl-violations.org/"&gt;gpl-violations.org&lt;/a&gt;! </description><link>http://volatility.tumblr.com/post/34254089</link><guid>http://volatility.tumblr.com/post/34254089</guid><pubDate>Fri, 09 May 2008 13:58:00 -0400</pubDate></item><item><title>Windows Hibernation File for Fun and Profit</title><description>&lt;a href="http://www.blackhat.com/html/bh-usa-08/bh-usa-08-schedule.html"&gt;Windows Hibernation File for Fun and Profit&lt;/a&gt;: Congratulations to &lt;a href="http://www.msuiche.net/"&gt;Matthieu Suiche&lt;/a&gt; on getting his presentation accepted to &lt;a href="http://www.blackhat.com/"&gt;Black Hat&lt;/a&gt;. You could probably even convince him to discuss recent GPL violations! While legal recourse is being pursued, maybe this will provide extra motivation for violators to respect the legal system and the community. Matthieu is doing some interesting work and has been a great help with some of the new functionality being added to &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility&lt;/a&gt; 1.3. If you are in Vegas, you should check out his presentation!</description><link>http://volatility.tumblr.com/post/33993172</link><guid>http://volatility.tumblr.com/post/33993172</guid><pubDate>Wed, 07 May 2008 07:47:00 -0400</pubDate></item><item><title>"Research maxims: 1) Pay attention to details. (2) Don’t make stuff up."</title><description>“Research maxims: 1) Pay attention to details. (2) Don’t make stuff up.”&lt;br/&gt;&lt;br/&gt; - &lt;em&gt;&lt;a href="http://www.cs.cmu.edu/~maxion/"&gt;&lt;b&gt;Prof. Roy A. Maxion&lt;/b&gt;&lt;/a&gt;, Carnegie Mellon University,Computer Science Department.&lt;/em&gt;</description><link>http://volatility.tumblr.com/post/33882282</link><guid>http://volatility.tumblr.com/post/33882282</guid><pubDate>Tue, 06 May 2008 07:27:59 -0400</pubDate></item><item><title>DFRWS 2008 Agenda</title><description>&lt;a href="http://dfrws.org/2008/program.shtml"&gt;DFRWS 2008 Agenda&lt;/a&gt;: The program for &lt;a href="http://dfrws.org/2008/"&gt;DFRWS 2008&lt;/a&gt; has been posted. There are a number of papers discussing important advancements in memory forensic analysis that you won’t want to miss. In particular, I want to congratulate &lt;a href="http://computer.forensikblog.de/en/"&gt;Andreas Schuster&lt;/a&gt; , &lt;a href="http://moyix.blogspot.com/"&gt;Brendan Dolan-Gavitt&lt;/a&gt; , &lt;a href="http://www.pyflag.net"&gt;Dr. Michael Cohen&lt;/a&gt; for getting their papers accepted. The great work these gentlemen are doing is helping to make &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility&lt;/a&gt; the most advanced memory forensics framework.  It’s encouraging to see people who are actually contributing to the open source community be rewarded for their hard work! Stay tuned for more exciting DFRWS announcements!</description><link>http://volatility.tumblr.com/post/33829874</link><guid>http://volatility.tumblr.com/post/33829874</guid><pubDate>Mon, 05 May 2008 18:43:26 -0400</pubDate></item><item><title>Linux Memory Forensics</title><description>&lt;a href="http://www.samag.com/documents/s=9053/sam0403e/0403e.htm"&gt;Linux Memory Forensics&lt;/a&gt;</description><link>http://volatility.tumblr.com/post/33690908</link><guid>http://volatility.tumblr.com/post/33690908</guid><pubDate>Sun, 04 May 2008 08:52:43 -0400</pubDate></item><item><title>"But it’s just about impossible to prevent secrets from being written to..."</title><description>“But it’s just about impossible to prevent secrets from being written to memory—presumably, your program needs access to the data at some point.”&lt;br/&gt;&lt;br/&gt; - &lt;em&gt;Chess, Brian and Jacob West. “Secure Programming with Static Analysis”. Addison-Wesley. 2007.&lt;/em&gt;</description><link>http://volatility.tumblr.com/post/33444154</link><guid>http://volatility.tumblr.com/post/33444154</guid><pubDate>Thu, 01 May 2008 13:25:00 -0400</pubDate></item><item><title>PTK Includes Volatility</title><description>&lt;a href="http://iritaly.blogspot.com/2008/04/ptk-memory-analysis.html"&gt;PTK Includes Volatility&lt;/a&gt;: For any of our Italian readers, &lt;a href="http://ptk.dflabs.com/index.html"&gt;PTK&lt;/a&gt; now includes support for &lt;a href="https://www.volatilesystems.com/default/volatility"&gt;Volatility&lt;/a&gt;. Once PTK is released, Volatility users will have the option of using PTK or &lt;a href="http://www.pyflag.net"&gt;PyFlag&lt;/a&gt;.  Thanks for the email Michele!</description><link>http://volatility.tumblr.com/post/33363272</link><guid>http://volatility.tumblr.com/post/33363272</guid><pubDate>Wed, 30 Apr 2008 18:05:49 -0400</pubDate></item><item><title>Software Forensics: Software fingerprints</title><description>&lt;a href="http://computer.forensikblog.de/en/2008/04/implementation_by_vendor_s.html#more"&gt;Software Forensics: Software fingerprints&lt;/a&gt;: You would hope that those same forensics companies claiming to help people enforce the law would at least respect the legal system. There is truly an amazing story going on behind the scenes.  I want to give my respect to all those people that are attempting to “empower the community” as opposed to “exploit the community”! </description><link>http://volatility.tumblr.com/post/33346665</link><guid>http://volatility.tumblr.com/post/33346665</guid><pubDate>Wed, 30 Apr 2008 14:25:42 -0400</pubDate></item><item><title>The 3 Vendors: Software Forensics</title><description>&lt;a href="http://computer.forensikblog.de/en/2008/04/the_3_vendors.html"&gt;The 3 Vendors: Software Forensics&lt;/a&gt;: This is a very interesting post by Andreas Schuster.  You should definitely take some time to check it out! I’m sure we will see a lot more of this activity with respect to volatile memory forensics software. Especially, as vendors are desperately trying to catch up to the research community! Nice work Andreas and others ;)!&lt;br/&gt; </description><link>http://volatility.tumblr.com/post/33112842</link><guid>http://volatility.tumblr.com/post/33112842</guid><pubDate>Mon, 28 Apr 2008 11:06:38 -0400</pubDate></item></channel></rss>
