WEBVTT

00:00:01.040 --> 00:00:05.270
[Autogenerated] requirement, 10.8 only applies to service providers.

00:00:05.740 --> 00:00:07.590
Now, if you're not a service provider,

00:00:07.590 --> 00:00:10.090
I'd like you to work through this requirement with me anyway,

00:00:10.180 --> 00:00:12.280
because it's a really important requirement.

00:00:12.530 --> 00:00:15.980
And requirements like this that are just aimed at service.

00:00:15.980 --> 00:00:19.600
Providers often appear in the next version of standards as

00:00:19.600 --> 00:00:23.510
mandatory for all organizations on the requirements.

00:00:23.510 --> 00:00:26.870
Concerned with the availability of security systems,

00:00:27.740 --> 00:00:31.190
it wants the organization to put in place systems or

00:00:31.190 --> 00:00:34.760
processes to detect when systems or services providing

00:00:34.760 --> 00:00:36.770
security functions error not working.

00:00:37.340 --> 00:00:40.010
The types of services concerned with a listed here,

00:00:40.200 --> 00:00:43.110
and these include most of the core technical security functions

00:00:43.110 --> 00:00:46.240
organizational have now this list is no exclusive,

00:00:46.240 --> 00:00:49.330
so your risk assessment should document what systems error

00:00:49.330 --> 00:00:51.050
going to be in scope of this requirement.

00:00:51.840 --> 00:00:56.490
Now, in my time, I've seen lots of forensic reports written after a data breach,

00:00:56.690 --> 00:00:59.870
and there's often a very common theme that the merchant or

00:00:59.870 --> 00:01:03.190
service provider had the technical control in place that would

00:01:03.190 --> 00:01:05.550
have defeated or detected the attacker.

00:01:05.630 --> 00:01:08.160
But it wasn't working properly or it was turned off.

00:01:08.340 --> 00:01:11.160
So this is a really sensible and important requirement,

00:01:11.160 --> 00:01:12.750
and even if you're not a service provider.

00:01:12.840 --> 00:01:17.280
I'd recommend that you do this to test it is in place.

00:01:17.390 --> 00:01:20.900
The QoS is going to first look for policies and procedures to

00:01:20.900 --> 00:01:24.540
understand how the failure or non functioning of a critical

00:01:24.540 --> 00:01:26.470
security system will be detected.

00:01:26.990 --> 00:01:30.200
And they'll also interview people to make sure those alerts error generated.

00:01:30.740 --> 00:01:32.270
And if I was the QC,

00:01:32.570 --> 00:01:35.570
I'd look for some historical evidence from the incident logs

00:01:35.740 --> 00:01:37.800
to make sure that this really happened so I'd look to see

00:01:37.800 --> 00:01:39.510
something stopped writing logs.

00:01:39.510 --> 00:01:42.070
It's a really good indication it's not functioning and then see

00:01:42.070 --> 00:01:43.970
if this policy and procedures were followed.

00:01:45.340 --> 00:01:49.060
The next requirement is also just for service provided,

00:01:49.540 --> 00:01:52.980
and it's concerned with what happens when the failure of a

00:01:52.980 --> 00:01:55.870
critical security system or control is detected.

00:01:56.540 --> 00:02:02.360
The requirement is that the organization follows a formal response process.

00:02:03.140 --> 00:02:04.680
Now, Wow,

00:02:04.690 --> 00:02:09.770
the standard is pretty detailed about what that response process includes and

00:02:09.770 --> 00:02:15.110
describes seven activities that must be followed firstly on.

00:02:15.110 --> 00:02:16.670
Perhaps unsurprisingly,

00:02:16.670 --> 00:02:20.310
the security function that failed needs to be made to work again,

00:02:20.320 --> 00:02:21.740
and that's the first in the listen.

00:02:21.880 --> 00:02:24.120
That's the first thing you should do next.

00:02:24.220 --> 00:02:26.280
The organization should make sure it records when the

00:02:26.280 --> 00:02:28.550
system failed when it was restored,

00:02:28.630 --> 00:02:31.510
which would be useful in any future forensic investigation.

00:02:31.510 --> 00:02:35.080
So you know that something you thought was there wasn't there on

00:02:35.080 --> 00:02:37.050
you could see even attacker took advantage of it.

00:02:37.840 --> 00:02:40.090
Thirdly, a root cause or,

00:02:40.090 --> 00:02:43.630
as I prefer to call them now contributing factor analysis must be

00:02:43.630 --> 00:02:47.260
performed so the organization can do understand what happened and take

00:02:47.260 --> 00:02:49.830
the necessary steps to prevent a re occurrence,

00:02:51.040 --> 00:02:54.160
and that will then feed into the fourth process that's required

00:02:54.160 --> 00:02:56.280
after a failure of a critical security system,

00:02:56.440 --> 00:02:59.610
which is to implement the recommendations that root cause or

00:02:59.610 --> 00:03:03.020
contributory factors analysis and implement technical or process

00:03:03.020 --> 00:03:05.860
controls to prevent the failure from happening again.

00:03:06.540 --> 00:03:09.600
The fifth thing that's required is to make sure you take a careful

00:03:09.600 --> 00:03:12.490
look at your logs and any instance raised during the time period the

00:03:12.490 --> 00:03:14.870
system had failed and investigate them.

00:03:14.930 --> 00:03:15.590
Remember,

00:03:15.600 --> 00:03:18.090
somebody else might have noticed one of your lives of

00:03:18.090 --> 00:03:21.950
protection have failed before you did next.

00:03:21.950 --> 00:03:25.510
The six thing is to formally Macon document a risk assessment to

00:03:25.510 --> 00:03:28.210
understand the risks while the system was down,

00:03:28.400 --> 00:03:32.450
and to make sure that the root cause analysis feeds into this risk assessment.

00:03:32.520 --> 00:03:35.150
So it's a forward looking risk assessment you would ask yourself.

00:03:35.280 --> 00:03:37.000
But what happens if this happens again?

00:03:37.000 --> 00:03:37.700
One of the risk?

00:03:37.760 --> 00:03:39.170
What do we need to do about it?

00:03:39.640 --> 00:03:40.420
And then, finally,

00:03:40.420 --> 00:03:43.250
to make sure that the monitoring of the system is also operational

00:03:43.250 --> 00:03:47.050
working properly so you'd notice if it went down again.

00:03:47.740 --> 00:03:49.520
To test this requirements in place,

00:03:49.520 --> 00:03:52.050
the QoS is going to check the written procedures and

00:03:52.050 --> 00:03:54.360
interview people to make sure they know what to do when a

00:03:54.360 --> 00:03:56.440
critical security system fails,

00:03:56.650 --> 00:04:00.280
The QoS is also going to look for evidence to see the processes were followed.

00:04:00.350 --> 00:04:04.660
So if there was a failure of the QoS Estelle from the testing procedure in 10.8,

00:04:04.790 --> 00:04:08.660
they look for the documentation you're supposed to have is 10.8 point one,

00:04:08.740 --> 00:04:10.200
such as the root cause analysis,

00:04:10.200 --> 00:04:14.650
the risk assessment and evidence that you went back and looked through the logs
