WEBVTT

00:00:00.000 --> 00:00:05.150
In this module, we're going to look at the remaining parts of requirement 6,

00:00:05.150 --> 00:00:07.552
and these are all about secure software development.

00:00:07.552 --> 00:00:10.398
So first of all, requirement 6.3,

00:00:10.399 --> 00:00:13.233
which is really about making sure that security is embedded

00:00:13.233 --> 00:00:16.059
in the software development lifecycle.

00:00:16.059 --> 00:00:18.062
The requirement is split into three parts.

00:00:18.062 --> 00:00:20.996
The software should be in accordance with PCI DSS,

00:00:20.996 --> 00:00:23.585
based on industry standards and best practice,

00:00:23.585 --> 00:00:27.923
and making sure that security is embedded in the software development lifecycle,

00:00:27.923 --> 00:00:31.722
and at each of those parts it's actually pretty large ask so

00:00:31.722 --> 00:00:33.419
let's quickly take a look at each one.

00:00:33.419 --> 00:00:37.061
Firstly, the requirement to develop software in accordance with PCI DSS,

00:00:37.062 --> 00:00:41.650
which you might think strange, because other than requirement 6,

00:00:41.651 --> 00:00:45.305
PCI DSS doesn’t have explicit software development standards,

00:00:45.305 --> 00:00:47.598
but if you think about it,

00:00:47.598 --> 00:00:50.352
there are lots of things that PCI DSS requires that

00:00:50.352 --> 00:00:53.180
will be implemented in software.

00:00:53.180 --> 00:00:56.999
Such as how requirement 3 wants stored PANs to be encrypted,

00:00:56.999 --> 00:00:58.300
hashed, or truncated,

00:00:58.301 --> 00:01:00.827
and that cardholder data needs to be encrypted in

00:01:00.827 --> 00:01:05.482
transit across open public networks, and that vulnerabilities have to be patched.

00:01:05.482 --> 00:01:08.509
So that implies any software that's developed would need to

00:01:08.509 --> 00:01:12.745
have a secure way of being patched or updated.

00:01:12.745 --> 00:01:16.722
And also that any developed software could comply with requirement

00:01:16.722 --> 00:01:21.472
7's need for least privilege access and requirement 8's barely

00:01:21.473 --> 00:01:24.377
prescriptive ways in handling user ids, passwords,

00:01:24.377 --> 00:01:25.801
and authorization,

00:01:25.801 --> 00:01:28.088
and that applications are written to support the

00:01:28.088 --> 00:01:29.566
logging specified in requirement 10,

00:01:29.566 --> 00:01:32.719
and so that's what this requirement is really about.

00:01:32.719 --> 00:01:35.490
That any developed software allows you to comply with

00:01:35.490 --> 00:01:39.002
all the requirements of PCI DSS.

00:01:39.002 --> 00:01:40.095
Let me give you an example.

00:01:40.096 --> 00:01:40.327
Look.

00:01:40.327 --> 00:01:43.784
If you build an application to process payment card data that had

00:01:43.784 --> 00:01:46.109
its own user and password management system,

00:01:46.109 --> 00:01:49.258
but you set the maximum length of the password field in

00:01:49.258 --> 00:01:51.332
this application to be six characters,

00:01:51.332 --> 00:01:56.082
the application would never be able to PCI DSS compliant.

00:01:56.083 --> 00:01:57.513
Look, I know it's a bit of a daft example,

00:01:57.513 --> 00:02:00.722
but no one would ever would create the password field of six characters,

00:02:00.722 --> 00:02:02.349
but you get the idea.

00:02:02.349 --> 00:02:06.787
Requirement 6.3 also wants software development to be based on best practice,

00:02:06.787 --> 00:02:11.088
and there are countless standards an organization can follow.

00:02:11.089 --> 00:02:14.466
The PCI Security Standards Council has published a relatively new standard,

00:02:14.466 --> 00:02:16.705
the Software Security Framework,

00:02:16.705 --> 00:02:21.864
which is a guide to writing secure software that processes cardholder data.

00:02:21.865 --> 00:02:23.747
It's not a requirement of PCI DSS that uses this,

00:02:23.747 --> 00:02:25.899
but it's actually a great baseline to use,

00:02:25.899 --> 00:02:29.594
and if you don't use this standard, pick another one to follow.

00:02:29.595 --> 00:02:33.470
The third part of 6.3 is that security has to be embedded in the

00:02:33.470 --> 00:02:36.865
software development lifecycle so this means that security needs to

00:02:36.865 --> 00:02:40.224
be embedded in requirements definition, software design,

00:02:40.224 --> 00:02:44.699
business analysis, the actual development itself,

00:02:44.699 --> 00:02:49.228
and the testing of the code, and finally how software is released.

00:02:49.228 --> 00:02:51.408
In testing requirement 6.3 and its sub requirements,

00:02:51.408 --> 00:02:55.364
the QSA is going to look at all the documentation relating to software

00:02:55.364 --> 00:02:58.710
development processes and the software development lifecycle.

00:02:58.710 --> 00:03:02.008
The QSA will also talk to your developers to make sure

00:03:02.008 --> 00:03:04.226
they know about it and that it's used,

