WEBVTT

00:00:01.661 --> 00:00:07.641 align:middle line:84%
For lab 1.4, you are going
to do a few steps to just dip

00:00:07.641 --> 00:00:09.861 align:middle line:90%
your toe in the Android waters.

00:00:09.861 --> 00:00:11.811 align:middle line:84%
In section 2, we're
going to dive full

00:00:11.811 --> 00:00:14.551 align:middle line:84%
into this pool of Android and
swim through all the evidence.

00:00:14.551 --> 00:00:18.051 align:middle line:84%
But for now, what I want
you to do is go to your VM--

00:00:18.051 --> 00:00:23.691 align:middle line:84%
if you go to G Cases
and look at Lab 1.4,

00:00:23.691 --> 00:00:29.341 align:middle line:84%
you will see that I created
a backup file using the UFED.

00:00:29.341 --> 00:00:31.351 align:middle line:84%
In the UFED, I
chose file system,

00:00:31.351 --> 00:00:34.361 align:middle line:90%
and it left me with a backup.

00:00:34.361 --> 00:00:36.061 align:middle line:84%
So if you wanted
to parse with UFED,

00:00:36.061 --> 00:00:39.241 align:middle line:84%
just click on Samsung right
here, and parse the data.

00:00:39.241 --> 00:00:41.671 align:middle line:84%
For those who like to
do things manually,

00:00:41.671 --> 00:00:43.411 align:middle line:84%
I gave you access
to the manual data.

00:00:43.411 --> 00:00:44.371 align:middle line:90%
There's backupab.

00:00:44.371 --> 00:00:46.111 align:middle line:90%
There's shared.ab.

00:00:46.111 --> 00:00:49.351 align:middle line:84%
Here's a Samsung directory
with the backups.

00:00:49.351 --> 00:00:53.731 align:middle line:84%
For those who want to use AXIOM,
I pre-process this for you

00:00:53.731 --> 00:00:54.991 align:middle line:90%
just for the speed.

00:00:54.991 --> 00:01:00.201 align:middle line:84%
So go into AXIOM, and
click on case.mfdb,

00:01:00.201 --> 00:01:01.701 align:middle line:84%
and it's been
pre-processed for you.

00:01:01.701 --> 00:01:03.381 align:middle line:90%
There's no waiting.

00:01:03.381 --> 00:01:06.501 align:middle line:84%
This lab should process very
quickly in Physical Analyzer

00:01:06.501 --> 00:01:07.621 align:middle line:90%
as well.

00:01:07.621 --> 00:01:11.971 align:middle line:84%
So you will see, I have it
loaded in Physical Analyzer.

00:01:11.971 --> 00:01:15.601 align:middle line:84%
I'm going to look at it in
AXIOM, which is opening.

00:01:15.601 --> 00:01:18.961 align:middle line:84%
I recommend that you
use at least two tools.

00:01:18.961 --> 00:01:20.791 align:middle line:90%
Now, the two tools could be--

00:01:20.791 --> 00:01:24.031 align:middle line:84%
OK I'm going to load it just
in AXIOM or Physical Analyzer,

00:01:24.031 --> 00:01:26.941 align:middle line:84%
and then I will use
DB Browser for SQLite,

00:01:26.941 --> 00:01:29.521 align:middle line:84%
or I'll export the file
and look at it manually.

00:01:29.521 --> 00:01:32.691 align:middle line:90%
That's acceptable.

00:01:32.691 --> 00:01:35.191 align:middle line:84%
The lab is going to walk you
through how to load in Physical

00:01:35.191 --> 00:01:38.611 align:middle line:90%
Analyzer, how to load in AXIOM.

00:01:38.611 --> 00:01:41.481 align:middle line:84%
And then there are
three questions.

00:01:41.481 --> 00:01:43.461 align:middle line:84%
Was the Android
device rooted prior

00:01:43.461 --> 00:01:44.631 align:middle line:90%
to the backup being created?

00:01:44.631 --> 00:01:47.991 align:middle line:84%
What supporting
evidence can you find?

