WEBVTT

00:00:02.046 --> 00:00:04.986 align:middle line:84%
This is the first lab
that we are introducing

00:00:04.986 --> 00:00:06.336 align:middle line:90%
in this on-demand studio.

00:00:06.336 --> 00:00:08.166 align:middle line:84%
So when we look at
this, any time you

00:00:08.166 --> 00:00:10.716 align:middle line:84%
see the slide that
says lab, you want

00:00:10.716 --> 00:00:12.616 align:middle line:84%
to go to that lab
in your workbook.

00:00:12.616 --> 00:00:13.606 align:middle line:90%
You have a few options.

00:00:13.606 --> 00:00:15.973 align:middle line:84%
Some people prefer
to work from the PDF.

00:00:15.973 --> 00:00:18.306 align:middle line:84%
Some people prefer to work
from the electronic workbook.

00:00:18.306 --> 00:00:20.346 align:middle line:90%
The choice is yours.

00:00:20.346 --> 00:00:23.156 align:middle line:84%
I am going to get
you through the steps

00:00:23.156 --> 00:00:27.056 align:middle line:84%
of loading this extraction and
following the instructions.

00:00:27.056 --> 00:00:28.626 align:middle line:90%
I will then review it.

00:00:28.626 --> 00:00:31.718 align:middle line:84%
So what you will hear
me say is at this point,

00:00:31.718 --> 00:00:33.926 align:middle line:84%
if you don't want to hear
the review, pause your VM--

00:00:33.926 --> 00:00:35.516 align:middle line:90%
or pause on-demand.

00:00:35.516 --> 00:00:37.669 align:middle line:84%
Stop because I don't want
to give you any spoilers.

00:00:37.669 --> 00:00:40.086 align:middle line:84%
So make sure you're listening
and you're paying attention,

00:00:40.086 --> 00:00:41.996 align:middle line:84%
not just zooming
through and then you're

00:00:41.996 --> 00:00:44.426 align:middle line:84%
disappointed when you hear
the answers to the lab.

00:00:44.426 --> 00:00:48.356 align:middle line:84%
In your VM, I'm going to
launch the E-Workbook.

00:00:51.126 --> 00:00:55.626 align:middle line:84%
Under Exercises, I'm
going to click on Lab 1.1.

00:00:55.626 --> 00:00:57.486 align:middle line:84%
And in here, it tells
you the objectives

00:00:57.486 --> 00:00:58.706 align:middle line:90%
and what you're going to do.

00:00:58.706 --> 00:01:01.196 align:middle line:84%
This lab is very easy
to load, and if you look

00:01:01.196 --> 00:01:04.136 align:middle line:84%
at the instructions it tells
you to go to Lab1.1 in G:

00:01:04.136 --> 00:01:06.856 align:middle line:84%
and double-click on
the UFED shortcut.

00:01:06.856 --> 00:01:09.721 align:middle line:90%
The G: drive is right here.

00:01:13.226 --> 00:01:14.696 align:middle line:90%
We have Lab1.1.

00:01:14.696 --> 00:01:16.136 align:middle line:90%
We click on it.

00:01:16.136 --> 00:01:17.711 align:middle line:90%
You just click on this file.

00:01:17.711 --> 00:01:19.836 align:middle line:84%
Physical Analyzer's going
to give you some options,

00:01:19.836 --> 00:01:21.396 align:middle line:84%
and I want to walk
you through this.

00:01:21.396 --> 00:01:23.256 align:middle line:84%
Now, I already have
it loaded, so I'm not

00:01:23.256 --> 00:01:26.376 align:middle line:90%
going to say yes to some things.

00:01:26.376 --> 00:01:29.076 align:middle line:84%
It's asking me do I want to
open it as a separate project

00:01:29.076 --> 00:01:31.466 align:middle line:90%
or add to the extraction?

00:01:31.466 --> 00:01:33.971 align:middle line:84%
If you ever see this, please
do open as a separate project

00:01:33.971 --> 00:01:35.846 align:middle line:84%
because otherwise, you're
going to be merging

00:01:35.846 --> 00:01:38.726 align:middle line:90%
your labs, which is not good.

00:01:38.726 --> 00:01:42.166 align:middle line:84%
Now, at this screen, follow
what your lab recommends.

00:01:42.166 --> 00:01:44.506 align:middle line:84%
Here it's telling you, hey,
you can carve for locations.

00:01:44.506 --> 00:01:45.673 align:middle line:90%
It can do additional things.

00:01:45.673 --> 00:01:47.536 align:middle line:84%
If you click Learn
More, it's saying

00:01:47.536 --> 00:01:50.526 align:middle line:84%
you can track your
progress and everything.

00:01:50.526 --> 00:01:52.629 align:middle line:84%
I recommend you just
go with the defaults

00:01:52.629 --> 00:01:53.796 align:middle line:90%
unless I tell you otherwise.

00:01:53.796 --> 00:01:56.406 align:middle line:84%
Do not do Selective app
decoding because it's going

00:01:56.406 --> 00:01:59.496 align:middle line:90%
to hinder everything you see.

00:01:59.496 --> 00:02:01.386 align:middle line:84%
Cryptocurrency-- only
if we tell you to.

00:02:01.386 --> 00:02:04.146 align:middle line:84%
You can also run this
on-demand at the end.

