WEBVTT

00:00:01.040 --> 00:00:02.540
For many people on IT,

00:00:02.550 --> 00:00:07.060
the movement towards the cloud is done a little bit apprehensively,

00:00:07.440 --> 00:00:12.130
especially for people in security who realize that going to the cloud,

00:00:12.130 --> 00:00:18.010
maybe we lose a bit of control over our direct security implementations.

00:00:18.740 --> 00:00:20.970
I do say sometimes, though,

00:00:20.970 --> 00:00:25.790
that organizations very often do securely poorly on their own,

00:00:26.060 --> 00:00:26.890
and therefore,

00:00:26.890 --> 00:00:29.990
going to the cloud may actually be more secure than

00:00:29.990 --> 00:00:31.660
what they've been doing until now.

00:00:32.140 --> 00:00:35.920
However, if I don't do things well on my own,

00:00:36.090 --> 00:00:39.720
there is a very good chance I won't do it very well when it depends on

00:00:39.720 --> 00:00:42.960
a relationship with another organization as well.

00:00:43.540 --> 00:00:46.090
So those are the things that we have to consider,

00:00:46.540 --> 00:00:51.400
but an organization is going to go to the cloud whether or not we,

00:00:51.400 --> 00:00:53.560
as security professionals, want it.

00:00:54.220 --> 00:00:57.650
Therefore, we have to have ways to make it secure.

00:00:58.040 --> 00:01:02.360
We have to understand what are the risks associated with the cloud.

00:01:02.740 --> 00:01:07.360
So why would an organization choose to go to cloud computing?

00:01:08.040 --> 00:01:08.410
Well,

00:01:08.410 --> 00:01:10.790
beyond the fact that maybe the cloud service

00:01:10.790 --> 00:01:13.160
providers have very good sales people,

00:01:13.640 --> 00:01:17.720
there are a number of other convincing arguments that can be made,

00:01:18.130 --> 00:01:22.460
such as capital cost control, the flexibility,

00:01:22.840 --> 00:01:27.250
access to skilled staff, and even environmental impact.

00:01:28.640 --> 00:01:32.000
If 15 companies move to cloud provider,

00:01:32.260 --> 00:01:36.300
that means that 15 companies can get rid of backup diesels,

00:01:36.300 --> 00:01:41.360
and batteries, and spare equipment, and so therefore,

00:01:41.940 --> 00:01:46.860
there can be quite an advantage, even environmentally as well.

00:01:47.940 --> 00:01:49.330
So the question comes,

00:01:49.560 --> 00:01:55.550
is the cloud secure or is the cloud more secure than what I have now?

00:01:56.140 --> 00:01:58.930
It's not an easy question because, of course,

00:01:58.930 --> 00:02:02.260
there is a wide variety of different cloud providers,

00:02:02.840 --> 00:02:04.160
and so therefore,

00:02:04.160 --> 00:02:08.080
we'd have to come back with that answer that means nothing saying,

00:02:08.090 --> 00:02:09.560
well, it depends.

00:02:10.240 --> 00:02:13.280
It depends on the maturity of the organization,

00:02:13.280 --> 00:02:18.570
both of the cloud consumer and of the cloud service provider.

00:02:19.440 --> 00:02:21.750
And it also depends on what I'm paying for,

00:02:22.240 --> 00:02:27.210
what services are stipulated in the contract because you can be fairly

00:02:27.210 --> 00:02:31.500
certain that if I have not put things into the contract,

00:02:31.510 --> 00:02:34.150
they won't end up being provided either.

00:02:36.100 --> 00:02:39.910
We also have to understand the legal and regulatory

00:02:39.910 --> 00:02:42.960
constraints and requirements of going to the cloud.

00:02:43.640 --> 00:02:48.040
Many organizations have even adopted cloud‑first strategy.

00:02:48.220 --> 00:02:52.550
We're going to go to the cloud unless there is a convincing reason not to.

00:02:53.040 --> 00:02:58.710
And that has been, in some cases, very good for governments and organizations,

00:02:59.200 --> 00:03:02.890
but we do have to consider things like legal jurisdiction.

00:03:03.640 --> 00:03:05.380
Where is my data stored?

00:03:05.550 --> 00:03:07.010
Where is it processed?

00:03:07.160 --> 00:03:09.160
Is it secure, for example.

00:03:09.740 --> 00:03:15.210
We need to understand that when we go to the cloud as a cloud consumer,

00:03:15.220 --> 00:03:19.340
it's not that I get rid of my security responsibilities.

00:03:19.670 --> 00:03:20.250
No,

00:03:20.260 --> 00:03:25.530
I have to make sure that I'm still executing due diligence to protect

00:03:25.530 --> 00:03:29.660
my data even though it's on somebody else's systems.

00:03:31.340 --> 00:03:33.580
We also have to look at the business case.

