WEBVTT

00:00:01.464 --> 00:00:03.006 align:middle line:84%
There is some
terminology here that I

00:00:03.006 --> 00:00:04.343 align:middle line:90%
want to make sure I clear up.

00:00:04.343 --> 00:00:05.676 align:middle line:90%
The first is garbage collection.

00:00:05.676 --> 00:00:08.436 align:middle line:84%
You can see, here we
have the 585 trash truck

00:00:08.436 --> 00:00:09.966 align:middle line:90%
coming through and cleaning up.

00:00:09.966 --> 00:00:12.786 align:middle line:84%
What garbage collection
does is, if you think back

00:00:12.786 --> 00:00:15.276 align:middle line:84%
to that solid state
slide where I talked

00:00:15.276 --> 00:00:17.946 align:middle line:84%
about that blue
chunk moving around,

00:00:17.946 --> 00:00:21.756 align:middle line:84%
garbage collection does not
wait for all of those pages

00:00:21.756 --> 00:00:24.546 align:middle line:84%
to be marked ready for
deletion before it clears it.

00:00:24.546 --> 00:00:29.346 align:middle line:84%
So garbage collection could go
in, let's say, once an hour,

00:00:29.346 --> 00:00:31.566 align:middle line:84%
once a week, and go through
and say, you know what?

00:00:31.566 --> 00:00:32.483 align:middle line:90%
I'm going to clean up.

00:00:32.483 --> 00:00:34.446 align:middle line:84%
I'm going to overwrite
those pages that

00:00:34.446 --> 00:00:35.886 align:middle line:90%
are no longer in use.

00:00:35.886 --> 00:00:39.156 align:middle line:90%
This protects your user privacy.

00:00:39.156 --> 00:00:41.813 align:middle line:84%
This, unfortunately, does
not help us forensically.

00:00:41.813 --> 00:00:43.896 align:middle line:84%
Now, some of you may say,
yes, that's very helpful

00:00:43.896 --> 00:00:47.106 align:middle line:84%
because it's fewer things that
I have to manually uncover.

00:00:47.106 --> 00:00:49.926 align:middle line:90%
It is cleaning up on the go.

00:00:49.926 --> 00:00:53.466 align:middle line:84%
Garbage collection happens
across the entire device.

00:00:53.466 --> 00:00:55.676 align:middle line:90%
Now, this is very important.

00:00:55.676 --> 00:00:57.476 align:middle line:84%
Android introduced
garbage collection,

00:00:57.476 --> 00:01:01.436 align:middle line:84%
I think, with the Samsung Galaxy
S3-- so many, many moons ago.

00:01:01.436 --> 00:01:04.076 align:middle line:84%
Apple does not use
garbage collection

00:01:04.076 --> 00:01:05.876 align:middle line:90%
across the entire iPhone.

00:01:05.876 --> 00:01:08.256 align:middle line:84%
Now, someone like me--
and I am a Mac user.

00:01:08.256 --> 00:01:08.966 align:middle line:90%
I have an iPhone.

00:01:08.966 --> 00:01:09.866 align:middle line:90%
I have a watch.

00:01:09.866 --> 00:01:11.786 align:middle line:90%
I buy into Apple.

00:01:11.786 --> 00:01:14.176 align:middle line:90%
I love Apple products.

00:01:14.176 --> 00:01:16.381 align:middle line:84%
I think that garbage
collection doesn't

00:01:16.381 --> 00:01:19.006 align:middle line:84%
happen across the entire device
because we've run out of space.

00:01:19.006 --> 00:01:21.106 align:middle line:84%
Now, that's just my
personal opinion.

00:01:21.106 --> 00:01:22.846 align:middle line:84%
As you run out of
space, what do you do?

00:01:22.846 --> 00:01:23.836 align:middle line:90%
You buy bigger.

00:01:23.836 --> 00:01:25.006 align:middle line:90%
You get more space.

00:01:25.006 --> 00:01:26.096 align:middle line:90%
You pay for more.

00:01:26.096 --> 00:01:29.476 align:middle line:84%
So remember, garbage
collection on an Apple device,

00:01:29.476 --> 00:01:32.956 align:middle line:84%
the entire device, is going
to wait for all of those pages

00:01:32.956 --> 00:01:35.236 align:middle line:84%
to be marked for deletion
before it clears it.

