WEBVTT

00:00:01.040 --> 00:00:04.010
[Autogenerated] requiring 11.2 demands that an organization of

00:00:04.010 --> 00:00:08.690
proactively carries out vulnerability scans on at least a quarterly

00:00:08.690 --> 00:00:13.560
basis and also after any significant change,

00:00:14.340 --> 00:00:17.310
scans a required both inside the 100 on from

00:00:17.310 --> 00:00:19.260
outside the organisation's perimeter.

00:00:19.840 --> 00:00:22.450
Each of these is a separate sub requirement.

00:00:22.840 --> 00:00:26.740
The rules around internal and external scans error suddenly different,

00:00:26.940 --> 00:00:28.660
and it's important not to confuse the two.

00:00:29.340 --> 00:00:32.100
There's no explicit testing procedure for 11.2.

00:00:32.259 --> 00:00:36.180
It just points to the test requiring the sub requirements on.

00:00:36.180 --> 00:00:40.730
The first of these is concerned with periodic internal vulnerability scans,

00:00:40.870 --> 00:00:42.550
which must be carried out quarterly.

00:00:43.440 --> 00:00:47.870
Typically, a vulnerability scan will detect previously unknown vulnerabilities.

00:00:48.120 --> 00:00:50.760
After all, that's the purpose of carrying it out.

00:00:51.380 --> 00:00:55.990
And so the requirement is not only to scan for vulnerabilities but to risk

00:00:55.990 --> 00:01:00.120
assess any vulnerabilities found based on the methodology the organization

00:01:00.120 --> 00:01:05.750
define for vulnerability management in requirements 6.1 and then the

00:01:05.750 --> 00:01:09.960
organization needs to rectify any critical or high vulnerabilities before

00:01:09.960 --> 00:01:11.610
re scanning the environment.

00:01:11.740 --> 00:01:15.740
To validate that the discovered vulnerabilities have been fixed on,

00:01:15.740 --> 00:01:18.060
this has to happen every quarter.

00:01:18.840 --> 00:01:19.380
Lastly,

00:01:19.580 --> 00:01:21.660
the requirement wants to make sure the vulnerability

00:01:21.660 --> 00:01:23.460
scanning was done by someone qualified.

00:01:24.040 --> 00:01:25.420
Which, of course, begs the question.

00:01:25.420 --> 00:01:27.080
Well, who can that be?

00:01:27.330 --> 00:01:27.760
Well,

00:01:28.140 --> 00:01:30.330
it needs to be someone who could demonstrate that they're

00:01:30.330 --> 00:01:33.270
qualified and trained in the use of the scanning tool.

00:01:33.940 --> 00:01:36.970
It doesn't mean a formal P CSS see quantification

00:01:36.970 --> 00:01:41.710
like an internal security assessor, qualified security assessor,

00:01:41.740 --> 00:01:45.390
unproved scanning vendor or even API CLI professional.

00:01:45.400 --> 00:01:48.970
And it's also not quantification like having assist or something like that.

00:01:49.740 --> 00:01:53.390
The person doing the scanning can be an external resource or

00:01:53.390 --> 00:01:55.200
someone that works for the organization.

00:01:55.260 --> 00:01:55.710
However,

00:01:55.720 --> 00:01:59.380
if they're in internal resource than this person must also be

00:01:59.390 --> 00:02:02.400
independent of the people managing the infrastructure on

00:02:02.400 --> 00:02:04.020
applications that are being scanned.

00:02:04.180 --> 00:02:05.760
They can't be in the same team.

00:02:06.840 --> 00:02:08.770
To validate this requirements in place,

00:02:09.030 --> 00:02:11.880
the QoS A is going to look for at least four scan

00:02:11.880 --> 00:02:13.920
reports covering the last four quarters,

00:02:14.060 --> 00:02:17.120
including those re scans to show that the critical on

00:02:17.120 --> 00:02:18.870
high vulnerabilities have been fixed.

