WEBVTT

00:00.530 --> 00:04.820
Hey Guys welcome to analysis of a Windows image with autopsy.

00:04.820 --> 00:11.260
Previously we introduced autopsy the new features a version for and how to install it on a Windows VM.

00:11.270 --> 00:15.380
We're going to take a look at how to analyze a Windows disk image with autopsy.

00:15.410 --> 00:20.390
We're going to create a new case then open the image and examine the various artifacts extracted from

00:20.390 --> 00:21.080
it.

00:21.080 --> 00:26.090
This includes files of metadata Internet artifacts deleted data and so on.

00:26.090 --> 00:30.260
Finally we're going to cover the timeline analysis and visualization.

00:30.260 --> 00:37.010
Let's assume our Windows VM an autopsy four is up and running autopsy for when opened shows an initial

00:37.010 --> 00:41.550
dialog box asking us to create a new case or open an existing one.

00:41.750 --> 00:48.710
We select Create new case another dialog window appears we can insert information about the case the

00:48.710 --> 00:56.190
name for example suspect PC and the base directory where we want to save the relative files the case

00:56.190 --> 00:58.570
type is single user.

00:58.810 --> 01:04.290
Then click on next we could insert other optional info like the case number and the examiner.

01:04.510 --> 01:10.900
We click on finish and the case is being created once the case is created.

01:10.980 --> 01:14.890
We have to select the data source that in our case is an image file.

01:16.850 --> 01:23.130
We downloaded a sample image from the hacking case scenario from the computer forensic reference data

01:23.130 --> 01:23.610
sets.

01:23.630 --> 01:31.330
At this you are el We've downloaded the image in the case format split into two files.

01:31.360 --> 01:36.730
Let's go back to the autopsy program and select our target image which we previously saved in a shared

01:36.730 --> 01:42.290
folder between the VM and the host system.

01:42.370 --> 01:48.330
Click on next in the next step we have to select which just modules to run for our analysis.

01:48.460 --> 01:53.280
Obviously the more modules we use the more will be the time and disk space needed.

01:53.350 --> 01:55.800
But the results will be more accurate and complete.

01:55.840 --> 02:01.270
This case the only module we exclude is the android analyzer and the VM extractor.

02:01.270 --> 02:03.690
We click on next then on finish.

02:04.900 --> 02:10.780
An autopsy starts running the modules showing the progress and the corresponding status bars which are

02:10.780 --> 02:12.110
in the bottom right corner.

02:12.250 --> 02:17.740
The interface of autopsy has an intuitive layout all the results of the analysis are organized under

02:17.740 --> 02:20.290
a tree structure on the left hand side of the window.

02:20.290 --> 02:22.460
This is called the tree viewer.

02:22.680 --> 02:28.140
The right hand side is divided into the result viewer the top pan and the content viewer the bottom

02:28.140 --> 02:29.140
pan.

02:29.340 --> 02:34.080
When the analysis is finished we could browse the tree view or to examine all the data and artifacts

02:34.080 --> 02:40.200
extracted from the image the data sources presents the image and the partitions in which it is divided.

02:40.320 --> 02:46.320
We select the NTFS partition and it's directories are listed under the tree viewer we can browse through

02:46.320 --> 02:49.020
the directories and files in the result viewer.

02:49.020 --> 02:52.310
We can browse through the directories and files and the result viewer

02:55.850 --> 03:00.460
the attributes of metadata are also listed for each directory and files.

03:00.470 --> 03:03.860
There's also a thumbnail view to see a preview of image files.

03:11.180 --> 03:19.280
Clicking on a file we can see its contents in the content viewer pan.

03:19.410 --> 03:29.770
Also it's hexadecimal representation and the output of the strings tool and the file meta data.

03:29.900 --> 03:35.580
If the file is in an image or a video we can view the file directly in the media view.

03:35.630 --> 03:40.760
Otherwise we can open it with an external application by right clicking on the file and selecting open

03:40.850 --> 03:48.600
an external view if the photo recover module is enabled the deleted files recovered during the analysis

03:48.600 --> 03:53.810
are displayed in the tree viewer under the views deleted file subtree

03:56.460 --> 04:01.110
another useful feature is the file search which we can access from the Tools menu

04:04.100 --> 04:10.220
the file search allows to search for files by the name size date and the known status

04:13.460 --> 04:17.680
we could choose to only view unknown known or known bad files.

04:19.260 --> 04:24.780
To filter files by the known status the hashed database lookup module must be enabled.

04:24.850 --> 04:31.340
This module calculates M.D five hash values for files and looks up hash values in a database.

04:32.180 --> 04:39.280
This database can be imported in the Tools Options menu selecting hashed database then clicking on import

04:39.280 --> 04:46.850
DB instead of importing the whole N.S. RL database we can import a pre-made index which can be downloaded

04:46.850 --> 04:53.420
from this autopsy project page on Source Forge dot net.

04:53.450 --> 04:57.660
The file is a pretty big download when the file has been downloaded.

04:57.670 --> 05:02.060
We unzip and then select the index file to be imported.

