WEBVTT

00:00.640 --> 00:01.130
Hi.

00:01.270 --> 00:05.910
And welcome to building a super timeline of the activities in the previous video.

00:05.920 --> 00:10.690
We looked at how to analyze and extract metadata for different types of files.

00:10.990 --> 00:17.260
In this video we're going to introduce timestamps timelines and super timelines then we're going to

00:17.260 --> 00:23.830
cover the log to timeline Placide framework for generating super timelines and show a practical example

00:23.920 --> 00:29.100
on a Windows system in digital forensics like in all forensic sciences.

00:29.230 --> 00:34.510
One of the fundamental questions in examiner answers is when one or more events have occurred.

00:34.510 --> 00:40.930
For this reason the extraction and analysis of Time of time artifacts or time stamps relative to files

00:40.960 --> 00:45.840
or to events generated by the OS applications and or users play a crucial role.

00:45.910 --> 00:51.310
A time stamp is a record that stores the date in time when an event has occurred and could be related

00:51.310 --> 00:58.150
to the file system to a user's activity such as log in time or a system activity like the time when

00:58.150 --> 01:03.030
a service has started and or stopped timestamps can be recorded in differe formats.

01:03.160 --> 01:10.300
For example Windows mainly uses the file time format where timestamps are stored in 64 bit values according

01:10.300 --> 01:14.440
to the Coordinated Universal Time but also uses other formats as well.

01:14.440 --> 01:21.610
Unix in Linux use the post-sex or IPAC 32 bit time format that records the number of seconds since midnight

01:21.610 --> 01:23.630
of January 1st 1970.

01:23.710 --> 01:30.070
Relative to the UTC time zone time stamps are converted in dates and times based on the system local

01:30.070 --> 01:31.050
time zone.

01:31.090 --> 01:36.390
On Windows the local time zone is stored under the registry key given here in the slide.

01:36.400 --> 01:44.200
While in Unix and Linux in C local time which is a link to a time zone directory under user share zone

01:44.200 --> 01:50.980
info file type stamps on Windows are generally referred to as Esmay Seabee times where n is the last

01:50.980 --> 01:55.850
file content modification time a is last file access time.

01:55.970 --> 02:02.080
See last file meditate change time and B file creation time.

02:02.170 --> 02:08.020
These timestamps are stored in the dollar sign standard information attribute within the master file

02:08.020 --> 02:09.110
table entry.

02:09.190 --> 02:15.970
Unix derived systems generally use the first three attributes MacT times and stores them and end notes

02:16.000 --> 02:19.270
analogs to MFT entries in the first video.

02:19.270 --> 02:23.470
The section overview of the sleuth and file system analysis.

02:23.470 --> 02:27.620
We covered the Mac time tool to generate a timeline of the file system activity.

02:27.640 --> 02:32.900
A timeline is a sequence of events in chronological order creating a timeline of the file system is

02:32.920 --> 02:38.980
certainly useful because it shows us when files had been created accessed or modified but we can't only

02:38.980 --> 02:39.640
rely on it.

02:39.640 --> 02:45.210
For example some OSes allow to disable the update of the files last access time.

02:45.220 --> 02:51.790
On Windows it can be achieved with a registry key reported here on Linux with no a time option of the

02:51.790 --> 02:52.800
mount command.

02:52.840 --> 02:59.080
For these reasons it's more useful to reconstruct the overall context in which the events have occurred.

02:59.080 --> 03:05.350
This is possible collecting timestamps from different sources like file system registry about logs Network

03:05.350 --> 03:11.120
Connections browser history etc. which is building so-called super timeline of the activities.

03:11.200 --> 03:17.230
For example a super timeline could tell us that a malicious file has been saved then executed by a user

03:17.800 --> 03:21.240
after he logged on the system and browse to a certain web page.

03:21.370 --> 03:27.940
In this video we cover a Python based framework to create super timeline's which is Plaxo based on log

03:27.940 --> 03:35.050
to timeline which is a CLID originally written in Perl by Kristen Gudmundsson which has been rewritten

03:35.110 --> 03:40.680
and included in class so which the latest version at the moment is onepoint 5.1.

03:40.840 --> 03:47.380
To timeline Parsees time stamp data from multiple sources to create a super timeline of the activities.

03:47.440 --> 03:53.320
It's made up of parser plugins for differe timestamps log to timeline is still the main tool and it

03:53.320 --> 03:57.010
extracts the time stamps and saves them in a plastic storage file.

03:57.010 --> 04:02.710
Other tools like info and piece sort have been added to filter and sort the data in the plastic storage

04:02.710 --> 04:06.780
file lock to time like can now parse image files directly.

04:06.780 --> 04:11.900
Plus it was not installed by default on Kelly Linux to install it.

04:11.900 --> 04:13.960
We simply run the usual command.

04:14.030 --> 04:15.170
Apt get install

04:20.780 --> 04:27.220
the input says that the placers is already installed and the newest version is 1.5 point 1.

04:27.440 --> 04:32.600
In this video we're going to create a super timeline from the Windows image we already used to show

04:32.600 --> 04:34.180
TS K in the first video.

