WEBVTT

00:00:01.640 --> 00:00:04.590
[Autogenerated] Now we come to what I think is the most

00:00:04.600 --> 00:00:07.830
important assurance activity required by PC IDE CSS,

00:00:08.109 --> 00:00:09.150
which is ___________.

00:00:09.150 --> 00:00:12.860
Testing on this is the subject of requirement 11.3,

00:00:13.840 --> 00:00:18.740
and the first requirement 11.3 is to have developed a methodology for

00:00:18.740 --> 00:00:22.060
___________ testing before you start to do any testing.

00:00:22.940 --> 00:00:26.840
And a reason for this requirement is that in many data breaches,

00:00:26.840 --> 00:00:29.830
when the forensic investigators looked at the ___________

00:00:29.830 --> 00:00:31.250
test that happened before the breach,

00:00:31.640 --> 00:00:34.550
they found they were totally inadequate and really poorly scoped.

00:00:35.040 --> 00:00:38.050
It was almost as if the organization didn't want the

00:00:38.050 --> 00:00:40.600
___________ testers to find any vulnerabilities in the

00:00:40.600 --> 00:00:43.360
organization that they sort of knew existed.

00:00:43.410 --> 00:00:45.060
So it was almost like, Well, don't look over here.

00:00:45.060 --> 00:00:46.050
Just look over there.

00:00:46.640 --> 00:00:49.840
So the idea of the methodology is that when the use A

00:00:49.840 --> 00:00:51.440
comes to do the annual assessment,

00:00:51.630 --> 00:00:56.190
they can look at the methodology and how the ___________ test was scoped out

00:00:56.300 --> 00:00:58.670
and then actually compare this the actual test results.

00:00:59.240 --> 00:01:00.340
It's gonna be really honest.

00:01:00.520 --> 00:01:03.600
There was also some not very good ___________ testing

00:01:03.600 --> 00:01:06.530
companies that basically just did a vulnerability scan

00:01:06.660 --> 00:01:08.060
and called the ___________ test.

00:01:08.440 --> 00:01:11.850
So this requirement was added to make sure that the organization buying the

00:01:11.850 --> 00:01:15.610
test can properly see what they're getting before they buy the test and know

00:01:15.610 --> 00:01:17.950
what they're going to have as a result of it.

00:01:18.740 --> 00:01:20.370
And if you look at the full standard,

00:01:20.370 --> 00:01:22.560
you'll see the requirements of what needs to be in the

00:01:22.560 --> 00:01:25.440
___________ destined methodology quite detailed.

00:01:25.440 --> 00:01:29.370
There are eight items specified on the QC is gonna

00:01:29.370 --> 00:01:31.370
look at the methodology used now.

00:01:31.370 --> 00:01:33.900
This could be part of a set of your own policies and

00:01:33.900 --> 00:01:36.360
procedures for the cardholder data environment.

00:01:36.460 --> 00:01:39.450
Or it could be a ___________ testing methodology produced

00:01:39.460 --> 00:01:41.720
in advance of each pen test separately,

00:01:41.920 --> 00:01:44.920
because often the ___________ testing company will just

00:01:44.920 --> 00:01:46.660
provide you with the methodology and saying,

00:01:46.840 --> 00:01:49.560
This is what I'm going to do now.

00:01:49.680 --> 00:01:53.180
Just as with vulnerability scans There are two types of ___________.

00:01:53.180 --> 00:01:54.040
Test required.

00:01:54.290 --> 00:01:58.170
An internal ___________ test on an external ___________ test.

00:01:58.940 --> 00:02:04.230
On it is these external test that is the subject of requirement 11.3 point one,

00:02:04.450 --> 00:02:06.730
which must at a minimum,

00:02:06.730 --> 00:02:10.110
be performed annually and also after one of those significant

00:02:10.110 --> 00:02:12.690
changes that could affect the security of the externally

00:02:12.690 --> 00:02:14.450
facing part of the organization.

00:02:15.140 --> 00:02:18.560
So the QoS is going to review the annual ___________ test report.

00:02:18.710 --> 00:02:20.840
They're also gonna look at change control again to see

00:02:20.840 --> 00:02:23.120
there any significant changes and if so,

00:02:23.200 --> 00:02:24.980
they want to the ___________ test report.

00:02:24.980 --> 00:02:30.510
Associating with that change a really good QoS A will want to validate

00:02:30.510 --> 00:02:35.030
that the ___________ test for the methodology on an exceptional QoS A

00:02:35.140 --> 00:02:39.200
will also match the scope of the ___________ test to their understanding

00:02:39.290 --> 00:02:41.080
of the scope of the external elements.

00:02:41.080 --> 00:02:48.210
Of the 500 requirement, 11.3 point two is almost identical to 11.3 point one,

00:02:48.210 --> 00:02:50.560
except this time is concerned with the ___________ tests

00:02:50.560 --> 00:02:53.550
performed inside the CD and again,

