WEBVTT

00:00:00.538 --> 00:00:05.028
So anywhere where people use compensating controls here?

00:00:05.028 --> 00:00:05.557
One,

00:00:05.557 --> 00:00:09.075
3.2 specifically the sub requirements about not

00:00:09.075 --> 00:00:11.749
storing the prohibited data elements, right,

00:00:11.749 --> 00:00:14.585
the magnetic stripe or chip-encoded data,

00:00:14.585 --> 00:00:17.380
the card security codes or values or the PINs,

00:00:17.380 --> 00:00:20.290
those are the only requirements where you cannot use compensating

00:00:20.290 --> 00:00:23.402
controls; you must comply with those requirements as is,

00:00:23.402 --> 00:00:23.619
right?

00:00:23.619 --> 00:00:26.677
So there's no compensating control for storing the card security code,

00:00:26.677 --> 00:00:30.023
there is just not, which means, well, no,

00:00:30.023 --> 00:00:34.318
that's caller recordings, and we're not going there.

00:00:34.318 --> 00:00:40.313
I guess I've seen some compensating controls for storage

00:00:40.313 --> 00:00:47.366
and retention where there's maybe a new policy that went

00:00:47.366 --> 00:00:49.686
into effect that limited storage,

00:00:49.686 --> 00:00:55.414
but then there's some historical archive of data and just

00:00:55.414 --> 00:00:59.576
that act of going and cleaning that out was,

00:00:59.576 --> 00:01:01.197
you know, labor intensive,

00:01:01.197 --> 00:01:05.515
and so that there were some compensating controls to sort of limit access

00:01:05.515 --> 00:01:09.462
to that archive until they could sort of get to an appropriate

00:01:09.462 --> 00:01:11.317
maintenance cycle and then go delete all that stuff.

00:01:11.317 --> 00:01:12.384
Okay, but it's not common?

00:01:12.384 --> 00:01:13.430
It's relatively uncommon.

00:01:13.430 --> 00:01:17.000
And the key message there, you can't compensate and control 3.2?

00:01:17.000 --> 00:01:20.302
You can't compensate control storage of PAN and CVV2 or anything like that.

00:01:20.302 --> 00:01:21.427
Right.

00:01:21.427 --> 00:01:22.689
And that's really sensible.

00:01:22.689 --> 00:01:23.689
Indeed.
