WEBVTT

00:00:01.603 --> 00:00:04.076
Requirement 6.2 follows on from vulnerability management

00:00:04.076 --> 00:00:06.448
and requires that you should patch vulnerabilities once

00:00:06.448 --> 00:00:08.967
the vendor releases a patch.

00:00:08.967 --> 00:00:13.436
The requirement is simple, that vendor-supplied patches need to be installed,

00:00:13.436 --> 00:00:17.326
period, and when the patch fixes a critical vulnerability,

00:00:17.326 --> 00:00:21.903
it should be installed within a month, and remember,

00:00:21.903 --> 00:00:23.561
this is your definition of the critical vulnerability; we

00:00:23.561 --> 00:00:27.018
should also include the environmental score relating to the

00:00:27.018 --> 00:00:30.411
criticality or importance of the assets.

00:00:30.411 --> 00:00:30.812
Now,

00:00:30.812 --> 00:00:34.211
although the standard says you should patch critical

00:00:34.211 --> 00:00:38.082
vulnerabilities within 30 days, please don't wait this long.

00:00:38.082 --> 00:00:43.572
My advice is that you patch critical vulnerabilities much sooner than this.

00:00:43.572 --> 00:00:45.691
The QSA is going to look at your policies,

00:00:45.691 --> 00:00:49.237
but also check actual systems to validate the patches that your policy

00:00:49.237 --> 00:00:53.873
says should have been applied have actually been applied.

00:00:53.873 --> 00:00:54.008
Typically,

00:00:54.008 --> 00:00:56.639
the QSA is going to look at systems that can show records of

00:00:56.639 --> 00:00:59.334
you making the risk assessment and then look through

00:00:59.334 --> 00:01:02.581
historical change control records.

00:01:02.581 --> 00:01:02.960
So look,

00:01:02.960 --> 00:01:04.678
if you've got a centralized system that pushes

00:01:04.678 --> 00:01:09.697
patches out to systems in the CDE, which I guess most people do nowadays,

00:01:09.697 --> 00:01:13.740
the QSA is going to look at that patch management and patch pushing system.

00:01:13.740 --> 00:01:17.299
Now we're going to join the discussion between Jacob and me where

00:01:17.299 --> 00:01:19.649
we discuss some of the typical problems in vulnerability

00:01:19.649 --> 00:01:23.625
management and to what extent it affected the breaches of

00:01:23.625 --> 00:01:26.486
cardholder data that we've both seen.
