WEBVTT

00:00:00.840 --> 00:00:05.000
When we take a look at some of the principles of secure cloud computing,

00:00:05.310 --> 00:00:09.990
we need to recognize what are the threats that we are trying to address.

00:00:10.450 --> 00:00:15.260
Some of the common cloud threats include attacks and failures that

00:00:15.260 --> 00:00:19.560
could happen at any of those layers of, then the system stack

00:00:19.940 --> 00:00:22.360
anywhere from, of course, the user layer,

00:00:22.360 --> 00:00:26.130
which is where we often say many of the problems lie,

00:00:26.130 --> 00:00:28.790
but then at the application layer,

00:00:29.030 --> 00:00:33.630
through the application program interfaces, at the database layer,

00:00:33.850 --> 00:00:37.350
of course, at the network itself, the operating system,

00:00:37.360 --> 00:00:38.740
the hypervisors,

00:00:38.800 --> 00:00:43.150
the hardware, and even, of course, the building or facility itself.

00:00:43.940 --> 00:00:47.770
All of these layers have their own vulnerabilities

00:00:47.780 --> 00:00:51.050
and potential vectors of an attack.

00:00:51.840 --> 00:00:55.280
We also mentioned earlier the problem with administrators,

00:00:55.290 --> 00:00:58.170
those who have access to all of these layers.

00:00:58.170 --> 00:01:02.820
Whether it's a database administrator, a network administrator,

00:01:02.920 --> 00:01:07.110
we know that that could be, of course, a method of a

00:01:07.110 --> 00:01:09.860
person being able to compromise the system.

00:01:11.340 --> 00:01:15.920
So now we have to look at what is adequate security.

00:01:15.930 --> 00:01:20.260
The problem with the term like adequate is that it's a word that can mean

00:01:20.270 --> 00:01:26.900
anything. When is enough enough? Maybe for one person, adequate was a very low

00:01:26.900 --> 00:01:31.950
level of security, whereas somebody else really thinks that security should be

00:01:31.950 --> 00:01:34.360
at the ultimate and lock everything down.

00:01:35.040 --> 00:01:35.820
But we,

00:01:35.830 --> 00:01:41.010
as cloud security professionals, have to understand how to be able

00:01:41.010 --> 00:01:45.500
to put together a good security program, one,

00:01:45.500 --> 00:01:50.850
which is based on risk like the common threats we just looked at, one,

00:01:50.850 --> 00:01:56.750
which is able to look at what options are currently available. And the reason

00:01:56.750 --> 00:02:02.450
I stress this is because there's been many cases in the past where a very good

00:02:02.550 --> 00:02:08.360
type of risk mitigation option was chosen. It was the chosen of the best

00:02:08.360 --> 00:02:11.610
available then, but things have changed.

00:02:11.760 --> 00:02:13.860
There are better solutions today.

00:02:14.340 --> 00:02:16.730
So as security professionals,

00:02:16.740 --> 00:02:22.330
it's always good to take a look at what options are available, go back

00:02:22.330 --> 00:02:28.140
to our risk register and say are today's solutions and risk

00:02:28.140 --> 00:02:33.750
mitigations adequate according to what we could do today? Maybe we

00:02:33.750 --> 00:02:36.660
need to repeat the risk management effort.

00:02:37.520 --> 00:02:41.670
We also have to look at what we are required to meet by regulations.

00:02:41.970 --> 00:02:46.090
Many of us work in sectors that are heavily regulated.

00:02:46.290 --> 00:02:50.830
We even have a legal requirement to have a certain level of uptime

00:02:50.830 --> 00:02:55.040
of our systems. We have regulations about the privacy of our

00:02:55.040 --> 00:02:59.490
systems, and all of these must be considered when we're putting

00:02:59.490 --> 00:03:02.860
together an adequate security solution.

00:03:03.640 --> 00:03:08.240
We also have to remember that the purpose of our IT systems,

00:03:08.320 --> 00:03:12.360
whether they are cloud‑based or not, is to support business.

00:03:12.740 --> 00:03:17.090
We can't come out with a solution that would mean the business can't operate.

00:03:17.640 --> 00:03:23.080
And so we have to be considerate of business goals and mission. In all of this,

00:03:23.080 --> 00:03:26.710
we come back to the title of the slide, Cost/Benefit

00:03:26.710 --> 00:03:32.530
Analysis. Cost/benefit analysis says I should never pay more

00:03:32.530 --> 00:03:35.050
to protect something than it's worth.

00:03:35.740 --> 00:03:37.170
So therefore,

00:03:37.300 --> 00:03:42.330
knowing what the level of risk is helps us to justify the

