WEBVTT

00:00:01.440 --> 00:00:03.080
[Autogenerated] Now I know that was quite a bit to

00:00:03.080 --> 00:00:05.250
think about in terms of ___________, testing.

00:00:05.840 --> 00:00:08.450
And of all the PC IDE CSS requirements,

00:00:08.840 --> 00:00:11.680
this is the one I've experienced the most variability

00:00:11.740 --> 00:00:13.850
in how well organizations do it.

00:00:14.440 --> 00:00:17.290
And it really comes down to whether the organization wants to

00:00:17.290 --> 00:00:20.730
learn about security and find vulnerabilities or if it just

00:00:20.730 --> 00:00:23.070
wants to take the 11.3 check box.

00:00:23.640 --> 00:00:24.250
Sadly,

00:00:24.450 --> 00:00:27.340
the box tickers the ones where the criminals end up

00:00:27.340 --> 00:00:29.850
providing a free of charge ___________ test.

00:00:30.540 --> 00:00:35.400
So for organizations that want to make the most of their ___________ testing on,

00:00:35.400 --> 00:00:37.370
make sure they also comply with the spirit of PC.

00:00:37.370 --> 00:00:38.150
Idea says.

00:00:38.400 --> 00:00:40.150
The question I get asked most is,

00:00:40.370 --> 00:00:43.450
what should the scope of the internal next colonel test be?

00:00:43.840 --> 00:00:46.020
So, Taking our example Network,

00:00:46.020 --> 00:00:49.750
Let me quickly explain how I'd scope the PC IDE CSS pen test.

00:00:50.740 --> 00:00:52.360
Firstly, external test.

00:00:53.140 --> 00:00:56.370
The tester shown here is that Purple Circle will be

00:00:56.370 --> 00:00:57.810
somewhere out on the Internet,

00:00:57.820 --> 00:01:01.110
and they'd be targeting all of the external interfaces the

00:01:01.110 --> 00:01:03.070
organization has exposed on the Internet.

00:01:03.440 --> 00:01:04.840
So it's a various obvious one.

00:01:04.840 --> 00:01:08.960
They're off the web service and the web service connection to the internet.

00:01:09.340 --> 00:01:12.300
But there's also that VPN connection between each store and head office.

00:01:12.430 --> 00:01:15.270
Because those firewalls could have vulnerabilities or

00:01:15.270 --> 00:01:16.260
there could be Miss Configured.

00:01:16.260 --> 00:01:19.540
I'd expect the external pen test to look at both of those

00:01:19.650 --> 00:01:21.850
firewalls and make sure there was nothing there.

00:01:23.040 --> 00:01:28.060
Now let's think about the internal ___________ test and here, I'd first asked.

00:01:28.060 --> 00:01:32.340
The test is to go to one of the retail stores and see what they can actors on

00:01:32.340 --> 00:01:37.530
the in store systems and then also follow the VPN connection to see what systems

00:01:37.530 --> 00:01:40.260
of data thead office are accessible from the store.

00:01:40.740 --> 00:01:42.000
Because, remember,

00:01:42.090 --> 00:01:46.140
the physical security controls at remote stores is usually pretty poor,

00:01:46.300 --> 00:01:49.260
and I've actually been countless attacks launched from retail stores.

00:01:50.240 --> 00:01:52.530
Next, the very obvious test,

00:01:52.530 --> 00:01:55.220
which is having the test error connected into the 500.

00:01:55.310 --> 00:01:58.630
On the scope of this will be the 500 the DMC,

00:01:58.630 --> 00:02:02.360
and again I actually asked him to go back up the VPN into the stores.

00:02:03.440 --> 00:02:06.050
I'll also ask the test to connect the DMZ,

00:02:06.440 --> 00:02:12.110
targeting both systems in the DMZ and the core CD from the DMZ.

00:02:13.140 --> 00:02:16.610
And finally I asked him to test from the Management Network to make sure that

00:02:16.610 --> 00:02:19.860
it wasn't Miss Configured or it contained vulnerabilities,

00:02:20.240 --> 00:02:24.050
and also that it was only allowed to connect to systems in the permitted ways.

00:02:24.540 --> 00:02:28.560
So that's all the test side wants to his apartment internal ___________ test,

00:02:28.940 --> 00:02:33.350
which then leaves the segmentation test to fulfill requirement 11.3 point four.

00:02:33.940 --> 00:02:36.340
And I've sort of said here that you know that we've

00:02:36.340 --> 00:02:37.940
gotten out of scope Corporate network.

00:02:37.940 --> 00:02:40.720
So the most obvious place for the tested to start is on

00:02:40.720 --> 00:02:42.800
that corporate network to validate.

00:02:42.800 --> 00:02:46.790
There's no way through into the cardholder data environment or into the D.

00:02:46.790 --> 00:02:47.490
M Z,

00:02:47.650 --> 00:02:50.800
and also that the test they can't access anything other than the

00:02:50.800 --> 00:02:55.230
permitted service in the management network and if it hadn't been

00:02:55.230 --> 00:02:57.040
covered properly in the internal test.

00:02:57.200 --> 00:03:01.200
I also want the segmentation between the DMC on the core CD

00:03:01.200 --> 00:03:04.800
validated to to prove that it's a segmented separate network on

00:03:04.800 --> 00:03:07.240
does not like in any any rule on that firewall,

00:03:07.450 --> 00:03:11.730
meaning that we're now storing cardholder data on that on that database server,

00:03:11.730 --> 00:03:15.050
which is effectively accessible to anyone from the outside.

00:03:15.740 --> 00:03:16.290
So look,

00:03:16.300 --> 00:03:18.390
because ___________ testing is one of the most

00:03:18.390 --> 00:03:20.870
valuable requirements in PC IDE CSS.

00:03:21.240 --> 00:03:23.780
But it's also the one where there's so much opportunity

00:03:23.780 --> 00:03:27.080
for variability based on the tester, the environment,

00:03:27.080 --> 00:03:29.670
the cure nested and organizations intent.

00:03:30.040 --> 00:03:33.500
There is a really useful information supplements on the P CSS See

00:03:33.500 --> 00:03:36.340
website and is really recommend reading it before you.

00:03:36.340 --> 00:03:38.780
Commissioner ___________ test to learn about the

00:03:38.780 --> 00:03:41.520
vulnerabilities in your cardholder data environment,

00:03:41.720 --> 00:03:44.050
but also meet the requirements of 11.3.

00:03:45.640 --> 00:03:48.000
Now let's join that conversation with Jacob where we

00:03:48.000 --> 00:03:50.160
discuss ___________ testing methodologies.

00:03:50.370 --> 00:03:54.930
How QoS Assess Requirement 11.3 on Jacob's thoughts

00:03:54.930 --> 00:03:57.320
on on lousy ___________ tests.
