WEBVTT

00:00.670 --> 00:07.330
Hey everyone welcome to extracting and analyzing browser email and I am artifacts in the previous video

00:07.330 --> 00:12.550
we learned how to use Regg repr to retrieve and analyze data from the Windows registry.

00:12.580 --> 00:18.640
Nowadays desktop PCs and laptops are almost always connected to the Internet and most of their usage

00:18.640 --> 00:21.580
is related to any sort of online activities.

00:21.580 --> 00:27.820
So it's easy to understand that the extraction and analysis of Internet artifacts plays a primary role

00:28.060 --> 00:30.220
in digital forensics.

00:30.220 --> 00:35.320
In this video we're going to take a look at how to take advantage of the tools installed on Kalli Linux

00:35.710 --> 00:42.490
to extract and analyze artifacts related to the most common internet activities web browsing email and

00:42.490 --> 00:43.780
instant messaging.

00:43.810 --> 00:50.050
We're going to examine artifacts from the most common browsers like Internet Explorer Firefox and Chrome.

00:50.050 --> 00:55.540
Next we're going to show how to retrieve e-mail messages for common client programs like Outlook and

00:55.540 --> 00:56.260
Thunderbird.

00:56.260 --> 01:00.720
Finally we're going to see how to extract artifacts from a popular I am quiet.

01:00.760 --> 01:06.960
Skype a myriad of data can be extracted from browsers most relevant for forensic investigation.

01:06.970 --> 01:12.100
Our catch history bookmarks cookies and downloaded files.

01:12.280 --> 01:18.730
We start taking a look at Internet Explorer or IEEE that is pre-installed by default on Windows and

01:18.730 --> 01:21.310
perhaps is still the most widespread browser.

01:21.420 --> 01:27.870
IEEE stores its data both and registry keys and in Biles under the user's profile directory typed you

01:27.900 --> 01:34.540
or else for auto completes and preferences are stored and registry keys under key underscore current

01:34.600 --> 01:41.830
underscore user slash software slash Microsoft slash Internet Explorer favorites are located in the

01:41.830 --> 01:47.170
same folder across all versions of Windows user profile favorites.

01:47.270 --> 01:54.450
They're saved just plain text files so they can be inspected directly prior to IEEE vs 10 browser history.

01:54.470 --> 02:01.030
Catch and cookies are stored in index godat files under the user's profile directory.

02:01.030 --> 02:05.260
Here they are locations of the history catch and cookies artifacts.

02:05.260 --> 02:11.140
Now we're going to introduce to Seelye tools that come pre-installed with Kallie Linux to analyze indexed

02:11.140 --> 02:15.460
Ahdaf files and cookies respectively Pascoe and GALERA.

02:15.670 --> 02:20.600
The usage of Pascoe could not be easier as it only takes one input parameter.

02:20.740 --> 02:25.020
The indexed Ahdaf bile and has no other options.

02:25.090 --> 02:28.590
We run it on an indexed Ahdaf file to show a practical example.

02:33.340 --> 02:39.730
The output shows data from a history file such as the visited you or else the access time file and so

02:39.730 --> 02:40.110
on.

02:42.110 --> 02:45.950
Now we take a look at Galera which is a Spanish word meaning cookie.

02:45.950 --> 02:48.500
So we moved to the directory where the cookies are stored

02:51.770 --> 02:53.420
list the contents of the directory

02:57.810 --> 03:00.450
and run the tool against for example this cookie

03:06.190 --> 03:12.670
usage of Galera is very similar to that of Pascoe as it takes a cookie txt file as input.

03:12.670 --> 03:18.250
The output is far more readable than look directly into the cookie text file and it shows information

03:18.250 --> 03:24.710
such as the site name of the variable and its value and the creation and expiration times from Bersa

03:24.730 --> 03:25.810
10 and above.

03:25.930 --> 03:32.530
IEEE stores data related to the browser history and extensible storage engine or EMC database file in

03:32.530 --> 03:36.250
particular web catch via one def file.

03:36.250 --> 03:42.250
These kind of files are not accessible using Pascoe to read and extract A.S.C. database as a package

03:42.250 --> 03:47.740
called lib SCDP containing libraries and tools has been developed.

03:47.740 --> 03:53.320
This package is not pre-installed with Cali Linux so we would have to install it through the usual command.

