WEBVTT

00:00:01.660 --> 00:00:04.630 align:middle line:84%
In order for this to work,
the first thing you must do

00:00:04.630 --> 00:00:05.718 align:middle line:90%
is enable USB debugging.

00:00:05.718 --> 00:00:07.510 align:middle line:84%
And I'm going to show
you in the next slide

00:00:07.510 --> 00:00:09.520 align:middle line:90%
how to actually do this.

00:00:09.520 --> 00:00:14.530 align:middle line:84%
USB debugging is required
to trust for ADB to work.

00:00:14.530 --> 00:00:17.405 align:middle line:90%
ADB is the Android Debug Bridge.

00:00:17.405 --> 00:00:19.030 align:middle line:84%
What I want you to
think about this is,

00:00:19.030 --> 00:00:22.222 align:middle line:84%
imagine that little green
guy walking across a bridge,

00:00:22.222 --> 00:00:23.680 align:middle line:84%
getting information
from the phone,

00:00:23.680 --> 00:00:26.020 align:middle line:84%
and bringing it back to
your forensic workstation.

00:00:26.020 --> 00:00:28.330 align:middle line:84%
That is exactly
what must happen.

00:00:28.330 --> 00:00:31.180 align:middle line:84%
If USB debugging is
not enabled, when

00:00:31.180 --> 00:00:34.270 align:middle line:84%
that Android guy tries to cross
the bridge, he hits a wall.

00:00:34.270 --> 00:00:37.092 align:middle line:84%
USB debugging will allow
him into the phone.

00:00:37.092 --> 00:00:38.800 align:middle line:84%
So if you think about
this little process

00:00:38.800 --> 00:00:42.750 align:middle line:84%
of going back and forth,
these two things are required.

00:00:42.750 --> 00:00:46.240 align:middle line:84%
A File System or
Advanced Logical

00:00:46.240 --> 00:00:48.740 align:middle line:84%
could be a combination
of several things.

00:00:48.740 --> 00:00:51.370 align:middle line:84%
One, it could essentially
just be a backup

00:00:51.370 --> 00:00:53.770 align:middle line:90%
that gets you those ab files.

00:00:53.770 --> 00:00:57.970 align:middle line:84%
It could be a backup and
also MTP protocols that

00:00:57.970 --> 00:01:02.210 align:middle line:90%
are run to pull SD card data.

00:01:02.210 --> 00:01:04.910 align:middle line:84%
It could be a software
agent that's actually

00:01:04.910 --> 00:01:06.140 align:middle line:90%
installed onto the phone.

00:01:06.140 --> 00:01:08.390 align:middle line:84%
And this is where people
are like, wait, what?

00:01:08.390 --> 00:01:12.470 align:middle line:84%
Yes, the commercial tools
will want to install software

00:01:12.470 --> 00:01:15.140 align:middle line:84%
onto that Android that
is evidence in order

00:01:15.140 --> 00:01:16.820 align:middle line:90%
to extract information.

00:01:16.820 --> 00:01:19.250 align:middle line:84%
And I'm going to show
you why this happens

00:01:19.250 --> 00:01:21.920 align:middle line:84%
and how to verify what that
software agent actually

00:01:21.920 --> 00:01:22.740 align:middle line:90%
looks like.

00:01:22.740 --> 00:01:24.710 align:middle line:84%
So we're going to treat
it almost like malware.

00:01:24.710 --> 00:01:27.520 align:middle line:84%
We're going to decompile
it and take a look at it.

00:01:27.520 --> 00:01:29.680 align:middle line:84%
Then there's something
called APK Downgrade.

00:01:29.680 --> 00:01:32.020 align:middle line:84%
Now, this is a
Cellebrite capability.

00:01:32.020 --> 00:01:34.510 align:middle line:84%
You can see here it says
last effort, but it works.

00:01:34.510 --> 00:01:37.360 align:middle line:90%
It could ruin the device.

00:01:37.360 --> 00:01:40.390 align:middle line:84%
Chances of it
ruining it are slim,

00:01:40.390 --> 00:01:42.160 align:middle line:84%
however, it does
make changes that

00:01:42.160 --> 00:01:43.780 align:middle line:90%
look like a lot of deletions.

00:01:43.780 --> 00:01:47.950 align:middle line:84%
If you don't believe
me, on section 6--

00:01:47.950 --> 00:01:51.400 align:middle line:84%
that's CTF--
[INAUDIBLE] Android--

00:01:51.400 --> 00:01:54.730 align:middle line:84%
we used APK Downgrade
to examine it.

00:01:54.730 --> 00:01:57.130 align:middle line:90%
It looks like massive deletion.

00:01:57.130 --> 00:02:00.340 align:middle line:84%
Best recommendations here--
if you're doing a backup,

00:02:00.340 --> 00:02:03.100 align:middle line:84%
do not assume it's going
to pull that SD card.

00:02:03.100 --> 00:02:07.210 align:middle line:84%
Do not assume it is going
to acquire the SIM card.

00:02:07.210 --> 00:02:09.910 align:middle line:84%
Nowhere in here do you
see SIM card mentioned.

00:02:09.910 --> 00:02:12.760 align:middle line:84%
You must take the SIM card
out and acquire it yourself.

00:02:12.760 --> 00:02:14.980 align:middle line:84%
Do that with the SD card
too if you have time.

00:02:14.980 --> 00:02:16.780 align:middle line:90%
It's definitely relevant.

00:02:16.780 --> 00:02:19.480 align:middle line:84%
I would write-protect it to
protect those lost access

00:02:19.480 --> 00:02:20.358 align:middle line:90%
dates.

00:02:20.358 --> 00:02:22.150 align:middle line:84%
And also, make sure
you're paying attention

00:02:22.150 --> 00:02:24.220 align:middle line:84%
because, as you see in
the slides coming up,

00:02:24.220 --> 00:02:27.670 align:middle line:84%
the user or examiner has
to interact with the device

00:02:27.670 --> 00:02:30.700 align:middle line:84%
in order to prevent a
screen from being missed.

00:02:30.700 --> 00:02:35.110 align:middle line:84%
Also note, it will cause
the phone to reboot.

00:02:35.110 --> 00:02:37.405 align:middle line:84%
Meaning, it will take a hot
device and make it cold.
