WEBVTT

00:00:00.000 --> 00:00:05.984
Requirement 6 is perhaps the most important in PCI DSS.

00:00:05.984 --> 00:00:07.110
In my experience,

00:00:07.110 --> 00:00:10.782
noncompliance with its requirements is the most common

00:00:10.782 --> 00:00:15.277
cause of breaches of cardholder data and also the most

00:00:15.277 --> 00:00:16.400
failures in annual assessments.

00:00:16.401 --> 00:00:20.011
The requirement is concerned with the development and maintenance of

00:00:20.011 --> 00:00:23.126
secure systems and is split into three logical sections,

00:00:23.126 --> 00:00:26.074
which we're going to explore over three modules.

00:00:26.074 --> 00:00:30.019
This module looks at the two requirements focused on

00:00:30.019 --> 00:00:31.997
vulnerability management and patching.

00:00:31.997 --> 00:00:35.416
Next, there's a whole module dedicated to requirement 6.4,

00:00:35.416 --> 00:00:39.344
which is all about change management, and then finally,

00:00:39.344 --> 00:00:41.275
a module concerned with software development,

00:00:41.275 --> 00:00:45.601
which includes the basic practices for managing software development,

00:00:45.601 --> 00:00:47.655
making sure that code is written securely,

00:00:47.655 --> 00:00:49.782
and the protection of web-facing applications,

00:00:49.782 --> 00:00:53.005
and as I'm sure you can guess,

00:00:53.005 --> 00:00:56.236
the last requirement wants to see the policies and procedures in

00:00:56.236 --> 00:00:58.790
place to ensure these practices to develop and maintain secure

00:00:58.790 --> 00:01:01.833
systems and applications are actually followed.

00:01:01.834 --> 00:01:04.928
Because requirement 6 is concerned with patching,

00:01:04.928 --> 00:01:06.524
vulnerability management, and change control,

00:01:06.524 --> 00:01:10.912
it is going to apply to all systems in scope of PCI DSS,

00:01:10.912 --> 00:01:14.149
and of course, if you develop any software internally,

00:01:14.149 --> 00:01:18.084
whether that's externally facing or just for internal use,

00:01:18.085 --> 00:01:20.857
if that software runs within that CDE,

00:01:20.857 --> 00:01:23.989
it's in the scope of the software development requirements.

00:01:23.990 --> 00:01:27.641
So let's start off by looking at requirement 6.1 and 6.2,

00:01:27.641 --> 00:01:30.897
which together address vulnerability management.

00:01:30.897 --> 00:01:35.323
Now requirement 6.1 is superficially very simple.

00:01:35.323 --> 00:01:38.080
It demands that you actively risk access vulnerabilities

00:01:38.080 --> 00:01:41.172
within the cardholder data environment.

00:01:41.172 --> 00:01:44.407
The requirement is split into two parts.

00:01:44.408 --> 00:01:44.596
Firstly,

00:01:44.596 --> 00:01:48.008
that you have a way of keeping track of new vulnerabilities that are announced,

00:01:48.008 --> 00:01:51.812
which could affect systems within the CDE.

00:01:51.812 --> 00:01:53.057
More specifically, actually,

00:01:53.057 --> 00:01:56.521
the requirement is that you make use of external resources.

00:01:56.521 --> 00:02:00.585
So those could be commercial vulnerability subscription services,

00:02:00.585 --> 00:02:02.248
vendors' websites,

00:02:02.249 --> 00:02:06.869
the Midas CVE list or the NIST National Vulnerability Database.

00:02:06.869 --> 00:02:11.375
The key thing is that you've got an inventory of what's in your CDE,

00:02:11.375 --> 00:02:14.641
and you're proactively making sure that you're aware of any

00:02:14.641 --> 00:02:19.163
vulnerabilities announced for software and for system components.

00:02:19.163 --> 00:02:22.890
The second part of 6.1 is that you assign some sort of

00:02:22.890 --> 00:02:24.968
risk ranking to each vulnerability.

00:02:24.968 --> 00:02:27.526
The standard gives examples of high, medium,

00:02:27.526 --> 00:02:32.219
and low, but you could pick any risk ranking methodology you want.

00:02:32.219 --> 00:02:35.393
What's important is that you have a process to identify

00:02:35.393 --> 00:02:37.304
and risk rank new vulnerabilities,

00:02:37.304 --> 00:02:40.153
and although I've talked about this in terms of

00:02:40.153 --> 00:02:42.342
inventories and awareness of vulnerabilities,

00:02:42.342 --> 00:02:46.202
there are plenty of agent-based tools you can use to create such inventories

00:02:46.202 --> 00:02:50.643
and which also talk to commercial vulnerability databases.

00:02:50.643 --> 00:02:53.902
Now in all my time working with PCI DSS,

00:02:53.903 --> 00:02:55.926
I've seen this requirement cause lots of confusion,

00:02:55.926 --> 00:03:00.378
because this isn't a requirement to use a vulnerability scanner that scans your

00:03:00.378 --> 00:03:04.429
CDE looking for assets and testing them for vulnerabilities.

00:03:04.430 --> 00:03:07.391
Vulnerability scanning is actually a separate requirement.

00:03:07.391 --> 00:03:11.128
It's in requirement 11, and we'll look at that later.

00:03:11.128 --> 00:03:15.160
Secondly, this requirement is not just about vulnerabilities.

00:03:15.161 --> 00:03:20.038
What asset the vulnerability affects is also really important.

00:03:20.038 --> 00:03:24.875
A vulnerability on a database server that stores 3 million payment cards is

00:03:24.875 --> 00:03:29.170
much more serious than an update service and within the CDE.

00:03:29.170 --> 00:03:31.368
So when you're working on risk ranking,

00:03:31.368 --> 00:03:34.177
it's really important to consider the asset as well.

00:03:34.178 --> 00:03:39.391
I've seen so many organizations just use the base CVSS scores

00:03:39.391 --> 00:03:42.421
without applying the environmental metrics.

00:03:42.421 --> 00:03:46.400
PCI DSS wants you to understand the risk to your

00:03:46.400 --> 00:03:48.531
environment caused by vulnerabilities,

00:03:48.531 --> 00:03:52.144
and you can't do that without understanding the role of

00:03:52.144 --> 00:03:54.415
the asset affected by the vulnerability.

00:03:54.416 --> 00:03:56.856
The standard is most keen that you identify critical vulnerabilities,

00:03:56.856 --> 00:04:00.154
which are those that pose an eminent threat to the environment,

00:04:00.154 --> 00:04:02.186
which impact critical systems,

00:04:02.186 --> 00:04:06.290
or those that may result in a potential compromise if not addressed.

00:04:06.290 --> 00:04:07.160
In an assessment,

00:04:07.160 --> 00:04:11.797
the QSA will look at the vulnerability management processes and policies.

00:04:11.798 --> 00:04:14.388
They'll talk to the people responsible for monitoring

00:04:14.388 --> 00:04:17.723
newly announced vulnerabilities, and also for conducting that risk scoring.

00:04:17.723 --> 00:04:22.114
Conscientious QSA may look at records of risk scoring over the past 12 months,

00:04:22.113 --> 00:04:25.577
and if you're using a system that relies on host-based agents to

00:04:25.577 --> 00:04:29.005
maintain an inventory of the software on each system,

00:04:29.005 --> 00:04:31.579
which is matched up with the commercial vulnerability database,

00:04:31.579 --> 00:04:38.568
the QSA will probably want to look at the central management console for this.
