WEBVTT

00:00:00.986 --> 00:00:03.695
Okay, and then we get to requirement 3.3,

00:00:03.695 --> 00:00:07.923
which is my favorite because it's one that really frustrates me,

00:00:07.923 --> 00:00:12.652
which is this thing about masking cardholder data when it's displayed on screen.

00:00:12.652 --> 00:00:17.880
Now the PCI Council, you know, have a glossary so they define what masking is,

00:00:17.880 --> 00:00:20.204
and we're going to talk about truncation in the next module.

00:00:20.204 --> 00:00:21.493
Right.

00:00:21.493 --> 00:00:23.467
There is an FAQ about masking and truncation,

00:00:23.467 --> 00:00:26.336
and I know a lot of people get them really confused,

00:00:26.336 --> 00:00:29.622
so before we go into like some practical examples,

00:00:29.622 --> 00:00:36.943
I just want to make sure that we can see on screen that there is an FAQ that

00:00:36.943 --> 00:00:39.946
talks about the difference between masking and truncation.

00:00:39.946 --> 00:00:43.499
So masking is displaying, you've got a whole PAN,

00:00:43.499 --> 00:00:46.373
but when you display it, you put stars in it.

00:00:46.373 --> 00:00:50.029
So the person seeing it doesn't see it, but the whole PAN is there.

00:00:50.029 --> 00:00:50.802
It is there.

00:00:50.802 --> 00:00:52.369
So it's sort of like behind the asterisk.

00:00:52.369 --> 00:00:53.567
Right.

00:00:53.567 --> 00:00:55.590
So the entity still has the card data.

00:00:55.590 --> 00:00:56.163
Right.

00:00:56.163 --> 00:00:58.900
And truncation is where you take bits out,

00:00:58.900 --> 00:01:00.313
and you never have the card data anymore.

00:01:00.313 --> 00:01:03.597
You replace it with stars, yeah.

00:01:03.597 --> 00:01:06.272
So masking is just on screen, but the card data is there,

00:01:06.272 --> 00:01:07.683
and the requirement says something like,

00:01:07.683 --> 00:01:08.978
and I'm doing this from memory,

00:01:08.978 --> 00:01:12.197
but you need to mask card data when it's displayed,

00:01:12.197 --> 00:01:15.134
unless the person's got a business requirement to see it.

00:01:15.134 --> 00:01:16.282
Right.

00:01:16.282 --> 00:01:19.059
Okay, and I have this terrible problem,

00:01:19.059 --> 00:01:23.356
actually with the merchant where their QSA had said,

00:01:23.356 --> 00:01:26.253
well the people on the telephone answering the card data,

00:01:26.253 --> 00:01:27.501
it had to be masked.

00:01:27.501 --> 00:01:30.335
So as they were typing it in, it was asterisks,

00:01:30.335 --> 00:01:34.134
and you can imagine what happened was their authorization rate declined,

00:01:34.134 --> 00:01:36.398
but they kept typing the number wrongly because they

00:01:36.398 --> 00:01:37.752
were listening to it on the phone,

00:01:37.752 --> 00:01:40.443
but the QSA said they weren't allowed to see it on screen.

00:01:40.443 --> 00:01:43.303
Is that right, because that struck me as idiocy.

00:01:43.303 --> 00:01:43.618
Well,

00:01:43.618 --> 00:01:46.848
I think that fails to sort of recognize that there's a

00:01:46.848 --> 00:01:50.751
legitimate need to see the PAN in that case,

00:01:50.751 --> 00:01:51.235
right?

00:01:51.235 --> 00:01:54.712
While that contact center agent or while that person that's hearing it on

00:01:54.712 --> 00:02:01.602
the phone or handling it in person is keying it in,

00:02:01.602 --> 00:02:01.891
sure,

00:02:01.891 --> 00:02:05.021
see the card number; there's a reasonable case to be made to say that

00:02:05.021 --> 00:02:07.920
person has a justifiable reason to see the PAN.

00:02:07.920 --> 00:02:10.383
Now once that transaction is over, that phone call is ended,

00:02:10.383 --> 00:02:12.097
you've handed the card back to the customer,

00:02:12.097 --> 00:02:15.370
do you get to then go, you know,

00:02:15.370 --> 00:02:18.905
and you've processed the order from the cashiering standpoint,

00:02:18.905 --> 00:02:22.824
do you get to go back to the order that you took an hour ago and go that PAN?

00:02:22.824 --> 00:02:23.053
No.

00:02:23.053 --> 00:02:23.220
No.

00:02:23.220 --> 00:02:25.670
Then it' masked, because you don't have a business need.

00:02:25.670 --> 00:02:27.109
Right, but at the time,

00:02:27.109 --> 00:02:31.082
saying you don't have a business need seems like a stretch.

00:02:31.082 --> 00:02:33.349
So it's the worst stretch, because the person is actually in their other hand,

00:02:33.349 --> 00:02:35.364
holding the card and can see the number,

00:02:35.364 --> 00:02:38.449
and it's just like, there is no risk; there's no increased risk.

