WEBVTT

00:00:00.000 --> 00:00:06.607
The fourth PCI DSS requirement is concerned with the protection

00:00:06.607 --> 00:00:10.202
of cardholder data in transit across open,

00:00:10.202 --> 00:00:11.658
public networks.

00:00:11.658 --> 00:00:15.654
Its aim is to prevent the interception of payment card data by attack.

00:00:15.654 --> 00:00:19.125
It's listening to a transmission or acting as a man in the middle.

00:00:19.125 --> 00:00:21.946
It's a relatively short and simple requirement,

00:00:21.946 --> 00:00:28.272
and this simplicity is reflected in there being just three sub requirements.

00:00:28.272 --> 00:00:29.620
To encrypt cardholder data in transit,

00:00:29.620 --> 00:00:35.297
to protect cardholder data when it is being sent over messaging services,

00:00:35.297 --> 00:00:38.519
and finally, to have those policies and procedures.

00:00:38.520 --> 00:00:42.131
Now, let's look at our sample network.

00:00:42.131 --> 00:00:44.946
Look requirement 4 is going to apply anywhere data is

00:00:44.946 --> 00:00:48.659
transmitted or received over an open public network,

00:00:48.659 --> 00:00:52.105
which in our case here is the VPN connection between

00:00:52.105 --> 00:00:53.888
a retail store and a head office,

00:00:53.889 --> 00:00:57.237
and also how cardholder data is encrypted between the

00:00:57.237 --> 00:00:59.877
customer and the e-commerce web server,

00:00:59.877 --> 00:01:03.534
and depending on where the TLS connection is terminated,

00:01:03.534 --> 00:01:07.809
that could be either at the firewall or at the web server itself,

00:01:07.809 --> 00:01:11.454
because some firewalls terminate the TLS connection and

00:01:11.454 --> 00:01:13.410
then send it onwards to the web server.

00:01:13.410 --> 00:01:17.846
Requirement 4.1 contains the main demand of this requirement,

00:01:17.846 --> 00:01:20.130
that strong cryptography is used.

00:01:20.130 --> 00:01:24.720
The actual requirement needs a closer look because there's quite a lot in it.

00:01:24.720 --> 00:01:29.040
Firstly, it's about transmission over open public networks.

00:01:29.040 --> 00:01:34.299
So first off, let's define what an open public network is.

00:01:34.299 --> 00:01:38.187
Well, the standard calls out the internet and any wireless technology,

00:01:38.188 --> 00:01:41.618
because it's pretty obvious that data could be accepted on any wireless

00:01:41.618 --> 00:01:45.396
network with someone with the right wireless type of receiver.

00:01:45.397 --> 00:01:47.376
So that's the internet and wireless networks.

00:01:47.377 --> 00:01:49.497
I personally use a stronger definition,

00:01:49.497 --> 00:01:52.698
which is basically any network that's got shared traffic on it,

00:01:52.698 --> 00:01:55.959
and if you think, well, does a wireless network have shared traffic on it?

00:01:55.959 --> 00:02:00.198
No, it probably might not, but the air has shared traffic on it,

00:02:00.198 --> 00:02:03.330
and so that's open and public defined.

00:02:03.330 --> 00:02:05.964
Now what about the other part of requirement 4.1?

00:02:05.964 --> 00:02:10.138
Strong cryptography, and when PCI DSS uses the words,

00:02:10.138 --> 00:02:12.534
strong cryptography, it references the glossary,

00:02:12.534 --> 00:02:16.302
which calls for a minimum of 112 bits of effective key strength,

00:02:16.302 --> 00:02:20.668
the standard algorithm, and proper key management.

00:02:20.668 --> 00:02:23.685
Although, as the glossary says, any new implementation,

00:02:23.685 --> 00:02:24.622
for example,

00:02:24.623 --> 00:02:30.081
that site-to-site VPN in our example network that's going to be using IPSec,

00:02:30.082 --> 00:02:31.177
I mean that needs to be using at least

00:02:31.177 --> 00:02:33.224
one-hundred-twenty-eight bits of effective key strength.

00:02:33.224 --> 00:02:34.790
Now if we look back at the requirement,