00:03:42.330 --> 00:03:47.400
cost we would incur in order to reduce that risk to an

00:03:47.410 --> 00:03:49.450
adequate or acceptable level.

00:03:51.140 --> 00:03:53.840
When we look at security controls in the cloud,

00:03:54.140 --> 00:03:58.570
the first and very important thing to remember always is that

00:03:58.570 --> 00:04:02.980
the first level of security in the cloud comes from contracts.

00:04:02.980 --> 00:04:07.500
Having things in service agreements, maintenance agreements,

00:04:07.500 --> 00:04:12.270
and contracts that we could say, well, that's kind of a soft thing,

00:04:12.280 --> 00:04:18.420
but that is the first and most important because that justifies and mandates

00:04:18.420 --> 00:04:22.460
what security will actually be built into our solution.

00:04:23.140 --> 00:04:27.060
We also have to look at who would be liable if there was a problem.

00:04:27.540 --> 00:04:32.850
And, of course, linked to that is what is the extent of that liability?

00:04:33.340 --> 00:04:36.460
It's the sort of case where very often we see this with the

00:04:36.460 --> 00:04:39.940
hardware is that they say if it breaks, we'll replace it.

00:04:40.130 --> 00:04:40.660
Yeah,

00:04:40.660 --> 00:04:44.610
but when it broke, that cost us maybe a million dollars in

00:04:44.610 --> 00:04:47.010
lost business. They don't cover that.

00:04:47.020 --> 00:04:48.810
That's not part of their liability.

00:04:49.180 --> 00:04:52.810
Their liability is only the few hundred dollars of the

00:04:52.810 --> 00:04:55.060
actual cost of that piece of hardware.

00:04:56.040 --> 00:04:59.120
We also have to remember that a lot of this comes down

00:04:59.120 --> 00:05:02.770
to ownership of risk. In the end,

00:05:02.960 --> 00:05:07.980
most of the risk is owned by the cloud consumer. It's their

00:05:07.980 --> 00:05:12.660
business. And the cloud service provider certainly has some

00:05:12.660 --> 00:05:16.760
risk to their reputation, financial risk, and so on.

00:05:17.140 --> 00:05:20.230
But when there's something that goes wrong,

00:05:20.240 --> 00:05:24.060
for example, with a company that is heavily regulated,

00:05:24.540 --> 00:05:27.160
it's not that they can turn around and say it's the

00:05:27.160 --> 00:05:29.130
fault of the cloud service provider,

00:05:29.440 --> 00:05:36.400
even if it was. The point is that the risk remains with that

00:05:36.410 --> 00:05:40.980
company that chose to outsource a certain service.

00:05:41.740 --> 00:05:45.130
One of the things we need to do, and we'll look at this especially in the next

00:05:45.130 --> 00:05:50.170
module when we look at evaluating cloud service providers, is to have some

00:05:50.170 --> 00:05:55.810
method that we can measure compliance, whether or not it's the right to audit,

00:05:55.820 --> 00:05:58.510
whether or not it's the regular reviews,

00:05:58.520 --> 00:06:04.720
even by a third party to make sure that the cloud service provider is living

00:06:04.720 --> 00:06:09.010
up to the terms of those contracts and service agreements.

00:06:10.640 --> 00:06:15.960
An important part of all this is to keep our systems secure, and this can

00:06:15.960 --> 00:06:19.560
become a little bit of a challenge when we're dealing with things like

00:06:19.570 --> 00:06:25.160
patching because we know that patching is something that is being done

00:06:25.170 --> 00:06:28.260
usually because there's a known vulnerability.

00:06:28.740 --> 00:06:31.860
But how do I know that, for example,

00:06:32.340 --> 00:06:37.180
the patches are being applied? And we want to have a process

00:06:37.180 --> 00:06:39.360
in place to make sure that's being done.

00:06:40.140 --> 00:06:45.950
The thing is that we have a baseline. Here is our security baseline. Here

00:06:45.950 --> 00:06:50.060
is the desired configuration of all of our systems.

00:06:50.440 --> 00:06:52.920
Now I said desired, though, in many cases,

00:06:52.920 --> 00:06:53.360
of course,

00:06:53.360 --> 00:06:59.140
truly a baseline should be required settings and configuration, and it

00:06:59.140 --> 00:07:02.900
could be based on some of those principles that we've discussed such as a

00:07:02.910 --> 00:07:09.930
zero‑trust type of relationship and the requirement that all systems,

00:07:10.000 --> 00:07:12.240
including even our virtual machines,

00:07:12.250 --> 00:07:18.380
are then patched on a regular basis or quickly after the patches are available.
