WEBVTT

00:00:01.694 --> 00:00:04.454 align:middle line:90%
OK, let's talk FDE versus FBE.

00:00:04.454 --> 00:00:06.404 align:middle line:84%
So on the left, we have
full-disk encryption.

00:00:06.404 --> 00:00:07.862 align:middle line:84%
Make sure you know
it is introduced

00:00:07.862 --> 00:00:10.364 align:middle line:84%
with Android 5, which
is Lollipop, started

00:00:10.364 --> 00:00:12.464 align:middle line:84%
being enforced with
Marshmallow, which

00:00:12.464 --> 00:00:15.944 align:middle line:84%
is version 6 as long as it
met hardware requirements.

00:00:15.944 --> 00:00:19.284 align:middle line:84%
There were backdoor bypasses
that were very easy to use.

00:00:19.284 --> 00:00:23.474 align:middle line:84%
So if you acquired an Android
running 5 or 6 with UFED,

00:00:23.474 --> 00:00:25.064 align:middle line:90%
it would decrypted on the fly.

00:00:25.064 --> 00:00:29.494 align:middle line:84%
So you could get full physical
access to that device.

00:00:29.494 --> 00:00:33.434 align:middle line:84%
File-based encryption--
introduced with Nougat.

00:00:33.434 --> 00:00:36.464 align:middle line:84%
This is where Direct
Boot can help you.

00:00:36.464 --> 00:00:38.474 align:middle line:90%
So what Direct Boot does--

00:00:38.474 --> 00:00:43.454 align:middle line:84%
Direct Boot is made for
impatient people like myself.

00:00:43.454 --> 00:00:45.854 align:middle line:84%
Imagine if you're
turning off your phone

00:00:45.854 --> 00:00:47.714 align:middle line:84%
or if you're entering
your passcode

00:00:47.714 --> 00:00:49.844 align:middle line:84%
and then you have to wait,
and you're, like, pwwt,

00:00:49.844 --> 00:00:51.761 align:middle line:84%
I have to wait for all
these files to decrypt?

00:00:51.761 --> 00:00:53.384 align:middle line:90%
This is ridiculous.

00:00:53.384 --> 00:00:56.144 align:middle line:84%
What Direct Boot enables you to
do is say, OK, you know what?

00:00:56.144 --> 00:00:58.844 align:middle line:84%
After I enter my
passcode, please show me

00:00:58.844 --> 00:01:01.574 align:middle line:90%
notifications from my Outlook.

00:01:01.574 --> 00:01:03.254 align:middle line:90%
Show me Gmail.

00:01:03.254 --> 00:01:05.204 align:middle line:90%
Show me missed calls.

00:01:05.204 --> 00:01:06.464 align:middle line:90%
Show me Facebook.

00:01:06.464 --> 00:01:09.464 align:middle line:84%
So whatever you say,
show me in Direct Boot,

00:01:09.464 --> 00:01:13.274 align:middle line:84%
we can actually access that in
a different way, forensically,

00:01:13.274 --> 00:01:18.474 align:middle line:84%
then we could everything that
waits for the entire device

00:01:18.474 --> 00:01:20.784 align:middle line:90%
to decrypt.

00:01:20.784 --> 00:01:23.724 align:middle line:84%
When we look at the
lock screen, you

00:01:23.724 --> 00:01:26.124 align:middle line:84%
are going to have to enter
the credentials to get access

00:01:26.124 --> 00:01:27.024 align:middle line:90%
to everything.

00:01:27.024 --> 00:01:30.954 align:middle line:84%
What this means is, if
your method of acquisition

00:01:30.954 --> 00:01:33.602 align:middle line:84%
does not require that device
to be fully logged into,

00:01:33.602 --> 00:01:35.394 align:middle line:84%
you're going to see a
lot of encrypted data

00:01:35.394 --> 00:01:39.624 align:middle line:84%
that's not going to make much
sense, which is not ideal.

00:01:39.624 --> 00:01:42.756 align:middle line:84%
If you want full
file system access,

00:01:42.756 --> 00:01:44.214 align:middle line:84%
you're going to
have to brute-force

00:01:44.214 --> 00:01:45.924 align:middle line:90%
that passcode if it's locked.

00:01:45.924 --> 00:01:47.394 align:middle line:90%
That's not good.

00:01:47.394 --> 00:01:50.154 align:middle line:84%
With file-based encryption,
if you have a hot device,

00:01:50.154 --> 00:01:52.224 align:middle line:84%
you want to acquire
it immediately.

00:01:52.224 --> 00:01:53.994 align:middle line:90%
It's so, so important.

00:01:53.994 --> 00:01:57.774 align:middle line:84%
Now, let's look at these
bottom two considerations here.

00:01:57.774 --> 00:02:00.234 align:middle line:84%
And when we looked at
our lab in lab 1.1,

00:02:00.234 --> 00:02:03.624 align:middle line:90%
we already saw user DE.

00:02:03.624 --> 00:02:06.894 align:middle line:84%
User CE would be
Credential Encrypted.

00:02:06.894 --> 00:02:10.074 align:middle line:84%
User DE would be
Device Encrypted.

00:02:10.074 --> 00:02:16.224 align:middle line:84%
So user CE requires the user
to fully unlock their device,

00:02:16.224 --> 00:02:19.104 align:middle line:84%
and all the files are
decrypted, before the user

00:02:19.104 --> 00:02:21.184 align:middle line:90%
can see anything.

00:02:21.184 --> 00:02:23.444 align:middle line:84%
That is the most
secure for a user.

00:02:23.444 --> 00:02:26.674 align:middle line:84%
User DE is when the user
is impatient and tells

00:02:26.674 --> 00:02:28.444 align:middle line:90%
Direct Boot, you know what?

00:02:28.444 --> 00:02:33.424 align:middle line:84%
Outlook, Facebook, calls,
calendar-- whatever you say

00:02:33.424 --> 00:02:34.684 align:middle line:90%
will be in Direct Boot.

00:02:34.684 --> 00:02:37.114 align:middle line:84%
So depending on your
level of extraction,

00:02:37.114 --> 00:02:39.369 align:middle line:84%
user DE may always
be a place that you

00:02:39.369 --> 00:02:40.744 align:middle line:84%
can get additional
artifacts that

00:02:40.744 --> 00:02:42.154 align:middle line:90%
may be otherwise protected.
