WEBVTT

00:00:03.561 --> 00:00:07.302
Requirement 3 is all about protecting stored cardholder data.

00:00:07.303 --> 00:00:09.690
It is split into seven sections.

00:00:09.691 --> 00:00:10.012
Firstly,

00:00:10.012 --> 00:00:12.715
a requirements to have retention policies to minimize

00:00:12.715 --> 00:00:14.933
the storage of cardholder data.

00:00:14.933 --> 00:00:15.602
Secondly,

00:00:15.602 --> 00:00:19.429
an absolute prohibition on storing sensitive

00:00:19.429 --> 00:00:21.735
authentication data after authorization,

00:00:21.735 --> 00:00:27.551
unless you are an issuer of cards, or support the issuing of cards.

00:00:27.551 --> 00:00:30.163
Next, a frequently misunderstood requirement,

00:00:30.163 --> 00:00:35.028
but concerns the display of card numbers on screens and on printouts.

00:00:35.028 --> 00:00:36.566
Then we come to encryption.

00:00:36.566 --> 00:00:37.045
Firstly,

00:00:37.045 --> 00:00:41.801
a requirement that all cardholder data stored must be

00:00:41.801 --> 00:00:44.163
encrypted or otherwise protected.

00:00:44.163 --> 00:00:47.799
Next, there are a couple of requirements detailing how to do encryption properly,

00:00:47.800 --> 00:00:51.669
and then finally, are friend policies and procedures at the end.

00:00:51.669 --> 00:00:53.355
If we look at our sample network,

00:00:53.355 --> 00:00:57.673
we need to determine where cardholder data may be stored to understand

00:00:57.673 --> 00:01:00.249
which components this requirement will apply to,

00:01:00.250 --> 00:01:03.923
and there are three places where we could find cardholder data here.

00:01:03.923 --> 00:01:06.551
The database server is the most obvious location,

00:01:06.551 --> 00:01:08.575
and in my experience,

00:01:08.576 --> 00:01:12.714
point of sale systems and local servers and retail stores are also

00:01:12.714 --> 00:01:15.322
good places where you will find cardholder data.

00:01:15.322 --> 00:01:19.175
Sometimes it's stored deliberately, sometimes accidentally.

00:01:19.175 --> 00:01:23.651
I've assumed in this example that neither the web server nor the payment gateway

00:01:23.652 --> 00:01:26.626
stores cardholder data after they've processed it; however,

00:01:26.626 --> 00:01:29.813
if I was carrying out an assessment of this organization,

00:01:29.813 --> 00:01:32.030
I'd have a good look at those systems,

00:01:32.031 --> 00:01:35.622
because you would often accidentally find cardholder data stored there.

00:01:35.623 --> 00:01:38.539
Well, actually your finding it wouldn't be an accident,

00:01:38.539 --> 00:01:41.030
but the data would've been stored there accidentally.

00:01:41.030 --> 00:01:45.352
Firstly, requirement 3.1 ; it's a simple one.

00:01:45.352 --> 00:01:47.545
If you don't need cardholder data, don't keep it.

00:01:47.545 --> 00:01:51.242
So the first thing you need is a retention policy that says what

00:01:51.243 --> 00:01:55.176
cardholder data you will keep and how long you'll keep it for,

00:01:55.176 --> 00:01:58.077
and why it's necessary to keep the data for the length

00:01:58.077 --> 00:01:59.992
of the period you've determined.

00:01:59.992 --> 00:02:02.807
So that means you need a written business justification,

00:02:02.807 --> 00:02:08.810
which might refer to legal, regulatory, or other business reasons.

00:02:08.810 --> 00:02:11.339
And then given you have a retention policy,

00:02:11.339 --> 00:02:15.988
cardholder data that falls outside of this retention policy must be deleted.

00:02:15.989 --> 00:02:21.170
And PCI DSS requires that you have a documented process for secured deletion,

00:02:21.170 --> 00:02:23.315
but the deletion process executes quarterly,

00:02:23.315 --> 00:02:27.124
and it securely deletes all cardholder data that falls

00:02:27.124 --> 00:02:29.426
outside the defined retention period.

00:02:29.426 --> 00:02:33.864
The QSA is going to look at all your documented processes to make sure

00:02:33.864 --> 00:02:36.975
they cover all the requirements here and will interview people to make

00:02:36.975 --> 00:02:41.528
sure that both processes are working and to understand all the locations

00:02:41.528 --> 00:02:43.429
where card holder data is stored.

00:02:43.429 --> 00:02:46.999
The QSA will then physically look at those stores of

00:02:46.999 --> 00:02:49.838
cardholder data to validate there is no cardholder data

00:02:49.838 --> 00:02:53.050
which exceeds the retention period.

00:02:53.051 --> 00:03:01.143
Finally, do I want to watch the processes used to delete the cardholder data.
