WEBVTT

00:00:03.529 --> 00:00:06.390
Requirement 3.3 is a bit of a strange one.

00:00:06.390 --> 00:00:10.371
It's concerned with people seeing primary account numbers or PANs,

00:00:10.371 --> 00:00:14.734
that's the 15- or 16-digit number; we all think of the card number,

00:00:14.734 --> 00:00:16.586
the big number on the front of the card,

00:00:16.586 --> 00:00:20.050
and the requirement is that unless there's a legitimate business need,

00:00:20.050 --> 00:00:22.070
when a PAN is displayed or printed,

00:00:22.070 --> 00:00:25.713
it is masked so that the person looking at the screen or

00:00:25.713 --> 00:00:29.374
the printout can only see a maximum of the first six and

00:00:29.374 --> 00:00:31.457
last four digits of the PAN.

00:00:31.457 --> 00:00:33.333
Let's look at what this means.

00:00:33.333 --> 00:00:36.821
Firstly, let's look at a situation where the PAN isn't masked.

00:00:36.821 --> 00:00:41.972
The PAN is stored in the database in full; when it needs to be shown to a user,

00:00:41.972 --> 00:00:43.966
the entire PAN is displayed.

00:00:43.966 --> 00:00:47.175
And actually what's interesting to note here is that this

00:00:47.175 --> 00:00:50.737
computer that's controlling the display of the PAN is now in

00:00:50.737 --> 00:00:55.024
scope with PCI DSS requirements, because it's now processing that PAN,

00:00:55.024 --> 00:00:55.850
which is cardholder data.

00:00:55.850 --> 00:00:59.736
Now let's look at what happens when a PAN is masked.

00:00:59.736 --> 00:01:01.636
The database still stores the full PAN,

00:01:01.636 --> 00:01:04.862
but rather than display the entire card number,

00:01:04.862 --> 00:01:08.447
some of it's obscured by asterisks when it's displayed,

00:01:08.447 --> 00:01:11.187
quite frequently just the four last digits are shown,

00:01:11.187 --> 00:01:13.303
but the standard actually does allow for the display of the

00:01:13.303 --> 00:01:15.434
first six digits and the last four digits,

00:01:15.434 --> 00:01:20.476
and systems displaying masked cardholder data do not process cardholder data

00:01:20.476 --> 00:01:25.016
so they can remain out of scope of PCI DSS's requirements.

00:01:25.016 --> 00:01:27.911
That's as long as the masking is done on the way to the display and

00:01:27.911 --> 00:01:31.163
actually not done in the display where the display's actually got the

00:01:31.163 --> 00:01:34.121
whole PAN hiding behind the masked number.

00:01:34.121 --> 00:01:37.701
Now the really important thing to remember in this requirement is

00:01:37.701 --> 00:01:40.979
that it only applies where personnel do not have a legitimate

00:01:40.979 --> 00:01:44.609
business need to see the card number in full.

00:01:44.609 --> 00:01:44.940
You know,

00:01:44.940 --> 00:01:48.655
in some of those places where this is legitimate can include merchant receipts,

00:01:48.655 --> 00:01:49.877
e-commerce websites,

00:01:49.877 --> 00:01:53.820
and where people are entering card details in contact centers.

00:01:53.820 --> 00:01:57.428
This somewhere I've seen some really stupid interpretations of the PCI

00:01:57.428 --> 00:02:00.191
DSS that actually have really harmed the business.

00:02:00.191 --> 00:02:02.444
I'm going to discuss these with Jacob in our

00:02:02.444 --> 00:02:04.885
conversation at the end of this module.

00:02:04.885 --> 00:02:08.919
I must emphasize that it's the responsibility of the merchant to

00:02:08.919 --> 00:02:11.611
determine where there's a legitimate business need.

00:02:11.611 --> 00:02:14.554
This isn't the role of the QSA; however,

00:02:14.554 --> 00:02:17.499
the QSA is responsible for checking the documentation that

00:02:17.499 --> 00:02:20.518
defines where there's a legitimate business need for a card

00:02:20.518 --> 00:02:22.058
number to be displayed or printed,

00:02:22.058 --> 00:02:25.520
and then checking all the places where card numbers are displayed to

00:02:25.520 --> 00:02:32.905
make sure they are masked when they need to be.