00:01:35.236 --> 00:01:38.786 align:middle line:84%
Garbage collection will run
on an Android periodically.

00:01:38.786 --> 00:01:40.466 align:middle line:90%
Now, where this is different--

00:01:40.466 --> 00:01:43.096 align:middle line:84%
some people think, oh, my gosh,
what about my text messages?

00:01:43.096 --> 00:01:44.216 align:middle line:90%
What about my call logs?

00:01:44.216 --> 00:01:45.466 align:middle line:90%
What about my apps?

00:01:45.466 --> 00:01:48.466 align:middle line:84%
Both Apple and Android
will do something

00:01:48.466 --> 00:01:50.836 align:middle line:90%
called database vacuuming.

00:01:50.836 --> 00:01:53.546 align:middle line:84%
Vacuuming happens
on a container.

00:01:53.546 --> 00:01:56.206 align:middle line:84%
So this is completely different
than garbage collection.

00:01:56.206 --> 00:01:58.606 align:middle line:84%
You could have
Facebook that vacuums

00:01:58.606 --> 00:01:59.986 align:middle line:90%
its database every hour.

00:01:59.986 --> 00:02:02.386 align:middle line:84%
You could have Whatsapp that
does it every time the user

00:02:02.386 --> 00:02:03.916 align:middle line:90%
closes the application.

00:02:03.916 --> 00:02:06.286 align:middle line:84%
You could have some
that happens weekly,

00:02:06.286 --> 00:02:08.146 align:middle line:90%
or every time you sync to cloud.

00:02:08.146 --> 00:02:11.116 align:middle line:84%
Every single application
is going to be different.

00:02:11.116 --> 00:02:13.336 align:middle line:84%
Now, how I want you
to think about this--

00:02:13.336 --> 00:02:17.006 align:middle line:84%
garbage collection
is the entire device.

00:02:17.006 --> 00:02:19.906 align:middle line:84%
So think about throwing
out your devices.

00:02:19.906 --> 00:02:21.736 align:middle line:84%
It's going through and
cleaning everything.

00:02:21.736 --> 00:02:25.606 align:middle line:84%
Vacuuming is happening in
small rooms or containers.

00:02:25.606 --> 00:02:26.716 align:middle line:90%
Think of that.

00:02:26.716 --> 00:02:27.766 align:middle line:90%
It's a database.

00:02:27.766 --> 00:02:32.026 align:middle line:84%
You're not going to vacuum an
entire house in five seconds.

00:02:32.026 --> 00:02:34.366 align:middle line:84%
Garbage collection
would do that.

00:02:34.366 --> 00:02:37.606 align:middle line:84%
Vacuuming is specific to
application containers,

00:02:37.606 --> 00:02:39.226 align:middle line:90%
specifically, databases.

00:02:39.226 --> 00:02:41.686 align:middle line:84%
So make sure you do not
confuse that terminology.

00:02:41.686 --> 00:02:44.026 align:middle line:84%
I hear it confused all the
time, where people say,

00:02:44.026 --> 00:02:46.246 align:middle line:84%
garbage collection
happened on Facebook.

00:02:46.246 --> 00:02:50.726 align:middle line:84%
No, vacuuming happened
on the Orca DB,

00:02:50.726 --> 00:02:54.206 align:middle line:84%
which stores Facebook
information, or FB Sync Store.

00:02:54.206 --> 00:02:56.726 align:middle line:90%
So database-- vacuuming.

00:02:56.726 --> 00:02:58.376 align:middle line:84%
And this is also why,
if you go and you

00:02:58.376 --> 00:03:00.926 align:middle line:84%
look for deleted text
messages on iPhone,

00:03:00.926 --> 00:03:02.096 align:middle line:90%
you're like, where are they?

00:03:02.096 --> 00:03:03.896 align:middle line:84%
Depending on how
quickly you respond,

00:03:03.896 --> 00:03:05.546 align:middle line:90%
vacuuming may have taken place.

00:03:05.546 --> 00:03:08.681 align:middle line:84%
And I have a fantastic
example and student scenario

00:03:08.681 --> 00:03:10.556 align:middle line:84%
that I'm going to share
with you in Section 3

00:03:10.556 --> 00:03:12.446 align:middle line:84%
to show you what this
really looks like.
