WEBVTT

00:00:01.714 --> 00:00:02.914 align:middle line:90%
Terminology matters.

00:00:02.914 --> 00:00:06.251 align:middle line:84%
You are going to hear the terms
shown on this slide many times.

00:00:06.251 --> 00:00:07.834 align:middle line:84%
And I want to make
sure I explain them

00:00:07.834 --> 00:00:10.114 align:middle line:90%
to you as frequently as I can.

00:00:10.114 --> 00:00:12.604 align:middle line:84%
When it comes to
Android versus iPhone,

00:00:12.604 --> 00:00:14.644 align:middle line:84%
there are differences
in terminology

00:00:14.644 --> 00:00:16.694 align:middle line:84%
and what will be your
best acquisition.

00:00:16.694 --> 00:00:20.314 align:middle line:90%
So let's start from the bottom.

00:00:20.314 --> 00:00:22.531 align:middle line:84%
When we look at
physical acquisition,

00:00:22.531 --> 00:00:24.364 align:middle line:84%
if you've done mobile
forensics for a while,

00:00:24.364 --> 00:00:26.406 align:middle line:84%
we have been trained that
physical acquisition is

00:00:26.406 --> 00:00:28.414 align:middle line:90%
supposed to be the very best.

00:00:28.414 --> 00:00:30.904 align:middle line:84%
It may obtain data
from that first

00:00:30.904 --> 00:00:33.014 align:middle line:90%
to the last bit on that device.

00:00:33.014 --> 00:00:36.454 align:middle line:84%
Now, do you notice how
"may" is in italics there?

00:00:36.454 --> 00:00:39.034 align:middle line:84%
Because we can't control
all different situations.

00:00:39.034 --> 00:00:42.004 align:middle line:84%
We can't control all of
the methods of acquisition.

00:00:42.004 --> 00:00:45.004 align:middle line:84%
Physical acquisition
is kind of a dying

00:00:45.004 --> 00:00:46.684 align:middle line:90%
trend, which is unfortunate.

00:00:46.684 --> 00:00:50.194 align:middle line:84%
For modern Android
and iOS devices,

00:00:50.194 --> 00:00:52.834 align:middle line:84%
we can no longer get a
physical acquisition of these,

00:00:52.834 --> 00:00:55.594 align:middle line:84%
depending on the level of
encryption on the device.

00:00:55.594 --> 00:00:59.464 align:middle line:84%
And on each section that
pertains to Android and iOS,

00:00:59.464 --> 00:01:01.434 align:middle line:90%
I will tell you why.

00:01:01.434 --> 00:01:04.044 align:middle line:84%
But something you
have to consider.

00:01:04.044 --> 00:01:05.964 align:middle line:84%
If you have an Android
device and you've

00:01:05.964 --> 00:01:07.704 align:middle line:84%
got a physical
acquisition of it,

00:01:07.704 --> 00:01:10.554 align:middle line:84%
you'd better open
that extraction

00:01:10.554 --> 00:01:13.164 align:middle line:84%
to make sure the data
is not encrypted.

00:01:13.164 --> 00:01:14.754 align:middle line:84%
If you do not do
this, this could

00:01:14.754 --> 00:01:16.344 align:middle line:90%
be a fatal mistake for you.

00:01:16.344 --> 00:01:19.567 align:middle line:84%
If you only get the physical
acquisition and everything

00:01:19.567 --> 00:01:21.234 align:middle line:84%
worked but all of the
data is encrypted,

00:01:21.234 --> 00:01:23.664 align:middle line:84%
and then you give it to an
investigator or examiner

00:01:23.664 --> 00:01:26.544 align:middle line:84%
to do analysis,
there's no going back.

00:01:26.544 --> 00:01:29.184 align:middle line:84%
Because, remember, decryption
happens on the device or not

00:01:29.184 --> 00:01:31.134 align:middle line:90%
at all.