00:01:47.991 --> 00:01:51.141 align:middle line:84%
Question two is not questioning
if Snapchat was deleted.

00:01:51.141 --> 00:01:55.101 align:middle line:84%
Snapchat was deleted prior
to creating the backup.

00:01:55.101 --> 00:01:58.491 align:middle line:84%
Can you recover the
username from Snapchat?

00:01:58.491 --> 00:02:00.561 align:middle line:84%
And what other artifacts
were left behind when

00:02:00.561 --> 00:02:02.331 align:middle line:90%
the app was deleted.

00:02:02.331 --> 00:02:05.341 align:middle line:84%
And then, list two websites that
were bookmarked by the user.

00:02:05.341 --> 00:02:08.241 align:middle line:84%
So things that should be
simple, but the different tools

00:02:08.241 --> 00:02:11.581 align:middle line:84%
may do some strange
things for you here.

00:02:11.581 --> 00:02:12.921 align:middle line:90%
So take your time.

00:02:12.921 --> 00:02:16.171 align:middle line:90%
Dig through it.

00:02:16.171 --> 00:02:17.801 align:middle line:90%
Access should happen quickly.

00:02:17.801 --> 00:02:20.001 align:middle line:90%
It's a small backup file.

00:02:20.001 --> 00:02:23.251 align:middle line:90%
And enjoy the lab.

00:02:23.251 --> 00:02:25.351 align:middle line:84%
If you are still
working on lab 1.4,

00:02:25.351 --> 00:02:27.211 align:middle line:84%
just pause the
on-demand recording

00:02:27.211 --> 00:02:28.951 align:middle line:84%
until you're ready
for the review.

00:02:28.951 --> 00:02:30.771 align:middle line:84%
For the first part
of this lab, we

00:02:30.771 --> 00:02:32.971 align:middle line:84%
wanted to know if the
device was rooted.

00:02:32.971 --> 00:02:35.131 align:middle line:84%
There are many things you
could do to detect this.

00:02:35.131 --> 00:02:37.921 align:middle line:90%
I'm going to start in AXIOM.

00:02:37.921 --> 00:02:43.021 align:middle line:84%
And I am going to go
under Application Usage

00:02:43.021 --> 00:02:45.251 align:middle line:90%
and look at the Installed Apps.

00:02:45.251 --> 00:02:47.111 align:middle line:84%
And right away, we
see a few things.

00:02:47.111 --> 00:02:49.391 align:middle line:84%
We can see this
oneclickroute, and we

00:02:49.391 --> 00:02:51.671 align:middle line:90%
can see chainfire.supersu.

00:02:51.671 --> 00:02:54.071 align:middle line:90%
These are related to root.

00:02:54.071 --> 00:02:55.211 align:middle line:90%
So we can see that.

00:02:55.211 --> 00:03:00.081 align:middle line:84%
That's a good indicator that
a root was actually installed.

00:03:00.081 --> 00:03:02.661 align:middle line:84%
You can actually
see the full path

00:03:02.661 --> 00:03:06.011 align:middle line:84%
as listed on the
right-hand side.

00:03:06.011 --> 00:03:10.701 align:middle line:84%
What you can also do is just
search for the word Root.

00:03:10.701 --> 00:03:13.911 align:middle line:84%
And here, we can see there's
Google searches for root--

00:03:13.911 --> 00:03:16.161 align:middle line:84%
which, a search does not
mean it was installed.

00:03:16.161 --> 00:03:18.771 align:middle line:84%
So here we see
searches for towelroot.

00:03:18.771 --> 00:03:23.241 align:middle line:84%
As we scroll out, we
could see more searches

00:03:23.241 --> 00:03:25.716 align:middle line:84%
for different root
keyword terms.

00:03:28.641 --> 00:03:32.501 align:middle line:84%
Under Media Pictures associated
with root-- not relevant.

00:03:32.501 --> 00:03:35.711 align:middle line:84%
But here, Google Play,
we see rootcheck,

00:03:35.711 --> 00:03:38.711 align:middle line:84%
Root Checker for the
account, goodbyefelicia11.