00:02:53.690 --> 00:02:56.810
the requirement is that the test is carried out annually on After a

00:02:56.810 --> 00:03:00.280
significant change and just as within external pen test,

00:03:00.280 --> 00:03:03.780
the QoS is going to check the methodology and then check the internal pen

00:03:03.780 --> 00:03:08.160
test report now having a ___________ test on its own.

00:03:08.260 --> 00:03:11.170
Whether that's an internal test or an external test is only half the

00:03:11.170 --> 00:03:14.300
story because of a test fires vulnerabilities,

00:03:14.440 --> 00:03:15.540
they need to be addressed,

00:03:15.550 --> 00:03:20.190
which is what required 11.3 point three is all about Ondas far as.

00:03:20.190 --> 00:03:21.500
The standard is concerned.

00:03:21.660 --> 00:03:24.050
This means that two things need to happen.

00:03:24.540 --> 00:03:27.960
Firstly, the vulnerabilities found need to be rectified.

00:03:28.540 --> 00:03:29.400
And secondly,

00:03:29.610 --> 00:03:33.320
the part of the ___________ test that exposed the vulnerability needs to be

00:03:33.320 --> 00:03:36.970
repeated to validate that the vulnerability was properly fixed.

00:03:37.640 --> 00:03:41.690
So the QoS A will look at the initial pen test and then the follow

00:03:41.690 --> 00:03:44.450
up pen test to validate this requirement was met.

00:03:45.040 --> 00:03:48.500
A good QoS is going to also look at the change control system to

00:03:48.500 --> 00:03:50.650
see that the change in release was followed.

00:03:50.830 --> 00:03:53.260
That's required 6.4 at the same time.

00:03:53.940 --> 00:03:56.690
Now we're almost at the end of ___________ testing.

00:03:56.910 --> 00:03:59.780
But there's one more very important requirement that was

00:03:59.780 --> 00:04:03.680
added in version 3.2 of PC IDE CSS as a result of some pretty

00:04:03.680 --> 00:04:05.760
big breaches of cardholder data,

00:04:06.140 --> 00:04:11.270
and it relates to using ___________ testing to validate segmentation controls.

00:04:11.940 --> 00:04:16.810
So requirement 11.3 point four applies if you segmented your

00:04:16.810 --> 00:04:19.640
network into the cardholder data environment,

00:04:19.790 --> 00:04:23.340
where the PC IDE CSS supplies and then other networks,

00:04:23.350 --> 00:04:26.230
other other networks that error your corporate networks that

00:04:26.230 --> 00:04:28.070
you've isolated with technical control,

00:04:28.070 --> 00:04:30.750
so they're not connected to the cardholder data environment,

00:04:31.040 --> 00:04:35.060
and you've stated that they are not in scope of the PC IDE CSS requirements.

00:04:36.340 --> 00:04:40.020
The requirement is that any technical segmentation is ___________

00:04:40.020 --> 00:04:44.070
tested to simulate what an attacker would do if the attack had

00:04:44.070 --> 00:04:45.980
compromised the out of Scope Network,

00:04:46.040 --> 00:04:49.120
who was now trying to escalate their attack from the out of Scope

00:04:49.120 --> 00:04:51.760
Network into the cardholder data environment.

00:04:52.940 --> 00:04:55.220
To validate this requirements being fulfilled,

00:04:55.400 --> 00:04:56.110
the QoS is,

00:04:56.110 --> 00:04:59.820
firstly going to go right back to the network diagram to determine

00:04:59.820 --> 00:05:01.970
what segmentation control should be in place.

00:05:02.340 --> 00:05:04.360
They're also gonna look at the configuration and

00:05:04.370 --> 00:05:06.660
operation of those segmentation controls.

00:05:07.240 --> 00:05:07.750
Next,

00:05:07.870 --> 00:05:11.590
the QoS is going to examine the ___________ testing methodology to see

00:05:11.590 --> 00:05:14.490
how it proposed to test those segmentation controls.

00:05:14.680 --> 00:05:15.510
And then finally,

00:05:15.510 --> 00:05:18.630
the QoS is going to review the parts of the ___________ tests

00:05:18.630 --> 00:05:20.770
that focused on the segmentation controls.

00:05:21.640 --> 00:05:24.690
There's actually a further some requirement to 11.3 point four,

00:05:24.910 --> 00:05:27.100
which applies just to service providers,

00:05:27.280 --> 00:05:30.200
and that is that they must undertake the segmentation

00:05:30.210 --> 00:05:33.850
___________ testing every six months, not just once a year.

00:05:34.340 --> 00:05:34.790
Um,

00:05:34.880 --> 00:05:38.380
on The reason for this is that there have been lots of data compromises

00:05:38.420 --> 00:05:41.700
where the attacker started off in the out scope network on,

00:05:41.700 --> 00:05:45.860
then escalated their way into the in scope network and stole the cardholder data