00:02:34.790 --> 00:02:39.252
the last thing to point out is the standard talked about transmission,

00:02:39.252 --> 00:02:41.776
and I've seen people claim this means it's nothing to do

00:02:41.776 --> 00:02:43.830
with the reception of cardholder data.

00:02:43.830 --> 00:02:45.760
That's a mistake.

00:02:45.761 --> 00:02:48.192
If you run a web server that controls the encryption used in the transmission

00:02:48.192 --> 00:02:51.140
of cardholder data between a client and the web server,

00:02:51.140 --> 00:02:53.698
you're responsible for how that data is encrypted,

00:02:53.698 --> 00:02:57.071
and so it's very clearly up to you to make sure that your

00:02:57.071 --> 00:02:59.618
server only established secure TLS connections,

00:02:59.618 --> 00:03:02.612
and you can see that this made quite clear in the guidelines.

00:03:02.612 --> 00:03:05.970
So practically we're talking TLS here for web

00:03:05.970 --> 00:03:07.671
browser to web server communications.

00:03:07.671 --> 00:03:10.125
So let's look at what's safe to use.

00:03:10.126 --> 00:03:15.080
All versions of SSL and TLS 1.0 should never be used.

00:03:15.080 --> 00:03:19.925
TLS 1.1 wasn't actually widely deployed.

00:03:19.926 --> 00:03:22.166
It's not actually deprecated either, and yeah,

00:03:22.166 --> 00:03:27.262
you can use it if you must, but let's face it now.

00:03:27.262 --> 00:03:30.542
TLS 1.2 and TLS 1.3 are preferred versions.

00:03:30.543 --> 00:03:32.202
There is one exception to this,

00:03:32.202 --> 00:03:38.562
which is the cryptography used in old point-of-sale POI systems that read cards,

00:03:38.562 --> 00:03:41.239
and that's typically because these systems can't be upgraded.

00:03:41.239 --> 00:03:43.593
So if you have old points of interaction,

00:03:43.593 --> 00:03:48.179
POIs, that still use SSL or TLS 1.0,

00:03:48.179 --> 00:03:50.315
there's a separate set of requirements in Appendix 2 of

00:03:50.315 --> 00:03:52.420
PCI DSS that you need to comply with,

00:03:52.420 --> 00:03:56.588
and you should talk to your merchant bank processor or acquiring bank,

00:03:56.588 --> 00:03:56.948
I mean,

00:03:56.948 --> 00:04:00.406
whoever it is that gave you the POIs to work out how they

00:04:00.406 --> 00:04:04.042
want you to comply or how they're going to help you comply

00:04:04.042 --> 00:04:07.540
with Appendix 2 of PCI DSS.

00:04:07.540 --> 00:04:08.760
To test requirement 4.1,

00:04:08.760 --> 00:04:12.602
the QSA is going to look at policies and standards and that the

00:04:12.602 --> 00:04:15.286
actual configuration of any system responsible for the

00:04:15.286 --> 00:04:17.943
transmission or receipt of cardholder data.

00:04:17.944 --> 00:04:22.272
The sub requirement 4.1 .1 particularly focuses on

00:04:22.272 --> 00:04:23.824
encryption of wireless networks,

00:04:23.824 --> 00:04:28.076
which is we now know are always classed as open public networks,

00:04:28.076 --> 00:04:32.618
and again the demand is for strong cryptography; however,

00:04:32.618 --> 00:04:35.766
this isn't just for wireless networks that transmit cardholder data,

00:04:35.766 --> 00:04:40.561
but any wireless network that is connected to the cardholder data environment,

00:04:40.561 --> 00:04:43.997
and that strong cryptography needs to be in use for

00:04:43.997 --> 00:04:46.058
both the transmission of data, and here's the important point,

00:04:46.058 --> 00:04:48.212
any authentication credentials.

00:04:48.212 --> 00:04:53.379
And of course, this means you're certainly not going to be using WEP.

00:04:53.379 --> 00:04:55.311
To assess compliance with this requirement,

00:04:55.312 --> 00:04:58.760
the QSA is going to look both at written standards and how any wireless

00:04:58.760 --> 00:05:04.577
networks in the environment are actually configured.