00:02:19.240 --> 00:02:21.790
They'll also interview the people responsibility for doing the

00:02:21.790 --> 00:02:24.850
scans to find out if they are indeed qualified.

00:02:25.340 --> 00:02:28.900
Now, if this is your first ever PC IDE CSS assessment,

00:02:29.030 --> 00:02:31.370
the QoS a will just look for one scan because obviously you

00:02:31.370 --> 00:02:34.070
haven't got a whole year's worth of quarterly scans.

00:02:34.840 --> 00:02:37.260
Now we come to external vulnerability scans,

00:02:37.370 --> 00:02:40.570
which error detailed and requiring 11.2 point two.

00:02:40.940 --> 00:02:43.460
Again, These need to be conducted quarterly.

00:02:43.940 --> 00:02:47.440
But these external scans must be undertaken by an

00:02:47.440 --> 00:02:50.530
organization called an approved scanning Vendor,

00:02:50.540 --> 00:02:51.560
or CSV.

00:02:51.940 --> 00:02:54.980
So that's a company licensed and approved by the Payment

00:02:54.980 --> 00:02:57.270
Card Industry Security Standards Council.

00:02:57.410 --> 00:02:59.560
To perform these vulnerability scans,

00:03:00.040 --> 00:03:04.250
you can find a list of all the approved scanning vendors on the P

00:03:04.250 --> 00:03:07.060
CSS See website that there are lots of them.

00:03:07.440 --> 00:03:07.990
And fact.

00:03:07.990 --> 00:03:11.070
If you use any of the reputable external vulnerability scanning

00:03:11.070 --> 00:03:14.060
companies now to check your external network perimeter,

00:03:14.070 --> 00:03:15.300
it's a fair assumption.

00:03:15.300 --> 00:03:16.860
They're also going to be in CSV.

00:03:18.240 --> 00:03:24.460
But API CSV scan is not the same as a general external vulnerability.

00:03:24.460 --> 00:03:26.850
Scan the type of scan you might be buying at the moment.

00:03:27.240 --> 00:03:29.350
It's conducted in a specific way,

00:03:29.580 --> 00:03:33.060
and there's an obligation on the company to issue a pass,

00:03:33.440 --> 00:03:36.340
which means that the scanner found no vulnerabilities

00:03:36.510 --> 00:03:38.990
with a CVS s score greater than four,

00:03:39.180 --> 00:03:44.360
or vulnerabilities that the P CSS see would consider an automatic fail.

00:03:45.440 --> 00:03:49.050
Quite often they're going to be false positives in CSV results,

00:03:49.180 --> 00:03:52.250
so you'll need to clarify those with the company.

00:03:52.640 --> 00:03:56.510
And sometimes you won't be able to re mediate a vulnerability on,

00:03:56.510 --> 00:04:00.310
so you'll need to demonstrate the CSV that you've other controls in place to

00:04:00.310 --> 00:04:03.170
mitigate the risk of that vulnerability being exploited.

00:04:04.140 --> 00:04:07.720
The requirement is that you have a passing scan each quarter,

00:04:07.720 --> 00:04:12.120
and that's what the NSA will want to see on again if this is your first

00:04:12.130 --> 00:04:15.470
PC IDE CSS assessment for look for one passing scan.

00:04:16.740 --> 00:04:20.760
The last vulnerability scanning requirement 11.2 point three,

00:04:21.140 --> 00:04:23.500
is that in addition to quarterly scans,

00:04:23.630 --> 00:04:26.600
the organization conducts internal and external

00:04:26.600 --> 00:04:31.820
scans after any significant change, which,

00:04:31.820 --> 00:04:33.530
of course, leads to the question of, Well,

00:04:33.560 --> 00:04:34.040
what?

00:04:34.040 --> 00:04:36.260
What is a significant change?

00:04:36.840 --> 00:04:40.350
I'm afraid there isn't a clear answer because it depends on your environment.