00:02:04.146 --> 00:02:06.516 align:middle line:84%
Same thing with
Media classification.

00:02:06.516 --> 00:02:09.156 align:middle line:84%
I recommend running
these after the fact

00:02:09.156 --> 00:02:12.036 align:middle line:84%
because it gets you access
to your data faster,

00:02:12.036 --> 00:02:13.086 align:middle line:90%
but it's up to you.

00:02:13.086 --> 00:02:16.356 align:middle line:84%
If there's ever anything that
you cannot run and I need you

00:02:16.356 --> 00:02:17.986 align:middle line:84%
to check the box
during processing,

00:02:17.986 --> 00:02:22.276 align:middle line:84%
it will be crystal clear
in your lab instructions.

00:02:22.276 --> 00:02:25.176 align:middle line:84%
So then you just click Examine
data, and when it's done,

00:02:25.176 --> 00:02:27.276 align:middle line:84%
it's going to
prompt you and say,

00:02:27.276 --> 00:02:29.766 align:middle line:90%
this time zone was recognized.

00:02:29.766 --> 00:02:34.116 align:middle line:84%
Do you want to adjust all
timestamps to that time zone?

00:02:34.116 --> 00:02:37.776 align:middle line:90%
Be very careful with that.

00:02:37.776 --> 00:02:39.336 align:middle line:90%
If you wanted to--

00:02:39.336 --> 00:02:42.686 align:middle line:84%
I always say no,
but I am currently

00:02:42.686 --> 00:02:46.466 align:middle line:84%
working a case where
it's a cold case murder,

00:02:46.466 --> 00:02:49.686 align:middle line:84%
and it took place
in Central time,

00:02:49.686 --> 00:02:52.526 align:middle line:84%
so it makes sense to put all
the things to Central time.

00:02:52.526 --> 00:02:54.296 align:middle line:84%
It depends on your
investigation.

00:02:54.296 --> 00:02:57.306 align:middle line:84%
With these devices,
they traveled worldwide,

00:02:57.306 --> 00:02:58.986 align:middle line:90%
so be very careful with that.

00:02:58.986 --> 00:03:02.216 align:middle line:84%
You can always go into
Tools and Project Settings

00:03:02.216 --> 00:03:04.116 align:middle line:84%
and verify what your
time zone setting is.

00:03:04.116 --> 00:03:07.016 align:middle line:84%
So here we can see
the time zone is UTC,

00:03:07.016 --> 00:03:08.486 align:middle line:90%
and I want to keep it that way.

00:03:08.486 --> 00:03:11.156 align:middle line:90%
And I say OK.

00:03:11.156 --> 00:03:13.826 align:middle line:84%
Another thing I want you to
verify when you're in here

00:03:13.826 --> 00:03:20.139 align:middle line:84%
is, if you go to Tools
and we go into Settings,

00:03:20.139 --> 00:03:21.556 align:middle line:84%
as we start looking
through this--

00:03:21.556 --> 00:03:23.848 align:middle line:84%
and this is very important--
if you're already parsing,

00:03:23.848 --> 00:03:25.916 align:middle line:84%
do you not change
anything for this lab.

00:03:25.916 --> 00:03:28.886 align:middle line:84%
But if you change this
while it's loaded,

00:03:28.886 --> 00:03:33.576 align:middle line:84%
it will take effect for
all your future labs.

00:03:33.576 --> 00:03:36.996 align:middle line:84%
Under Decoding, and where we are
right here, General Settings,

00:03:36.996 --> 00:03:40.166 align:middle line:84%
Decoding-- this is
super important--

00:03:40.166 --> 00:03:44.386 align:middle line:84%
if you do not have Use deep
carving for SQLite checked,

00:03:44.386 --> 00:03:47.036 align:middle line:84%
in labs that start
with Section 2,

00:03:47.036 --> 00:03:49.786 align:middle line:84%
you will not get the same
amount of deleted information

00:03:49.786 --> 00:03:50.546 align:middle line:90%
that I have.

00:03:50.546 --> 00:03:52.546 align:middle line:90%
So I will remind you of this.

00:03:52.546 --> 00:03:56.676 align:middle line:84%
I also like to have Recover
data from archive files checked.

00:03:56.676 --> 00:03:59.526 align:middle line:84%
Enable AppGenie on
all app categories--

00:03:59.526 --> 00:04:01.686 align:middle line:84%
I am not going to check
that yet because I

00:04:01.686 --> 00:04:04.626 align:middle line:84%
want to show you what the error
looks like when you get it.

00:04:04.626 --> 00:04:08.256 align:middle line:84%
So again, I check Use
deep carving and Recover

00:04:08.256 --> 00:04:09.156 align:middle line:90%
data from SQLite.

00:04:09.156 --> 00:04:13.596 align:middle line:84%
If you don't check those,
they're not going to--

00:04:13.596 --> 00:04:16.446 align:middle line:84%
your lab answers won't look
the same as mine essentially.

00:04:16.446 --> 00:04:19.566 align:middle line:84%
Also, this will not take
effect until you reparse.

00:04:19.566 --> 00:04:23.586 align:middle line:84%
So do it now, and then
when you hit your next labs

