WEBVTT

00:00:01.723 --> 00:00:02.443 align:middle line:90%
SD cards.

00:00:02.443 --> 00:00:05.683 align:middle line:84%
These are the most compact data
storage we have on devices.

00:00:05.683 --> 00:00:08.773 align:middle line:84%
You will find that many
Androids have restrictions

00:00:08.773 --> 00:00:12.073 align:middle line:84%
on how much space of an SD
card it will actually leverage.

00:00:12.073 --> 00:00:15.373 align:middle line:84%
Let's say you have a
1-terabyte SD card.

00:00:15.373 --> 00:00:19.723 align:middle line:84%
The Android may only mount
256 gigabytes and leverage it.

00:00:19.723 --> 00:00:23.293 align:middle line:84%
However, the user could easily
take that SD card out, plug it

00:00:23.293 --> 00:00:27.763 align:middle line:84%
into their Mac or their PC, and
store anything they want on it.

00:00:27.763 --> 00:00:29.600 align:middle line:84%
That's what I mean
by transient devices.

00:00:29.600 --> 00:00:31.183 align:middle line:84%
I could have all of
my text documents.

00:00:31.183 --> 00:00:34.843 align:middle line:84%
I could have photos
that exist on an SD card

00:00:34.843 --> 00:00:37.243 align:middle line:84%
that the phone never
even acknowledges.

00:00:37.243 --> 00:00:38.893 align:middle line:90%
Keep that in mind.

00:00:38.893 --> 00:00:42.753 align:middle line:84%
The data that is
stored here-- again,

00:00:42.753 --> 00:00:44.283 align:middle line:84%
if it's acquired
through the phone,

00:00:44.283 --> 00:00:47.043 align:middle line:84%
it may change last
accessed time stamps.

00:00:47.043 --> 00:00:52.093 align:middle line:84%
So the best method is going to
be to acquire the device as is.

00:00:52.093 --> 00:00:57.033 align:middle line:84%
But if you care about last
accessed time stamps on that SD

00:00:57.033 --> 00:01:00.453 align:middle line:84%
card, remove it, write-protect
it, and acquire it

00:01:00.453 --> 00:01:02.193 align:middle line:90%
outside of the device first.

00:01:02.193 --> 00:01:04.413 align:middle line:84%
If you have time, I recommend
doing it both ways--

00:01:04.413 --> 00:01:06.333 align:middle line:90%
inside the device and outside.

00:01:06.333 --> 00:01:08.373 align:middle line:84%
Preference would be
to outside if you

00:01:08.373 --> 00:01:10.713 align:middle line:84%
need to preserve last
accessed timestamps.

00:01:10.713 --> 00:01:12.343 align:middle line:90%
Very, very important.

00:01:12.343 --> 00:01:15.453 align:middle line:84%
Now, let's say you get a
device, and you're looking--

00:01:15.453 --> 00:01:16.953 align:middle line:84%
maybe you didn't
do the acquisition.

00:01:16.953 --> 00:01:18.753 align:middle line:90%
It just arrived to your lab.

00:01:18.753 --> 00:01:20.733 align:middle line:84%
And you look at it,
and you're like, why

00:01:20.733 --> 00:01:23.523 align:middle line:84%
did the person look at all
of these photos on the state?

00:01:23.523 --> 00:01:24.393 align:middle line:90%
Maybe they didn't.

00:01:24.393 --> 00:01:27.543 align:middle line:84%
Compare that timestamp to
the acquisition timestamp.

00:01:27.543 --> 00:01:29.283 align:middle line:90%
And what I just said occurred.

00:01:29.283 --> 00:01:32.096 align:middle line:84%
The time stamps on an SD card
came through to the device,

00:01:32.096 --> 00:01:33.888 align:middle line:84%
and last accessed time
stamps were changed.
