WEBVTT

00:00:00.830 --> 00:00:05.747
So requirement 3, all about the storage and encryption of cardholder data,

00:00:05.747 --> 00:00:10.462
and I know, Jacob, we could probably spend a day talking about encryption,

00:00:10.462 --> 00:00:13.471
because it's like both of our favorite topics.

00:00:13.471 --> 00:00:14.855
It is.

00:00:14.855 --> 00:00:15.471
Right, so we're not going to do that.

00:00:15.471 --> 00:00:16.762
No, let's not.

00:00:16.762 --> 00:00:18.880
So I'm going to start off with a really 
 
 [00:41: 49.000 ] 
 simple question.

00:00:18.880 --> 00:00:21.483
For most merchants, not service providers,

00:00:21.483 --> 00:00:23.724
they shouldn't be storing cardholder data anyway.

00:00:23.724 --> 00:00:24.460
Probably not.

00:00:24.460 --> 00:00:29.140
Why on earth are people still wanting to hold onto cardholder data?

00:00:29.140 --> 00:00:33.679
It's about, you know, this requirement is about reducing the attack footprint.

00:00:33.679 --> 00:00:35.471
If you don't have cardholder data, no one can steal it from you.

00:00:35.471 --> 00:00:36.982
Right.

00:00:36.982 --> 00:00:39.429
So do you still have clients that keep cardholder data?

00:00:39.429 --> 00:00:44.422
There are some clients that still keep cardholder data.

00:00:44.422 --> 00:00:49.920
I'd say more and more merchants are sort of wising to this idea and saying,

00:00:49.920 --> 00:00:51.248
I don't want it, right?

00:00:51.248 --> 00:00:53.907
I don't want to deal with the cryptographic sort of nonsense; I

00:00:53.907 --> 00:00:55.681
don't want to deal with the storage nonsense.

00:00:55.681 --> 00:00:58.597
I don't want to deal with the data disposal stuff.

00:00:58.597 --> 00:01:01.613
I can make the payment processor do all of that for me,

00:01:01.613 --> 00:01:05.363
and I can get some tokens or I can just not have it,

00:01:05.363 --> 00:01:07.624
and I want to do that.

00:01:07.624 --> 00:01:12.518
Where I see large merchants continuing to hang on to payment card

00:01:12.518 --> 00:01:16.496
data is when they have sort of legacy functions,

00:01:16.496 --> 00:01:17.086
right?

00:01:17.086 --> 00:01:22.286
And maybe legacy arrangements with their payment processing entity,

00:01:22.286 --> 00:01:27.923
where sort of un-pinning that and going to an agreement where

00:01:27.923 --> 00:01:31.756
the payment processor does some tokenization.

00:01:31.756 --> 00:01:33.221
I guess, I don't know, right?

00:01:33.221 --> 00:01:37.304
I'm not privy to their contracts, but it could be significant.

00:01:37.304 --> 00:01:39.368
So they might be doing authorization and then doing their

00:01:39.368 --> 00:01:41.479
own clearing and capture files themselves,

00:01:41.479 --> 00:01:43.155
those types of arrangements?

00:01:43.155 --> 00:01:44.812
Potentially, right, right,

00:01:44.812 --> 00:01:50.999
or just where the agreement is just the payment processing service and you know,

00:01:50.999 --> 00:01:53.164
oh, the tokenization would be an add-on or something like that,

00:01:53.164 --> 00:01:58.817
and they're reluctant to go down that road.