00:04:23.586 --> 00:04:25.536 align:middle line:84%
going forward when we
use Physical Analyzer,

00:04:25.536 --> 00:04:26.646 align:middle line:90%
it will take place.

00:04:26.646 --> 00:04:29.376 align:middle line:84%
Any time you update, do
not assume these boxes

00:04:29.376 --> 00:04:30.876 align:middle line:90%
will remain checked.

00:04:30.876 --> 00:04:35.406 align:middle line:84%
So you just click OK, and
that's all that you need.

00:04:35.406 --> 00:04:37.466 align:middle line:90%
So at this point, I release you.

00:04:37.466 --> 00:04:39.086 align:middle line:90%
Go do Lab 1.1.

00:04:39.086 --> 00:04:40.748 align:middle line:84%
Become familiar with
Physical Analyzer.

00:04:40.748 --> 00:04:42.206 align:middle line:84%
The key points are
for you to learn

00:04:42.206 --> 00:04:46.526 align:middle line:84%
how to navigate the file
system, keyword search,

00:04:46.526 --> 00:04:48.686 align:middle line:84%
understand bugs in
keyword searching,

00:04:48.686 --> 00:04:52.646 align:middle line:84%
and then how to hop from a
specific artifact of interest

00:04:52.646 --> 00:04:56.316 align:middle line:84%
into the file system
to find the offset.

00:04:56.316 --> 00:04:58.996 align:middle line:84%
We are now going
to review Lab 1.1.

00:04:58.996 --> 00:05:01.566 align:middle line:84%
And a few things I didn't
cover in the overview

00:05:01.566 --> 00:05:03.516 align:middle line:84%
that we're actually
going to see here

00:05:03.516 --> 00:05:07.446 align:middle line:84%
is the Settings on
Physical Analyzer.

00:05:07.446 --> 00:05:09.456 align:middle line:84%
So I will tell you
when to pause your VM.

00:05:09.456 --> 00:05:11.136 align:middle line:84%
But if you're still
working this lab,

00:05:11.136 --> 00:05:14.766 align:middle line:84%
you may have seen this
screenshot come up.

00:05:14.766 --> 00:05:16.666 align:middle line:90%
Be careful when you use it.

00:05:16.666 --> 00:05:19.746 align:middle line:84%
So here it's saying the time
zone detected was UTC-05:00,

00:05:19.746 --> 00:05:21.096 align:middle line:90%
and it is going to--

00:05:21.096 --> 00:05:23.106 align:middle line:84%
if you check this
box-- automatically

00:05:23.106 --> 00:05:27.996 align:middle line:84%
adjust all the timestamps
to that time zone.

00:05:27.996 --> 00:05:30.456 align:middle line:84%
In this class, Lee and
I travel worldwide, so

00:05:30.456 --> 00:05:32.249 align:middle line:90%
be careful if you choose this.

00:05:32.249 --> 00:05:33.666 align:middle line:84%
However, there are
some situations

00:05:33.666 --> 00:05:34.916 align:middle line:90%
where you may want to do this.

00:05:34.916 --> 00:05:37.806 align:middle line:84%
I am currently working a
cold-case homicide that

00:05:37.806 --> 00:05:41.526 align:middle line:84%
took place in Central time, and
we have specific time frames

00:05:41.526 --> 00:05:42.466 align:middle line:90%
of interest.

00:05:42.466 --> 00:05:45.366 align:middle line:84%
So it makes sense to
convert the time stamps

00:05:45.366 --> 00:05:47.706 align:middle line:84%
because we know when the
murder actually happened.

00:05:47.706 --> 00:05:50.556 align:middle line:84%
But for this, I'm
going to say no.

00:05:50.556 --> 00:05:55.378 align:middle line:84%
The next thing I want you to do
is go into Tools and Settings.

00:05:55.378 --> 00:05:57.336 align:middle line:84%
And I want everyone to
do this, no matter where

00:05:57.336 --> 00:06:00.376 align:middle line:84%
you are in the lab because
this is really important.

00:06:00.376 --> 00:06:04.736 align:middle line:84%
As you scroll down, I
want you to make sure

00:06:04.736 --> 00:06:08.426 align:middle line:84%
that these two boxes I just
unchecked are checked--

00:06:08.426 --> 00:06:12.446 align:middle line:84%
Use deep carving for SQLite
and Recover data from archives.

00:06:12.446 --> 00:06:15.416 align:middle line:84%
And again, this is just
in General Settings

00:06:15.416 --> 00:06:16.676 align:middle line:90%
under Decoding.

00:06:16.676 --> 00:06:21.116 align:middle line:84%
If you don't do this, when
we parse labs going forward,

00:06:21.116 --> 00:06:23.846 align:middle line:84%
you will miss information
or your answers

00:06:23.846 --> 00:06:26.216 align:middle line:84%
will not match what's
in that E-Workbook.

00:06:26.216 --> 00:06:28.446 align:middle line:84%
So please make sure
you check these boxes.

00:06:28.446 --> 00:06:31.496 align:middle line:84%
And again, it's Use Deep carving
for SQLite and Recover data

00:06:31.496 --> 00:06:32.696 align:middle line:90%
from archive files.

00:06:32.696 --> 00:06:34.286 align:middle line:84%
Now, it won't help
you in this lab

