Timeline Creation and Analysis Guides PDF
Timeline Creation and Analysis Guides PDF
Disclaimer:
This document contains information based on research that has been gathered by employee(s) of The
Senator Patrick Leahy Center for Digital Investigation (LCDI). The data contained in this project is
submitted voluntarily and is unaudited. Every effort has been made by LCDI to assure the accuracy and
reliability of the data contained in this report. However, LCDI nor any of our employees make no
representation, warranty or guarantee in connection with this report and hereby expressly disclaims any
liability or responsibility for loss or damage resulting from use of this data. Information in this report can
be downloaded and redistributed by any person or persons. Any redistribution must maintain the LCDI
logo and any references from this report must be properly annotated.
Contents
1 Introduction .......................................................................................................................................... 4
1.1 How to use this guide.................................................................................................................... 4
1.2 Overview of EnCase ...................................................................................................................... 4
1.3 Overview of Forensic Tool Kit ....................................................................................................... 4
1.4 Overview of Log2Timeline ............................................................................................................ 4
1.4.1 Log2Timeline Modules .......................................................................................................... 4
1.4.2 Log2Timeline Time zones ...................................................................................................... 5
1.4.3 Log2Timeline Output ............................................................................................................ 5
1.5 Other Log2Timeline Options ......................................................................................................... 6
1.6 Log2Timeline in SIFT ..................................................................................................................... 7
1.6.1 Preparing Sources for Log2Timeline in SIFT .......................................................................... 7
2 Timeline Creation and Analysis with EnCase 6.19 and 7.04 ................................................................. 8
2.1 Timeline Analysis with EnCase 6.19 .............................................................................................. 8
2.2 Timeline Analysis with EnCase 7.04 ............................................................................................ 11
2.3 Timeline Analysis with Geoff Black’s Timeline EnScript.............................................................. 12
3 Timeline Creation and Analysis with Forensic Tool Kit 4 .................................................................... 15
3.1 Timeline Analysis with Forensic Tool Kit 4 .................................................................................. 15
4 Timeline Creation and Analysis with Log2Timeline in SIFT 2.14 ......................................................... 22
4.1 Configuring SIFT for Log2Timeline .............................................................................................. 22
4.2 Preparing Exhibits for Log2Timeline in SIFT ................................................................................ 24
4.3 Running Log2Timeline-SIFT ......................................................................................................... 27
4.4 Running Log2Timeline for Linux and Macintosh Partitions ........................................................ 28
4.4.1 Running Log2Timeline on a Linux Exhibit ........................................................................... 28
4.4.2 Running Log2Timeline on a Macintosh Exhibit ................................................................... 28
1 Introduction
Another unique file output type is the TLN format. This output is a tab delimited format, though
it is also used by Harlan Carvey’s tools. The TLN is in the ASCII format and can be opened with
most worksheet applications such as Microsoft Excel; it can be converted to CSV format as well.
Another common file output type is SQLite, which will place the information in a database to
allow querying for timeline information versus reading an entire file. The SQLite format can be
useful as the output files may become extremely large, preventing them from being opened by
common applications such as Microsoft Excel or Notepad ++ (we have encountered output files
as large as 2 GB). These are only a few of the supported file formats; the rest can be found at:
http://log2timeline.net/#output.
1
Information from sluethkit.org regarding sample output of the mactime format.
http://wiki.sleuthkit.org/index.php?title=Mactime_output
Figure 1
With the versatility to run across multiple platforms and the options to generate timelines for
sources with a variety of time zones and operating systems, the Log2Timeline framework is the
cornerstone of forensic timeline creation. What makes this framework so incredibly popular
and widely known is its integration with different forensic platforms such as SIFT and
TAPEWORM.
Since DD images do not support compression or encryption, the E01 format is commonly used to
provide both compression and encryption
To begin timeline analysis with EnCase 6.19, a case must be created or opened and evidence must be
added to it (see Figure 1).
Once evidence is added into EnCase, and the software is done parsing the MFT (Master File Table) and
other pre-processing requirements, the timeline feature can be used. By green plating an evidence file
(whether it is an entire case, partition, folder, or uncompressed compound file), all of the entries within
the evidence file will be displayed. Then, after selecting the “Timeline” view from the right pane, the
program will display a graphical representation of the drive in relation to the calendar displayed (See
Figure 2).
To change the focus, a user can zoom in on the data in a specific range by double clicking on a cell. The
right click menu can be used to zoom in and out as well. The focus ranges from a year view (Figure 2) to
a minute view (Figure 3), and the focus can also be modified using the options menu and adjusting the
resolution (See Figure 4).
EnCase 6.19 does not have a native timeline exporting tool comparable to Log2Timeline. EnCase is
intended for case analysis while Log2Timeline is designed as a preprocessing platform. EnCase excels at
case analysis, however, and has the ability to mount files in the case so that each one is revealed. This
allows each file to be individually identified and processed, a feature missing from Log2Timeline.
As with EnCase 6.19, a case needs to be created and evidence must be added before the timeline
feature can be utilized. Once the evidence is added, it is good practice to run the file mounter option in
the case processor, to ensure that all files within compound files are expanded and accurately
represented by the EnCase timeline.
Similar to EnCase 6.19, a green plated evidence file can be viewed by the timeline tab within the
evidence pane. Within the Timeline tab, there are buttons to increase/decrease the timeline resolution,
making it more convenient to use the timeline feature within EnCase.
Similarly to EnCase 6.19, EnCase 7.04 does not offer a timeline exporting tool similar to Log2Timeline,
though EnCase 7.04 is meant for case analysis not preprocessing as Log2Timeline is. However, it should
be noted that Encase 6.19 and 7.04 both support EnScripts, which can use the EnCase platform to create
an exported timeline similar to Log2Timeline.
To create a timeline using this EnScript, the target evidence must be loaded into a case in EnCase (see
Figure 1). Once loaded in, it is best practice to always run the file mounter EnScript, to ensure all of the
compound files can be accurately represented. For the EnScript, use the blue checking to select which
files should be included in the exported timeline. Once the files are selected, open the Timeline Report
EnScript within the EnScript pane of EnCase, and the option window will appear (see Figure 6). In this
window, a series of options can be selected for creating a timeline (see Figure 6).
The script ran quickly and took roughly nine seconds to process the entire partition [See Figure 7]. While
faster than Log2Timeline, the time to create the case and set it up should be accounted for as well. This
timeline created by EnScript will contain more data than its log2timeline counterpart, as it has expanded
compound files, but it also creates additional entries due to its structure. The exported TSV document of
the timeline is shown in Figure 8, and the HTML output is show in Figure 9.
The HTML outputs are split into multiple files and are sorted by Firefox (FF) and Internet Explorer (IE) file
types. Each file is split when it is around 11 MB in size. It appears that the TSV file does not split,
although it was only tested at 15MB.
Figure 11
Once the new case is opened, evidence must be added to the case [See Figure 2]. FTK is built to handle
multiple partitions and file system types, including HFS+, EXT4, NTFS, and FAT partitions, all found in the
FIRE image used for this guide.
Figure 12
Once evidence is added to the case, selecting the refinement options allows the desired processing
options to run. To create a timeline in FTK, remember to select the HTML and/or CSV file listing options
from the evidence processing window [See Figure 3]. These options tell FTK to create a list of files in
HTML/CSV format, including the path, file name, MAC timestamps, and MD5, among others. This is the
only feature allowing for timeline analysis of the drive, so be extra diligent in selecting them while
processing the case.
Figure 13
Figure 14
Running the preprocessing with this many options selected can be time consuming and can also cause
FTK to consume a large number of computer resources while it runs. Once the task is complete, navigate
to the job folder or select the job folder button on the data processing window [See Figure 4]. Within
the case directory are the HTML/CSV file listings generated by FTK [See Figure 5].
Figure 15
The CSV report can be opened with Microsoft Excel and formatted as desired [See Figure 6].
Figure 16
The HTML document can be opened with any web browser [See Figure 7].
Figure 17
It is important to note that both report types contain file names & attributes, such as MD5 and logical
sizes, along with created/modified/accessed dates for each entry found within the FTK 4.1 case for the
evidence.
Table of Contents
Configuring TAPEWORM for Log2Timeline ................................................................................................. 22
Running Log2Timeline in TAPEWORM .......................................................................................................... 4
Reading the output from TAPEWORM ......................................................................................................... 6
The minimum specifications are preconfigured into this VM( Figure 1), but can be altered if more
memory or processing is available. Figure 2 shows increased allocations for the SIFT VM.
Additionally, you can adjust the virtual machine settings to enable shared folders between the host and
guest machines. This allows for the virtual machine to read exhibits from the host machine and to export
the output to the host computer. How to enable this feature is shown in Figure 3.
With shared folders enabled, the virtual machine can be powered on, and SIFT is ready for use on the
workstation. The login screen will appear, prompting for the password (forensics) before granting access
(see Figure 4).
Figure 22 – Using ewfmount to prepare the E01 file for use with Log2Timeline
If the exhibit is Microsoft Windows only, skip to the next section to the section about log2timline-sift
which is Windows only. Drives with partitions other than NTFS (Microsoft Windows) need further
processing before use with Log2Timeline. To ensure that Macintosh or Linux partitions are completely
processed, they must be fully mounted. Once the ewfmount command is run, the individual partitions
must be mounted from the newly converted block file. SIFT also has the mmls utility bundle, allowing for
partition structures to be viewed.
2
For more information and references on block files and loop devices: http://wiki.osdev.org/Loopback_Device
Another command that provides essential information when preparing the block file to be mounted is
the parted framework. This framework allows the partition information to be read from a block file.
Parted shows information regarding the specific file systems in place on the block file as well as byte
information, as opposed to sector information provided my mmls (Figure 7).
To convert the sector offsets listed by mmls to the byte offset needed for the mount command, the
starting sector should be multiplied by the Bytes per sector (See Table 1 for an example conversion).
Now that the partitions within the block file have been identified, they can be individually mounted.
Using the Linux mount command, the Windows partition is mounted to a pre-made directory illustrated
in Figure 8.
Figure 25 – Mounting the Windows partition with the Linux mount command
This same mount process can be repeated for the offsets provided by the mmls conversions (Figure 9
shows Linux mounting only).
Once the partitions are mounted, SIFT is able to run Log2Timeline against the exhibit. Skip to the section
Running Log2Timeline to create a timeline from the new mount point.
When the command is complete, the output is placed in the “cases” directory on the SIFT desktop. From
here, the CSV file can be copied onto the host machine and opened with Microsoft Excel. Once the file is
opened in Excel, the columns must be delimited, as Excel does not automatically parse the information
into columns (See Figure 11). If it parses correctly, it will look similar to the worksheet shown in Figure
12.
Figure 30 – Previewing the Time Zone Set for the Linux Partition
Once the command is run, the timezone stored in the /etc/timezone system file of the partition will be
displayed and log2timeline can be run. The command to run log2timeline is log2timeline –z [exhibit
time zone] –f [selected modules] –o [output format] –v –log [logfile output location] –r –p
[Evidence/exhibit mount point location] (Figure 14).
Figure 32 – Previewing the Time Zone Set for the Macintosh Partition
The text highlighted in Figure 16 suggests the timezone is America/New_York, known as EST5EDT in
log2timeline.
After determining the time zone information from the Macintosh partition, follow the steps outlined for
creating a timeline for Linux (Figure 14).
• datetime
• win32::api
• date::manip
• xml::libxml
• carp::assert
• digest::crc
• data::hexify
• image::exiftool
• file::mork
• datetime::format::strptime
• parse::win32registry
• html::scrubber
Copy the entire directory of XML-Entities/lib/XML folder into the Perl installation/lib/XML directory. After you have copied this,
create a folder within the Perl installation lib/ directory named Mac. Copy the files from the Mac-Properties lib directory into the
newly created Mac folder next. Then you can follow the steps outlined in Table 1.
After completing the installation, the acquired image must be mounted. To do this, use FTK Imager to open the E01 file
(in this example it is FIRE-041913.E01). Right click on the image and select “Image Mounting…” from the context menu.
Then select the “Physical & Logical” mount type and assign a drive letter using the “Block Device/Read Only” mount
method (See Figure 2). Clicking mount will now virtually mount each partition of the E01 as a drive, allowing
Log2Timeline to parse through the partitions.
the test image contained 3 partitions, and the run above run was only for the Windows 7 partition. Windows 7 only
recognizes the NTFS, exFAT, and FAT file systems. Since FTK virtually mounts as a drive on Windows, Windows does not
mount the drives as usable. Windows 7 Is not able to interpret data on EXT or HFS+ file systems, preventing the
Macintosh and Linux partitions from being mounted.
Once the zip file for TAPEWORM is downloaded and unzipped, it can be opened in VMWare Workstation 7, 8,
9,;VMWare Fusion; or VMWare Player, 3, 4, or 5. Additionally, it can be converted for use with VirtualBox ( using the
latest version of any software is recommended). Once it has been opened in the virtualization product, VMWare (shown
in Figure 1) can be configured for the host machine.
Opening the “Edit virtual machine settings” window allows the user to change the number of processors, amount of
RAM, and shared folders to be configured for use. The recommended specifications are preset into the virtual machine.
Figure 2 shows the shared folder configuration.
As seen in Figure 4, the TAPEWORM interface has case options that need to be filled out in regards to the specific case
being processed. After filling out case details, select the evidence type. For creating a timeline, the disk image option is
most often used due to the E01, DD, or AFF files used to acquire exhibits. Additionally, Log2Timeline can be run against a
folder or logical image (but not a single file) using TAPEWORM’s interface.
Once the evidence type is selected, select your evidence and output location. After choosing the input and output
locations and selecting Log2Timeline, hit run. TAPEWORM will automate the process. It allows multiple tools to run in
Timeline Creation and Analysis Guides 6/17/2013 Page 4 of 40
Patrick Leahy Center for Digital Investigation (LCDI)
succession as well, so if the evidence requires other processing, you can select the appropriate tools and options to run
alongside the timeline at this point.
TAPEWORM utilizes a number of the same steps taken when creating a timeline in SIFT 2.14. TAPEWORM begins by
mounting the image, determining the partition types, creating necessary mount points, and doing the math for offsets,
as well as starting and ending sectors.
For the test image used in this tutorial (FIRE 04192013.E01), TAPEWORM was able to create a timeline in 25 hours and
17 minutes. It is important to note that this exhibit had 3 operating systems installed: Windows 7, Mac OSX, and
BackTrack Linux. Each of these Operating Systems runs on a separate time zone, each with unique user data. If the 25
hour and 17 minute run may seem extremely long, note that TAPEWORM ran Log2Timeline against every partition in the
correct time zone, as well as in every format type in one instance without the use of a single command.
Once the timeline is completed, a new folder can be found in the output directory containing an organized (by tool)
output. Inside the log2timeline directory are the file types and logs for running log2timeline, with the partition offset in
the file names. TAPEWORM exports the timelines in CSV, bodyfile, mactime, or TLN formats. The CSV format is fairly
common and can be opened with Microsoft Excel or any other spreadsheet program. The bodyfile and mactime format
can be used with the Sleuth Kit and other open source forensic tools for timeline analysis. The TLN format is a custom
format that can function with Harlan Carvey’s tools.
Opening the CSV files in Microsoft Excel shows the data neatly organized by column: sorted by date and time from
oldest to newest (See Figure 6). Using Excel’s data sort feature, the first row can be used to sort and filter content
throughout the document.
To enable the sorting feature, select the “data” tab in excel (See Figure 7).
Table of Contents
Configuring SIFT for Log2Timeline .............................................................................................................. 22
Preparing Exhibits for Log2Timeline in SIFT ................................................................................................ 24
Running Log2Timeline-SIFT ......................................................................................................................... 27
Running Log2Timeline for Linux and Macintosh Partitions ........................................................................ 28
Running Log2Timeline on a Linux Exhibit ............................................................................................... 28
Running Log2Timeline on a Macintosh Exhibit ....................................................................................... 28