00:01:31.134 --> 00:01:32.634 align:middle line:90%
Full file system.

00:01:32.634 --> 00:01:34.434 align:middle line:84%
This is typically
the best acquisition

00:01:34.434 --> 00:01:37.164 align:middle line:84%
we can get on most
Android and iOS devices.

00:01:37.164 --> 00:01:41.394 align:middle line:84%
It is going to give us access
to the most application

00:01:41.394 --> 00:01:45.394 align:middle line:84%
data that is otherwise
protected by that device.

00:01:45.394 --> 00:01:46.824 align:middle line:84%
And again, as this
course goes on,

00:01:46.824 --> 00:01:48.504 align:middle line:84%
this will make
more sense to you.

00:01:48.504 --> 00:01:50.789 align:middle line:84%
For some full file
system access,

00:01:50.789 --> 00:01:52.164 align:middle line:84%
you're going to
have to use tools

00:01:52.164 --> 00:01:54.204 align:middle line:84%
like GrayKey or
Cellebrite Premium

00:01:54.204 --> 00:01:57.174 align:middle line:84%
or send it in to CAS, the
Cellebrite Advanced Services

00:01:57.174 --> 00:01:58.794 align:middle line:90%
lab, to get access.

00:01:58.794 --> 00:02:00.304 align:middle line:90%
That is not always the case.

00:02:00.304 --> 00:02:03.024 align:middle line:84%
And I'm going to teach you
tips and tricks in Section 2

00:02:03.024 --> 00:02:07.604 align:middle line:84%
and Section 3 on how to
get the best acquisition.

00:02:07.604 --> 00:02:10.694 align:middle line:84%
Advanced Logical or
file system is not

00:02:10.694 --> 00:02:12.861 align:middle line:84%
to be confused with
full file system.

00:02:12.861 --> 00:02:14.069 align:middle line:90%
This is completely different.

00:02:14.069 --> 00:02:17.444 align:middle line:84%
You may find where a file
system acquisition is simply

00:02:17.444 --> 00:02:20.954 align:middle line:84%
a backup of an Android
or a backup of an iPhone.

00:02:20.954 --> 00:02:22.636 align:middle line:84%
So really, if you
think about this,

00:02:22.636 --> 00:02:24.344 align:middle line:84%
when you look at file
system, some people

00:02:24.344 --> 00:02:25.496 align:middle line:90%
are like, wait a second.

00:02:25.496 --> 00:02:26.954 align:middle line:84%
If it's just the
backup, couldn't I

00:02:26.954 --> 00:02:28.604 align:middle line:90%
have done that for free?

00:02:28.604 --> 00:02:29.534 align:middle line:90%
Yes, you could.

00:02:29.534 --> 00:02:31.874 align:middle line:84%
And I'm going to teach
you how so you understand

00:02:31.874 --> 00:02:33.964 align:middle line:90%
what this looks like.

00:02:33.964 --> 00:02:35.404 align:middle line:90%
Logical.

00:02:35.404 --> 00:02:39.004 align:middle line:84%
Logical is something I
typically do not leverage,

00:02:39.004 --> 00:02:42.394 align:middle line:90%
with exception of Android.

00:02:42.394 --> 00:02:46.534 align:middle line:84%
When we talked about the
terminology on GSM and CDMA,

00:02:46.534 --> 00:02:49.714 align:middle line:84%
you may find that a full file
system acquisition cannot

00:02:49.714 --> 00:02:50.594 align:middle line:90%
acquire that data.

00:02:50.594 --> 00:02:52.594 align:middle line:84%
And that's where people
are like, wait a second.

00:02:52.594 --> 00:02:54.884 align:middle line:84%
You just said that's
the best acquisition.

00:02:54.884 --> 00:02:55.384 align:middle line:90%
I did.

00:02:55.384 --> 00:02:56.404 align:middle line:90%
Android's weird.

00:02:56.404 --> 00:02:59.554 align:middle line:84%
Android is difficult.
Also, when you

