WEBVTT

00:00:01.707 --> 00:00:06.777 align:middle line:84%
IOS wiping-- if you find
this file called obliterated,

00:00:06.777 --> 00:00:11.277 align:middle line:84%
this is a key indicator that
that device has been wiped.

00:00:11.277 --> 00:00:14.587 align:middle line:84%
Now, what you have to be careful
on are refurbished devices.

00:00:14.587 --> 00:00:17.444 align:middle line:84%
So let's say you drop your
phone into a swimming pool.

00:00:17.444 --> 00:00:19.527 align:middle line:84%
You take it back to your
network service provider,

00:00:19.527 --> 00:00:21.537 align:middle line:90%
and they give you a new phone.

00:00:21.537 --> 00:00:23.307 align:middle line:84%
The chances of that
phone being brand new

00:00:23.307 --> 00:00:24.867 align:middle line:90%
are probably slim to none.

00:00:24.867 --> 00:00:27.207 align:middle line:84%
They often give you
a refurbished phone,

00:00:27.207 --> 00:00:29.677 align:middle line:84%
which means it has
probably been wiped.

00:00:29.677 --> 00:00:32.487 align:middle line:84%
So wiping doesn't necessarily
mean that something bad

00:00:32.487 --> 00:00:33.837 align:middle line:90%
happened on the device.

00:00:33.837 --> 00:00:35.937 align:middle line:84%
I wipe a lot of my test
phones to set them up

00:00:35.937 --> 00:00:37.137 align:middle line:90%
as something new.

00:00:37.137 --> 00:00:38.997 align:middle line:84%
I have wiped my
own personal device

00:00:38.997 --> 00:00:44.537 align:middle line:84%
in the past to create space
to upgrade when I had smaller

00:00:44.537 --> 00:00:47.267 align:middle line:90%
storage space on those iPhones.

00:00:47.267 --> 00:00:51.887 align:middle line:84%
What you want to do is try
to timeline from obliterated

00:00:51.887 --> 00:00:54.227 align:middle line:84%
or some of these other files
I'm going to talk about

00:00:54.227 --> 00:00:57.437 align:middle line:84%
to see if it makes sense, if
it was malicious in nature,

00:00:57.437 --> 00:00:59.197 align:middle line:90%
and why.

00:00:59.197 --> 00:01:01.367 align:middle line:84%
Other files that you
see listed here--

00:01:01.367 --> 00:01:05.042 align:middle line:84%
so containermanagerd.log-- do
you notice it's in italics?

00:01:05.042 --> 00:01:06.667 align:middle line:84%
You're going to need
a full file system

00:01:06.667 --> 00:01:08.587 align:middle line:90%
extraction to get this file.

00:01:08.587 --> 00:01:11.587 align:middle line:84%
Purplebuddy-- the
com.apple.purplebuddy.plist,

00:01:11.587 --> 00:01:13.297 align:middle line:84%
you will get this
with every backup.

00:01:13.297 --> 00:01:14.677 align:middle line:90%
Make sure you encrypted them.

00:01:14.677 --> 00:01:16.837 align:middle line:84%
You'll get that with
advanced logical.

00:01:16.837 --> 00:01:18.797 align:middle line:84%
Every extraction
should have that.

00:01:18.797 --> 00:01:21.367 align:middle line:84%
However, if you get
full file system,

00:01:21.367 --> 00:01:24.997 align:middle line:84%
purplebuddy will be inside
of that data.ark.plist.

00:01:24.997 --> 00:01:28.607 align:middle line:84%
And that's exactly like
we saw it on lab 3.3.

00:01:28.607 --> 00:01:31.135 align:middle line:90%
The logd.0.log is interesting.

00:01:31.135 --> 00:01:32.927 align:middle line:84%
And we're going to take
a look at this file

00:01:32.927 --> 00:01:36.107 align:middle line:84%
and show how that the
user wiped their device

00:01:36.107 --> 00:01:37.457 align:middle line:90%
and started using it again.
