WEBVTT

00:00:00.040 --> 00:00:02.750
[Autogenerated] and way move to the other sort of scanning,

00:00:02.750 --> 00:00:03.740
which is vulnerability.

00:00:03.740 --> 00:00:04.680
Scanning, Yes.

00:00:05.640 --> 00:00:09.490
Quarterly, internally and externally.

00:00:09.500 --> 00:00:10.060
Yes.

00:00:10.140 --> 00:00:13.730
This this is actually one of the most troublesome requirements.

00:00:14.060 --> 00:00:14.620
Uh,

00:00:14.630 --> 00:00:21.240
in that all the other requirements don't have sort of a historical

00:00:21.250 --> 00:00:24.520
demonstration of compliance element to them,

00:00:24.530 --> 00:00:24.950
right?

00:00:24.960 --> 00:00:26.820
They can all be completely fallen down.

00:00:26.830 --> 00:00:29.510
I show up, do the assessment, and they fix it all.

00:00:29.520 --> 00:00:30.890
You know, go and sin no more.

00:00:30.890 --> 00:00:31.180
Right?

00:00:31.180 --> 00:00:31.640
Great.

00:00:31.650 --> 00:00:37.150
Um, but if you have to say, did you have four quarterly passing scans?

00:00:37.160 --> 00:00:37.640
Right.

00:00:37.650 --> 00:00:40.980
And in the report on compliance, the external scan section in the summer,

00:00:40.980 --> 00:00:44.540
he says, Tell me about your four passing scans right now.

00:00:44.540 --> 00:00:47.360
I don't think the intent is that if you've missed the cue to

00:00:47.360 --> 00:00:50.940
scan from six months ago that you are intended to sort of sit

00:00:50.950 --> 00:00:53.810
in the non compliant penalty box, you know,

00:00:53.810 --> 00:00:57.060
for whatever period of time it takes you to get this four passing scans.

00:00:57.340 --> 00:01:01.360
Uh, but it kind of feels like it, right,

00:01:01.370 --> 00:01:04.760
and and, you know, just so with internal scans,

00:01:04.769 --> 00:01:05.750
um,

00:01:05.760 --> 00:01:08.320
I have a lot of clients that maybe have a relatively

00:01:08.320 --> 00:01:10.350
small internet facing sort of surface,

00:01:10.360 --> 00:01:14.710
but a vast internal array of systems and their

00:01:14.710 --> 00:01:16.960
internal scans are very problematic.

00:01:16.940 --> 00:01:21.010
Where there there's always new vulnerabilities coming up and even as they

00:01:21.010 --> 00:01:24.130
patch them and run the risk and new things sort of crop up.

00:01:24.140 --> 00:01:28.340
And what comes out of that what what I see is A is a

00:01:28.340 --> 00:01:29.980
really sort of common trouble spot.

00:01:29.990 --> 00:01:33.810
Uh, is that maybe they run a scan and they get a scan output,

00:01:33.820 --> 00:01:36.350
you know, file from whatever utility they're using,

00:01:36.360 --> 00:01:37.420
Uh,

00:01:37.430 --> 00:01:42.200
but then they're not like managing those findings in some

00:01:42.200 --> 00:01:45.230
meaningful way scanning and putting in the right,

00:01:45.230 --> 00:01:48.570
the scanning putting in the drawer or even if they're fixing stuff.

00:01:48.580 --> 00:01:52.520
Uh, you know, the I run a scan and I find these vulnerabilities.

00:01:52.530 --> 00:01:54.350
And then I fix those vulnerabilities.

00:01:54.360 --> 00:01:57.610
And then I run or re scan to show that those error fixed and I

00:01:57.610 --> 00:02:00.030
find new vulnerabilities like you have to have.

00:02:00.040 --> 00:02:01.040
That's the way the world works.

00:02:01.040 --> 00:02:02.900
It was the way the world works and you have to have.

00:02:02.900 --> 00:02:03.640
I mean, you know,

00:02:03.640 --> 00:02:05.240
you could do with a spreadsheet or you could do it with

00:02:05.240 --> 00:02:06.870
something more sophisticated than that.

00:02:06.940 --> 00:02:10.050
Some sort of mechanism to track that and to say Okay,

00:02:10.050 --> 00:02:11.650
found this vulnerability on this date,

00:02:11.660 --> 00:02:14.440
which means I have to have it fixed by this date,

00:02:14.450 --> 00:02:14.870
right?

00:02:14.880 --> 00:02:17.220
And then when I ran the scan at that point,

00:02:17.220 --> 00:02:20.240
I found some new vulnerability that then has to be fixed on some later date.

00:02:20.250 --> 00:02:23.220
And you have to be able to sort of roll forward with that.

00:02:23.230 --> 00:02:25.920
And you have to be able to, you know,

00:02:25.930 --> 00:02:29.440
manage your your sort of disposition of those vulnerabilities.

00:02:29.440 --> 00:02:31.400
If you look at it and say that's a false positive,

00:02:31.410 --> 00:02:34.620
right and you can substantiate that great,