00:06:34.286 --> 00:06:36.476 align:middle line:84%
because it's already
parsed, but it's also not

00:06:36.476 --> 00:06:37.796 align:middle line:90%
relevant to this lab.

00:06:37.796 --> 00:06:41.516 align:middle line:84%
It will be relevant to
labs starting Lab 1.4,

00:06:41.516 --> 00:06:43.736 align:middle line:84%
so very important
that you do that.

00:06:43.736 --> 00:06:45.626 align:middle line:84%
If you are still
working the lab,

00:06:45.626 --> 00:06:51.086 align:middle line:84%
press Pause in your VM or
your on-demand recording right

00:06:51.086 --> 00:06:54.476 align:middle line:84%
now because I'm going to
spoil the answers for you.

00:06:54.476 --> 00:06:57.906 align:middle line:84%
For those ready to
review, the first question

00:06:57.906 --> 00:06:59.566 align:middle line:90%
is about keyword searching.

00:06:59.566 --> 00:07:03.876 align:middle line:84%
So if you searched for "the
pool" up here in the top right,

00:07:03.876 --> 00:07:06.266 align:middle line:90%
you get no hits.

00:07:06.266 --> 00:07:09.276 align:middle line:84%
If we then go over
to Advanced and we

00:07:09.276 --> 00:07:17.546 align:middle line:84%
search for "the pool" and
press Enter, we get 0 hits.

00:07:17.546 --> 00:07:20.056 align:middle line:84%
You're like, OK, this
Is not going well.

00:07:20.056 --> 00:07:23.046 align:middle line:84%
So I'm going to cut that one and
put it into All of these terms.

00:07:23.046 --> 00:07:25.736 align:middle line:84%
So now I'm searching
for "the" and "pool."

00:07:25.736 --> 00:07:27.296 align:middle line:84%
If you're not
getting hits for any,

00:07:27.296 --> 00:07:31.186 align:middle line:84%
chances are good you're not
going to get hits for all.

00:07:31.186 --> 00:07:33.566 align:middle line:84%
So then you may
say, you know what?

00:07:33.566 --> 00:07:35.366 align:middle line:84%
I'm going to try Search
in file contents.

00:07:35.366 --> 00:07:37.241 align:middle line:84%
And when you press this
and you press Search,

00:07:37.241 --> 00:07:38.366 align:middle line:90%
you will get hits.

00:07:38.366 --> 00:07:41.966 align:middle line:84%
So you can definitely do that
and you'll get keyword hits.

00:07:41.966 --> 00:07:44.036 align:middle line:84%
Something else you can
do while that's running

00:07:44.036 --> 00:07:47.256 align:middle line:84%
is you can go into the file
system and search that way.

00:07:47.256 --> 00:07:49.316 align:middle line:84%
So here we can see
that we have hits

00:07:49.316 --> 00:07:53.126 align:middle line:84%
for this main.db
associated to Skype.

00:07:53.126 --> 00:07:55.976 align:middle line:90%
Now this is what's interesting.

00:07:55.976 --> 00:07:59.596 align:middle line:84%
When Skype for
Business was released,

00:07:59.596 --> 00:08:03.346 align:middle line:84%
the file main.db was
used only for call logs.

00:08:03.346 --> 00:08:07.546 align:middle line:84%
And sflusername.db started
storing all the chats

00:08:07.546 --> 00:08:09.606 align:middle line:90%
and other interactions.

00:08:09.606 --> 00:08:13.003 align:middle line:84%
Physical Analyzer has
always parsed this file,

00:08:13.003 --> 00:08:14.586 align:middle line:84%
this main.db that
we're highlighted on

00:08:14.586 --> 00:08:18.276 align:middle line:90%
right here, until version 7.52.

00:08:18.276 --> 00:08:20.556 align:middle line:84%
So remember, when I told
you as tools update,

00:08:20.556 --> 00:08:22.236 align:middle line:90%
sometimes you find bugs.

00:08:22.236 --> 00:08:25.306 align:middle line:84%
Sometimes you find older
apps just aren't supported.

00:08:25.306 --> 00:08:28.296 align:middle line:84%
I did report this as a
bug because the issue

00:08:28.296 --> 00:08:30.661 align:middle line:84%
is main.db is still
used for call logs.

00:08:30.661 --> 00:08:32.286 align:middle line:84%
So this is a file
you want to make sure

00:08:32.286 --> 00:08:34.826 align:middle line:90%
that it's always parsed.

00:08:34.826 --> 00:08:37.946 align:middle line:84%
If you want to be even more
thorough, what you could do

00:08:37.946 --> 00:08:39.806 align:middle line:84%
is what I mentioned
in the walkthrough--

00:08:39.806 --> 00:08:42.386 align:middle line:84%
Run fuzzy model plugin, and
let's see what this hits.

00:08:42.386 --> 00:08:43.886 align:middle line:84%
Let's see if it
even found anything.

00:08:43.886 --> 00:08:49.578 align:middle line:84%
So under Analyzed Data,
Manual Data Collection--

00:08:49.578 --> 00:08:51.036 align:middle line:84%
and as we look
through here, I want

00:08:51.036 --> 00:08:52.631 align:middle line:90%
to see if it found main.db.

00:08:52.631 --> 00:08:53.256 align:middle line:90%
And guess what?

