WEBVTT

00:00:01.550 --> 00:00:05.213
Requirement 6.6 is also concerned with the security of web applications,

00:00:05.213 --> 00:00:09.229
but this time just public-facing web applications,

00:00:09.229 --> 00:00:10.880
not web applications that are just used internally,

00:00:10.880 --> 00:00:14.936
just ones that are public facing, connected to the internet,

00:00:14.936 --> 00:00:18.046
and that is because of the additional risk associated with the web application

00:00:18.046 --> 00:00:23.553
that's accessible and attackable by anyone on the internet.

00:00:23.553 --> 00:00:27.147
This requirement demands that there's another layer of protection in place,

00:00:27.147 --> 00:00:33.013
and PCI DSS gives two options for this additional layer of protection.

00:00:33.013 --> 00:00:35.873
The first is that all web applications have a separate

00:00:35.873 --> 00:00:39.444
security view by an external organization that specializes

00:00:39.444 --> 00:00:44.246
in secure application review, and this could be an automated review.

00:00:44.246 --> 00:00:47.970
So here the standard is really looking for things like dynamic code analysis,

00:00:47.970 --> 00:00:52.192
automated application vulnerability testing like fuzzing on auto testers,

00:00:52.192 --> 00:00:55.755
and as the standard knows, this is not a simple normal vulnerability scan,

00:00:55.755 --> 00:01:01.291
and it also needs to be carried out by an external specialist organization.

00:01:01.291 --> 00:01:03.695
It doesn't have to be any organization approved by the PCI SSE,

00:01:03.695 --> 00:01:05.924
but it has to be an organization that's a

00:01:05.924 --> 00:01:10.122
specialist at doing secure code reviews.

00:01:10.122 --> 00:01:12.990
The other option if you don't want to do that is to install a web application

00:01:12.990 --> 00:01:17.045
firewall between the internet and your web application.

00:01:17.045 --> 00:01:17.315
Personally,

00:01:17.315 --> 00:01:20.178
even though the standard gives you the choice of using either

00:01:20.178 --> 00:01:22.258
of these two added layers of protection,

00:01:22.258 --> 00:01:26.497
I would always use both for high-value, public-facing web assets.

00:01:26.497 --> 00:01:29.042
If you've chosen to go with the external vulnerability assessment,

00:01:29.042 --> 00:01:32.479
then the QSA is going to check the process documentation,

00:01:32.479 --> 00:01:37.249
check that the assessment is done by an external specialist organization,

00:01:37.249 --> 00:01:41.835
check that all of the vulnerabilities in requirement 6.5 are checked for,

00:01:41.835 --> 00:01:44.557
and that any vulnerabilities found are fixed and the

00:01:44.557 --> 00:01:47.306
application retested after the fix has been applied.

00:01:47.306 --> 00:01:51.203
They're also going to interview people and more importantly look for

00:01:51.203 --> 00:01:56.030
documentary evidence this process is really being followed.

00:01:56.030 --> 00:01:58.852
On the other hand, if you've chosen to display a web application firewall,

00:01:58.852 --> 00:02:01.263
which most people call a WAF,

00:02:01.263 --> 00:02:03.609
the QSA is going to look at the operation and configuration

00:02:03.609 --> 00:02:06.610
of the WAF and also interview people responsible for the

00:02:06.610 --> 00:02:08.365
application firewall's operation.

00:02:08.365 --> 00:02:11.880
The QSA should check that there's no root from the internet to

00:02:11.880 --> 00:02:14.049
the web application that bypasses the WAF,

00:02:14.049 --> 00:02:18.125
and a good QSA will also try the types of activity that should be

00:02:18.125 --> 00:02:20.897
blocked by the WAF to make sure it's working correctly.

00:02:20.897 --> 00:02:24.265
A really good QSA is also going to check that that WAF

00:02:24.265 --> 00:02:27.296
is properly writing to the log files.
