WEBVTT

00:00:01.669 --> 00:00:04.739 align:middle line:84%
If you obtain a backup
from iCloud or iTunes,

00:00:04.739 --> 00:00:06.799 align:middle line:84%
it should not matter
when it comes to parsing

00:00:06.799 --> 00:00:08.089 align:middle line:90%
the data in the tool.

00:00:08.089 --> 00:00:10.019 align:middle line:90%
Now, there are some exceptions.

00:00:10.019 --> 00:00:12.859 align:middle line:84%
If you reach out to Apple,
and you get warrant data,

00:00:12.859 --> 00:00:15.619 align:middle line:84%
that should be loaded as
warrant data into your tools.

00:00:15.619 --> 00:00:18.019 align:middle line:84%
But if it's just
typical iCloud data,

00:00:18.019 --> 00:00:22.279 align:middle line:84%
I want to show you a good
way to load this information.

00:00:22.279 --> 00:00:26.799 align:middle line:84%
If we go into our VM, I
have Physical Analyzer open.

00:00:26.799 --> 00:00:30.099 align:middle line:84%
I'm going to go to
File, Open Case.

00:00:30.099 --> 00:00:34.869 align:middle line:84%
Now this is where you're going
to have some options under Add.

00:00:34.869 --> 00:00:37.778 align:middle line:84%
Under Add, if it's warrant,
click Warrant Returns,

00:00:37.778 --> 00:00:39.199 align:middle line:90%
and load it accordingly.

00:00:39.199 --> 00:00:42.261 align:middle line:84%
But if not, you can go
to Common Source, Backup,

00:00:42.261 --> 00:00:44.469 align:middle line:84%
and this is where you'll
look, and you'll see iTunes.

00:00:44.469 --> 00:00:47.319 align:middle line:84%
You technically could load
it as an iTunes backup,

00:00:47.319 --> 00:00:49.479 align:middle line:84%
but I have a better way
I want to show you so you

00:00:49.479 --> 00:00:51.639 align:middle line:90%
can control the environment.

00:00:51.639 --> 00:00:54.359 align:middle line:90%
I'm going to say Open Advanced.

00:00:54.359 --> 00:00:59.699 align:middle line:84%
I want to start without
a UFED extraction.

00:00:59.699 --> 00:01:02.501 align:middle line:90%
I'm going to select Device.

00:01:02.501 --> 00:01:03.584 align:middle line:90%
I'm going to choose Apple.

00:01:11.022 --> 00:01:12.314 align:middle line:90%
And I'm going to choose iCloud.

00:01:16.009 --> 00:01:16.919 align:middle line:90%
Select that.

00:01:16.919 --> 00:01:18.919 align:middle line:84%
Now, you're going to have
multiple options here.

00:01:18.919 --> 00:01:20.389 align:middle line:84%
And from my
experience, I'm going

00:01:20.389 --> 00:01:22.929 align:middle line:84%
to share with you what
I think works the best.

00:01:22.929 --> 00:01:26.179 align:middle line:90%
So click Next.

00:01:26.179 --> 00:01:28.311 align:middle line:84%
If it's Apple production,
you could load this.

00:01:28.311 --> 00:01:30.019 align:middle line:84%
But I also find it
works better sometimes

00:01:30.019 --> 00:01:33.249 align:middle line:84%
loading it as Warrant
Data by other tools,

00:01:33.249 --> 00:01:35.199 align:middle line:90%
I don't typically use.

00:01:35.199 --> 00:01:38.739 align:middle line:84%
What I use is Legacy Raw Format
because, when you download

00:01:38.739 --> 00:01:40.659 align:middle line:84%
cloud data, you will
see that you usually

00:01:40.659 --> 00:01:43.479 align:middle line:84%
have a parent container
that has multiple snapshots

00:01:43.479 --> 00:01:44.439 align:middle line:90%
underneath it.

00:01:44.439 --> 00:01:47.191 align:middle line:84%
If you load the parent
container like this,

00:01:47.191 --> 00:01:49.149 align:middle line:84%
it will parse all of
them, so that's definitely

00:01:49.149 --> 00:01:50.019 align:middle line:90%
what I recommend.
