WEBVTT

00:00:01.536 --> 00:00:06.962
Requirement 3.2 is a general prohibition against storing sensitive

00:00:06.962 --> 00:00:10.648
authentication data or SAD after authorization.

00:00:10.648 --> 00:00:13.299
Before we look in depth at the requirements in 3.2,

00:00:13.299 --> 00:00:18.257
let's remind ourselves about sensitive authentication data.

00:00:18.257 --> 00:00:22.193
This is the table from the beginning of the published PCI DSS.

00:00:22.193 --> 00:00:23.229
As you can see,

00:00:23.229 --> 00:00:27.558
there are three elements that are defined as sensitive authentication data.

00:00:27.558 --> 00:00:30.244
The full track data from a card,

00:00:30.244 --> 00:00:33.173
the security code used in card-not-present transactions,

00:00:33.173 --> 00:00:38.211
which helpfully all the PCI SSE brands have a different name for.

00:00:38.211 --> 00:00:40.110
Okay, that's not helpful, is it?

00:00:40.110 --> 00:00:43.486
And finally, the PIN or the PIN block.

00:00:43.486 --> 00:00:47.937
So requirement 3.2 says do not store sensitive authentication

00:00:47.937 --> 00:00:50.974
data after a transaction has been authorized,

00:00:50.974 --> 00:00:54.471
and if you have stored it between receiving the data

00:00:54.471 --> 00:00:56.061
and authorizing the transaction,

00:00:56.061 --> 00:01:01.579
it must be securely deleted immediately after authorization.

00:01:01.579 --> 00:01:03.020
There is one exception to this rule.

00:01:03.020 --> 00:01:07.311
If you are a card issuer or someone who works for a card issuer and you have

00:01:07.311 --> 00:01:10.879
a business need to retain sensitive authentication data,

00:01:10.879 --> 00:01:12.102
you can.

00:01:12.102 --> 00:01:13.819
There's actually separate requirements and testing

00:01:13.819 --> 00:01:16.759
procedures for each of the three types of SAD,

00:01:16.759 --> 00:01:19.619
which are detailed in the next three sub requirements,

00:01:19.619 --> 00:01:21.656
but generally in each of them,

00:01:21.656 --> 00:01:24.603
the QSA is going to look at stores of cardholder data and

00:01:24.603 --> 00:01:27.594
look to see there's any sensitive authentication data

00:01:27.594 --> 00:01:29.769
retained after authorization.

00:01:29.769 --> 00:01:34.480
If the terms authorization or issuer don't mean much to you,

00:01:34.480 --> 00:01:38.588
then I can highly recommend the first module of one of my other

00:01:38.588 --> 00:01:41.848
Pluralsight courses; Payment Card Security,

00:01:41.848 --> 00:01:43.779
Processing, and the PCI Standards,

00:01:43.779 --> 00:01:47.289
because this first module covers the different stages in a

00:01:47.289 --> 00:01:49.477
payment card transaction including authorization,

00:01:49.477 --> 00:01:51.295
clearing, and settlements,

00:01:51.295 --> 00:01:55.091
along with the roll of the different participants in the transaction,

00:01:55.091 --> 00:01:58.087
including issuers and merchant acquiring banks.

00:01:58.087 --> 00:02:02.606
The first sub requirement in 3.2 concerns track data or the

00:02:02.606 --> 00:02:05.401
track equivalent data stored on a chip card.

00:02:05.401 --> 00:02:07.611
If we look at the back of a payment card,

00:02:07.611 --> 00:02:09.970
there's generally a magnetic stripe on it,

00:02:09.970 --> 00:02:13.959
and within that magnetic stripe, if you could see the data encoded in it,

00:02:13.959 --> 00:02:17.465
there are two tracks of data, Track 1 and Track 2.

00:02:17.465 --> 00:02:20.337
There is information within each track, which can be stored,

00:02:20.337 --> 00:02:21.908
but storing the entire track,

00:02:21.908 --> 00:02:28.691
which as a whole is defined as sensitive authentication data cannot be stored.

00:02:28.691 --> 00:02:31.002
Similarly, looking at the front,

00:02:31.002 --> 00:02:34.652
there's the same type of track information encoded within the chip on the card,

00:02:34.652 --> 00:02:38.100
and the requirement is simple; it is to not store

00:02:38.100 --> 00:02:40.210
this track data after authorization.

00:02:40.210 --> 00:02:43.461
You'll also actually hear this often referred to as mag strip data or

