WEBVTT

00:00:01.773 --> 00:00:04.263 align:middle line:84%
At this point, you're
going to start lab 4.4.

00:00:04.263 --> 00:00:07.513 align:middle line:84%
Now, in this lab, it's designed
a little bit differently.

00:00:07.513 --> 00:00:09.453 align:middle line:84%
We give you
directories, and you are

00:00:09.453 --> 00:00:12.033 align:middle line:84%
going to have to dig for
evidence destruction.

00:00:12.033 --> 00:00:14.133 align:middle line:84%
We wanted to take the
tool away from you

00:00:14.133 --> 00:00:17.323 align:middle line:84%
to force you to do
some manual analysis.

00:00:17.323 --> 00:00:19.923 align:middle line:84%
If we look at lab
4.4, you're going

00:00:19.923 --> 00:00:22.083 align:middle line:84%
to see we did
process it in AXIOM.

00:00:22.083 --> 00:00:28.413 align:middle line:84%
So you can simply go into
the Lab4.4, scroll down,

00:00:28.413 --> 00:00:30.183 align:middle line:90%
and click on Case.mfdb.

00:00:33.523 --> 00:00:36.593 align:middle line:84%
We also ran Alexis's
script for you.

00:00:36.593 --> 00:00:40.553 align:middle line:84%
So you can see the usagestats.db
or the results.sql,

00:00:40.553 --> 00:00:42.553 align:middle line:84%
depending on how you want
to look at that if you

00:00:42.553 --> 00:00:45.233 align:middle line:90%
don't want to run the script.

00:00:45.233 --> 00:00:47.423 align:middle line:84%
In order to run the
usagestat script,

00:00:47.423 --> 00:00:52.863 align:middle line:84%
you have to go into System,
usagestats, and copy that out.

00:00:52.863 --> 00:00:55.943 align:middle line:84%
Now, what I recommend is that
you load the entire user data

00:00:55.943 --> 00:00:58.343 align:middle line:84%
partition into Physical
Analyzer so you

00:00:58.343 --> 00:01:01.353 align:middle line:84%
have two tools of interest
and that you run ALEAPP.

00:01:01.353 --> 00:01:03.653 align:middle line:84%
So I'm going to show you
both ways of doing this.

00:01:03.653 --> 00:01:07.433 align:middle line:84%
In Physical Analyzer,
you can go to File,

00:01:07.433 --> 00:01:20.333 align:middle line:84%
Open case, Add, Common
Source, SD card,

00:01:20.333 --> 00:01:22.583 align:middle line:84%
and that's how you're going
to point it to the folder.

00:01:22.583 --> 00:01:25.343 align:middle line:84%
Point it to that entire user
data folder and bring in.

00:01:25.343 --> 00:01:27.410 align:middle line:84%
Do not point it to lab
4.4 because then it's

00:01:27.410 --> 00:01:29.243 align:middle line:84%
going to try to bring
in all the AXIOM data,

00:01:29.243 --> 00:01:30.543 align:middle line:90%
and it's going to go crazy.

00:01:30.543 --> 00:01:37.703 align:middle line:84%
So just SD card,
folder, user data.

00:01:37.703 --> 00:01:38.543 align:middle line:90%
And let it process.

00:01:38.543 --> 00:01:40.335 align:middle line:84%
It should not take long
because there's not

00:01:40.335 --> 00:01:41.663 align:middle line:90%
much it's going to process.

00:01:41.663 --> 00:01:48.748 align:middle line:84%
If you want to run ALEAPP,
I'm going to go to ALEAPP GUI.

00:01:52.453 --> 00:01:54.373 align:middle line:84%
I'm going to point
it to a folder

00:01:54.373 --> 00:01:56.803 align:middle line:84%
and point it to the
entire user data folder.

00:01:56.803 --> 00:01:57.943 align:middle line:90%
Oh, sorry, I chose file.

00:01:57.943 --> 00:01:58.943 align:middle line:90%
I want to choose folder.