00:02:38.449 --> 00:02:38.806
Yeah,

00:02:38.806 --> 00:02:43.714
there's no incremental risk from displaying it on the screen

00:02:43.714 --> 00:02:46.714
in terms of what that does for the person,

00:02:46.714 --> 00:02:46.901
yeah.

00:02:46.901 --> 00:02:50.133
That just seems like a way to increase errors and frustration.

00:02:50.133 --> 00:02:50.294
Yeah,

00:02:50.294 --> 00:02:52.824
so I think my key message is if you have an accessor that's

00:02:52.824 --> 00:02:54.925
saying something that sounds really idiotic,

00:02:54.925 --> 00:02:56.938
but oh, that person can't see that card number,

00:02:56.938 --> 00:02:58.534
and you think, well, they're the fraud department,

00:02:58.534 --> 00:03:01.232
they need to see the card number; that's their job,

00:03:01.232 --> 00:03:01.633
right?

00:03:01.633 --> 00:03:02.594
If it's your job,

00:03:02.594 --> 00:03:05.737
PCI DSS doesn't say you can't do this; PCI DSS says very

00:03:05.737 --> 00:03:07.494
clearly if you have a business requirement,

00:03:07.494 --> 00:03:10.021
they can see the card numbers, and as an assessor,

00:03:10.021 --> 00:03:10.988
you're looking for the business requirement,

00:03:10.988 --> 00:03:11.653
aren't you?

00:03:11.653 --> 00:03:11.879
Right.

00:03:11.879 --> 00:03:15.260
Now, I've seen this go the other way where the organization says,

00:03:15.260 --> 00:03:18.821
all of our people have a business requirement because they might

00:03:18.821 --> 00:03:22.058
in some remote circumstance need to see the PAN for some obscure

00:03:22.058 --> 00:03:24.822
thing that happens infrequently, right?

00:03:24.822 --> 00:03:30.466
And that's kind of the shoe on the other foot, like that's idiocy, right?

00:03:30.466 --> 00:03:31.625
Okay, the fraud department, fine.

00:03:31.625 --> 00:03:34.837
Okay, cashiers, at the time of, fine.

00:03:34.837 --> 00:03:39.152
Okay, maybe there are some other specific use cases,

00:03:39.152 --> 00:03:41.648
right, but everybody always?

00:03:41.648 --> 00:03:42.384
Nonsense!

00:03:42.384 --> 00:03:44.422
So it sounds to me, common sense is what we're after here.

00:03:44.422 --> 00:03:45.313
Generally, yeah.

00:03:45.313 --> 00:03:50.630
Okay, that's requirements 3.1, 3.2, and 3.3.

00:03:50.630 --> 00:03:53.962
So is there anything generally with those requirements we should think about?

00:03:53.962 --> 00:03:58.131
So any architectural principles in terms of that,

00:03:58.131 --> 00:04:01.988
or anywhere that people have failed their assessments when you look there?

00:04:01.988 --> 00:04:06.423
Well, so I think with 3.3, with the question of who gets to see the whole PAN,

00:04:06.423 --> 00:04:10.684
think about kind of the roles, alright,

00:04:10.684 --> 00:04:13.282
the groupings of who gets to do that and who doesn't,

00:04:13.282 --> 00:04:16.055
and then how you enforce that, right?

00:04:16.055 --> 00:04:19.278
So if it's this kind of mishmash of oh, you know,

00:04:19.278 --> 00:04:22.105
this person does and that person doesn't,

00:04:22.105 --> 00:04:24.157
and this person does and that person does,

00:04:24.157 --> 00:04:28.769
and they're all on the same team, they're all in the same group,

00:04:28.769 --> 00:04:29.394
that's, you know,

00:04:29.394 --> 00:04:32.039
then you have a very difficult time sort of managing enforcement,

00:04:32.039 --> 00:04:32.561
right?

00:04:32.561 --> 00:04:36.565
But if you're saying, okay, our customer service team generally does not,

00:04:36.565 --> 00:04:40.335
but then we have a, you know, customer service plus,

00:04:40.335 --> 00:04:45.086
right, that does these other functions and they have the right to do that,

00:04:45.086 --> 00:04:49.422
right, and then you can clearly assign, you know,

00:04:49.422 --> 00:04:50.903
people into those roles, good!

00:04:50.903 --> 00:04:53.068
So you're looking for role-based, if you people see PANs,

00:04:53.068 --> 00:04:55.209
you're looking for role-based access?

00:04:55.209 --> 00:04:56.035
Yes.

00:04:56.035 --> 00:04:58.973
And, you know, need-to-know basis basically.

00:04:58.973 --> 00:05:00.601
And there's just some clear linkage between that, right?

00:05:00.601 --> 00:05:02.931
How do you determine who gets that role?

00:05:02.931 --> 00:05:04.648
How do you have those roles defined,

00:05:04.648 --> 00:05:08.607
and then what is the enforcement mechanism for that role?

00:05:08.607 --> 00:05:15.607
Okay, when we talk about any requirement,