00:04:40.740 --> 00:04:42.280
The guidance is helpful here.

00:04:42.530 --> 00:04:46.990
And so my take is that if you change anything in the system that stores or

00:04:46.990 --> 00:04:51.160
process or transmits cardholder data or anything that's explicitly there to

00:04:51.160 --> 00:04:54.300
provide a security function like a firewall,

00:04:54.450 --> 00:04:58.060
then that's significant because the thing to remember is that

00:04:58.070 --> 00:05:01.080
running a vulnerability scan generally is free.

00:05:01.090 --> 00:05:02.260
It shouldn't cost you anything,

00:05:02.640 --> 00:05:05.890
so there's really no excuse not to do it more frequently.

00:05:05.980 --> 00:05:09.210
Whether it's a significant change or even a minor change,

00:05:09.210 --> 00:05:09.590
you think, Well,

00:05:09.590 --> 00:05:11.540
I'll just do a quick vulnerability scan to make sure

00:05:11.540 --> 00:05:13.260
I'm not introduce the vulnerability.

00:05:13.640 --> 00:05:15.860
The scanning after a significant change,

00:05:15.870 --> 00:05:18.950
has to be conducted by someone qualified and independent.

00:05:19.340 --> 00:05:21.750
But in this case, if it's an external scan,

00:05:21.820 --> 00:05:23.830
it doesn't actually need to be done by CSV.

00:05:23.830 --> 00:05:27.650
It's not looking for a passing scan after a significant change.

00:05:28.540 --> 00:05:30.430
To meet the testing requirement,

00:05:30.650 --> 00:05:33.610
the QoS A will want to review or change control system to see

00:05:33.620 --> 00:05:36.670
evidence of changes on the justification than being in the

00:05:36.670 --> 00:05:39.550
clusters significant or non significant.

00:05:40.140 --> 00:05:42.860
Then where there's been a significant change,

00:05:42.860 --> 00:05:46.050
the QoS A will want to review the scan reports to validate.

00:05:46.170 --> 00:05:49.310
The scans were carried out on that they were carried out by qualified

00:05:49.320 --> 00:05:52.980
independent resources and that for an external scan,

00:05:53.080 --> 00:05:55.360
no vulnerabilities with the CBSS score,

00:05:55.360 --> 00:05:59.860
more than four were not re mediated and for an internal scan,

00:05:59.990 --> 00:06:02.970
no higher critical vulnerabilities were not fixed.

00:06:03.940 --> 00:06:07.180
Now there have been a surprising number of F accuse published on

00:06:07.180 --> 00:06:10.060
the P CSS See website about vulnerability scans.

00:06:10.440 --> 00:06:12.570
These are some of the most useful ones for you.

00:06:12.990 --> 00:06:18.440
Fake 108 7 helpfully say, is what a quarter is so like.

00:06:18.450 --> 00:06:21.770
It says it's every three months or 90 days you can take your pick.

00:06:22.330 --> 00:06:22.820
Fake.

00:06:22.830 --> 00:06:27.360
1152 is really useful for complex, changing environment,

00:06:27.490 --> 00:06:30.710
where the organization could never get a clean passing scan

00:06:30.800 --> 00:06:33.070
because as soon as it fixes one vulnerability,

00:06:33.210 --> 00:06:35.170
another one is introduced and found.

00:06:35.640 --> 00:06:39.230
The states that as long as there's evidence showing that vulnerabilities

00:06:39.230 --> 00:06:43.520
error identified via scans on fixed and then re scans conducted showing

00:06:43.520 --> 00:06:47.130
the previous vulnerabilities were fixed on that we get services scans

00:06:47.290 --> 00:06:48.970
demonstrating this over each quarter.

00:06:49.050 --> 00:06:49.690
That's fine.

00:06:49.690 --> 00:06:55.310
That will pass on F A Q 1317 goes into more detail about how to

00:06:55.310 --> 00:06:59.160
determine in your organization what a significant changes
