WEBVTT

00:00:01.666 --> 00:00:03.496 align:middle line:84%
When we talked about
data moving around

00:00:03.496 --> 00:00:07.126 align:middle line:84%
on the solid state drive
of the actual device,

00:00:07.126 --> 00:00:09.046 align:middle line:90%
wear leveling can occur.

00:00:09.046 --> 00:00:10.936 align:middle line:84%
What you're seeing
here in this slide is,

00:00:10.936 --> 00:00:14.816 align:middle line:84%
we searched for a term--
"is that not awesome?"

00:00:14.816 --> 00:00:18.616 align:middle line:84%
And you could see here that
it provided 478 results.

00:00:18.616 --> 00:00:22.486 align:middle line:84%
So I'm going to zoom in just
in case you cannot see that.

00:00:22.486 --> 00:00:24.316 align:middle line:90%
And we could see 478 right here.

00:00:24.316 --> 00:00:26.826 align:middle line:90%
Let me magnify.

00:00:26.826 --> 00:00:31.116 align:middle line:84%
Where this is so important-- if
you simply exported or created

00:00:31.116 --> 00:00:33.396 align:middle line:84%
a forensic report from
this point, saying,

00:00:33.396 --> 00:00:35.796 align:middle line:84%
I searched for "is
that not awesome?"

00:00:35.796 --> 00:00:40.446 align:middle line:84%
And the user typed that
478 times, that is false.

00:00:40.446 --> 00:00:43.026 align:middle line:84%
When we look at the
source, you see where

00:00:43.026 --> 00:00:45.786 align:middle line:90%
it says message 7, message 1.

00:00:45.786 --> 00:00:49.146 align:middle line:84%
"Is that not awesome?"
was actually typed--

00:00:49.146 --> 00:00:52.806 align:middle line:84%
received one time incoming
message, one time outgoing.

00:00:52.806 --> 00:00:59.226 align:middle line:84%
So two messages on that entire
phone resulting in 478 times.

00:00:59.226 --> 00:01:01.656 align:middle line:84%
The reason we see
all of these results

00:01:01.656 --> 00:01:05.676 align:middle line:84%
is, that file was moved
around that phone,

00:01:05.676 --> 00:01:08.776 align:middle line:84%
because the person also
texted with other people.

00:01:08.776 --> 00:01:10.776 align:middle line:84%
This is the perfect
example of what

00:01:10.776 --> 00:01:12.766 align:middle line:90%
wear leveling can look like.

00:01:12.766 --> 00:01:14.976 align:middle line:84%
And again, this is
in Physical Analyzer.

00:01:14.976 --> 00:01:17.766 align:middle line:84%
I'm going to keep
telling you this.

00:01:17.766 --> 00:01:21.706 align:middle line:84%
Wear leveling is often
cleaned up on these devices.

00:01:21.706 --> 00:01:24.276 align:middle line:84%
So if you're working
an older Android,

00:01:24.276 --> 00:01:25.926 align:middle line:84%
chances are good
you will see it.

00:01:25.926 --> 00:01:27.396 align:middle line:84%
If you're working
an older iPhone,

00:01:27.396 --> 00:01:29.536 align:middle line:84%
chances are extremely good
you're going to see it.

00:01:29.536 --> 00:01:33.126 align:middle line:84%
But if you have an
Android 10, 11, 12 device,

00:01:33.126 --> 00:01:35.196 align:middle line:84%
even a little bit
older than that,

00:01:35.196 --> 00:01:37.836 align:middle line:84%
chances are good that
the Android will clean up

00:01:37.836 --> 00:01:39.906 align:middle line:84%
after itself, and you're
not going to get access

00:01:39.906 --> 00:01:41.016 align:middle line:90%
to this information.