00:02:34.630 --> 00:02:35.030
right.

00:02:35.040 --> 00:02:39.310
But you need some sort of records keeping to show That's a false positive,

00:02:39.320 --> 00:02:39.550
right?

00:02:39.550 --> 00:02:42.050
So as a necessity, you are looking for that management process.

00:02:42.050 --> 00:02:42.700
Exactly.

00:02:42.710 --> 00:02:45.830
Scam Re Mediate Scan re Mediate.

00:02:45.840 --> 00:02:47.410
Is that a managed process,

00:02:47.420 --> 00:02:50.640
or is it someone just with the scanner and put in the drawer?

00:02:50.650 --> 00:02:51.110
Right.

00:02:51.120 --> 00:02:55.660
Okay, Now I often got a lot of questions about vulnerability scanning.

00:02:55.660 --> 00:02:57.920
So let's talk about external first.

00:02:57.920 --> 00:02:59.990
It has to be a particular type of company that does it,

00:02:59.990 --> 00:03:02.970
and to be correct, um,

00:03:03.340 --> 00:03:06.520
on the one thing I often so I when I used to receive

00:03:06.520 --> 00:03:10.100
reports on compliance for service providers.

00:03:10.110 --> 00:03:12.410
I would actually check that.

00:03:12.410 --> 00:03:14.640
The people in scanning, we're in CSV.

00:03:14.650 --> 00:03:15.150
Right.

00:03:15.160 --> 00:03:18.450
You'll be surprised at how often that isn't that you still the same?

00:03:18.460 --> 00:03:19.400
Same problem.

00:03:19.400 --> 00:03:21.420
You do see that problem every now and again,

00:03:21.430 --> 00:03:23.730
or or even, uh,

00:03:23.740 --> 00:03:26.490
some of those SVS have a couple of different kinds of

00:03:26.490 --> 00:03:28.270
vulnerability scanning service options.

00:03:28.280 --> 00:03:28.650
Right?

00:03:28.640 --> 00:03:32.310
And some of them are like one of them is the CSV scanning,

00:03:32.320 --> 00:03:35.010
and one of them is some other kind of vulnerable is can.

00:03:35.010 --> 00:03:36.550
And there's nothing wrong with that.

00:03:36.560 --> 00:03:40.320
But don't use the knot CSV stuff for the A S V requirement,

00:03:40.330 --> 00:03:43.320
because that's a really tight requirement from the council is

00:03:43.330 --> 00:03:44.840
because the council actually have a program.

00:03:44.840 --> 00:03:47.840
Where, where they test the scanners actually doing the right job, right?

00:03:47.850 --> 00:03:50.250
Yeah, Right now, Internal scans.

00:03:50.240 --> 00:03:51.260
Who can do those?

00:03:51.270 --> 00:03:52.500
Does that have to be a QC?

00:03:52.510 --> 00:03:57.230
No, no, the the organization can do their own internal scans.

00:03:57.240 --> 00:03:59.860
Uh, if they've got the people right, people,

00:03:59.860 --> 00:04:02.380
the people who are qualified, who understand what they're doing,

00:04:02.380 --> 00:04:06.420
who can operate the scanning utility and who are sort of usefully independent,

00:04:06.420 --> 00:04:06.590
right?

00:04:06.590 --> 00:04:09.440
You don't want the sys admin zones who are

00:04:09.440 --> 00:04:11.050
responsible for managing those systems,

00:04:11.050 --> 00:04:13.160
then also running the vulnerability scans.

00:04:13.740 --> 00:04:16.570
So that could be that could be sort of tricky for organizations that

00:04:16.570 --> 00:04:18.440
don't have a big enough sort of spread of I t.

00:04:18.440 --> 00:04:22.000
People or who don't have a separate security department or something like that.

00:04:22.010 --> 00:04:24.710
Because maybe you just don't have enough expertise.

00:04:24.720 --> 00:04:27.070
These object is not to hand this to, you know,

00:04:27.070 --> 00:04:28.190
the sales person say, hey,

00:04:28.200 --> 00:04:32.810
run the scanning utility on that because then you don't

00:04:32.810 --> 00:04:33.930
have somebody with the right expertise.

00:04:33.930 --> 00:04:36.150
Okay, so there's independence from the people,

00:04:36.150 --> 00:04:40.170
maintaining the controls, effectively qualified.

00:04:40.180 --> 00:04:40.710
Right.

00:04:40.720 --> 00:04:41.900
You qualify.

00:04:41.900 --> 00:04:43.070
What, you mean qualified?

00:04:43.070 --> 00:04:43.870
They've been on the course.

00:04:43.870 --> 00:04:45.570
They they've got an exam.

00:04:45.540 --> 00:04:49.260
They have to be able to demonstrate to the assessor some competence.

00:04:49.260 --> 00:04:52.260
Okay, so when you go and do an assessment, you're looking at the scans.

00:04:52.340 --> 00:04:54.950
We also interviewing the person doing the scanning, right?

00:04:54.960 --> 00:04:55.450
Right.

