WEBVTT

00:00:00.458 --> 00:00:04.144
So let's start from requirement 3.1,

00:00:04.144 --> 00:00:06.092
and 3.1 is really easy; it's just like if you don't need it,

00:00:06.092 --> 00:00:06.982
don't keep it, yeah?

00:00:06.982 --> 00:00:10.423
Right, and well, if you do need it, so if you don't need it,

00:00:10.423 --> 00:00:12.915
don't keep it, that's the easy way, right?

00:00:12.915 --> 00:00:17.772
The hard way is if you do need it, then figure out for how long you need it,

00:00:17.772 --> 00:00:21.254
right, and you may have different categories for you know,

00:00:21.254 --> 00:00:24.481
this case merits this retention period and that case

00:00:24.481 --> 00:00:28.759
merits some other retention period, and so that could get complex very quickly,

00:00:28.759 --> 00:00:29.145
right?

00:00:29.145 --> 00:00:31.830
And then when you get to the end of that retention period,

00:00:31.830 --> 00:00:36.460
have some meaningful way of disposing of those records.

00:00:36.460 --> 00:00:36.599
Right.

00:00:36.599 --> 00:00:39.041
So as an assessor you're looking for retention policy?

00:00:39.041 --> 00:00:39.755
I am.

00:00:39.755 --> 00:00:43.040
Right, and then you're looking for how that retention policy is implemented?

00:00:43.040 --> 00:00:43.461
Right.

00:00:43.461 --> 00:00:46.404
And is that okay if it's oh,

00:00:46.404 --> 00:00:49.812
Fred goes into database every few weeks and does it manually?

00:00:49.812 --> 00:00:54.589
So the manual process can be done.

00:00:54.589 --> 00:00:59.838
I'd say you want some assurance that it's working the way you expect so

00:00:59.838 --> 00:01:04.537
that somebody maybe is auditing whatever Fred is doing,

00:01:04.537 --> 00:01:08.581
to say, okay, every couple weeks,

00:01:08.581 --> 00:01:13.512
which should be somewhat defined as opposed to whenever Fred remembers,

00:01:13.512 --> 00:01:14.161
right?

00:01:14.161 --> 00:01:14.933
It's going,

00:01:14.933 --> 00:01:18.903
looking at data and saying which of these records have hit their

00:01:18.903 --> 00:01:22.699
retention period and then is he catching them all,

00:01:22.699 --> 00:01:23.120
right?

00:01:23.120 --> 00:01:28.455
And then is that sort of satisfactory for all of the different storage types?

00:01:28.455 --> 00:01:32.792
Now, I'd say this is relatively easy in a database,

00:01:32.792 --> 00:01:38.651
right, where you can go make queries and drop rows or what have you.

00:01:38.651 --> 00:01:42.095
I'd say if you've got maybe recordings of cardholder data,

00:01:42.095 --> 00:01:45.222
from a contact center or something like that,

00:01:45.222 --> 00:01:47.775
like the spoken numbers that are recorded,

00:01:47.775 --> 00:01:50.414
which is for a variety of reasons,

00:01:50.414 --> 00:01:55.942
kind of a snake pit of compliance difficulties.

00:01:55.942 --> 00:01:56.357
You know,

00:01:56.357 --> 00:01:59.048
then maybe that's more troublesome because those call

00:01:59.048 --> 00:02:02.770
recordings won't necessarily identify themselves as this one

00:02:02.770 --> 00:02:05.048
has card data and this one doesn't.

00:02:05.048 --> 00:02:07.627
So that can get messy very quickly.

00:02:07.627 --> 00:02:08.697
Very quickly.

00:02:08.697 --> 00:02:09.261
Very quickly.

00:02:09.261 --> 00:02:12.090
I'm actually going to stay away from call recordings.

00:02:12.090 --> 00:02:12.729
Okay, let's do that.

00:02:12.729 --> 00:02:15.795
We can actually run a whole course on how to do

00:02:15.795 --> 00:02:17.889
contact-sensitive call recordings.

00:02:17.889 --> 00:02:21.681
Right, and the easy way involves a chemical accelerant and a fire,

00:02:21.681 --> 00:02:24.536
and the hard way is much, much harder.

00:02:24.536 --> 00:02:26.454
The easy way is actually using analog tape because it's

00:02:26.454 --> 00:02:27.902
not digital and PCI doesn't apply.

00:02:27.902 --> 00:02:29.429
You could do that.

00:02:29.429 --> 00:02:30.343
But no one has analog tapes anymore.

00:02:30.343 --> 00:02:35.494
Yeah, where does one go to acquire analog such a thing?