00:03:04.226 --> 00:03:08.477
and although it's not listed as a testing requirement,

00:03:08.477 --> 00:03:11.305
the QSA will undoubtedly look for historic evidence

00:03:11.305 --> 00:03:15.882
that the processes have been in use.

00:03:15.882 --> 00:03:20.233
There are a couple of sub requirements in 6.3 ; the first,

00:03:20.233 --> 00:03:23.872
requirement 6.3 .1 wants to make sure that any credentials used in the

00:03:23.872 --> 00:03:27.096
development environment don't get released into production.

00:03:27.096 --> 00:03:31.526
And by credentials I mean application accounts, user ids, or passwords.

00:03:31.527 --> 00:03:34.890
The reason for this is once the application is released to live,

00:03:34.890 --> 00:03:37.645
an attacker can use this information to discover the

00:03:37.645 --> 00:03:39.561
inside workings of an application,

00:03:39.562 --> 00:03:41.885
which they could then use to compromise the running application,

00:03:41.885 --> 00:03:44.907
and this is particularly true for point-of-sale applications,

00:03:44.907 --> 00:03:48.342
and that's really where this requirement came for.

00:03:48.342 --> 00:03:51.216
The QSA is going to check this is a requirement of that development process,

00:03:51.216 --> 00:03:54.503
they'll also speak with the developers or the people responsible for

00:03:54.503 --> 00:03:58.153
the promotion of systems from development to test to live or production

00:03:58.153 --> 00:04:01.528
to make sure the credentials are removed.

00:04:01.528 --> 00:04:07.944
Requirement 6.32 wants code reviews for all custom development activity.

00:04:07.945 --> 00:04:10.195
The requirement itself is pretty simple.

00:04:10.195 --> 00:04:13.634
The custom code must be reviewed by either automated or

00:04:13.634 --> 00:04:15.343
manual processes before it is released,

00:04:15.343 --> 00:04:17.739
but it's actually quite a complex requirement,

00:04:17.739 --> 00:04:20.409
and I'm not showing the full text on the slide,

00:04:20.409 --> 00:04:21.754
but it's got four parts to it.

00:04:21.754 --> 00:04:24.341
The review's got to be done by an independent,

00:04:24.341 --> 00:04:25.652
knowledgeable person,

00:04:25.653 --> 00:04:28.215
it's got to be based on written standards that the organization has.

00:04:28.216 --> 00:04:31.018
The errors round have got to be fixed,

00:04:31.019 --> 00:04:32.679
and there's got to be management oversight of it.

00:04:32.679 --> 00:04:35.281
So let's take a quick look at these in a bit more detail.

00:04:35.281 --> 00:04:35.937
Firstly then,

00:04:35.937 --> 00:04:40.016
the review needs to be conducted by someone who knows what they're doing,

00:04:40.016 --> 00:04:44.028
and that cannot be the developer who wrote the code.

00:04:44.028 --> 00:04:46.388
The review doesn't have to be undertaken by an external company.

00:04:46.389 --> 00:04:50.951
An experienced developer would be fine, probably not from the same team,

00:04:50.951 --> 00:04:53.701
though, so I've always said not from the same,

00:04:53.702 --> 00:04:55.348
like direct line manager.

00:04:55.349 --> 00:04:57.990
It's also going to be fine to use an automated tool,

00:04:57.990 --> 00:04:58.920
but again,

00:04:58.921 --> 00:05:02.415
the responsibility for running an automated tool and interpreting the

00:05:02.415 --> 00:05:04.752
output shouldn't rest with the original developer.

00:05:04.753 --> 00:05:07.916
So this might be a separate to something that you've actually got

00:05:07.916 --> 00:05:11.576
running on an automated build and a check-in process,

00:05:11.577 --> 00:05:14.915
but you'll actually have a separate manual code review by

00:05:14.915 --> 00:05:19.364
somebody else who is independent of the developer.

00:05:19.365 --> 00:05:22.134
The second thing is that the code review needs to be based on the

00:05:22.134 --> 00:05:24.640
organization's secure coding standards or guidelines.

00:05:24.640 --> 00:05:25.087
Thirdly,

00:05:25.087 --> 00:05:28.674
that any errors picked up by the code review are

00:05:28.674 --> 00:05:32.603
fixed before the code is released, which sort of sounds like common sense to me.

00:05:32.603 --> 00:05:33.457
But finally,

00:05:33.457 --> 00:05:36.340
there's a management oversight of this process while

00:05:36.340 --> 00:05:38.356
where we're checking of the code review,

00:05:38.356 --> 00:05:40.399
sign off that the code was reviewed,

00:05:40.399 --> 00:05:45.710
and that all issues found in the code review were fixed before release.

00:05:45.711 --> 00:05:46.569
To test this requirement,

00:05:46.569 --> 00:05:50.062
the QSA is going to start off by looking at the documented development process

00:05:50.062 --> 00:05:54.243
to check how and what sort of code reviews are required.

00:05:54.243 --> 00:05:56.752
They'll then talk to the developers and code reviewers to see

00:05:56.752 --> 00:05:58.700
the process is being followed and finally,

00:05:58.700 --> 00:06:02.126
they'll check the release or development records to see if

00:06:02.126 --> 00:06:07.126
there's been required management approval.