03:53.320 --> 03:54.580
Apt get install

04:01.560 --> 04:04.380
the output shows that the package is already installed.

04:04.380 --> 04:10.200
We execute the utility ECD be export on the sample web catch via 1. dat file

04:19.800 --> 04:24.870
as you could see in the directory listing a folder with the same name of the input file and the suffix

04:24.900 --> 04:27.340
export has been created.

04:27.480 --> 04:34.990
If we list the lib ESG directory we could see a bunch of text files has been generated.

04:35.060 --> 04:37.100
These files could be created manually.

04:37.100 --> 04:42.920
Unfortunately at the moment no open source tools seem to be available on Linux to automatically extract

04:42.920 --> 04:46.850
and present the data in a more readable and time ordered manner.

04:46.850 --> 04:52.580
Some free tools have been developed for Windows by inner soft and Mandaean so they can be run on Linux

04:52.660 --> 04:54.560
use in the wine program.

04:54.560 --> 05:00.410
As we've seen with Reg Ripper in the last video now that we've covered IEEE we cover other two very

05:00.410 --> 05:03.170
common browsers Firefox and Chrome.

05:03.170 --> 05:06.900
They both store most of their data in sequel database files.

05:07.100 --> 05:08.540
The files are as follows.

05:08.540 --> 05:15.960
History and bookmarks places not sequel lite cookies cookies not sequel lite downloaded files downloads

05:16.000 --> 05:21.020
not sequel light form auto completes form history dot sequel lite.

05:21.200 --> 05:24.990
Firefox also stores its data in one location app data.

05:25.130 --> 05:32.900
Google Chrome on Windows XP and older and an app data local Google Chrome on Windows Vista and newer

05:33.110 --> 05:33.950
on Linux.

05:34.010 --> 05:35.900
The path is home name.

05:36.020 --> 05:41.620
Mozilla Firefox Chrome also stores its data in one location app data.

05:41.690 --> 05:49.250
Google Chrome on Windows XP an older app data local Google Chrome on Windows Vista and newer on Linux.

05:49.250 --> 05:51.770
The paths home user name config.

05:51.800 --> 05:57.920
Google Chrome the name of the piles of interest are SELP explicative for example cookies for cookies

05:57.920 --> 06:02.540
and history for history to read and extract data from a sequel database file.

06:02.600 --> 06:07.760
We could use the sequel IDB browser that is installed by default on Kelly Linux.

06:07.790 --> 06:14.020
Data is stored in various tables within the databases so sequel queries must be executed.

06:14.060 --> 06:19.850
To extrapolate the data of interest we're only going to see how to extract browser activity data from

06:19.850 --> 06:22.330
sample Firefox and Chrome history file.

06:30.680 --> 06:33.220
First we open with sequel IDB browser.

06:33.290 --> 06:40.410
The place is not sequel lite database that contains the Firefox history data.

06:40.480 --> 06:47.470
Notice the database is composed of 11 tables two tables store the basic browsing history data.

06:47.470 --> 06:56.390
Most history visits and most places that are linked between the ID field in most places in most history

06:56.390 --> 06:56.990
visits

07:00.040 --> 07:01.670
to display the browser history.

07:01.750 --> 07:08.170
We can execute an opposite sequel query that I saved or convenience in a text file as the query is quite

07:08.170 --> 07:09.940
long to digit it manually.

07:09.970 --> 07:15.530
We could select and copy the query paste it into the execute sequel window and execute it.

07:24.650 --> 07:30.250
We could see in the output the visited you Your else ordered by the visit date and time for crome.

07:30.290 --> 07:42.560
The procedure is very similar.

07:42.590 --> 07:50.640
We open the history file and see there are nine tables of which you are else and visits store the browser

07:50.640 --> 07:51.540
activity data

08:00.670 --> 08:04.570
to display the data we execute a query similar to that of Firefox

08:13.290 --> 08:16.430
copy the query and paste it in the execute sequel window.

08:22.420 --> 08:28.180
To extract other types of data such as cookies and bookmarks we can execute similar queries on the relative

08:28.180 --> 08:30.040
databases and tables.

08:30.040 --> 08:34.000
So far we've seen how to extract artifacts from the most common browser.

08:34.000 --> 08:39.820
Now it's time to see how to extract and analyze e-mails from two of the most common email clients outlook

