WEBVTT

00:00:01.240 --> 00:00:03.650
[Autogenerated] I'm going to skip over, require 11.3,

00:00:03.660 --> 00:00:07.690
which is concerned with ___________ testing because it's such a big requirement,

00:00:07.970 --> 00:00:11.260
and it's with one of the most important security controls in the deeds.

00:00:11.480 --> 00:00:13.450
It justifies its own module,

00:00:14.040 --> 00:00:17.740
so we're going to move on to the other two items left in required 11.

00:00:18.030 --> 00:00:21.060
These last to a detective controls the first,

00:00:21.060 --> 00:00:25.700
of which 11.4 is a requirement to have intruded detection on

00:00:25.700 --> 00:00:27.870
perhaps intruder prevention techniques.

00:00:28.340 --> 00:00:31.540
Now it's important to note this, Jenner says, techniques.

00:00:31.550 --> 00:00:35.960
So it's neutral when it comes to how this is implemented in your organization,

00:00:36.540 --> 00:00:39.340
although is usually going to be on a perimeter device like a

00:00:39.340 --> 00:00:43.360
firewall on the standard sort of requires or implies that because

00:00:43.360 --> 00:00:45.450
it talks about having it at the perimeter,

00:00:45.840 --> 00:00:48.550
although you know it will be equally valid for you to

00:00:48.550 --> 00:00:50.620
have this on a network span port on,

00:00:50.620 --> 00:00:53.210
analyze traffic for a whole network segment and look

00:00:53.210 --> 00:00:55.430
for intruders on that segment on,

00:00:55.430 --> 00:00:58.270
then feed that back into a primitive control device

00:00:58.270 --> 00:01:01.020
from something like the I PS detector.

00:01:01.250 --> 00:01:04.640
Another a couple more things to think about because as

00:01:04.640 --> 00:01:07.170
well as at the perimeter of the 500.

00:01:07.640 --> 00:01:11.750
The Standard also talks about monitoring traffic at critical points.

00:01:12.240 --> 00:01:15.600
So it's a question of thinking where the best points would be on the

00:01:15.600 --> 00:01:19.570
network to detect attacker traffic that pose the highest risk to

00:01:19.570 --> 00:01:22.510
cardholder data in our sample network.

00:01:22.510 --> 00:01:25.630
The main points I'd be looking for intruder detection capability

00:01:25.830 --> 00:01:29.980
would be the main perimeter of the e commerce Web servers then that

00:01:29.980 --> 00:01:33.340
firewall that provides the connection into head office from the

00:01:33.340 --> 00:01:37.190
retail stores that also be quite pleased to have some ideas

00:01:37.190 --> 00:01:39.970
functionality on the retail stores, firewalls.

00:01:40.640 --> 00:01:43.650
But the key place I would want IDE s is that firewall that

00:01:43.650 --> 00:01:47.230
connected the Dems to the payment systems on also provides the

00:01:47.230 --> 00:01:49.030
connection to the management network.

00:01:49.130 --> 00:01:53.150
Because that's the most likely route into my 500 for an attacker.

00:01:54.040 --> 00:01:57.070
The testing procedures pretty comprehensive for this requirement.

00:01:57.540 --> 00:02:00.700
The QoS is first going to look at the network diagram and cardholder

00:02:00.700 --> 00:02:04.550
data flows to make sure that they understand what is the perimeter on

00:02:04.550 --> 00:02:06.720
where the critical places in the CDR,

00:02:06.730 --> 00:02:10.229
where intruder detection or prevention will be necessary Next,

00:02:10.259 --> 00:02:13.820
they're going to look at the configuration of IDE s or IOPS systems to

00:02:13.820 --> 00:02:16.340
make sure they're set to produce alerts on the QoS.

00:02:16.340 --> 00:02:18.550
I will also want to interview the people who should

00:02:18.550 --> 00:02:20.210
be responding to those alerts.

00:02:20.640 --> 00:02:21.150
Finally,

00:02:21.540 --> 00:02:24.690
the validate that the system's the IDE is or IOPS systems

00:02:24.780 --> 00:02:28.650
are getting regular vendor updates such as new signatures

00:02:28.650 --> 00:02:32.670
or new behavioral algorithms, or even just system upgrades.