00:02:59.554 --> 00:03:01.744 align:middle line:84%
look at all of these ones
I've already talked about,

00:03:01.744 --> 00:03:04.684 align:middle line:84%
I did not mention
SIM card or SD card.

00:03:04.684 --> 00:03:08.274 align:middle line:84%
Do not assume they are
going to be acquired.

00:03:08.274 --> 00:03:10.284 align:middle line:84%
Manual examination
can be your friend.

00:03:10.284 --> 00:03:13.984 align:middle line:84%
And I will show
you hints on this.

00:03:13.984 --> 00:03:17.654 align:middle line:84%
Let's say you have a device
and you're like, where

00:03:17.654 --> 00:03:18.924 align:middle line:90%
are all of the call logs?

00:03:18.924 --> 00:03:22.014 align:middle line:84%
Why did my extraction
not get the call logs?

00:03:22.014 --> 00:03:23.334 align:middle line:90%
Look on the phone.

00:03:23.334 --> 00:03:25.524 align:middle line:90%
Click on the phone icon.

00:03:25.524 --> 00:03:28.649 align:middle line:84%
If there are no call logs,
the user deleted them.

00:03:28.649 --> 00:03:30.024 align:middle line:84%
If there are call
logs, something

00:03:30.024 --> 00:03:32.044 align:middle line:90%
is wrong with your extraction.

00:03:32.044 --> 00:03:35.104 align:middle line:90%
What about secure applications?

00:03:35.104 --> 00:03:36.934 align:middle line:84%
Section 5 of this
course, all we talk about

00:03:36.934 --> 00:03:40.084 align:middle line:84%
are secure apps and all of
the scary things that apps

00:03:40.084 --> 00:03:42.394 align:middle line:84%
do in the background
that help us forensically

00:03:42.394 --> 00:03:44.262 align:middle line:90%
that are terrifying as users.

00:03:44.262 --> 00:03:46.054 align:middle line:84%
But what happens if
you don't see something

00:03:46.054 --> 00:03:47.074 align:middle line:90%
in your extraction?

00:03:47.074 --> 00:03:49.624 align:middle line:84%
You can always do
manual examination

00:03:49.624 --> 00:03:51.172 align:middle line:90%
of that device to verify.

00:03:51.172 --> 00:03:53.464 align:middle line:84%
Now, if you were doing manual
examination of a device--

00:03:53.464 --> 00:03:56.284 align:middle line:84%
I worked an investigation
once-- it was a sexual assault

00:03:56.284 --> 00:03:57.514 align:middle line:90%
investigation--

00:03:57.514 --> 00:04:00.011 align:middle line:84%
where my tool was not
capturing the text messages.

00:04:00.011 --> 00:04:01.594 align:middle line:84%
And I just scrolled
through that phone

00:04:01.594 --> 00:04:03.484 align:middle line:84%
and take pictures
of every screen.

00:04:03.484 --> 00:04:04.804 align:middle line:90%
It's awful.

00:04:04.804 --> 00:04:08.584 align:middle line:84%
I will try to teach you
tricks on each section

00:04:08.584 --> 00:04:10.444 align:middle line:90%
to avoid doing that.

00:04:10.444 --> 00:04:14.104 align:middle line:84%
But you may find that
if you have an Android,

00:04:14.104 --> 00:04:16.354 align:middle line:84%
you're going to have to
do multiple extractions.

00:04:16.354 --> 00:04:19.534 align:middle line:84%
If you have an iOS device
and you get full file system,

00:04:19.534 --> 00:04:22.114 align:middle line:84%
that is typically good
enough, with the exception

00:04:22.114 --> 00:04:24.484 align:middle line:84%
of some bonus hints
that we throw in

00:04:24.484 --> 00:04:27.244 align:middle line:84%
there to get you
additional log files that

00:04:27.244 --> 00:04:28.894 align:middle line:90%
may aid in your investigation.
