WEBVTT

00:00:00.140 --> 00:00:00.860
[Autogenerated] So, Jacob,

00:00:01.340 --> 00:00:05.680
we started talking about making sure things were working in Requirement 10.

00:00:05.690 --> 00:00:06.090
Yes,

00:00:06.090 --> 00:00:08.470
that requirement for service providers spells report

00:00:08.480 --> 00:00:10.550
to to do things with failures.

00:00:10.560 --> 00:00:12.720
Requirement 11 is all about checking things.

00:00:12.720 --> 00:00:13.760
Error working, isn't it?

00:00:14.140 --> 00:00:16.470
And it starts off by looking at wireless access.

00:00:16.470 --> 00:00:18.440
This is a really weird one, because it is an odd one.

00:00:18.450 --> 00:00:20.100
So So talk me through.

00:00:20.110 --> 00:00:23.370
I could tell you why it's there because it's there because there

00:00:23.370 --> 00:00:26.680
was a very big breach a long time ago where somebody sat in the

00:00:26.680 --> 00:00:31.690
car park and siphoned cardholder data from a big fashion retailer

00:00:31.700 --> 00:00:32.820
over the wireless network.

00:00:32.820 --> 00:00:34.650
So that's why we have that requirement in place,

00:00:34.660 --> 00:00:37.210
yes, but as a necessity time, you know,

00:00:37.210 --> 00:00:39.750
I often see just mouth is not a place where we don't have any wireless networks.

00:00:39.760 --> 00:00:41.240
Well, that that's an error, right?

00:00:41.250 --> 00:00:47.030
Because the goal in 11 1 is to say, find hostile wireless devices, right?

00:00:47.040 --> 00:00:49.940
And in the early part of my career, when I did ___________,

00:00:49.940 --> 00:00:53.590
testing some of the internal kind of half social engineering,

00:00:53.590 --> 00:00:55.760
half kind of technical pen testing was figuring out,

00:00:56.040 --> 00:01:01.450
Can we walk into a place and plug a wireless network into into a network,

00:01:01.450 --> 00:01:04.239
jack somewhere that we shouldn't and then have the end

00:01:04.239 --> 00:01:05.880
of the colleague in the car park, you know,

00:01:05.880 --> 00:01:08.520
connect to the network and do something terrible right on.

00:01:08.520 --> 00:01:11.170
The answer was generally, yeah, we could do that, right.

00:01:11.180 --> 00:01:13.640
We could disable the door control system.

00:01:13.740 --> 00:01:15.760
Um, testing for was network.

00:01:16.180 --> 00:01:19.510
If I just pull out my phone and scan for wireless networks,

00:01:19.510 --> 00:01:21.830
you know, 50 or 60 of them quite frequently.

00:01:21.830 --> 00:01:22.340
Sure.

00:01:22.350 --> 00:01:22.770
So?

00:01:22.780 --> 00:01:26.030
So there's, I think once upon a time,

00:01:26.040 --> 00:01:28.900
it was an intern with nets Tumbler on a laptop,

00:01:28.910 --> 00:01:29.260
Right?

00:01:29.270 --> 00:01:32.640
Uh, you know, in advance of the mobile phone that could do that for you.

00:01:32.650 --> 00:01:37.040
Kind of wandering around the space, looking for wireless networks anymore.

00:01:37.050 --> 00:01:39.100
That seems like a more troublesome approach,

00:01:39.100 --> 00:01:39.240
right,

00:01:39.240 --> 00:01:41.960
Because you can't tell if that radio signal is connected

00:01:41.960 --> 00:01:43.460
to your network or somebody else's.

00:01:43.440 --> 00:01:46.910
I think you have to go through kind of the other side, right?

00:01:46.920 --> 00:01:51.950
And a lot of the sort of general kind of asset management stuff will cover this,

00:01:51.960 --> 00:01:52.250
right?

00:01:52.260 --> 00:01:54.560
What is plugged into my switches?

00:01:54.570 --> 00:01:55.240
Right.

00:01:55.250 --> 00:01:58.720
Uh, and and on a small enough scale,

00:01:58.730 --> 00:02:00.970
somebody going and looking at the back of the switch and

00:02:00.970 --> 00:02:02.480
saying what is plugged into my switches?

00:02:02.480 --> 00:02:03.830
Can I follow the wires?

00:02:03.840 --> 00:02:06.070
Do they all go to the places I expect them to?

00:02:06.540 --> 00:02:09.680
Could work right on the larger scale that gets that gets,

00:02:09.690 --> 00:02:11.960
you know, uh, troublesome very quickly.

00:02:11.970 --> 00:02:15.780
But if you're able to, then see, what are all the things that are connected,

00:02:15.790 --> 00:02:16.260
right?

00:02:16.270 --> 00:02:17.200
Do I recognize them?

00:02:17.200 --> 00:02:20.730
Do they belong, uh, you know, is sort of one way to do it.

00:02:20.730 --> 00:02:22.730
And then 11, 1 morphed a little bit along the way.

00:02:22.730 --> 00:02:25.250
I think in this sort of 3.1, uh,

00:02:25.260 --> 00:02:29.770
time frame where it wasn't just about wireless devices

00:02:29.770 --> 00:02:31.870
connected over a network connection.

00:02:31.880 --> 00:02:33.400
But if somebody is inserting,

00:02:33.400 --> 00:02:36.850
like a USB wireless interface into a server or

00:02:36.850 --> 00:02:40.180
workstation or something like that, uh, that also matters.

00:02:40.190 --> 00:02:44.700
So, uh, you know, it may be the case where you know,

00:02:44.700 --> 00:02:48.390
if you have a handful of rack racks of systems in a data center,

00:02:48.390 --> 00:02:50.850
you go look and somebody plug something into the USB ports,

00:02:51.040 --> 00:02:51.350
right?

00:02:51.360 --> 00:02:55.940
Or again, You look at you know, the, uh,

00:02:55.950 --> 00:02:59.610
device sort of configuration logs or a D message on UNIX,

00:02:59.610 --> 00:03:02.660
a Linux systems or whatever, and like what's plugged into the USB ports.

00:03:02.670 --> 00:03:05.310
Yeah, but you know, the standard says very clearly.

00:03:05.320 --> 00:03:08.040
If you've got very good network access control,

00:03:08.050 --> 00:03:10.020
like road devices can't get plugged in.

00:03:10.020 --> 00:03:10.370
Right?

00:03:10.380 --> 00:03:13.290
That has the that fulfills the intent of the required does.

00:03:13.300 --> 00:03:13.960
It does.

00:03:14.240 --> 00:03:17.470
So you don't need a wireless specific utility to do that.

00:03:17.480 --> 00:03:18.250
There's an accessory.

00:03:18.250 --> 00:03:20.730
You seeing more people relying on the network level control

00:03:20.730 --> 00:03:22.130
rather than the scanning for wireless.

00:03:22.140 --> 00:03:23.270
Yes, very much so.

00:03:23.440 --> 00:03:24.000
Yeah.

00:03:24.010 --> 00:03:27.310
Just you can see for water in any public environment.

00:03:27.310 --> 00:03:31.380
I don't I don't see how it works, even in a co location facility right there.

00:03:31.390 --> 00:03:31.680
You know,

00:03:31.680 --> 00:03:34.150
there might be other tenants in that cola who have some

00:03:34.150 --> 00:03:35.470
WAP in there for whatever reason.