00:02:05.963 --> 00:02:09.683 align:middle line:84%
And my export, I'm going to
save it in G Cases ALEAPP.

00:02:14.673 --> 00:02:16.473 align:middle line:90%
and say process.

00:02:16.473 --> 00:02:19.173 align:middle line:84%
So that way you have three
tools to do this analysis.

00:02:19.173 --> 00:02:21.723 align:middle line:84%
You could also, if you wanted
to leverage some of the bonus

00:02:21.723 --> 00:02:24.483 align:middle line:84%
tools, you could throw this
into to Cellebrite Inspector.

00:02:24.483 --> 00:02:27.428 align:middle line:84%
You could throw it
into Paraben E3.

00:02:27.428 --> 00:02:28.053 align:middle line:90%
That will work.

00:02:28.053 --> 00:02:30.093 align:middle line:84%
So there are multiple
options for you.

00:02:30.093 --> 00:02:31.893 align:middle line:90%
Use at least two tools.

00:02:31.893 --> 00:02:34.833 align:middle line:84%
But don't be afraid
to use ALEAPP as well.

00:02:34.833 --> 00:02:36.213 align:middle line:90%
It's really quick.

00:02:36.213 --> 00:02:38.853 align:middle line:84%
It's going to parse information
for you that may add value

00:02:38.853 --> 00:02:42.313 align:middle line:90%
to this investigation.

00:02:42.313 --> 00:02:45.343 align:middle line:84%
We are now going
to review lab 4.4.

00:02:45.343 --> 00:02:47.773 align:middle line:84%
If you're still working it,
as always, just press pause,

00:02:47.773 --> 00:02:49.393 align:middle line:84%
and then resume
when you're ready.

00:02:49.393 --> 00:02:53.173 align:middle line:84%
For this case that
we have here, one

00:02:53.173 --> 00:02:55.273 align:middle line:84%
of the first things
we want to prove

00:02:55.273 --> 00:03:00.353 align:middle line:84%
is, was Discord ever installed
and used on this device?

00:03:00.353 --> 00:03:04.853 align:middle line:84%
So if you go and you look
at Installed Applications,

00:03:04.853 --> 00:03:06.713 align:middle line:84%
you're going to see
that you don't have it.

00:03:06.713 --> 00:03:09.383 align:middle line:84%
We purposely took
that away from you.

00:03:09.383 --> 00:03:12.623 align:middle line:84%
You could go into Applications
and try to hunt for Discord

00:03:12.623 --> 00:03:13.893 align:middle line:90%
if you wanted to.

00:03:13.893 --> 00:03:17.943 align:middle line:84%
But the easiest way to approach
this is to keyword search.

00:03:17.943 --> 00:03:20.363 align:middle line:90%
So I'm going to go in the AXIOM.

00:03:20.363 --> 00:03:23.093 align:middle line:84%
At the top right, I'm just
going to type Discord,

00:03:23.093 --> 00:03:24.723 align:middle line:90%
and let's see what we get.

00:03:24.723 --> 00:03:26.265 align:middle line:90%
We have a lot of stuff here.

00:03:26.265 --> 00:03:27.473 align:middle line:90%
So we could see a few things.

00:03:27.473 --> 00:03:31.733 align:middle line:84%
We can see that under
/storage/emulated/0/Discord,

00:03:31.733 --> 00:03:36.173 align:middle line:84%
we have some hits, which
means there's user data that

00:03:36.173 --> 00:03:40.313 align:middle line:84%
potentially existed on
storage under primary user

00:03:40.313 --> 00:03:41.843 align:middle line:90%
Pictures/Discord.

00:03:41.843 --> 00:03:45.983 align:middle line:84%
We see some date/time
stamps here.

00:03:45.983 --> 00:03:48.768 align:middle line:84%
So as we keep looking,
we have Google Play.

00:03:48.768 --> 00:03:50.143 align:middle line:84%
And what I'm going
to actually do

00:03:50.143 --> 00:03:52.313 align:middle line:84%
is click on the actual
artifacts on the left.