00:03:38.711 --> 00:03:42.161 align:middle line:84%
Now, Root Checker checks to
make sure your device is rooted.

00:03:42.161 --> 00:03:44.831 align:middle line:84%
Most people wouldn't download
that unless they were paranoid

00:03:44.831 --> 00:03:47.164 align:middle line:84%
that someone was on their
device or they wanted to check

00:03:47.164 --> 00:03:49.381 align:middle line:90%
and make sure they had root.

00:03:49.381 --> 00:03:52.501 align:middle line:90%
We have rootcheck.

00:03:52.501 --> 00:03:54.831 align:middle line:84%
And then we have oneclickroot,
which actually shows as

00:03:54.831 --> 00:03:56.901 align:middle line:90%
installed, so that's helpful.

00:03:56.901 --> 00:04:00.081 align:middle line:84%
Under Operating System,
under Android Downloads,

00:04:00.081 --> 00:04:01.941 align:middle line:84%
you can see that the
person did download

00:04:01.941 --> 00:04:05.271 align:middle line:90%
towelroot and oneclickroot.

00:04:05.271 --> 00:04:06.861 align:middle line:90%
Now look at this towelroot.

00:04:06.861 --> 00:04:08.631 align:middle line:90%
Look at the timestamp.

00:04:08.631 --> 00:04:12.021 align:middle line:84%
So it's towelroot
APK, towelroot-1.apk,

00:04:12.021 --> 00:04:14.631 align:middle line:90%
towelroot-2.apk.

00:04:14.631 --> 00:04:17.481 align:middle line:84%
Malware in roots
and anything that

00:04:17.481 --> 00:04:21.111 align:middle line:84%
could be malicious in nature
with the same timestamp

00:04:21.111 --> 00:04:23.361 align:middle line:84%
will download multiple
versions to make sure they land

00:04:23.361 --> 00:04:24.346 align:middle line:90%
on your device.

00:04:24.346 --> 00:04:25.971 align:middle line:84%
I will mention this
again in section 4,

00:04:25.971 --> 00:04:28.411 align:middle line:90%
but I like to mention it here.

00:04:28.411 --> 00:04:30.721 align:middle line:84%
And then there's obviously
keywords and snippets.

00:04:30.721 --> 00:04:33.061 align:middle line:84%
You should be able to find
similar results if you

00:04:33.061 --> 00:04:35.101 align:middle line:84%
search for a root
in Physical Analyzer

00:04:35.101 --> 00:04:36.941 align:middle line:90%
and look at your results.

00:04:36.941 --> 00:04:37.644 align:middle line:90%
So same thing.

00:04:37.644 --> 00:04:39.061 align:middle line:84%
You'll see installed
applications,

00:04:39.061 --> 00:04:42.181 align:middle line:84%
you'll see the searches,
you'll see what was installed.

00:04:42.181 --> 00:04:44.441 align:middle line:84%
It's just up to you
on your preference.

00:04:44.441 --> 00:04:46.441 align:middle line:84%
You don't have to use
two tools for this one.

00:04:46.441 --> 00:04:48.481 align:middle line:84%
So chances are good
that the device

00:04:48.481 --> 00:04:55.981 align:middle line:84%
was rooted because we found
the actual install of the root.

00:04:55.981 --> 00:04:58.801 align:middle line:90%
For the next part, Snapchat--

00:04:58.801 --> 00:05:00.541 align:middle line:84%
so again, this is
not up for debate.

00:05:00.541 --> 00:05:02.251 align:middle line:90%
Snapchat was deleted.

00:05:02.251 --> 00:05:05.071 align:middle line:84%
But what I want to do is,
I want to go into Tools.

00:05:05.071 --> 00:05:10.691 align:middle line:84%
And I'm going to run Fuzzy
Model plugin and let it Run.

00:05:10.691 --> 00:05:14.691 align:middle line:84%
I'm just going to
do a quick glimpse

00:05:14.691 --> 00:05:16.941 align:middle line:84%
and see if I see anything
associated to Snapchat

