WEBVTT

00:00:01.723 --> 00:00:04.283 align:middle line:84%
Now, this slide I know looks
really confusing and busy,

00:00:04.283 --> 00:00:06.263 align:middle line:90%
but it's super important.

00:00:06.263 --> 00:00:08.593 align:middle line:84%
So we're going to do some
date/time comparisons.

00:00:08.593 --> 00:00:11.873 align:middle line:84%
And remember, we are not
trusting the Windows date/time

00:00:11.873 --> 00:00:12.373 align:middle line:90%
stamps.

00:00:12.373 --> 00:00:15.103 align:middle line:84%
In each of these, we are
looking at the time stamps

00:00:15.103 --> 00:00:17.533 align:middle line:90%
within the plist.

00:00:17.533 --> 00:00:20.113 align:middle line:84%
So here, on the
left-hand side, we

00:00:20.113 --> 00:00:23.653 align:middle line:84%
see AppData Roaming, AppData
Roaming, AppData Roaming.

00:00:23.653 --> 00:00:27.093 align:middle line:84%
This is the native
version of iTunes.

00:00:27.093 --> 00:00:34.043 align:middle line:84%
Manifest.plist has a date
of 9/22/2019 at 09:31:47,

00:00:34.043 --> 00:00:41.243 align:middle line:84%
Status at 09:50:19,
Info at 09:50:49.

00:00:41.243 --> 00:00:45.023 align:middle line:84%
So the truth of this is someone
did a backup on Heather's

00:00:45.023 --> 00:00:47.183 align:middle line:90%
iPhone using iTunes.

00:00:47.183 --> 00:00:50.315 align:middle line:90%
They encrypted it at 09:31:47.

00:00:53.043 --> 00:00:56.283 align:middle line:90%
It completed at 09:50:19.

00:00:56.283 --> 00:01:01.083 align:middle line:84%
And it finally cached
to the PC at 09:50:49.

00:01:01.083 --> 00:01:03.683 align:middle line:84%
That is the literal
path you want to walk.

00:01:03.683 --> 00:01:05.903 align:middle line:84%
Now, I'm going to throw
you throw a loop here.

00:01:05.903 --> 00:01:08.633 align:middle line:84%
If the Microsoft version
of iTunes is used,

00:01:08.633 --> 00:01:11.573 align:middle line:84%
some of the artifacts
that we're looking at

00:01:11.573 --> 00:01:15.023 align:middle line:84%
aren't going to take place
or be pertinent to this.

00:01:15.023 --> 00:01:23.033 align:middle line:84%
Status.plist, 6/15/2018,
Manifest.plist, 6/15/2018.

00:01:23.033 --> 00:01:27.623 align:middle line:84%
So here we can see at
09:03:39, 09:20:09.

00:01:27.623 --> 00:01:32.423 align:middle line:84%
However, look at
Info.plist down here.

00:01:32.423 --> 00:01:34.913 align:middle line:84%
9/9/2019, so you're,
like, wait a second.

00:01:34.913 --> 00:01:36.783 align:middle line:90%
That's a year difference.

00:01:36.783 --> 00:01:38.003 align:middle line:90%
The truth of this--

00:01:38.003 --> 00:01:39.878 align:middle line:84%
and this was through
thorough testing again--

00:01:43.653 --> 00:01:50.133 align:middle line:84%
I created a backup on
9/9/2019 around 21:05.

00:01:50.133 --> 00:01:51.993 align:middle line:84%
Now, notice I'm saying
around because you

00:01:51.993 --> 00:01:53.823 align:middle line:84%
can see the seconds
difference that it

00:01:53.823 --> 00:01:57.303 align:middle line:90%
takes to cache Info.plist.

00:01:57.303 --> 00:02:02.523 align:middle line:84%
Someone had used the real
version of iTunes on 6/15/2018.

00:02:02.523 --> 00:02:06.678 align:middle line:84%
They encrypted it at 09:03:39
and it completed at 9:29

00:02:06.678 --> 00:02:08.373 align:middle line:90%
09:20:09.

00:02:08.373 --> 00:02:10.623 align:middle line:84%
So there's another
backup that exists

00:02:10.623 --> 00:02:14.073 align:middle line:84%
for this device on
someone's computer.

00:02:14.073 --> 00:02:16.053 align:middle line:90%
It was not on mine.

00:02:16.053 --> 00:02:19.185 align:middle line:90%
So this was a phone of a friend.

00:02:19.185 --> 00:02:20.643 align:middle line:84%
Her sister had
died, and she wanted

00:02:20.643 --> 00:02:22.143 align:middle line:84%
to see if I could get
the photos for her.

00:02:22.143 --> 00:02:23.973 align:middle line:84%
So I told her what I would
do is create a backup

00:02:23.973 --> 00:02:26.473 align:middle line:84%
and give her access to it, and
she could do what she wanted.

00:02:26.473 --> 00:02:30.663 align:middle line:84%
I created that backup on
9/9/2019, which is Info.plist.

00:02:30.663 --> 00:02:32.403 align:middle line:90%
It was not at this exact time.

00:02:32.403 --> 00:02:33.643 align:middle line:90%
It was right before that.

00:02:33.643 --> 00:02:35.793 align:middle line:84%
So just be careful
how you word it.

00:02:35.793 --> 00:02:38.853 align:middle line:84%
But clearly, her sister
had done a backup before.

00:02:38.853 --> 00:02:44.723 align:middle line:84%
She encrypted it at 09:03, and
it completed at 09:20 on June

00:02:44.723 --> 00:02:47.033 align:middle line:90%
15, 2018.

00:02:47.033 --> 00:02:49.623 align:middle line:84%
So I know this can
be really confusing.

00:02:49.623 --> 00:02:51.603 align:middle line:90%
Look at the file path.

00:02:51.603 --> 00:02:54.003 align:middle line:84%
If it's native
iTunes, and we see it

00:02:54.003 --> 00:02:57.063 align:middle line:84%
in Apple Computer
MobileSync, the Status.plist

00:02:57.063 --> 00:02:58.863 align:middle line:90%
is our best time stamp.

00:02:58.863 --> 00:03:00.783 align:middle line:84%
Manifest is one
encryption was changed,

00:03:00.783 --> 00:03:03.063 align:middle line:84%
and Info is when it
cached to the system.

00:03:03.063 --> 00:03:06.273 align:middle line:84%
If it's the Microsoft
version of iTunes,

00:03:06.273 --> 00:03:09.963 align:middle line:84%
it's going to be in
Apple MobileSync Backup.

00:03:09.963 --> 00:03:11.913 align:middle line:90%
You cannot trust Manifest.plist.

00:03:11.913 --> 00:03:13.713 align:middle line:90%
You can not trust Status.plist.

00:03:13.713 --> 00:03:18.183 align:middle line:84%
You can only say, right
before this time om Info,

00:03:18.183 --> 00:03:19.563 align:middle line:90%
that that backup was created.