00:04:55.450 --> 00:04:59.480
And and generally I want to see how that scanner is configured, right?

00:04:59.490 --> 00:05:03.260
Most scanners, most vulnerability scanners are signature based, right?

00:05:03.270 --> 00:05:06.640
Which means there are more signatures tomorrow than there were today.

00:05:06.650 --> 00:05:07.000
Right?

00:05:07.010 --> 00:05:09.090
Are you getting those?

00:05:09.100 --> 00:05:13.690
Are you configuring the scanner to use the sort of correct set of signatures.

00:05:13.690 --> 00:05:17.370
It's very easy to configure it to use a limited set, right?

00:05:17.380 --> 00:05:18.430
And maybe that's appropriate.

00:05:18.430 --> 00:05:18.560
Right?

00:05:18.560 --> 00:05:22.640
Maybe you don't want to have your scanner run with tests that

00:05:22.640 --> 00:05:24.370
could affect the denial service condition,

00:05:24.340 --> 00:05:24.670
right?

00:05:24.680 --> 00:05:26.140
You don't generally want to do that.

00:05:26.150 --> 00:05:29.260
You don't have to do that from API CSS compliance standpoint.

00:05:29.340 --> 00:05:30.130
Uh,

00:05:30.140 --> 00:05:33.420
but you do want to make sure that you're actually testing for

00:05:33.430 --> 00:05:35.830
sort of a usefully broad set of vulnerabilities,

00:05:35.840 --> 00:05:36.140
right?

00:05:36.150 --> 00:05:39.870
A question that again, lots of people ask.

00:05:40.440 --> 00:05:44.460
This applies to internal and external scans, credentials or not credentials.

00:05:45.040 --> 00:05:46.270
Hmm.

00:05:46.840 --> 00:05:51.480
There is not an express requirement in any of the

00:05:51.480 --> 00:05:54.190
language for credential scanning, right?

00:05:54.200 --> 00:05:55.510
Eso que s I?

00:05:55.510 --> 00:05:57.620
You have to accept non credentials.

00:05:57.620 --> 00:06:00.100
I think I have to accept non credential scans.

00:06:00.110 --> 00:06:01.780
Um, does that make you happy?

00:06:01.790 --> 00:06:02.590
No.

00:06:02.590 --> 00:06:03.830
It's super frustrating.

00:06:03.840 --> 00:06:05.160
There are.

00:06:05.160 --> 00:06:07.100
There are often, you know,

00:06:07.100 --> 00:06:11.430
loads of vulnerabilities that you won't find without credential.

00:06:11.430 --> 00:06:13.250
Scans right on.

00:06:13.250 --> 00:06:15.110
And you know that I look at my colleagues,

00:06:15.120 --> 00:06:17.960
uh, in my company who are part of our federal practice,

00:06:17.960 --> 00:06:22.880
which is the, uh, standard for assessing entities that provide services to the U.

00:06:22.880 --> 00:06:22.990
S.

00:06:22.990 --> 00:06:23.550
Government.

00:06:23.560 --> 00:06:28.100
Right and federal expressly requires credential scans, right?

00:06:28.110 --> 00:06:29.820
I think they looked at, you know,

00:06:29.820 --> 00:06:32.990
the sort of absence of that express statement in PC ideas.

00:06:32.990 --> 00:06:33.550
Hasn't said,

00:06:33.840 --> 00:06:37.460
Let's not do that s o they get credentialed scans and they get

00:06:37.460 --> 00:06:40.750
all this information and frustrating TIFF.

00:06:41.440 --> 00:06:42.680
Is that something you've passed back to?

00:06:42.680 --> 00:06:44.110
The council is because the, you know,

00:06:44.110 --> 00:06:46.020
the council ask every three years of feedback.

00:06:46.020 --> 00:06:46.410
All right.

00:06:46.420 --> 00:06:48.870
You know, I think I think the number of people have asked for it.

00:06:48.880 --> 00:06:54.190
So from a risk perspective, you advise only client 2D credential scans.

00:06:54.740 --> 00:06:57.420
Yeah, well, I certainly would advise that.

00:06:57.420 --> 00:07:00.140
Yeah, I think you get better data and and,

00:07:00.150 --> 00:07:00.590
ah,

00:07:00.590 --> 00:07:04.000
lot of the scanning utilities anymore can provide

00:07:04.000 --> 00:07:05.690
some other very useful services.

00:07:05.690 --> 00:07:09.160
If their credential, they can tell you how devices error configured.

00:07:09.170 --> 00:07:09.470
Right?

00:07:09.480 --> 00:07:12.470
You can use your scanning utility to get some

00:07:12.470 --> 00:07:14.410
configuration management stuff to help you,

00:07:14.410 --> 00:07:16.860
even with things like a requirement to or requirement six.

00:07:16.840 --> 00:07:17.170
Right.

00:07:17.170 --> 00:07:19.000
So you know that Ah,

00:07:19.000 --> 00:07:22.300
lot of these things converge more more if you have more sophisticated tooling.

00:07:22.300 --> 00:07:23.290
So why wouldn't you do that?
