WEBVTT

00:00.790 --> 00:05.360
Hey everyone welcome to analysis of an android image with autopsy.

00:05.380 --> 00:07.980
Previously we learned how to analyze a Windows image.

00:07.990 --> 00:09.250
Use an autopsy.

00:09.250 --> 00:14.440
For now we're going to take a look at how to extract and analyze artifacts from an Android device.

00:14.440 --> 00:18.210
Image use an autopsy Android analyzer module.

00:18.280 --> 00:23.820
It's one of the new features introduced with V for will introduce the Android analyzer module.

00:23.830 --> 00:29.740
Then show a practical example of using it to analyze an android image Kelly Linux does it come with

00:29.740 --> 00:36.130
tools designed to forensically analyze mobile devices and Android devices in particular autopsy since

00:36.160 --> 00:38.710
v3 provides a valuable feature.

00:38.710 --> 00:44.560
That is the capability of extracting and analyzing artifacts from an android image implemented by the

00:44.560 --> 00:46.450
Android analyzer module.

00:46.690 --> 00:52.720
This module works on physical Dubbs for most Android devices but does not support older devices that

00:52.720 --> 00:54.400
do not have a volume system.

00:54.400 --> 01:00.640
This video we're going to show the module in action we assume have an autopsy for already running on

01:00.640 --> 01:08.020
a Windows VM this time instead of opening a new case will open an existing one of a suspect Android

01:08.020 --> 01:10.620
device image that's already been analyzed.

01:13.140 --> 01:19.830
If we open a new case instead we would ensure to enable Android analyzer in the in just modules configuration

01:19.830 --> 01:20.630
window.

01:20.700 --> 01:23.330
The module has no per run settings.

01:23.430 --> 01:29.140
The results of the analysis are displayed as usual under the tree viewer.

01:29.320 --> 01:35.220
The data source is subtree reports all the partitions identified on the device.

01:35.470 --> 01:37.870
We could select a partition and browse through it.

01:37.870 --> 01:39.820
Inspecting directories and Biles

01:44.980 --> 01:48.370
undervalues deleted files.

01:48.580 --> 01:55.080
We could view all the deleted files recovered by the photo read Carver module the results extracted

01:55.080 --> 01:56.210
contents subtree.

01:56.370 --> 02:01.560
Besides the Internet artifacts and X of meta data like we've already seen in the last video with the

02:01.560 --> 02:09.000
Windows image show specific Android artifacts like call logs contacts and messages.

02:09.000 --> 02:15.600
Android stores these data in sequel databases for example if we take a look at the call logs we could

02:15.600 --> 02:21.510
see the table with the list of calls and the relative info we could choose which columns to display

02:21.540 --> 02:22.510
in a list.

02:22.680 --> 02:26.750
This case I've hidden the phone numbers and names for privacy issues.

02:27.880 --> 02:33.130
The call logs or contacts are stored in the contacts to get DB sequel like database file.

02:33.130 --> 02:38.570
We can also extract these files by right clicking on it then clicking on extract files.

02:38.740 --> 02:43.280
Save it open it later with a sequel light viewer to execute queries on it.

02:43.540 --> 02:49.660
If you right click on contacts to date DBI file we can also see its location on the device file system

02:50.990 --> 02:55.770
by clicking on view source file in directory.

02:55.830 --> 02:57.890
It takes a while to complete the execution

03:01.040 --> 03:01.930
this case.

03:02.060 --> 03:19.850
We could see that the database is located here at data Comcare Android providers contacts databases.

03:19.920 --> 03:26.550
The message is so Tree displays a list of messages outgoing or incoming the message type the date and

03:26.550 --> 03:28.240
time zone.

03:28.300 --> 03:31.330
Even in this case the names of phone numbers are hidden.

03:31.330 --> 03:38.950
The database for the messages is and SS and s not D.B we can see its location by right clicking on it

03:39.190 --> 03:41.530
and selecting view source file in directory

03:44.820 --> 03:48.410
this case we can see the location is data com.

03:48.470 --> 03:57.370
Android providers telephony databases telephony databases as we seen in the previous video.

03:57.390 --> 04:02.110
We can analyze the Android image in the same way as we've analyzed the Windows image.

04:02.340 --> 04:07.860
For example for searching for specific files and keywords and viewing and examining the timeline of

04:07.860 --> 04:15.270
the events for searching for specific files and keywords viewing and examining the timeline of the events.

04:15.300 --> 04:21.570
Great work in this video we've come to the end of the section we've introduced autopsy and the new features

04:21.570 --> 04:23.180
that come with before.

04:23.370 --> 04:29.100
We also covered how to install this version on a Windows VM and show two practical examples of how to

04:29.100 --> 04:35.550
extract and analyze artifacts from a Windows and Android images from windows and Android image.

04:35.550 --> 04:40.830
Autopsy 4 is a really valuable tool that allows to easily analyze forensic images.

04:40.860 --> 04:42.530
Also local disks.

04:42.570 --> 04:47.820
Next section we're going to cover the techniques and tools to acquire and analyze RAM memory.
