Difference between pages "Log2timeline" and "CAINE Live CD"

From ForensicsWiki
(Difference between pages)
Jump to: navigation, search
(Links)
 
 
Line 1: Line 1:
==log2timeline==
+
{{Infobox_Software |
 +
  name = CAINE Live CD |
 +
  maintainer = [[CAINE Project]] |
 +
  os = {{Linux}} |
 +
  genre = {{Live CD}} |
 +
  license = {{GPL}}, others |
 +
  website = [http://www.caine-live.net/] |
 +
}}
  
log2timeline is designed as a framework for artifact timeline creation and analysis. The main purpose is to provide a single tool to parse various log files and artifacts found on suspect systems (and supporting systems, such as network equipment) and produce a body file that can be used to create a timeline, using tools such as mactime from TSK, for forensic investigators.
+
'''CAINE Live CD''' is a forensic [[Live CD]] built on top of [[Ubuntu]].
  
The tool is written in Perl for Linux but has been tested using Mac OS X (10.5.7 and 10.5.8). Parts of it should work natively in Windows as well (with ActiveState Perl installed).
+
== Bootable Side ==
  
==Description==
+
== Live Side ==
log2timeline takes a log file (or a directory) and parses it to produce a body file that can be imported into other tools for timeline analysis. The tool has both a modular based approach to the input file as well as the output file. The default behavior of the current version is to export the timeline in a body format readable by TSK's (The SleuthKit) [http://wiki.sleuthkit.org/index.php?title=Body_file mactime] (although this can be easily changed). log2timeline is build as a series of scripts, this one being the front-end, which uses other scripts to actually parse the log files (called modules). The tool is build to be easily extended for anyone that wants to create a new module.
+
  
The tool contains (current version of 0.51 nightly build (20102608)) three front-ends:
+
== Forensic Issues ==
* '''log2timeline''' - The main front-end.  A tool capable of parsing a single log file/directory pointed to the tool using a selected input module.
+
* '''timescanner''' - A recursive front-end capable of parsing a directory passed to the tool and recursively go through each and every file/dir and try to parse it with every or selected input modules (to provide an automatic method of creating a super timeline).
+
* '''glog2timeline''' - A simple GUI front-end, with similar capabilities as log2timeline (the main front-end)
+
  
==Currently Supported Input Modules==
+
* CAINE Live CD versions before 1.0 will automount [[Ext3]] file systems during the boot process and recover them if required (bug in ''initrd'' scripts);
 +
* '''Caine Live CD Version 1.0 uses brand new mounting policies''':
  
The currently supported input modules (as of version 0.51 nightly build (20102608)) are:
+
The mounting policy for any internal or external devices adopted by CAINE: never mount automatically any device and when the user clicks on the device icon the system will mount it in read only mode on a LOOP device.
 +
- When a user decide to mount a device through the Disk Mounter applet, it will always mounted with the following options: ro,loop,noatime,noexec,nosuid,nodev.
  
* '''apache2_access''' - Parse the content of a Apache2 access log file
+
- If the user decides to mount a device via terminal, he can use the “mount” command but all the mount options must be specified.
* '''apache2_error''' - Parse the content of a Apache2 error log file
+
The ext3 driver will be ignored when ext2 and ext3 partitions are mounted in the future and the ext2 driver used instead. This protects any ext3 partitions from a forensic point-of-view. Ext2 does not use journaling, so when an ext3 partition is mounted, there is no danger of modifying the meta-data when increasing the count inside said journal.
* '''chrome''' - Parse the content of a Chrome history file
+
Applying a special patch (Maxim Suhanov's patch) we fixed the bug, that changed the journal of the ext3/ext4 file system, when the computer was switch off not using the shutdown procedure. Fixed in the fstab: forbidding the auto-mounting of the MMCs and put a control for the "esotic names" like /dev/sdad1
* '''evt''' - Parse the content of a [[Windows Event Log (EVT)|Windows 2k/XP/2k3 Event Log]]
+
* '''evtx''' - Parse the content of a [[Windows XML Event Log (EVTX)]] file
+
* '''exif''' - Extract metadata information from files using ExifTool
+
* '''ff_bookmark''' - Parse the content of a Firefox bookmark file
+
* '''firefox2''' - Parse the content of a Firefox 2 browser history
+
* '''firefox3''' - Parse the content of a Firefox 3 history file
+
* '''iehistory''' - Parse the content of an index.dat file containg IE history
+
* '''iis''' - Parse the content of a IIS W3C log file
+
* '''isatxt''' - Parse the content of a ISA text export log file
+
* '''mactime''' - Parse the content of a body file in the mactime format
+
* '''mcafee''' - Parse the content of a log file
+
* '''opera''' - Parse the content of an Opera's global history file
+
* '''oxml''' - Parse the content of an OpenXML document (Office 2007 documents)
+
* '''pcap''' - Parse the content of a PCAP file
+
* '''pdf''' - Parse some of the available PDF document metadata
+
* '''prefetch''' - Parse the content of the Prefetch directory
+
* '''recycler''' - Parse the content of the recycle bin directory
+
* '''restore''' - Parse the content of the restore point directory
+
* '''setupapi''' - Parse the content of the SetupAPI log file in Windows XP
+
* '''sol''' - Parse the content of a .sol (LSO) or a Flash cookie file
+
* '''squid''' - Parse the content of a Squid access log (http_emulate off)
+
* '''syslog''' - Parse the content of a Linux Syslog log file
+
* '''tln''' - Parse the content of a body file in the TLN format
+
* '''userassist''' - Parses the NTUSER.DAT registry file
+
* '''volatility''' - Parse the content of a Volatility output files (psscan2, sockscan2, ...)
+
* '''win_link''' - Parse the content of a Windows shortcut file (or a link file)
+
* '''wmiprov''' - Parse the content of the wmiprov log file
+
* '''xpfirewall''' - Parse the content of a XP Firewall log
+
  
 +
- If the user wants to mount and write on an NTFS media should instead use the "ntfs-3g" command (e.g., $ sudo ntfs-3g /dev/sda1 /media/sda1).
  
==Currently Supported Output Modules==
+
    * $ sudo ntfs-3g /device-path /your-mount-point
 
+
The currently supported output modules (as of version 0.51 nightly build (20102608)) are:
+
 
+
* '''beedocs''' - Output timeline using tab-delimited file to import into BeeDocs
+
* '''cef''' - Output timeline using the ArcSight Commen Event Format (CEF)
+
* '''cftl''' - Output timeline in a XML format that can be read by CFTL
+
* '''csv''' - Output timeline using CSV (Comma Separated Value) file
+
* '''mactime''' - Output timeline using mactime format
+
* '''mactime_l''' - Output timeline using legacy version of the mactime format (version 1.x and 2.x)
+
* '''simile''' - Output timeline in a XML format that can be read by a SIMILE widget
+
* '''sqlite''' - Output timeline into a SQLite database
+
* '''tab''' - Output timeline using TDV (Tab Delimited Value) file
+
* '''tln''' - Output timeline using H. Carvey's TLN format
+
* '''tlnx''' - Output timeline using H. Carvey's TLN format in XML
+
 
+
 
+
== External Links ==
+
; [http://log2timeline.net log2timeline web site]
+
; [http://www.sans.org/reading_room/whitepapers/logging/mastering-super-timeline-log2timeline_33438 SANS GCFA Gold paper about the tool]
+
; [http://blogs.sans.org/computer-forensics/2010/03/19/digital-forensic-sifting-super-timeline-analysis-and-creation/ A quick run on how to create a super timeline]
+
; [http://blog.kiddaland.net/?s=log2timeline Blog posts about the tool]
+
; [https://blogs.sans.org/computer-forensics/2009/08/13/artifact-timeline-creation-and-analysis-tool-release-log2timeline/ Part 1 of the SANS Forensic blog post about the tool]
+
; [https://blogs.sans.org/computer-forensics/2009/08/14/artifact-timeline-creation-and-analysis-part-2/ Part 2 of the SANS forensic blog post about the tool]
+

Revision as of 10:20, 11 November 2009

CAINE Live CD
Maintainer: CAINE Project
OS: Linux
Genre: Live CD
License: GPL, others
Website: [1]

CAINE Live CD is a forensic Live CD built on top of Ubuntu.

Bootable Side

Live Side

Forensic Issues

  • CAINE Live CD versions before 1.0 will automount Ext3 file systems during the boot process and recover them if required (bug in initrd scripts);
  • Caine Live CD Version 1.0 uses brand new mounting policies:

The mounting policy for any internal or external devices adopted by CAINE: never mount automatically any device and when the user clicks on the device icon the system will mount it in read only mode on a LOOP device. - When a user decide to mount a device through the Disk Mounter applet, it will always mounted with the following options: ro,loop,noatime,noexec,nosuid,nodev.

- If the user decides to mount a device via terminal, he can use the “mount” command but all the mount options must be specified. The ext3 driver will be ignored when ext2 and ext3 partitions are mounted in the future and the ext2 driver used instead. This protects any ext3 partitions from a forensic point-of-view. Ext2 does not use journaling, so when an ext3 partition is mounted, there is no danger of modifying the meta-data when increasing the count inside said journal. Applying a special patch (Maxim Suhanov's patch) we fixed the bug, that changed the journal of the ext3/ext4 file system, when the computer was switch off not using the shutdown procedure. Fixed in the fstab: forbidding the auto-mounting of the MMCs and put a control for the "esotic names" like /dev/sdad1

- If the user wants to mount and write on an NTFS media should instead use the "ntfs-3g" command (e.g., $ sudo ntfs-3g /dev/sda1 /media/sda1).

   * $ sudo ntfs-3g /device-path /your-mount-point