WEBVTT

00:00:01.140 --> 00:00:03.750
Now that we know our threat,

00:00:03.760 --> 00:00:07.550
we now need to think about how we would treat the

00:00:07.550 --> 00:00:10.070
risk with that specific threat.

00:00:10.080 --> 00:00:16.960
ISO 27005: Information Security Risk management has 4 possibilities

00:00:16.960 --> 00:00:20.690
when we think about responses to risk treatment.

00:00:20.700 --> 00:00:23.580
There is something in the updated language called

00:00:23.580 --> 00:00:26.200
modification which used to be mitigation,

00:00:26.200 --> 00:00:31.320
which I do like the update because a mitigation is an assumption.

00:00:31.330 --> 00:00:33.120
A modification is a fact.

00:00:33.130 --> 00:00:35.300
You changed the environment,

00:00:35.310 --> 00:00:39.040
but you don't know that you actually mitigated it so it's a nice update.

00:00:39.050 --> 00:00:43.890
Retention has replaced this idea of acceptance because when you really think

00:00:43.890 --> 00:00:47.600
about it, is an organization really accepting the risk.

00:00:47.610 --> 00:00:52.050
No, they're just retaining the system in the same way that it was before.

00:00:52.140 --> 00:00:58.770
Avoidance is a really good terminology because that one didn't change much,

00:00:58.780 --> 00:01:02.770
except they change that you could avoid the specific thing that is

00:01:02.770 --> 00:01:07.560
causing the risk rather than avoiding the whole ecosystem.

00:01:07.570 --> 00:01:12.810
And sharing is a really great update as well because it's

00:01:12.810 --> 00:01:15.370
really not transferring the risk fully.

00:01:15.380 --> 00:01:19.660
So modification is a course of action that would implement

00:01:19.660 --> 00:01:22.900
the controls that are both technical, environmental,

00:01:22.910 --> 00:01:24.110
or cultural.

00:01:24.120 --> 00:01:27.890
Can you go back to the data center that we said is

00:01:27.890 --> 00:01:29.780
threatened by flooding in the previous clip?

00:01:29.790 --> 00:01:32.460
What might be a modification step to take?

00:01:32.940 --> 00:01:38.160
Yes, you could move the servers up to the fifth floor away from the flood zone.

00:01:38.170 --> 00:01:43.470
You should make sure that you don't exceed this thing called the ALE,

00:01:43.470 --> 00:01:49.160
the annual loss expectancy, without some real business justification.

00:01:51.440 --> 00:01:55.940
Retention means retaining the risk without further action.

00:01:55.950 --> 00:01:59.650
In our previous case with the threat of the data center flooding,

00:01:59.660 --> 00:02:04.680
we decide that we are going to do nothing, but business as usual.

00:02:04.690 --> 00:02:10.520
So we're not taking any extraordinary precaution or steps,

00:02:10.530 --> 00:02:15.460
and we need to make sure that there is formal acceptance by the business.

00:02:16.440 --> 00:02:17.520
When we think of avoidance,

00:02:17.530 --> 00:02:20.900
it's avoiding the activity or condition that precipitates the risk.

00:02:20.910 --> 00:02:26.830
Avoid might be that we don't do business related to needing that data center,

00:02:26.840 --> 00:02:30.660
but the new definition includes avoiding the specific threat.

00:02:31.240 --> 00:02:36.560
And finally, when we think of sharing, the risk is shared with another party.

00:02:36.570 --> 00:02:40.150
So this could be contractual, it could be subcontractual,

00:02:40.160 --> 00:02:43.270
it could also be insurance of some type,

00:02:43.280 --> 00:02:46.220
and we said that this was formally called transfer,

00:02:46.220 --> 00:02:51.760
but this like the update of the other three terms makes more sense as we are

00:02:51.770 --> 00:02:55.660
actually never going to transfer things like accountability,

00:02:55.940 --> 00:03:00.140
and even responsibility cannot be fully transferred,

00:03:00.150 --> 00:03:02.120
but we are sharing,

00:03:02.130 --> 00:03:06.580
and the line or the watermark of the sharing could vary depending on the

00:03:06.580 --> 00:03:09.220
type of service that you're consuming in the cloud.

00:03:09.940 --> 00:03:13.690
Finally, let's look at applying the risk process.

00:03:13.700 --> 00:03:15.660
If we were to put it in motion,

00:03:15.670 --> 00:03:18.760
what are the activities that we should be thinking about?