00:03:52.313 --> 00:03:53.743 align:middle line:90%
So here, this is interesting.

00:03:53.743 --> 00:03:58.273 align:middle line:84%
We have a picture and a
date/time stamp of 4/10/2020.

00:03:58.273 --> 00:04:00.448 align:middle line:90%
Last access 6/13/21.

00:04:03.083 --> 00:04:04.333 align:middle line:90%
Here, we have another picture.

00:04:04.333 --> 00:04:08.523 align:middle line:84%
It looks like a
computer sideways.

00:04:08.523 --> 00:04:12.763 align:middle line:84%
Under Application Usage,
usage history is very helpful.

00:04:12.763 --> 00:04:14.793 align:middle line:84%
So here we have multiple
date/time stamps

00:04:14.793 --> 00:04:18.023 align:middle line:90%
of when Discord was used.

00:04:18.023 --> 00:04:21.065 align:middle line:84%
And look where this is being
pulled from, usagestats.

00:04:21.065 --> 00:04:23.023 align:middle line:84%
So this will be great to
correlate with ALEAPP.

00:04:27.343 --> 00:04:33.163 align:middle line:84%
We could see Discord was
installed by mraceventura1980,

00:04:33.163 --> 00:04:35.413 align:middle line:84%
when it was last updated,
when it was downloaded,

00:04:35.413 --> 00:04:36.703 align:middle line:90%
all of that information.

00:04:36.703 --> 00:04:39.080 align:middle line:84%
And we are pulling this
from localappstatedb,

00:04:39.080 --> 00:04:41.038 align:middle line:84%
which means it came from
the Google Play store.

00:04:44.783 --> 00:04:50.063 align:middle line:84%
Under Custom, we can see
that external.db was parsed.

00:04:50.063 --> 00:04:53.243 align:middle line:84%
And this is where we could see
those actual pictures that were

00:04:53.243 --> 00:04:55.253 align:middle line:90%
stored in a Discord folder.

00:04:55.253 --> 00:04:59.303 align:middle line:84%
Now, the issue is, if they don't
exist any more on that device,

00:04:59.303 --> 00:05:02.003 align:middle line:84%
you would have to dig for them
other ways, maybe in cloud

00:05:02.003 --> 00:05:03.123 align:middle line:90%
or something else.

00:05:03.123 --> 00:05:05.373 align:middle line:90%
So Discord was definitely used.

00:05:05.373 --> 00:05:07.523 align:middle line:84%
There are so many locations
that you can find this.

00:05:07.523 --> 00:05:11.643 align:middle line:84%
If we want to compare
this to usagestats--

00:05:11.643 --> 00:05:20.333 align:middle line:84%
so if I go into ALEAPP,
and I go to usagestat0,

00:05:20.333 --> 00:05:28.610 align:middle line:84%
I could search for Discord and
also get those same results.

00:05:28.610 --> 00:05:30.443 align:middle line:84%
For this next one, you
may have to break out

00:05:30.443 --> 00:05:32.153 align:middle line:90%
a calendar to check it out.

00:05:32.153 --> 00:05:34.493 align:middle line:84%
Was the application and
use during the hours

00:05:34.493 --> 00:05:36.173 align:middle line:84%
where the user was
prohibited from

00:05:36.173 --> 00:05:38.960 align:middle line:84%
using their device Monday
through Friday while at work?

00:05:38.960 --> 00:05:40.793 align:middle line:84%
So you have to assume
Monday through Friday,

00:05:40.793 --> 00:05:42.943 align:middle line:90%
maybe 9:00 to 5:00.

00:05:42.943 --> 00:05:46.243 align:middle line:84%
We have those pictures
from October 4th.

00:05:46.243 --> 00:05:52.703 align:middle line:84%
So when we look at the
pictures on October 4, 2019,

00:05:52.703 --> 00:05:54.203 align:middle line:84%
you would have to
look at a calendar