00:08:53.256 --> 00:08:55.236 align:middle line:90%
It did.

00:08:55.236 --> 00:08:59.976 align:middle line:84%
So if you ran fuzzy model and
you look, we have accounts.

00:08:59.976 --> 00:09:07.106 align:middle line:84%
If we look at Fuzzy
objects, we have main.db.

00:09:07.106 --> 00:09:09.976 align:middle line:90%
Here we have contacts.

00:09:09.976 --> 00:09:11.476 align:middle line:90%
We have main.corrupt.

00:09:11.476 --> 00:09:13.696 align:middle line:84%
Now main.corrupt is
really interesting.

00:09:13.696 --> 00:09:17.006 align:middle line:84%
What that is if you're
using Skype and it crashes,

00:09:17.006 --> 00:09:19.616 align:middle line:84%
it creates a new
database called .corrupt,

00:09:19.616 --> 00:09:22.258 align:middle line:84%
and then it relaunches and
creates a brand new main.db.

00:09:22.258 --> 00:09:23.716 align:middle line:84%
So when you're
looking at this, you

00:09:23.716 --> 00:09:25.341 align:middle line:84%
can see it's just
showing you contacts.

00:09:25.341 --> 00:09:27.886 align:middle line:84%
It's not actually
showing you what we're

00:09:27.886 --> 00:09:29.251 align:middle line:90%
seeing in our search hits.

00:09:31.756 --> 00:09:33.353 align:middle line:84%
And if we look at
our Advanced search,

00:09:33.353 --> 00:09:34.936 align:middle line:84%
I'm going to close
some of these tabs.

00:09:43.106 --> 00:09:46.106 align:middle line:84%
So we search for this,
we can see that it's

00:09:46.106 --> 00:09:48.116 align:middle line:90%
saying it found it in main.db.

00:09:48.116 --> 00:09:52.096 align:middle line:84%
So what I want to do is I
want to click on main.db,

00:09:52.096 --> 00:09:55.576 align:middle line:84%
and in Database View, we should
have some kind of chats where

00:09:55.576 --> 00:09:56.896 align:middle line:90%
the words "the pool"--

00:09:56.896 --> 00:10:00.166 align:middle line:84%
I'm just going to
type it in here--

00:10:00.166 --> 00:10:00.916 align:middle line:90%
was found.

00:10:00.916 --> 00:10:02.876 align:middle line:84%
And it's like, OK
it's not there.

00:10:02.876 --> 00:10:05.823 align:middle line:84%
So you can go back and say,
OK, if it's not in chats,

00:10:05.823 --> 00:10:06.656 align:middle line:90%
what could it be in?

00:10:06.656 --> 00:10:08.476 align:middle line:90%
Could it be in Conversations?

00:10:08.476 --> 00:10:09.046 align:middle line:90%
Maybe.

00:10:09.046 --> 00:10:10.458 align:middle line:90%
Let's try that.

00:10:10.458 --> 00:10:12.166 align:middle line:84%
And that's where this
can be frustrating.

00:10:12.166 --> 00:10:14.596 align:middle line:84%
If you're like, where
is this, where is this?

00:10:14.596 --> 00:10:17.326 align:middle line:84%
Instead of doing what I'm doing
right now, what I recommend you

00:10:17.326 --> 00:10:20.396 align:middle line:90%
do is switch to the Hex View.

00:10:20.396 --> 00:10:23.146 align:middle line:90%
Click on the magnifying glass.

00:10:23.146 --> 00:10:24.076 align:middle line:90%
Search for "the pool."

00:10:28.366 --> 00:10:31.166 align:middle line:84%
So here I'm searching
for "the pool."

00:10:31.166 --> 00:10:35.376 align:middle line:84%
I'm going to click Find, and it
will dig through and tell you

00:10:35.376 --> 00:10:36.916 align:middle line:90%
if it's in there or not.

00:10:36.916 --> 00:10:40.916 align:middle line:84%
So as it's searching, you
can see we have a hit.

00:10:40.916 --> 00:10:43.436 align:middle line:84%
And here is your message,
"I saw you at the pool!

00:10:43.436 --> 00:10:45.279 align:middle line:90%
Haha."

00:10:45.279 --> 00:10:47.196 align:middle line:84%
Another way some people
find it, if you didn't

00:10:47.196 --> 00:10:49.476 align:middle line:90%
find the database first--

00:10:49.476 --> 00:10:55.386 align:middle line:84%
you can go into File Systems,
scroll all the way to the top,

00:10:55.386 --> 00:10:58.296 align:middle line:84%
click on your Memory
Image in your FileDump.

00:10:58.296 --> 00:11:00.669 align:middle line:84%
Click on your magnifying
glass, and you'll

00:11:00.669 --> 00:11:02.836 align:middle line:84%
notice it knows I searched
for that in the database.

00:11:02.836 --> 00:11:04.296 align:middle line:90%
You use that same thing.

00:11:04.296 --> 00:11:06.221 align:middle line:90%
Press Find.

00:11:06.221 --> 00:11:07.846 align:middle line:84%
And then you can see
it finds two hits.

00:11:07.846 --> 00:11:10.173 align:middle line:84%
It's saying, hey, I
know that this one