04:34.180 --> 04:39.820
The section we move in the directory where the image resides and executes log to timeline.

04:39.860 --> 04:44.520
Py.

04:44.740 --> 04:48.970
The first parameter is the output class file that we call suspect Plaxo

04:54.400 --> 04:58.210
while the second parameter is the directory where we've mounted the windows in the file

05:02.910 --> 05:03.950
log to timeline.

05:03.990 --> 05:12.040
Also provides the feature of filtering events with the f option specifying the filter file if the offset

05:12.040 --> 05:14.960
inside the image is not specified with the o option.

05:15.000 --> 05:18.490
The available partitions are displayed we choose the partition.

05:18.550 --> 05:22.830
Hit enter and wait for the execution to terminate log to timeline.

05:22.840 --> 05:28.560
Also provides filtering of the events with the f option specifying a filter file.

05:28.630 --> 05:34.670
In this case we can use a pre-installed filter file for Windows that we can find under user share placers

05:34.720 --> 05:35.980
directory.

05:35.980 --> 05:41.020
The filter file is named filter Windows not text.

05:41.020 --> 05:49.050
Now we can execute the command.

05:49.220 --> 05:54.230
Now that we have the Placide storage file we can obtain detailed information we can obtain detailed

05:54.290 --> 05:56.500
information about it with the info tool

05:59.900 --> 06:07.790
this command returns info like the detected OS the parsers used and the counter of time stamp artifacts

06:07.790 --> 06:08.870
for each parser.

06:08.870 --> 06:10.860
The class of file is not readable.

06:11.060 --> 06:14.100
So we have to convert it with the post-processing tool piece swerd

06:17.260 --> 06:27.720
to see a list of compatible output formats we can use the log to time like tool with the Imphal option.

06:27.790 --> 06:31.450
We could see that the supported output formats are listed here.

06:31.450 --> 06:39.610
For example CXXVI separated value an excel sheet format we could convert the file into the CSP or the

06:39.640 --> 06:42.430
X LS X format with the sort tool

06:47.740 --> 06:50.170
we specify the output format with the o option

06:54.310 --> 07:03.100
and the w option to specify the output file.

07:03.200 --> 07:05.600
Then the last argument is the plaster file.

07:12.420 --> 07:17.650
We could analyze the X LS X file using a program like Liberty office Kelk.

07:17.700 --> 07:24.030
Each row was related to an event and contains attributes like the date and time the source description

07:24.510 --> 07:26.710
user file name and so on.

07:27.630 --> 07:30.420
As you can see events are chronologically ordered.

07:31.220 --> 07:34.860
Since the CXXVI file can be very large to analyze manually.

07:35.120 --> 07:37.610
And we could only be interested in certain data.

07:37.640 --> 07:44.180
We could also export output to a sequel like database file to see the list of supported database formats

07:44.570 --> 07:53.150
we could execute the log to timeline tool with the simple option.

07:53.380 --> 07:58.810
We could see that the supported formats are my sequel and sequel lite we could execute the piece or

07:58.810 --> 07:59.820
tool again.

08:03.870 --> 08:13.120
Specified the sequel light output format with 0 option.

08:13.330 --> 08:15.940
Then the W option with the name of the output file.

08:15.970 --> 08:17.770
And finally Plass so file

08:27.500 --> 08:36.960
we can open the generated sequel database with sequel IDB browser.

08:37.000 --> 08:40.630
It shows the structure of the database with various tables.

08:40.780 --> 08:47.080
We can execute sequel queries to display data that interests us based on different attributes like time

08:47.080 --> 08:50.650
slice source file name user etc..

08:50.800 --> 08:55.270
The range of sequel queries we can make is really infinite peace.

08:55.270 --> 08:58.660
It also allows to apply a filter to the output data.

08:58.660 --> 09:04.480
It also provides the slice state option that displays all events that happened x minutes before and

09:04.480 --> 09:11.430
after the defined date X is controlled by the parameter slice size but defaults to 5 minutes.

09:11.590 --> 09:17.320
For example to display all the events that happened 60 minutes before and after the specified time we

09:17.320 --> 09:21.970
could execute the previous command with the slice option followed by the date in time

09:32.410 --> 09:33.880
and the slice size option

09:38.460 --> 09:45.260
with slice time specified in minutes well done in this section.

09:45.290 --> 09:50.570
We've covered the extraction and analysis phase of the digital forensic process and took advantage of

09:50.570 --> 09:53.810
the appropriate command line tools installed on Kelly Linux.

09:53.810 --> 10:00.290
We covered the sleuthed kit a set of Selye tools to analyze file systems and Reg Ripper a tool specifically

10:00.290 --> 10:02.620
written to analyze the Windows registry.

10:02.630 --> 10:08.720
We looked at various tools to extract and analyze browser email and I am artifacts and tools to analyze

10:09.050 --> 10:15.530
and extract meta data for common types of files like executive Bull's images and documents.

10:15.530 --> 10:22.340
Finally we saw how to build a super timeline with log to timeline Plaxo in the next section we're going

10:22.340 --> 10:26.020
to cover file carving process and recovery of deleted data.
