WEBVTT

00:00:01.340 --> 00:00:01.880
[Autogenerated] requirement.

00:00:01.880 --> 00:00:03.680
11 is all about assurance,

00:00:03.850 --> 00:00:07.530
testing systems and environments to find flaws and vulnerabilities in the

00:00:07.530 --> 00:00:12.280
cardholder data environment before a criminal does and making sure that

00:00:12.280 --> 00:00:14.060
the controls error working as they should be.

00:00:14.540 --> 00:00:16.850
So, although the theme is testing,

00:00:17.240 --> 00:00:21.060
it's actually a strange mix soup of requirements starting off with the

00:00:21.060 --> 00:00:24.170
need to test for the presence of wireless access points.

00:00:24.540 --> 00:00:28.070
Then a requirement to conduct internal and external vulnerability

00:00:28.070 --> 00:00:31.460
scans quarterly and ___________ tests annually,

00:00:31.940 --> 00:00:32.310
which,

00:00:32.310 --> 00:00:36.350
because it's such a complex area we're going to talk about in the next module.

00:00:37.040 --> 00:00:39.660
Then we come to a protective and Detective Control,

00:00:39.850 --> 00:00:42.860
which would actually sit much better requirements 12 and three,

00:00:43.000 --> 00:00:46.550
which is to have intruder detection or intruder prevention systems,

00:00:47.040 --> 00:00:49.570
and also something like file integrity monitoring to

00:00:49.570 --> 00:00:51.400
check the changes to critical files.

00:00:51.700 --> 00:00:52.270
And finally,

00:00:52.270 --> 00:00:56.160
the usual requirement for all this to be supported by policies and procedures.

00:00:57.140 --> 00:01:00.170
Because of the needs of vulnerability, scan and ___________ test,

00:01:00.540 --> 00:01:04.519
all systems within and connected to the CD will be in scope of

00:01:04.519 --> 00:01:06.660
some of the demands of this requirement.

00:01:07.540 --> 00:01:09.900
So let's start off with Requirement 1.1,

00:01:10.180 --> 00:01:13.720
which is designed to discover rogue wireless access points on the

00:01:13.720 --> 00:01:17.170
network because at one stage over the past 10 years,

00:01:17.540 --> 00:01:20.910
this really was a very common criminal attack in

00:01:20.910 --> 00:01:23.400
retail and head office environments.

00:01:23.540 --> 00:01:26.750
One of the most famous ever was a wireless attack.

00:01:27.340 --> 00:01:29.680
The requirement is actually a little more complex.

00:01:29.910 --> 00:01:35.680
It wants the organization to detect and identify both authorized and

00:01:35.690 --> 00:01:38.860
unauthorized wireless access points every three months.

00:01:39.640 --> 00:01:42.420
This is actually a really hard control to implement,

00:01:42.440 --> 00:01:44.770
which Jacob and I discuss at the end of the module,

00:01:45.240 --> 00:01:48.360
because you can't just walk around with wireless scanner like,

00:01:48.360 --> 00:01:49.490
perhaps he once could.

00:01:49.630 --> 00:01:52.320
There's so money wireless networks out there transmitting.

00:01:52.600 --> 00:01:56.460
And so let's look at the helpful note, which is included in the requirement,

00:01:57.340 --> 00:02:01.350
which says that you can achieve this by something like network access control

00:02:01.650 --> 00:02:04.270
that would prevent a rogue access point being connected.

00:02:04.740 --> 00:02:09.289
Or maybe by using some wireless I'd Sipes technology that would

00:02:09.289 --> 00:02:12.520
notice a new wireless access point in rage and then attempts to

00:02:12.520 --> 00:02:14.400
see the connection in Scope network.

00:02:14.430 --> 00:02:16.260
And if so, it disables it.

00:02:17.040 --> 00:02:20.550
The QoS is testing Procedure is quite varied because it allows

00:02:20.550 --> 00:02:22.550
for the organization to the implemented.

00:02:22.770 --> 00:02:25.890
Any one of the very many ways of meeting this requirement.

00:02:26.160 --> 00:02:26.860
Essentially,

00:02:26.980 --> 00:02:30.630
the QoS I would want to see the documented process for validating the

00:02:30.630 --> 00:02:33.740
presence of wireless access points costly on also what tools and

00:02:33.740 --> 00:02:36.270
techniques error in place on that they're working.

00:02:37.740 --> 00:02:40.150
There are a couple of sub requirements to 11.1.

00:02:40.420 --> 00:02:43.650
The first is that the organization should keep a register of

00:02:43.650 --> 00:02:45.650
the authorized wireless access points,

00:02:45.660 --> 00:02:49.550
along with a documented reason they exist and error allowed to be

00:02:49.550 --> 00:02:53.230
connected to the 500 because it's essential to keep a documented

00:02:53.230 --> 00:02:55.630
infantry of approved wireless access points has.

00:02:55.630 --> 00:02:58.930
Then it sees snow that a connected wireless x excess point

00:02:58.930 --> 00:03:01.930
that's not on the industry's rows or it hasn't gone through

00:03:01.930 --> 00:03:03.450
the correct internal processes.

00:03:04.340 --> 00:03:06.220
The testing procedure is for the QoS A.

00:03:06.220 --> 00:03:09.420
To check the inventory and make sure there's a recorded business

00:03:09.420 --> 00:03:12.170
justification for each wireless access point.

00:03:13.140 --> 00:03:17.150
The other sub requirement here is that the organization does something

00:03:17.250 --> 00:03:20.670
when an unauthorized wireless access point is detected,

00:03:21.040 --> 00:03:25.780
which requires there to be an incident response procedures to be followed on.

00:03:25.780 --> 00:03:29.200
You won't be surprised to discover that the testing procedures for the QoS A.

00:03:29.210 --> 00:03:32.420
To check those incident response procedures and also speak with the

00:03:32.420 --> 00:03:35.660
relevant people to make sure that they would be followed in the event of

00:03:35.660 --> 00:03:38.070
a rogue wireless access point being detected.