00:11:10.173 --> 00:11:11.256 align:middle line:90%
is "I saw you at the pool!

00:11:11.256 --> 00:11:13.536 align:middle line:90%
Haha."

00:11:13.536 --> 00:11:16.936 align:middle line:84%
And in here, there's something
about the pool as well.

00:11:16.936 --> 00:11:18.676 align:middle line:84%
So this is where this
is very important.

00:11:18.676 --> 00:11:20.736 align:middle line:84%
It could be wear-leveling
but different ways

00:11:20.736 --> 00:11:22.536 align:middle line:90%
to keyword search.

00:11:22.536 --> 00:11:25.356 align:middle line:84%
Again, if you want to
close all the things,

00:11:25.356 --> 00:11:29.223 align:middle line:84%
right-click and do Close
All But This or Close all.

00:11:29.223 --> 00:11:31.056 align:middle line:84%
If you ever forget where
your extraction is,

00:11:31.056 --> 00:11:33.656 align:middle line:84%
click on your home
and it comes back.

00:11:33.656 --> 00:11:35.666 align:middle line:84%
The next question is
about a calendar entry.

00:11:35.666 --> 00:11:38.636 align:middle line:84%
When did the user have
scheduled to pick up a gurney?

00:11:38.636 --> 00:11:42.466 align:middle line:84%
So I'm going to
click on Calendar,

00:11:42.466 --> 00:11:44.296 align:middle line:84%
and under Default
calendars, you can

00:11:44.296 --> 00:11:46.126 align:middle line:90%
see we have "Pick up gurney."

00:11:46.126 --> 00:11:48.346 align:middle line:84%
Now my question for you
all, how many of you

00:11:48.346 --> 00:11:50.926 align:middle line:90%
got this answer wrong?

00:11:50.926 --> 00:11:52.676 align:middle line:84%
The reason you got it
wrong is because you

00:11:52.676 --> 00:11:56.425 align:middle line:84%
clicked on the source file,
you went to "Pick up gurney"

00:11:56.425 --> 00:11:58.946 align:middle line:84%
and you reported
this hex offset.

00:11:58.946 --> 00:12:00.626 align:middle line:90%
That is not correct.

00:12:00.626 --> 00:12:03.656 align:middle line:84%
That would be correct if I
asked you where in the database.

00:12:03.656 --> 00:12:06.085 align:middle line:84%
But this question is
specifically asking you where

00:12:06.085 --> 00:12:07.925 align:middle line:90%
in the file system.

00:12:07.925 --> 00:12:12.345 align:middle line:84%
So what you have to do is
go into your file system

00:12:12.345 --> 00:12:14.116 align:middle line:90%
and use that trick I showed you.

00:12:14.116 --> 00:12:22.486 align:middle line:84%
Click on FileDump, go
back to your calendar,

00:12:22.486 --> 00:12:27.366 align:middle line:84%
click on "Pick up gurney,"
switch to your FileDump,

00:12:27.366 --> 00:12:28.515 align:middle line:90%
and it takes you to it.

00:12:28.515 --> 00:12:32.386 align:middle line:84%
So now when you see
"Pick up gurney,"

00:12:32.386 --> 00:12:33.976 align:middle line:90%
that is the correct answer--

00:12:33.976 --> 00:12:34.845 align:middle line:90%
hex 4FF2BFD.

00:12:37.845 --> 00:12:40.576 align:middle line:84%
So make sure you're reading
the question thoroughly

00:12:40.576 --> 00:12:43.066 align:middle line:84%
and you're looking at what is
the offset in the entire file

00:12:43.066 --> 00:12:47.646 align:middle line:84%
system versus where it was
stored in the database.

00:12:47.646 --> 00:12:50.526 align:middle line:84%
This next one this is the first
ringer I'm throwing your way.

00:12:50.526 --> 00:12:53.906 align:middle line:84%
We have not talked
about pictures yet.

00:12:53.906 --> 00:12:59.755 align:middle line:84%
I want to know if you
are in a situation--

00:12:59.755 --> 00:13:01.296 align:middle line:84%
so this question
is, the user was

00:13:01.296 --> 00:13:02.546 align:middle line:90%
accused of stealing a handgun.

00:13:02.546 --> 00:13:05.796 align:middle line:84%
Can you find any
photographs to support it?

00:13:05.796 --> 00:13:11.196 align:middle line:84%
Put yourself in the user or
criminal or suspect's situation

00:13:11.196 --> 00:13:13.303 align:middle line:84%
at times and think if
you were doing something,

00:13:13.303 --> 00:13:14.386 align:middle line:90%
what would you do with it?

00:13:14.386 --> 00:13:16.136 align:middle line:84%
We're going to talk
about hidden pictures,

00:13:16.136 --> 00:13:17.866 align:middle line:84%
deleted pictures,
all kinds of things.

00:13:17.866 --> 00:13:19.716 align:middle line:84%
But for this
specific one, we want

00:13:19.716 --> 00:13:22.656 align:middle line:84%
to go into Media
and into Images.

00:13:22.656 --> 00:13:24.966 align:middle line:84%
And I want to show
you some tricks.

00:13:24.966 --> 00:13:26.196 align:middle line:90%
So you could sit here--

00:13:26.196 --> 00:13:28.656 align:middle line:84%
you could look at the
Table View, not preferred