08:39.940 --> 08:41.020
and Thunderbird.

08:41.050 --> 08:43.930
These clients are mostly used within corporate environments.

08:44.050 --> 08:50.500
While Web based e-mail services are far more used by private users we don't cover web email because

08:50.500 --> 08:55.410
in this case e-mails are stored on the mail server not on the local system.

08:55.510 --> 09:02.260
Outlook stores emails impersonal storage table or PSP files that could store emails from M-S exchange

09:02.260 --> 09:03.320
service.

09:03.490 --> 09:12.850
Also from P3 IMAP even HTP emails can also be stored in offline storage table or OS t format a Microsoft

09:12.850 --> 09:17.590
Exchange based environments the locations where the user's PC files are located.

09:17.620 --> 09:20.080
For Windows XP and older are as follows.

09:20.080 --> 09:28.570
Windows XP and older app data Microsoft Outlook for Windows Vista newer app data roaming Microsoft Outlook

09:28.780 --> 09:36.230
Thunderbird instead uses the mbox format that is a plain text format mainly used on cross-platform clients.

09:36.250 --> 09:38.810
It stores its data in the following locations.

09:38.830 --> 09:48.070
Windows XP an older app data Thunderbird Vista a newer app data roaming Thunderbird for Linux home user

09:48.070 --> 09:49.640
named Thunderbird.

09:49.720 --> 09:56.260
P.S. TIF files cannot be analyzed directly but we have to use specific tools one of the tools pre-installed

09:56.260 --> 09:59.470
on Kelly Linux is called Read p.s..

09:59.740 --> 10:03.280
This converts P.S. TIF files into the mbox format.

10:03.340 --> 10:09.120
We open a message to analyze its headers that are the metadata associated with the message.

10:09.220 --> 10:16.540
The headers are numerous and are added by the sender's client by the A.P. servers that process the message.

10:16.540 --> 10:21.760
We might have to establish if an e-mail has really been sent from the claimed address or if it's a spoofed

10:21.760 --> 10:23.100
phishing email.

10:23.170 --> 10:28.570
The Received headers show the routing information in reverse chronological order with the host names

10:28.600 --> 10:33.420
and IP addresses of the same T.P. servers that process the email.

10:33.490 --> 10:40.590
We could see the center's mail server that should be on the same domain to that of the sender's email

10:40.590 --> 10:41.420
address.

10:42.330 --> 10:46.010
If it's from a different domain it's likely to be spoofed.

10:46.110 --> 10:49.780
In some cases the senator's IP address is also show.

10:49.890 --> 10:56.280
So we could trace e-mail back to the source last topic of the video is the extraction of artifacts from

10:56.280 --> 11:03.180
an I am program Skype which is one of the most popular in use Skype also keeps its data in sequel databases

11:03.510 --> 11:05.810
located in the following directories.

11:05.850 --> 11:13.680
Windows XP an older app data Skype Skype profile Windows Vista and newer app data roaming Skype Skype

11:13.680 --> 11:19.200
profile for Linux home username Skype Skype profile.

11:19.200 --> 11:26.010
Most of the data like chats messages calls contacts are kept in the main db file while the configuration

11:26.010 --> 11:28.080
settings are stored in the config.

11:28.170 --> 11:29.700
SML file.

11:29.700 --> 11:34.500
We open the main db database with sequel IDB browser to view its structure

11:37.670 --> 11:43.280
to view its structure and we can see all the tables relative to chat's messages calls contacts and so

11:43.280 --> 11:43.470
on

11:51.010 --> 11:53.270
to extract the data that interest us.

11:53.350 --> 11:58.900
We could execute sequel queries like we've done with Firefox and Chrome.

11:58.900 --> 12:04.990
Great job in this video we've examined artifacts from the most common browsers like internet explorer

12:05.320 --> 12:08.220
like i.e. Firefox Chrome.

12:08.410 --> 12:13.840
We also showed how to retrieve email messages from Commack client programs like Outlook and Thunderbird

12:14.050 --> 12:18.890
and we saw how to extract artifacts from a popular I am client Skype.

12:19.060 --> 12:24.370
In the next video file analysis tools we're going to cover the analysis of different kinds of files

12:24.670 --> 12:28.200
using the CLID tools installed on Kalli Linux.