00:05:54.203 --> 00:05:58.523 align:middle line:84%
to see October 4, 2019, is
this during the work week?

00:05:58.523 --> 00:05:59.711 align:middle line:90%
And it actually is.

00:05:59.711 --> 00:06:01.253 align:middle line:84%
So that's a good
indication that they

00:06:01.253 --> 00:06:02.798 align:middle line:90%
were using it during that time.

00:06:05.533 --> 00:06:08.233 align:middle line:84%
Are there any indicators
on this that the user was

00:06:08.233 --> 00:06:11.563 align:middle line:84%
trying to cover their
tracks or cover up evidence?

00:06:14.153 --> 00:06:21.803 align:middle line:84%
This is where I would search
for things like erase, clean,

00:06:21.803 --> 00:06:23.048 align:middle line:90%
so you could do wipe.

00:06:27.913 --> 00:06:31.723 align:middle line:84%
So in clean, oh, I got very
lucky with that search.

00:06:31.723 --> 00:06:38.273 align:middle line:84%
We can see right, here
piriform.ccleaner on 1/19/2020.

00:06:38.273 --> 00:06:40.321 align:middle line:84%
Let's see what else we
have, application usage.

00:06:40.321 --> 00:06:41.363 align:middle line:90%
Let's check this one out.

00:06:41.363 --> 00:06:46.938 align:middle line:84%
Look here, ramcleaner,
cleanmaster, avgcleaner.

00:06:46.938 --> 00:06:49.313 align:middle line:84%
So this person was definitely
trying to do some cleaning.

00:06:49.313 --> 00:06:50.963 align:middle line:84%
They were searching
the Play Store.

00:06:50.963 --> 00:06:53.573 align:middle line:84%
And we could see app
data, app history,

00:06:53.573 --> 00:06:55.193 align:middle line:90%
we have time stamps for it.

00:06:55.193 --> 00:06:58.993 align:middle line:90%
That's very interesting.

00:06:58.993 --> 00:07:02.113 align:middle line:84%
If we go to some of
these, you should

00:07:02.113 --> 00:07:05.335 align:middle line:84%
see that we'll find it in
localappstate.db as well.

00:07:05.335 --> 00:07:06.793 align:middle line:84%
You could search
that if you wanted

00:07:06.793 --> 00:07:08.383 align:middle line:90%
to go straight to the database.

00:07:08.383 --> 00:07:09.133 align:middle line:90%
It doesn't matter.

00:07:09.133 --> 00:07:10.633 align:middle line:84%
I honestly think
staying in the tool

00:07:10.633 --> 00:07:15.123 align:middle line:84%
and just keyword
searching is just as easy.

00:07:15.123 --> 00:07:16.833 align:middle line:84%
Now the things that
you're missing--

00:07:16.833 --> 00:07:19.083 align:middle line:84%
we didn't give you the
entire forensic extraction,

00:07:19.083 --> 00:07:21.543 align:middle line:84%
so you couldn't find the
wipe time, the setup time.

00:07:21.543 --> 00:07:24.763 align:middle line:84%
But these may be important
in this course going forward.

00:07:24.763 --> 00:07:28.113 align:middle line:84%
So I would start with, can you
tell when the device was wiped?

00:07:28.113 --> 00:07:30.123 align:middle line:84%
Can you tell when
it was restored?

00:07:30.123 --> 00:07:31.893 align:middle line:90%
Go to usagestats.

00:07:31.893 --> 00:07:33.303 align:middle line:90%
Leverage ALEAPP.

00:07:33.303 --> 00:07:35.373 align:middle line:84%
Let it run against
that image file.

00:07:35.373 --> 00:07:37.083 align:middle line:84%
And see what it can
pull out for you

00:07:37.083 --> 00:07:40.413 align:middle line:84%
so you know exactly when the
user started using that device,

00:07:40.413 --> 00:07:42.723 align:middle line:84%
when specific
applications were run,

00:07:42.723 --> 00:07:45.123 align:middle line:84%
how to search for cleaning
applications, and more.
