WEBVTT

00:00:01.694 --> 00:00:04.204 align:middle line:84%
So in the slide that
shows you we're on health.

00:00:04.204 --> 00:00:05.284 align:middle line:90%
We're in the FileDump.

00:00:05.284 --> 00:00:06.964 align:middle line:90%
And you can go back and forth.

00:00:06.964 --> 00:00:08.614 align:middle line:84%
What we're going
to do here is let's

00:00:08.614 --> 00:00:11.104 align:middle line:90%
find something of interest.

00:00:11.104 --> 00:00:15.214 align:middle line:84%
So let's say Social
Media, Facebook.

00:00:21.934 --> 00:00:29.014 align:middle line:90%
We have this wall post here.

00:00:29.014 --> 00:00:32.619 align:middle line:84%
If I asked you where in
the database this existed,

00:00:32.619 --> 00:00:35.934 align:middle line:84%
you would click on
this source file.

00:00:35.934 --> 00:00:38.084 align:middle line:84%
But if I ask you where
in the entire file

00:00:38.084 --> 00:00:42.434 align:middle line:84%
system does this exist, what's
the offset, what you need to do

00:00:42.434 --> 00:00:44.364 align:middle line:84%
is something
completely different.

00:00:44.364 --> 00:00:48.154 align:middle line:84%
You have to go
into File Systems.

00:00:48.154 --> 00:00:49.954 align:middle line:84%
You have to scroll
all the way to the top

00:00:49.954 --> 00:00:51.954 align:middle line:90%
and click on that FileDump.

00:00:51.954 --> 00:00:56.044 align:middle line:84%
So what you want to
see is that raw hex.

00:00:56.044 --> 00:00:58.654 align:middle line:84%
You want to see this green
that we just searched.

00:00:58.654 --> 00:01:02.844 align:middle line:84%
And then when you go back to
Facebook and you click on this,

00:01:02.844 --> 00:01:04.974 align:middle line:84%
if you switch to FileDump
it should take you to it,

00:01:04.974 --> 00:01:05.579 align:middle line:90%
and it did.

00:01:05.579 --> 00:01:06.954 align:middle line:84%
Sometimes it
doesn't work and you

00:01:06.954 --> 00:01:08.746 align:middle line:84%
have to make sure you're
not over-clicking.

00:01:08.746 --> 00:01:12.084 align:middle line:84%
But what this did was
it took us to that

00:01:12.084 --> 00:01:18.984 align:middle line:84%
offset in the entire extraction
on where that artifact exists.

00:01:18.984 --> 00:01:20.664 align:middle line:84%
This is different
than the database,

00:01:20.664 --> 00:01:22.014 align:middle line:90%
and it's so important.

00:01:22.014 --> 00:01:24.714 align:middle line:84%
Because there are so many times
that if you find something

00:01:24.714 --> 00:01:26.094 align:middle line:84%
that the user
thinks they deleted

00:01:26.094 --> 00:01:29.076 align:middle line:84%
or they think that
doesn't exist or you're

00:01:29.076 --> 00:01:30.534 align:middle line:84%
trying to prove
wear leveling, this

00:01:30.534 --> 00:01:32.384 align:middle line:90%
is how you're going to do it.

00:01:32.384 --> 00:01:39.614 align:middle line:84%
So again, you find-- let me
find something else, a call log,

00:01:39.614 --> 00:01:40.114 align:middle line:90%
maybe.

00:01:43.944 --> 00:01:45.651 align:middle line:84%
I could click on
calllog.db, but that's

00:01:45.651 --> 00:01:47.734 align:middle line:84%
going to tell me in that
database where it exists.

00:01:47.734 --> 00:01:49.684 align:middle line:90%
That's not what I want.

00:01:49.684 --> 00:01:54.134 align:middle line:84%
For this call to Cafe,
I click on the FileDump

00:01:54.134 --> 00:01:56.042 align:middle line:84%
and it takes me out
to the call logs now.

00:01:56.042 --> 00:01:57.584 align:middle line:84%
And then we can see
that information.

00:01:57.584 --> 00:01:59.984 align:middle line:84%
If you hover above it
and you can click on it,

00:01:59.984 --> 00:02:02.286 align:middle line:84%
it's because it's
parsed by the tool.

00:02:02.286 --> 00:02:03.744 align:middle line:84%
You're going to do
this in your lab

00:02:03.744 --> 00:02:06.954 align:middle line:84%
as well because
it's very important.

00:02:06.954 --> 00:02:09.224 align:middle line:84%
And if you get it wrong,
wait for the review.
