WEBVTT

00:00:01.040 --> 00:00:02.300
[Autogenerated] now closely aligned with the

00:00:02.300 --> 00:00:04.670
requirement to update the policy annually.

00:00:04.910 --> 00:00:09.670
And one of the factors that may lead to a policy update is PC IEDs

00:00:09.670 --> 00:00:12.560
requirement to conduct an annual risk assessment.

00:00:13.340 --> 00:00:17.810
Now I've heard people argue that this is a useless requirement

00:00:17.870 --> 00:00:20.330
because in developing the PC IDE Assess,

00:00:20.570 --> 00:00:25.280
the P CSS C has done the risk assessment for you and worked out all the

00:00:25.280 --> 00:00:27.650
threats and therefore the controls that required.

00:00:28.640 --> 00:00:30.560
I'm afraid that's simply not the case,

00:00:30.940 --> 00:00:33.970
because the DSS is a baseline security standards.

00:00:34.440 --> 00:00:37.260
There are millions of companies all around the world that process

00:00:37.260 --> 00:00:41.900
payment cards right from single site small e commerce merchants to the

00:00:41.900 --> 00:00:45.150
world's largest airlines on supermarkets.

00:00:45.640 --> 00:00:47.830
Onder standards also fairly static,

00:00:47.840 --> 00:00:50.510
so it doesn't change as quickly as people invent new

00:00:50.510 --> 00:00:52.070
US of processing payment cards.

00:00:52.250 --> 00:00:55.360
So you have to do an annual risk assessment,

00:00:56.240 --> 00:00:59.140
a great example of why we need annual risk assessments and

00:00:59.140 --> 00:01:03.650
how the way we change with way we process payment cars mean

00:01:03.650 --> 00:01:05.250
we need to do risk assessments.

00:01:05.360 --> 00:01:07.660
Is that JavaScript key logger attack?

00:01:07.750 --> 00:01:10.970
I discuss with Troy Hunts in a Pluralsight play by play

00:01:11.230 --> 00:01:14.580
that new way that e commerce merchants accept payment cars

00:01:14.590 --> 00:01:16.070
has its own vulnerabilities,

00:01:16.240 --> 00:01:19.450
which a risk assessment would have identified and then found some

00:01:19.450 --> 00:01:21.460
new controls that should have been applied.

00:01:22.040 --> 00:01:24.920
So every organization needs to look at how it works.

00:01:24.920 --> 00:01:26.310
With payment card data,

00:01:26.470 --> 00:01:29.730
y excess will be attractive to Attackers and understand how

00:01:29.730 --> 00:01:31.970
they're going to defend and protect those assets.

00:01:32.340 --> 00:01:36.400
The requirement is that the risk assessment is done each year and

00:01:36.400 --> 00:01:38.930
also after significant change in your environment.

00:01:39.160 --> 00:01:41.820
Whatever risk assessment methodologies used,

00:01:42.000 --> 00:01:45.450
it must include the core components of asset identification,

00:01:45.670 --> 00:01:49.210
threat, identification, vulnerability, analysis and,

00:01:49.450 --> 00:01:53.460
most importantly, but the risk assessment has to be documented.

00:01:54.440 --> 00:01:57.410
The QoS is going to review the risk assessment and check that

00:01:57.410 --> 00:01:59.360
it was completed within the past 12 months.

00:01:59.740 --> 00:02:04.730
A good QoS A would also look to see if the policy required in 12.1

00:02:04.740 --> 00:02:07.570
had been amended as a result of the risk assessment