00:05:16.941 --> 00:05:20.141 align:middle line:90%
that jumps out.

00:05:20.141 --> 00:05:21.851 align:middle line:90%
And I don't.

00:05:21.851 --> 00:05:26.301 align:middle line:84%
If you weren't sure, you
could type Snapchat and see,

00:05:26.301 --> 00:05:27.681 align:middle line:90%
and you don't have anything.

00:05:27.681 --> 00:05:32.721 align:middle line:84%
What I also want to do is I'm
going to go into App Insights,

00:05:32.721 --> 00:05:34.421 align:middle line:84%
no matter how you
want to get to it.

00:05:34.421 --> 00:05:35.796 align:middle line:84%
I'm going to search
for Snapchat.

00:05:40.111 --> 00:05:45.411 align:middle line:84%
And I'm going to run the
AppGenie on it right here

00:05:45.411 --> 00:05:49.029 align:middle line:84%
and just see what
it can get for me.

00:05:49.029 --> 00:05:50.571 align:middle line:84%
Because we know it
was deleted, so we

00:05:50.571 --> 00:05:52.251 align:middle line:90%
want to see if we have any luck.

00:05:52.251 --> 00:05:55.141 align:middle line:84%
And you can see no AppGenie
artifacts were found.

00:05:55.141 --> 00:05:56.421 align:middle line:90%
So that's a bummer.

00:05:56.421 --> 00:05:59.131 align:middle line:90%
Let's go into Magnet.

00:05:59.131 --> 00:06:05.711 align:middle line:84%
And under Custom, I'm
going to look for Snapchat.

00:06:05.711 --> 00:06:07.401 align:middle line:90%
I just want to see if anything.

00:06:07.401 --> 00:06:11.201 align:middle line:84%
Oh, and I have a Clear a Filter
because it's limiting me.

00:06:13.943 --> 00:06:15.526 align:middle line:84%
So I'm just scrolling
down and quickly

00:06:15.526 --> 00:06:17.881 align:middle line:84%
and looking for Snapchat,
and I don't see anything.

00:06:17.881 --> 00:06:21.261 align:middle line:84%
Now, this is where you have to
keyword search in y our tools.

00:06:21.261 --> 00:06:23.631 align:middle line:90%
So I would type Snapchat.

00:06:23.631 --> 00:06:27.351 align:middle line:84%
And all we need to uncover
is the username and anything

00:06:27.351 --> 00:06:30.011 align:middle line:90%
that's residual on it.

00:06:30.011 --> 00:06:33.691 align:middle line:84%
So here, we have a,
Welcome to Snapchat."

00:06:33.691 --> 00:06:37.441 align:middle line:84%
The account is
goodbyefelicia11@gmail.com.

00:06:37.441 --> 00:06:41.991 align:middle line:84%
And we can see, as we scroll
down, it says, "Hello,

00:06:41.991 --> 00:06:43.611 align:middle line:90%
feliciajones11.

00:06:43.611 --> 00:06:46.251 align:middle line:84%
We now have the
username, feliciajones11.

00:06:46.251 --> 00:06:49.431 align:middle line:84%
Where it's pulling this from
is this amazing little file

00:06:49.431 --> 00:06:51.411 align:middle line:90%
right here called logs.db.

00:06:51.411 --> 00:06:54.081 align:middle line:84%
Now, this logs.db is
unique to Samsung.

00:06:54.081 --> 00:06:56.841 align:middle line:84%
I'm going to talk more
about it in section 2.

00:06:56.841 --> 00:06:58.674 align:middle line:84%
What its purpose
is, I have no idea.

00:06:58.674 --> 00:06:59.841 align:middle line:90%
But let's take a look at it.

00:06:59.841 --> 00:07:02.621 align:middle line:84%
It's kind of cool
what you can get.

00:07:02.621 --> 00:07:05.581 align:middle line:84%
And let's switch
to Database view.

00:07:05.581 --> 00:07:11.531 align:middle line:84%
And under Logs, this is where
you could just type the word up

00:07:11.531 --> 00:07:14.076 align:middle line:90%
here Snap.