00:13:28.656 --> 00:13:30.246 align:middle line:90%
for this specific question.

00:13:30.246 --> 00:13:33.526 align:middle line:84%
You can go to Folder View,
you could go to Gallery View.

00:13:33.526 --> 00:13:36.425 align:middle line:84%
I also don't recommend Gallery
View for this situation.

00:13:36.425 --> 00:13:40.602 align:middle line:84%
In Folder View, start with
if the user physically uses

00:13:40.602 --> 00:13:43.185 align:middle line:84%
their phone to take a picture,
where is it going to be stored?

00:13:43.185 --> 00:13:46.416 align:middle line:84%
This is going to be stored
possibly on an SD card in DCIM,

00:13:46.416 --> 00:13:47.986 align:middle line:90%
so I'm going to start with that.

00:13:47.986 --> 00:13:50.856 align:middle line:84%
I'm going to click on
this little green button,

00:13:50.856 --> 00:13:53.585 align:middle line:84%
and it's going to pop
out all of the photos.

00:13:53.585 --> 00:13:57.755 align:middle line:84%
Now, if you think 104 are too
many, go back into your Images

00:13:57.755 --> 00:13:59.136 align:middle line:90%
and say, you know what?

00:13:59.136 --> 00:14:01.845 align:middle line:84%
I don't want thumbnails
to start with.

00:14:01.845 --> 00:14:03.095 align:middle line:90%
I don't want to include those.

00:14:03.095 --> 00:14:07.716 align:middle line:84%
I just want the actual pictures,
and you can start with 38.

00:14:07.716 --> 00:14:09.996 align:middle line:84%
Now what you see here,
these are all the photos

00:14:09.996 --> 00:14:11.835 align:middle line:84%
that the person took
with that camera.

00:14:11.835 --> 00:14:13.416 align:middle line:84%
So as you start
looking through, you

00:14:13.416 --> 00:14:17.106 align:middle line:90%
will stumble across a handgun.

00:14:17.106 --> 00:14:18.845 align:middle line:84%
As you look at
this, you're going

00:14:18.845 --> 00:14:21.755 align:middle line:90%
to see that we have the handgun.

00:14:21.755 --> 00:14:23.416 align:middle line:84%
If you look on the
right-hand side,

00:14:23.416 --> 00:14:25.606 align:middle line:84%
you have the metadata
associated with it.

00:14:25.606 --> 00:14:27.576 align:middle line:84%
We can even see a
location of where

00:14:27.576 --> 00:14:30.444 align:middle line:90%
the person is, the position.

00:14:30.444 --> 00:14:32.486 align:middle line:84%
You could-- this should
be a good example-- where

00:14:32.486 --> 00:14:35.425 align:middle line:90%
we could do hop to location.

00:14:35.425 --> 00:14:37.136 align:middle line:90%
It will take you on a map.

00:14:37.136 --> 00:14:40.466 align:middle line:84%
And you could say, OK, for
this one, if you're online,

00:14:40.466 --> 00:14:43.015 align:middle line:84%
you can do right-click
and Retrieve addresses.

00:14:45.736 --> 00:14:49.156 align:middle line:84%
And it tells you the location
where that person was.

00:14:49.156 --> 00:14:53.040 align:middle line:84%
Now I can tell you-- because
this is a picture of someone I

00:14:53.040 --> 00:14:54.376 align:middle line:90%
know holding a handgun--

00:14:54.376 --> 00:14:56.626 align:middle line:90%
that is not the correct address.

00:14:56.626 --> 00:14:58.406 align:middle line:84%
It is probably a
rendered address.

00:14:58.406 --> 00:15:02.776 align:middle line:84%
But if you zoom in on that
location, it's pretty close.

00:15:02.776 --> 00:15:04.366 align:middle line:90%
It was in Vienna, Virginia.

00:15:04.366 --> 00:15:06.416 align:middle line:90%
The street is just off.

00:15:06.416 --> 00:15:09.286 align:middle line:84%
So again, make sure
you're validating

00:15:09.286 --> 00:15:11.536 align:middle line:84%
these artifacts, especially
location information.

00:15:11.536 --> 00:15:14.119 align:middle line:84%
We're going to talk heavily on
that in Section Two and Section

00:15:14.119 --> 00:15:15.676 align:middle line:90%
3 as we dive in.

00:15:15.676 --> 00:15:20.676 align:middle line:84%
But you will find key
artifacts in here.

00:15:20.676 --> 00:15:24.876 align:middle line:84%
If anyone found it anywhere
else, good job for you.

00:15:24.876 --> 00:15:26.618 align:middle line:90%
So there is one instance of it.

00:15:26.618 --> 00:15:28.326 align:middle line:84%
Now this is where you
have to be careful.

00:15:28.326 --> 00:15:30.786 align:middle line:84%
If you narrow it
down too much, you

00:15:30.786 --> 00:15:32.976 align:middle line:84%
could miss other
instances of it.

00:15:32.976 --> 00:15:36.376 align:middle line:84%
If we look at
WhatsApp images, we're

00:15:36.376 --> 00:15:37.709 align:middle line:90%
going to find that same handgun.

00:15:37.709 --> 00:15:39.084 align:middle line:84%
And now some of
you will be like,