00:03:33.860 --> 00:03:37.010
Not all businesses are suited for the cloud.

00:03:37.540 --> 00:03:38.350
For example,

00:03:38.350 --> 00:03:41.780
you take something which is real time sensors that require

00:03:41.780 --> 00:03:45.750
immediate reaction in case of say a safety issue.

00:03:46.150 --> 00:03:52.050
It could be the latency or delay of going to a cloud or the unreliability

00:03:52.050 --> 00:03:55.700
of a network could mean a life threatening situation.

00:03:56.140 --> 00:03:56.950
So therefore,

00:03:56.950 --> 00:04:02.260
some services just don't really lend themselves to a cloud type of environment.

00:04:02.940 --> 00:04:06.870
We also know that a person who works for a cloud service

00:04:06.870 --> 00:04:10.560
provider very often will have access to my data.

00:04:11.040 --> 00:04:15.860
If my data is highly sensitive, maybe that could be a problem.

00:04:16.240 --> 00:04:21.459
Maybe that data could be leaked either intentionally or accidentally.

00:04:21.940 --> 00:04:24.510
So these are things we're going to look at in more detail

00:04:24.510 --> 00:04:26.950
as we get into this course as well.

00:04:28.040 --> 00:04:32.310
The idea of migrating to the cloud and moving to a cloud type of

00:04:32.310 --> 00:04:36.460
environment requires us to consider some important factors.

00:04:36.840 --> 00:04:38.660
What type of business we are,

00:04:39.240 --> 00:04:42.990
what are the legal requirements such as reliability,

00:04:42.990 --> 00:04:46.350
we could call that up time, as well as reporting.

00:04:46.740 --> 00:04:49.400
Will I be able to report if there is any problem,

00:04:49.410 --> 00:04:53.370
issue, what is my level of insight into the cloud,

00:04:53.370 --> 00:04:57.760
as well as there are many different cloud options available.

00:04:58.140 --> 00:04:59.660
Which is the best for me?

00:05:00.140 --> 00:05:04.360
Go with one of the big companies or maybe go with a small boutique

00:05:04.360 --> 00:05:08.890
firm that maybe can provide better customization and maybe even a

00:05:08.890 --> 00:05:10.960
better price than the large guys.

00:05:11.740 --> 00:05:15.640
We have to look at what type of delivery model works for us,

00:05:15.640 --> 00:05:16.960
and that, of course,

00:05:16.960 --> 00:05:19.910
could look at from anything on‑site private to

00:05:19.910 --> 00:05:22.910
offsite private to community cloud.

00:05:23.180 --> 00:05:25.760
There are many different options, of course,

00:05:25.770 --> 00:05:29.150
even from a Software to Platform as a Service.

00:05:30.140 --> 00:05:34.650
Very often, one of the considerations for going to the cloud was economic.

00:05:34.790 --> 00:05:35.940
You'll save money.

00:05:36.160 --> 00:05:38.590
Well, that's not always the case.

00:05:38.840 --> 00:05:43.080
It could well be that I can change the way I pay,

00:05:43.280 --> 00:05:44.540
but in many cases,

00:05:44.540 --> 00:05:48.420
we find that companies thought that they would save money by going to the cloud,

00:05:48.540 --> 00:05:51.090
and in the end, found out they didn't really,

00:05:51.640 --> 00:05:55.150
but there are some very good advantages to the cloud.

00:05:57.840 --> 00:05:59.690
When I need to understand the business,

00:05:59.690 --> 00:06:02.150
I have to understand what type of business am I in,

00:06:02.150 --> 00:06:07.860
a competitive, a am I a service‑oriented organization,

00:06:08.240 --> 00:06:10.710
and of course, where do I do business,

00:06:10.720 --> 00:06:14.750
just locally or do I do it nationally or even internationally?

00:06:15.140 --> 00:06:18.160
That can very much affect cloud service as well.

00:06:18.540 --> 00:06:21.810
Who are my customers and what are the expectations of my

00:06:21.810 --> 00:06:25.050
customers for protecting their data?

00:06:25.740 --> 00:06:28.730
We also have to look at network requirements.

00:06:29.240 --> 00:06:33.550
Do I have a network capacity that will support my

00:06:33.550 --> 00:06:36.200
business in real‑time operations,

00:06:36.210 --> 00:06:41.920
or will maybe there be latency or unreliability there with networks?

00:06:42.740 --> 00:06:47.660
We have to look at how much data storage and processing do we need.

00:06:48.240 --> 00:06:48.950
Very often,

00:06:48.950 --> 00:06:54.830
the cloud works well when my level of data storage or processing can vary

00:06:55.050 --> 00:06:58.360
because I can change the number of services available,

00:06:58.550 --> 00:07:01.760
but that also comes at a price as well.