00:07:14.076 --> 00:07:15.951 align:middle line:84%
You don't have to write
a whole query always.

00:07:15.951 --> 00:07:19.041 align:middle line:84%
So here, we have Team
Snapchat, datetime stamp,

00:07:19.041 --> 00:07:23.151 align:middle line:84%
when you look at this, I would
say Unix Epoch millisecond

00:07:23.151 --> 00:07:24.361 align:middle line:90%
because it's too long.

00:07:24.361 --> 00:07:25.656 align:middle line:90%
It's more than 10.

00:07:25.656 --> 00:07:27.831 align:middle line:90%
So let's convert that guy.

00:07:27.831 --> 00:07:31.631 align:middle line:84%
We look at this, and we
see, yeah, milliseconds.

00:07:31.631 --> 00:07:33.181 align:middle line:90%
So we start looking through.

00:07:33.181 --> 00:07:34.516 align:middle line:90%
You can use your Over Arrow.

00:07:38.461 --> 00:07:39.461 align:middle line:90%
And there's the message.

00:07:39.461 --> 00:07:41.801 align:middle line:84%
Hello feliciajones11,
Before you start Snapping,

00:07:41.801 --> 00:07:44.891 align:middle line:90%
goodbyefelicia11@gmail.com.

00:07:44.891 --> 00:07:46.241 align:middle line:90%
So the tool did it right.

00:07:46.241 --> 00:07:49.941 align:middle line:84%
You can look in AXIOM if you
want, whatever you prefer.

00:07:49.941 --> 00:07:52.751 align:middle line:84%
This is a perfect example of,
we quickly found the answer.

00:07:52.751 --> 00:07:54.371 align:middle line:90%
We quickly validated.

00:07:54.371 --> 00:07:57.731 align:middle line:84%
We did not have to
write a query, done.

00:07:57.731 --> 00:08:01.491 align:middle line:84%
This file right here
is super important.

00:08:01.491 --> 00:08:02.961 align:middle line:90%
Under Shared, 0--

00:08:02.961 --> 00:08:04.371 align:middle line:90%
0 is the primary user--

00:08:04.371 --> 00:08:06.261 align:middle line:90%
you have a Snapchat directory.

00:08:06.261 --> 00:08:09.111 align:middle line:90%
It is 0 bytes in size.

00:08:09.111 --> 00:08:12.531 align:middle line:84%
Depending on how the user
deletes the app, you could say,

00:08:12.531 --> 00:08:15.171 align:middle line:84%
do you want to delete all
the user-created files,

00:08:15.171 --> 00:08:18.021 align:middle line:84%
or do you just want to delete
the application for use?

00:08:18.021 --> 00:08:22.101 align:middle line:84%
So different forms of deletion
will impact what you can find.

00:08:22.101 --> 00:08:23.781 align:middle line:84%
All of the tools
should show you,

00:08:23.781 --> 00:08:27.811 align:middle line:84%
even if it's an empty directory,
you still want to see it.

00:08:27.811 --> 00:08:33.371 align:middle line:84%
So if I go into File System,
click on my Top Directory,

00:08:33.371 --> 00:08:40.381 align:middle line:84%
change this to All Subfolders,
and then Search for Snapchat,

00:08:40.381 --> 00:08:43.831 align:middle line:84%
you should see that we
get that empty directory.

00:08:43.831 --> 00:08:45.901 align:middle line:84%
So AXIOM does the
exact same thing.

00:08:50.591 --> 00:08:52.301 align:middle line:90%
OK the final one--

00:08:52.301 --> 00:08:53.441 align:middle line:90%
I'm going to go back--

00:08:53.441 --> 00:09:00.411 align:middle line:84%
is name-- think bookmarks
is what we're looking for,

00:09:00.411 --> 00:09:04.101 align:middle line:90%
user-created bookmarks.

00:09:04.101 --> 00:09:08.151 align:middle line:84%
There's two websites that
were bookmarked by the user.

00:09:08.151 --> 00:09:12.271 align:middle line:84%
So if we go into AXIOM,
and we go into Web-Related,