00:15:39.084 --> 00:15:40.556 align:middle line:90%
how the heck did you find that?

00:15:40.556 --> 00:15:44.986 align:middle line:84%
So here we have that same
handgun shared in WhatsApp.

00:15:44.986 --> 00:15:49.316 align:middle line:84%
Go back to your original
image and think about this.

00:15:49.316 --> 00:15:53.186 align:middle line:84%
We have 3/9/2013 as
the modified date.

00:15:53.186 --> 00:15:56.071 align:middle line:84%
Remember the Go to
cheat that I taught you?

00:15:56.071 --> 00:15:56.946 align:middle line:90%
Let's go to timeline.

00:15:56.946 --> 00:15:59.236 align:middle line:90%
Why not?

00:15:59.236 --> 00:16:04.586 align:middle line:84%
What you can do is under
imaged or type, we could say,

00:16:04.586 --> 00:16:05.956 align:middle line:90%
OK we don't care about audio.

00:16:05.956 --> 00:16:07.373 align:middle line:84%
Clearly, you're
not going to share

00:16:07.373 --> 00:16:09.916 align:middle line:84%
a picture of a handgun in
audio, probably not calls.

00:16:09.916 --> 00:16:11.756 align:middle line:84%
And just narrow down
some things here.

00:16:11.756 --> 00:16:14.566 align:middle line:84%
So I'm going to
keep narrowing down.

00:16:14.566 --> 00:16:16.686 align:middle line:84%
I'm not going to
say fuzzy events.

00:16:16.686 --> 00:16:19.696 align:middle line:90%
Images we want, yes--

00:16:19.696 --> 00:16:22.316 align:middle line:90%
Installed Applications.

00:16:22.316 --> 00:16:25.466 align:middle line:84%
So just narrow down
some things of interest.

00:16:25.466 --> 00:16:27.506 align:middle line:84%
And as you keep
narrowing it down,

00:16:27.506 --> 00:16:30.166 align:middle line:84%
you're going to see
right after there looks

00:16:30.166 --> 00:16:34.506 align:middle line:90%
to be like instant messages.

00:16:34.506 --> 00:16:38.706 align:middle line:84%
As you keep looking down, you
will find the WhatsApp message

00:16:38.706 --> 00:16:40.128 align:middle line:90%
where this was actually shared.

00:16:40.128 --> 00:16:41.586 align:middle line:84%
So as you scroll
through it, that's

00:16:41.586 --> 00:16:43.756 align:middle line:84%
how some people
stumbled upon it.

00:16:43.756 --> 00:16:46.006 align:middle line:84%
And they're like, oh, this
is definitely where it was.

00:16:46.006 --> 00:16:50.046 align:middle line:84%
This is how the user
shared that information.

00:16:50.046 --> 00:16:52.356 align:middle line:84%
Again, if you're like,
OK it's still too much,

00:16:52.356 --> 00:16:55.756 align:middle line:84%
go back in and say I don't
want all these images.

00:16:55.756 --> 00:16:59.436 align:middle line:84%
You can keep narrowing down what
you need until you find what

00:16:59.436 --> 00:17:01.906 align:middle line:90%
you actually are looking for.

00:17:01.906 --> 00:17:03.666 align:middle line:84%
So it's kind of
interesting what you

00:17:03.666 --> 00:17:09.386 align:middle line:84%
can do with these different
types of filters in the tool.

00:17:09.386 --> 00:17:12.346 align:middle line:84%
But some people look through all
the pictures and they find it.

00:17:12.346 --> 00:17:15.976 align:middle line:84%
Some people find the
WhatsApp image first.

00:17:15.976 --> 00:17:17.566 align:middle line:84%
It all depends on
your methodology.

00:17:17.566 --> 00:17:19.426 align:middle line:84%
Remember, it doesn't
matter as long as you

00:17:19.426 --> 00:17:21.196 align:middle line:90%
get to the correct answer.

00:17:21.196 --> 00:17:23.086 align:middle line:90%
Key takeaways from this lab--

00:17:23.086 --> 00:17:24.736 align:middle line:84%
keyword searching
is so important.

00:17:24.736 --> 00:17:26.776 align:middle line:84%
Know the different
ways to keyword search.

00:17:26.776 --> 00:17:29.026 align:middle line:90%
Do not fear the hex search.

00:17:29.026 --> 00:17:30.466 align:middle line:90%
It is so important.

00:17:30.466 --> 00:17:32.386 align:middle line:84%
I recommend going out
and reading my blog

00:17:32.386 --> 00:17:35.746 align:middle line:84%
on hex diving that can be
found on the Cellebrite site.

00:17:35.746 --> 00:17:38.266 align:middle line:84%
If you Google "Heather
Mahalik hex diving Cellebrite"

00:17:38.266 --> 00:17:39.436 align:middle line:90%
you'll find it.

00:17:39.436 --> 00:17:42.286 align:middle line:84%
It walks you through
differences on how important it

00:17:42.286 --> 00:17:44.676 align:middle line:90%
can be in your investigation.

00:17:44.676 --> 00:17:47.526 align:middle line:84%
Remember, finding
information in a database

00:17:47.526 --> 00:17:49.476 align:middle line:84%
is different than finding
it in the file dump.
