WEBVTT

00:00:01.611 --> 00:00:03.771 align:middle line:84%
First, we need to talk
about some basics.

00:00:03.771 --> 00:00:05.671 align:middle line:90%
Android uses NAND flash memory.

00:00:05.671 --> 00:00:07.281 align:middle line:84%
So if you think back
to when we talked

00:00:07.281 --> 00:00:10.161 align:middle line:84%
about solid-state storage and
how the data's moved around

00:00:10.161 --> 00:00:12.891 align:middle line:84%
on the device, that's what
we're going to see with Android.

00:00:12.891 --> 00:00:15.411 align:middle line:84%
Where leveling
will be into play.

00:00:15.411 --> 00:00:19.701 align:middle line:84%
However, starting with Android,
I think Samsung Galaxy S3,

00:00:19.701 --> 00:00:21.951 align:middle line:84%
Garbage Collection
started cleaning up.

00:00:21.951 --> 00:00:24.351 align:middle line:84%
In addition to garbage
collection, which

00:00:24.351 --> 00:00:26.601 align:middle line:84%
cleans the entire
device, you will

00:00:26.601 --> 00:00:28.911 align:middle line:84%
have databases being
vacuumed, which

00:00:28.911 --> 00:00:33.301 align:middle line:84%
is going to go through and clear
anything marked for deletion.

00:00:33.301 --> 00:00:35.281 align:middle line:84%
We are going to have an
operating system that

00:00:35.281 --> 00:00:39.061 align:middle line:90%
is based on the Linux kernel.

00:00:39.061 --> 00:00:40.831 align:middle line:84%
We will also see,
with Android, things

00:00:40.831 --> 00:00:43.621 align:middle line:84%
get a little bit difficult. If
you look at the third bullet,

00:00:43.621 --> 00:00:46.381 align:middle line:84%
Android is open source,
which means users can

00:00:46.381 --> 00:00:48.151 align:middle line:90%
do many things with Android.

00:00:48.151 --> 00:00:50.671 align:middle line:84%
Manufacturers can do
many things with Android.

00:00:50.671 --> 00:00:53.701 align:middle line:84%
You will find different
flavors as you

00:00:53.701 --> 00:00:55.411 align:middle line:84%
go through these
devices, and you

00:00:55.411 --> 00:00:58.101 align:middle line:84%
have to handle them
in different ways.

00:00:58.101 --> 00:01:01.021 align:middle line:84%
Most data is going to be
stored in SQLite databases.

00:01:01.021 --> 00:01:03.981 align:middle line:84%
So if you enjoyed the
last lab, amazing.

00:01:03.981 --> 00:01:06.441 align:middle line:90%
If you hated it, do not panic.

00:01:06.441 --> 00:01:08.931 align:middle line:84%
The tools will do a
great job at parsing most

00:01:08.931 --> 00:01:11.361 align:middle line:90%
of this information for you.

00:01:11.361 --> 00:01:13.391 align:middle line:84%
We're also going to see
something unique here.

00:01:13.391 --> 00:01:18.131 align:middle line:84%
This application sandboxing,
this will really come into play

00:01:18.131 --> 00:01:20.141 align:middle line:90%
at the end of section 2.

00:01:20.141 --> 00:01:21.731 align:middle line:84%
At the end of section
2, we are going

00:01:21.731 --> 00:01:24.971 align:middle line:84%
to try to put a
user at a location

00:01:24.971 --> 00:01:28.811 align:middle line:84%
when an artifact was created and
say the person actually created

00:01:28.811 --> 00:01:30.301 align:middle line:90%
that thing.

00:01:30.301 --> 00:01:34.081 align:middle line:84%
The UID, this Unique
ID for applications,

00:01:34.081 --> 00:01:36.091 align:middle line:84%
will be tracked
with battery stats

00:01:36.091 --> 00:01:39.601 align:middle line:84%
and other things of interest
that will tell you the truth.

00:01:39.601 --> 00:01:41.011 align:middle line:90%
What's killing the battery?

00:01:41.011 --> 00:01:44.971 align:middle line:84%
What's happening on the
device at that point in time?

00:01:44.971 --> 00:01:48.034 align:middle line:84%
Android, unfortunately,
if you asked me,

00:01:48.034 --> 00:01:49.451 align:middle line:84%
I don't know maybe
five years ago,

00:01:49.451 --> 00:01:52.561 align:middle line:84%
I would say Android is probably
the easiest device to acquire.

00:01:52.561 --> 00:01:55.211 align:middle line:84%
Android is now becoming
the most difficult.

00:01:55.211 --> 00:01:57.841 align:middle line:84%
And the reason
are the variances.

00:01:57.841 --> 00:01:59.161 align:middle line:90%
Is it full-disk encryption?

00:01:59.161 --> 00:02:00.511 align:middle line:90%
Is it file-based encryption?

00:02:00.511 --> 00:02:02.041 align:middle line:90%
What chipset is on it?

00:02:02.041 --> 00:02:04.141 align:middle line:84%
There's so many
different manufacturers,

00:02:04.141 --> 00:02:06.631 align:middle line:84%
and there are so many
different versions of Android

00:02:06.631 --> 00:02:08.291 align:middle line:90%
that exist in the wild--

00:02:08.291 --> 00:02:10.831 align:middle line:84%
whereas, compared
to iOS, most people

00:02:10.831 --> 00:02:13.591 align:middle line:84%
are probably between
iOS 13 and 15.

00:02:13.591 --> 00:02:15.721 align:middle line:84%
For Android, my
dad is still using

00:02:15.721 --> 00:02:17.551 align:middle line:90%
Android version 5 I think.

00:02:17.551 --> 00:02:18.751 align:middle line:90%
We're up to 12.

00:02:18.751 --> 00:02:20.529 align:middle line:84%
You have to be ready
for the unexpected

00:02:20.529 --> 00:02:21.571 align:middle line:90%
when it comes to Android.