00:09:12.271 --> 00:09:16.251 align:middle line:84%
what you can also do-- let's
see if we can do it this way.

00:09:16.251 --> 00:09:21.341 align:middle line:84%
In Artifacts, type
Bookmarks, excellent.

00:09:21.341 --> 00:09:23.731 align:middle line:84%
I'm going to check
these and start here.

00:09:23.731 --> 00:09:26.151 align:middle line:84%
See if I can answer
the question.

00:09:26.151 --> 00:09:27.141 align:middle line:90%
It looks like we can.

00:09:27.141 --> 00:09:29.241 align:middle line:90%
So Samsung browser bookmarks--

00:09:29.241 --> 00:09:32.001 align:middle line:84%
we can see it looks like we
have smarterforensics.com,

00:09:32.001 --> 00:09:34.011 align:middle line:90%
smartequinepak, and target.

00:09:34.011 --> 00:09:36.681 align:middle line:84%
Now, how do I know these
three are user-created.

00:09:36.681 --> 00:09:39.751 align:middle line:84%
Look at the differences--
device name.

00:09:39.751 --> 00:09:44.681 align:middle line:84%
If I scroll over, we
can see when it was

00:09:44.681 --> 00:09:47.201 align:middle line:90%
added, when it was modified.

00:09:47.201 --> 00:09:50.921 align:middle line:84%
So you can tell the difference
in user-created versus not.

00:09:50.921 --> 00:09:55.301 align:middle line:84%
It also tells you that the table
is bookmarked-- pretty easy.

00:09:55.301 --> 00:09:58.411 align:middle line:84%
AXIOM made that
simple, easy for us.

00:09:58.411 --> 00:10:05.291 align:middle line:84%
And Physical Analyzer, you
could search for Bookmarks here,

00:10:05.291 --> 00:10:08.141 align:middle line:90%
and you get 0 results.

00:10:08.141 --> 00:10:12.211 align:middle line:84%
So it looks like it
didn't parse bookmarks.

00:10:12.211 --> 00:10:15.288 align:middle line:90%
You could go into--

00:10:15.288 --> 00:10:16.621 align:middle line:90%
you could keyword search for it.

00:10:16.621 --> 00:10:18.331 align:middle line:84%
You could actually dive
into where you knew,

00:10:18.331 --> 00:10:20.248 align:middle line:84%
but if you didn't know
where you were looking,

00:10:20.248 --> 00:10:22.831 align:middle line:84%
and if you didn't have
AXIOM, let's go in here.

00:10:22.831 --> 00:10:24.361 align:middle line:90%
We're in these databases now.

00:10:26.891 --> 00:10:28.691 align:middle line:84%
You could try to search
for bookmarks here,

00:10:28.691 --> 00:10:30.251 align:middle line:90%
and it finds any hits.

00:10:30.251 --> 00:10:33.129 align:middle line:84%
And it found that
partnerbookmarks one,

00:10:33.129 --> 00:10:34.421 align:middle line:90%
but that doesn't have anything.

00:10:34.421 --> 00:10:37.341 align:middle line:90%
These are all non-user-created.

00:10:37.341 --> 00:10:38.709 align:middle line:90%
So what we need is the SBrowser.

00:10:38.709 --> 00:10:40.001 align:middle line:90%
So you can search for SBrowser.

00:10:53.321 --> 00:10:58.391 align:middle line:84%
SBrowser.db bookmarks--
there they are.

00:11:02.321 --> 00:11:04.211 align:middle line:84%
So not all tools
are created equally.

00:11:04.211 --> 00:11:06.111 align:middle line:90%
AXIOM made it super easy.

00:11:06.111 --> 00:11:08.951 align:middle line:84%
You can go up and filter and
just say, show me bookmarks,

00:11:08.951 --> 00:11:09.941 align:middle line:90%
and it worked.

00:11:09.941 --> 00:11:12.191 align:middle line:84%
Cellebrite didn't do
so well on that one.

00:11:12.191 --> 00:11:15.131 align:middle line:84%
This is where you need more than
one tool to work these labs.