00:02:43.461 --> 00:02:46.821
magnetic strip data because it came from the magnetic stripe.

00:02:46.821 --> 00:02:49.018
The QSA is going to look at lot of system components

00:02:49.018 --> 00:02:50.974
to try to find full track data,

00:02:50.974 --> 00:02:55.788
as well as point-of-sale systems and sales within an individual retail premises.

00:02:55.788 --> 00:02:59.091
They'll be looking at any systems where payment card data obtained

00:02:59.091 --> 00:03:02.509
in customer present transactions is consolidated.

00:03:02.509 --> 00:03:06.175
The QSA is going to pay particular attention to logging,

00:03:06.175 --> 00:03:09.240
which is a common place to find accidentally stored

00:03:09.240 --> 00:03:10.566
sensitive authentication data.

00:03:10.566 --> 00:03:13.927
So it has error logs, transaction history logs,

00:03:13.927 --> 00:03:16.909
history files, any trace files used for debugging,

00:03:16.909 --> 00:03:18.429
and all databases.

00:03:18.429 --> 00:03:22.863
The QSA will make sure they look carefully at database

00:03:22.863 --> 00:03:25.521
schemas and at database contents.

00:03:25.521 --> 00:03:29.502
Requirement 3.2 .2 concerns the card verification code

00:03:29.502 --> 00:03:31.840
using customer not present transactions,

00:03:31.840 --> 00:03:36.369
and again the requirement is not to store this value after authorization.

00:03:36.369 --> 00:03:38.603
Annoyingly, and it is annoying,

00:03:38.603 --> 00:03:43.774
the card brands that make up the PCA SSC have a different name for this code.

00:03:43.774 --> 00:03:46.392
So you might have it referred to as the CVV2,

00:03:46.392 --> 00:03:51.872
the CAV2, or the CVC2, but look,

00:03:51.872 --> 00:03:54.540
it's that three-digit number that's typically printed at the end

00:03:54.540 --> 00:03:57.832
of the signature strip on the back of the card.

00:03:57.832 --> 00:04:00.840
Okay, apart from on American Express cards,

00:04:00.840 --> 00:04:03.908
it's a four-digit number printed on the front of the card,

00:04:03.908 --> 00:04:07.934
and for what it's worth, AMEX refers to this as the CID,

00:04:07.934 --> 00:04:09.890
but it doesn't matter what it's called.

00:04:09.890 --> 00:04:13.018
It should not be stored after the transaction has been authorized,

00:04:13.018 --> 00:04:15.413
and to prove that it hasn't,

00:04:15.413 --> 00:04:18.664
the QSA is going to look at all systems that may have

00:04:18.664 --> 00:04:22.193
received these values such as web servers,

00:04:22.193 --> 00:04:25.332
contact center systems, payment gateways,

00:04:25.332 --> 00:04:29.810
anything involved in processing customer-not-present transactions.

00:04:29.810 --> 00:04:33.371
They're going to pay particular attention again to trace files,

00:04:33.371 --> 00:04:34.705
log files, error reports,

00:04:34.705 --> 00:04:37.906
as well as looking for obvious places the card data

00:04:37.906 --> 00:04:39.539
would've been unintentionally stored,

00:04:39.539 --> 00:04:42.850
but also looking for places it might've been written by systems

00:04:42.850 --> 00:04:45.931
or applications and actually nobody knew the system or

00:04:45.931 --> 00:04:47.906
application was writing the data there.

00:04:47.906 --> 00:04:52.547
The final sub requirement in 3.2 is the prohibition against storing

00:04:52.547 --> 00:04:57.276
personal identification numbers or PINs after authorization.

00:04:57.276 --> 00:04:58.377
The requirement is pretty straightforward,

00:04:58.377 --> 00:05:02.143
not to store the PIN or encrypted PIN block after authorization.

00:05:02.143 --> 00:05:02.580
And look.

00:05:02.580 --> 00:05:06.584
This is pretty rare so this is mainly going to supply to banks and

00:05:06.584 --> 00:05:09.901
perhaps some very large retailers who decrypt and re-encrypt PINs

00:05:09.901 --> 00:05:11.695
when we're routing payment transactions,

00:05:11.695 --> 00:05:14.359
and to some service providers.

00:05:14.359 --> 00:05:14.868
And again,

00:05:14.868 --> 00:05:18.485
the QSA is going to look everywhere and anywhere that they

00:05:18.485 --> 00:05:27.903
think they may find a PIN or a PIN block.
