Difference between pages "Upcoming events" and "Rekall"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Conferences)
 
m (Linux)
 
Line 1: Line 1:
<b>PLEASE READ BEFORE YOU EDIT THE LISTS BELOW</b><br>
+
{{Infobox_Software |
When events begin the same day, events of a longer length should be listed first.  New postings of events with the same date(s) as other events should be added after events already in the list. Please use three-letter month abbreviations (i.e. Sep, NOT Sept. or September), use two digit dates (i.e. Jan 01 NOT Jan 1), and use date ranges rather than listing every date during an event(i.e. Jan 02-05, NOT Jan 02, 03, 04, 05).<br>
+
  name = Rekall |
<i>Some events may be <u>limited</u> to <b>Law Enforcement Only</b> or to a specific audience. Such restrictions should be noted when known.</i>
+
  maintainer = [[Michael Cohen]] |
 +
  os = {{Cross-platform}} |
 +
  genre = {{Memory analysis}}, {{Memory imaging}} |
 +
  license = {{GPL}} |
 +
  website = [https://code.google.com/p/rekall/ code.google.com/p/rekall/] |
 +
}}
  
This is a BY DATE listing of upcoming events relevant to [[digital forensics]].  It is not an all inclusive list, but includes most well-known activities.  Some events may duplicate events on the generic [[conferences]] page, but entries in this list have specific dates and locations for the upcoming event.
+
Rekall is the stand-alone continuation of the [[Volatility]] Technology Preview (TP) version, aka the scudette branch.
  
This listing is divided into three sections (described as follows):<br>
+
One of Rekalls goals is to provide better integration with [[GRR]] by improved modularity of the framework and having memory acquisition capability.[http://docs.rekall.googlecode.com/git/overview.html#_history]
<ol><li><b><u>[[Upcoming_events#Calls_For_Papers|Calls For Papers]]</u></b> - Calls for papers for either Journals or for Conferences, relevant to Digital Forensics (Name, Closing Date, URL)</li><br>
+
<li><b><u>[[Upcoming_events#Conferences|Conferences]]</u></b> - Conferences relevant for Digital Forensics (Name, Date, Location, URL)</li><br>
+
<li><b><u>[[Training Courses and Providers]]</u></b> - Training </li><br></ol>
+
  
== Calls For Papers ==
+
== Memory acquisition drivers ==
Please help us keep this up-to-date with deadlines for upcoming conferences that would be appropriate for forensic research.
+
  
{| border="0" cellpadding="2" cellspacing="2" align="top"
+
The drivers can be found under:
|- style="background:#bfbfbf; font-weight: bold"
+
<pre>
! width="30%|Title
+
rekall/tools/linux
! width="15%"|Due Date
+
rekall/tools/osx
! width="15%"|Notification Date
+
rekall/tools/windows
! width="40%"|Website
+
</pre>
|-
+
|2012 secau Security Congress
+
|Sep 30, 2012
+
|Oct 28, 2012
+
|http://conferences.secau.org/
+
|-
+
|First International Workshop on Cloud Computing for Forensics use – IWCCF 2012 –
+
|Oct 03, 2012
+
|Oct 05, 2012
+
|http://edas.info/N12791 - http://www.wikicfp.com/cfp/servlet/event.showcfp?eventid=23756
+
|-
+
|}
+
  
See also [http://www.wikicfp.com/cfp/servlet/tool.search?q=forensics WikiCFP 'Forensics']
+
=== Linux ===
 +
In rekall RC11 the advanced Linux acquisition tool (LMAP) was added. lmap allows to inject the pmem functionality into existing kernel modules to bypass having to build a pmem kernel module for every different kernel version. See the corresponding DFRWS EU 2014 paper for more information about LMAP.
  
== Conferences ==
+
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:
{| border="0" cellpadding="2" cellspacing="2" align="top"
+
<pre>
|- style="background:#bfbfbf; font-weight: bold"
+
cd rekall/tools/linux/
! width="40%"|Title
+
make
! width="20%"|Date/Location
+
</pre>
! width="40%"|Website
+
|-
+
|European Symposium on Research in Computer Security
+
|Sep 10-12<br>Pisa, Italy
+
|http://www.iit.cnr.it/esorics2012/
+
|-
+
|15th International Symposium on Research in Attacks, Intrusions and Defenses
+
|Sep 12-14<br>Vrije Universiteit, Amsterdam, The Netherlands
+
|http://www.raid2012.org/
+
|-
+
|HTCIA International Conference & Training Expo
+
|Sep 16-19<br>Hershey, PA
+
|http://www.htcia.org/index.shtml
+
|-
+
|VirusBulletin 2012
+
|Sep 26-28<br>Dallas, TX
+
|http://www.virusbtn.com/conference/vb2012/index.xml
+
|-
+
|3rd Annual Sleuth Kit and Open Source Digital Forensics Conference
+
|Oct 02-03<br>Chantilly, VA
+
|http://www.basistech.com/about-us/events/open-source-forensics-conference/2012/
+
|-
+
|International Conference on Security in Computer Networks and Distributed Systems (SNDS'12)
+
|Oct 11-12<br>Trivandrum, India
+
|http://www.snds-conference.org/
+
|-
+
|7th IEEE LCN Workshop on Security In Communication Networks
+
|Oct 22-25<br>Clearwater, FL
+
|http://www.sick-workshop.org
+
|-
+
|4th International Conference on Digital Forensics & Cyber Crime
+
|Oct 24-28<br>West Lafayette, IN
+
|http://d-forensics.org/2012/show/home
+
|-
+
|Paraben Forensic Innovations Conference
+
|Nov 03-07<br>Park City, UT
+
|http://www.pfic-conference.com/
+
|-
+
|8th International Conference on Information Assurance and Security (IAS'12)
+
|Nov 21-23<br>Sao Carlos, Brazil
+
|http://www.mirlabs.org/ias12
+
|-
+
|Forensics@NIST 2012
+
|Nov 28-30<br>Rockville, MD
+
|http://www.nist.gov/oles/forensics-2012.cfm
+
|-
+
|IEEE International Workshop on Information Forensics and Security
+
|Dec 02-05<br>Tenerife, Spain
+
|http://www.wifs12.org/index.html
+
|-
+
|28th Annual Computer Security Applications Conference (ACSAC 2012)
+
|Dec 03-07<br>Orlando, FL
+
|http://www.acsac.org
+
|-
+
|2012 secau Security Congress
+
|Dec 03-05<br>Perth, Western Australia
+
|http://conferences.secau.org/
+
|-
+
|2013 DoD Cybercrime Conference
+
|Jan 29-Feb 01<br>Louisville, KY
+
|http://www.dodcybercrime.com/
+
|-
+
|65th Annual AAFS Meeting
+
|Feb 18-23<br>Washington, DC
+
|http://www.aafs.org/aafs-2013-annual-meeting
+
|-
+
|DFRWS 2013
+
|Aug 04-07<br>Monterey, CA
+
|http://dfrws.org/2013
+
|-
+
|Regional Computer Forensics Group GMU 2012
+
|Aug 05-09<br>Fairfax, VA
+
|http://www.rcfg.org
+
|-
+
|}
+
  
==See Also==
+
The acquisition driver is named pmem.ko.
* [[Training Courses and Providers]]
+
 
==References==
+
To load the driver:
* [http://faculty.cs.tamu.edu/guofei/sec_conf_stat.htm Computer Security Conference Ranking and Statistic]
+
<pre>
* [http://www.kdnuggets.com/meetings/ Meetings and Conferences in Data Mining and Discovery]
+
sudo insmod pmem.ko
* http://www.conferencealerts.com/data.htm Data Mining Conferences World-Wide]
+
</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>
 +
rekall/tools/linux/README
 +
</pre>
 +
 
 +
=== Mac OS X ===
 +
 
 +
For more information see:
 +
<pre>
 +
rekall/tools/osx/OSXPMem/README
 +
</pre>
 +
 
 +
=== Windows ===
 +
Since recent versions of Windows require a signed driver rekall comes with both pre-built (signed binary) and source versions of the driver.
 +
 
 +
Both the i386 and amd64 binary version of the driver can be found in the directory:
 +
<pre>
 +
rekall/tools/windows/winpmem/binaries
 +
</pre>
 +
 
 +
E.g.
 +
<pre>
 +
rekall/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>
 +
rekall/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>
 +
 
 +
Note that running dd directly on this device file can crash the machine.
 +
Use the winpmem.exe tool instead because it handles protected memory regions.
 +
 
 +
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>
 +
rekall/tools/windows/README
 +
</pre>
 +
 
 +
== See Also ==
 +
* [[Memory analysis]]
 +
* [[Memory Imaging]]
 +
* [[Volatility]]
 +
 
 +
== External Links ==
 +
* [https://code.google.com/p/rekall/ Project site]
 +
* [http://docs.rekall.googlecode.com/git/index.html Project documentation]
 +
* [http://rekall-forensic.blogspot.com/ Rekall Memory Forensics blog]
 +
* [http://www.rekall-forensic.com/docs/References/Papers/DFRWS2013.html Anti-forensic resilient memory acquisition]] by [[Johannes Stüttgena]] [[Michael Cohen]], August 2013
 +
* [http://www.rekall-forensic.com/docs/References/Papers/DFRWS2014EU.html Robust Linux memory acquisition with minimal target impact], [[Johannes Stüttgena]] [[Michael Cohen]], May 2014

Revision as of 04:33, 25 June 2014

Rekall
Maintainer: Michael Cohen
OS: Cross-platform
Genre: Memory Analysis,Memory Imaging
License: GPL
Website: code.google.com/p/rekall/

Rekall is the stand-alone continuation of the Volatility Technology Preview (TP) version, aka the scudette branch.

One of Rekalls goals is to provide better integration with GRR by improved modularity of the framework and having memory acquisition capability.[1]

Memory acquisition drivers

The drivers can be found under:

rekall/tools/linux
rekall/tools/osx
rekall/tools/windows

Linux

In rekall RC11 the advanced Linux acquisition tool (LMAP) was added. lmap allows to inject the pmem functionality into existing kernel modules to bypass having to build a pmem kernel module for every different kernel version. See the corresponding DFRWS EU 2014 paper for more information about LMAP.

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:

cd rekall/tools/linux/
make

The acquisition driver is named pmem.ko.

To load the driver:

sudo insmod pmem.ko

To check if the driver is running:

sudo lsmod

The driver create a device file named:

/dev/pmem

To unload the driver:

sudo rmmod pmem

To read acquire the memory just read from the device file. e.g.

dd if=/dev/pmem of=image.raw

For more information see:

rekall/tools/linux/README

Mac OS X

For more information see:

rekall/tools/osx/OSXPMem/README

Windows

Since recent versions of Windows require a signed driver rekall comes with both pre-built (signed binary) and source versions of the driver.

Both the i386 and amd64 binary version of the driver can be found in the directory:

rekall/tools/windows/winpmem/binaries

E.g.

rekall/tools/winpmem/binaries/amd64/winpmem.sys

A standalone tool for imaging memory that uses an embedded copy of the pmem driver can be found as winpmem.exe in:

rekall/tools/winpmem/executables/Release/

To load the driver:

winpmem.exe -l

The device filename is (This can not be changed without recompiling):

\\.\pmem

Note that running dd directly on this device file can crash the machine. Use the winpmem.exe tool instead because it handles protected memory regions.

To read and acquire the physical memory and write it to image.raw:

winpmem.exe image.raw

To unload the driver:

winpmem.exe -u 

For more information see:

rekall/tools/windows/README

See Also

External Links