05:02.240 --> 05:06.920
The results of the hash database look a module can be seen in the tree viewer under the hash net hits

05:06.920 --> 05:11.160
tab autopsy allows to search for keywords.

05:11.460 --> 05:17.340
Clicking on the keyword search tab where we can search an exact string where we could search an exact

05:17.340 --> 05:20.550
string substring or regular expression.

05:20.940 --> 05:26.460
Clicking on keyword list we can also search using built in keywords that are regular expressions that

05:26.460 --> 05:34.750
identify phone numbers IP addresses email and your Elle's even credit card numbers.

05:36.840 --> 05:42.330
Using these built in list can produce a very large number of results so we can define our keyword lists

05:42.420 --> 05:50.010
that can also be based on the regular expressions to do so we click on manage list then a new list.

05:50.010 --> 05:51.840
We type a name for the list.

05:51.840 --> 05:56.520
For example names we could add new keywords.

05:56.540 --> 06:02.930
Clicking on the corresponding button we could specify exact strings to match substrings and also regular

06:02.930 --> 06:09.400
expressions.

06:09.440 --> 06:15.500
The keyword lists can also be specified in the Tools menu options then in keyword search module configuration

06:15.740 --> 06:17.090
where we can add new lists

06:21.720 --> 06:26.900
the list can be used by the module to automatically search for the specified keywords.

06:26.970 --> 06:33.040
The search results are displayed under the keyword hits subtree in the tree viewer.

06:33.080 --> 06:39.470
For example we could see a list of all the email addresses and for each address the file where the file

06:39.470 --> 06:44.700
where it's been found under the extracted content subtree.

06:44.700 --> 06:55.070
We can examine several artifacts and data extracted from the image the attached devices OS information

06:57.530 --> 06:58.760
OS user accounts

07:03.770 --> 07:15.670
recent documents and various web artifacts like bookmarks cookies Web history and web search

07:20.620 --> 07:26.010
e-mail messages are extracted by the email parser module and shown under the relative node in the tree

07:26.010 --> 07:27.120
viewer.

07:27.460 --> 07:32.830
An important feature that has been introduced with V3 and significantly enhanced with before is the

07:32.840 --> 07:35.650
timeline analysis and visualization.

07:35.650 --> 07:41.590
This feature includes from all the autopsy results that appear in the tree viewer with with the associated

07:41.590 --> 07:42.600
time stamps.

07:42.880 --> 07:47.950
Each event has a time stamp type and description to generate a timeline.

07:47.980 --> 07:53.860
We click on the timeline button and the process takes several minutes to complete.

07:54.010 --> 07:59.320
After the process is complete a second window is open as we could see in the timeline window.

07:59.320 --> 08:06.340
There are three view modes Kountze details and list counts shows a stacked bar chart and displays the

08:06.340 --> 08:12.550
amount of events of a given type that occurred in a given timeframe but does not show specific events.

08:12.550 --> 08:19.380
For instance events related to the file system are displayed in red while those related to web activity

08:19.380 --> 08:21.910
is green.

08:22.030 --> 08:27.810
We can filter events based on their type and subtypes show and only those that interest us.

08:27.940 --> 08:32.590
Events can also be filtered based on a text string and hiding known files.

08:32.680 --> 08:37.420
If we're interested in viewing the events of a more limited timeframe we could click on the Zoom in

08:37.420 --> 08:41.070
and out tool then select a specific time frame.

08:41.100 --> 08:50.810
For instance one single day we can also select it using the calendar having select a time range.

08:50.850 --> 08:56.340
We would like to see the succession and details of the events that occurred to do so we change to the

08:56.340 --> 08:57.240
details view

09:02.550 --> 09:09.120
details view shows individual or groups of related events where the x axis represents the date and time

09:09.860 --> 09:14.970
it shows specific events that happened in a given timeframe or the events occurred before or after a

09:14.970 --> 09:16.140
given event.

09:16.140 --> 09:22.710
Now the y axis is only used as a space to lay out overlapping events events with the same type of description

09:22.710 --> 09:28.110
that occur close together and time may be clustered together and can be expanded.

09:32.130 --> 09:35.500
And collapsed moving the mouse cursor over the event.

09:35.640 --> 09:37.110
Events can also be pinned

09:42.230 --> 09:45.420
list view displays the events in chronological order.

09:45.560 --> 09:49.190
One event for each row with a relative attributes.

09:49.190 --> 09:53.950
It's also possible to save a screen capture of the current view to be included in the report.

09:53.960 --> 10:00.770
Clicking on snapshot report will see more details how to generate reports of the whole forensic analysis

10:00.830 --> 10:02.640
in the last section of the course.

10:02.690 --> 10:10.430
The reporting phase great work in this video we looked at how to analyze a Windows disk image with autopsy.

10:10.430 --> 10:15.820
First we created a new case then open the image and examine the various artifacts extracted from it.

10:15.860 --> 10:19.130
We also cover timeline analysis and visualization.

10:19.160 --> 10:23.840
Next video we're going to see how to analyze an Android device image with autopsy for.
