WEBVTT

00:00:01.040 --> 00:00:03.950
Let's start looking at various cloud deployment models

00:00:03.950 --> 00:00:07.060
from a very high overview perspective.

00:00:08.140 --> 00:00:11.930
NIST defines the cloud deployment models as composed

00:00:11.930 --> 00:00:16.120
of five essential characteristics, three service models,

00:00:16.129 --> 00:00:22.260
and four deployment models in the special publication 800‑145.

00:00:23.240 --> 00:00:26.770
Those five essential characteristics of the cloud

00:00:26.770 --> 00:00:31.450
include on‑demand self‑service, broad network access,

00:00:31.680 --> 00:00:37.060
resource pooling, rapid elasticity, and measured service.

00:00:38.340 --> 00:00:39.100
However,

00:00:39.110 --> 00:00:43.630
even NIST admits that many cloud deployments do not have all

00:00:43.630 --> 00:00:47.130
of these five essential characteristics,

00:00:47.540 --> 00:00:50.620
but this is what makes the cloud so flexible,

00:00:50.620 --> 00:00:54.050
usable, and practical for many organizations.

00:00:54.840 --> 00:00:58.360
You can expand and retract some of the resources

00:00:58.360 --> 00:01:01.380
you use as a self‑service option.

00:01:01.550 --> 00:01:03.620
You only pay for what you use.

00:01:03.700 --> 00:01:08.610
You have access to a pool of resources, rather than having to buy it yourself,

00:01:08.610 --> 00:01:09.500
for example.

00:01:10.840 --> 00:01:15.960
If we look at an overview, for example, of a public cloud implementation,

00:01:16.160 --> 00:01:19.130
we see a number of different elements to this.

00:01:19.300 --> 00:01:22.550
We see the cloud provider in the center with all of their

00:01:22.550 --> 00:01:25.370
various types of equipment that are available,

00:01:25.380 --> 00:01:29.650
servers, for example, for both compute and storage needs,

00:01:30.040 --> 00:01:33.280
and they are continuously improving those,

00:01:33.280 --> 00:01:40.450
replacing them, but it operates as a single unit to the cloud consumer.

00:01:40.940 --> 00:01:46.550
You have clients that initiate access wanting to subscribe to a cloud service.

00:01:47.140 --> 00:01:51.470
You then have all of those computers that are providing

00:01:51.470 --> 00:01:57.870
service through some type of a network, public clients accessing the cloud,

00:01:58.040 --> 00:02:03.230
and of course, new hardware going in and old hardware coming out.

00:02:03.230 --> 00:02:08.750
Then you have, of course, clients terminating access, leaving the cloud as well.

00:02:09.539 --> 00:02:13.600
If we went back to a traditional type of operation,

00:02:13.810 --> 00:02:17.970
we had then a consumers facility with their users and quite

00:02:17.970 --> 00:02:20.140
often they would have their own equipment,

00:02:20.350 --> 00:02:21.450
but now,

00:02:22.350 --> 00:02:27.500
they are able to subscribe to a cloud‑based service and not necessarily

00:02:27.500 --> 00:02:32.260
have to have that equipment on their own site or location.

00:02:33.040 --> 00:02:38.260
They have, of course, the need to provide proper security and isolation,

00:02:38.640 --> 00:02:42.610
and this is where very often we put up that security perimeter,

00:02:42.890 --> 00:02:47.750
that is where we can control access from our building to,

00:02:47.750 --> 00:02:49.860
say, the cloud service providers.

00:02:50.440 --> 00:02:54.800
So this is a high‑level overview of initiating,

00:02:54.810 --> 00:03:00.760
terminating, maintaining access the relationships between the various entities.

00:03:01.840 --> 00:03:04.670
We have three primary service models.

00:03:04.750 --> 00:03:09.080
Now, almost anything these days can be called as a service,

00:03:09.090 --> 00:03:13.560
Disaster Recovery as a Service, even Ransomware as a Service,

00:03:14.140 --> 00:03:18.090
but the three that are defined by NIST and 800‑145

00:03:18.090 --> 00:03:22.410
include Software as a Service, Platform as a Service,

00:03:22.420 --> 00:03:24.980
and Infrastructure as a Service,

00:03:24.980 --> 00:03:28.760
and we'll look at each of these a little bit more later on,

00:03:28.970 --> 00:03:35.560
however, we know that one of the important things with this is where is control,

00:03:36.040 --> 00:03:37.990
who has responsibility?

00:03:38.360 --> 00:03:42.360
If we looked, for example, of a high level at Software as a Service,

00:03:42.630 --> 00:03:49.450
we can see that the cloud provider really has total control over the facility,

00:03:49.650 --> 00:03:53.650
the hardware, the operating system, the middleware,

00:03:54.040 --> 00:03:58.360
and they do administrative control over the application.

00:03:58.940 --> 00:04:05.530
The cloud consumer has no control over the building or equipment, and they

00:04:05.530 --> 00:04:08.740
only have a limited level of administrative control,

00:04:08.740 --> 00:04:14.350
say, for example, setting up user access levels than for the application.

00:04:15.940 --> 00:04:20.360
We have four primary deployment models: the private

00:04:20.360 --> 00:04:24.710
cloud on‑premise or off‑premise, community cloud,

00:04:25.240 --> 00:04:26.170
public cloud,

00:04:26.440 --> 00:04:32.050
and a combination of cloud providers in a hybrid cloud type of deployment.

00:04:33.440 --> 00:04:36.000
One of the important things we looked at a moment ago

00:04:36.000 --> 00:04:38.310
was the idea of a security perimeter.

00:04:38.840 --> 00:04:44.990
Having a defined area of responsibility that says what is within or inside

00:04:44.990 --> 00:04:49.550
my perimeter is that which I must maintain control over.

00:04:49.630 --> 00:04:52.910
Sometimes that was known as the trusted computing base.

00:04:53.640 --> 00:04:58.930
That which was outside of the perimeter was beyond my direct control,

00:04:59.130 --> 00:05:04.330
and I could try and control how data flowed from inside to outside

00:05:04.340 --> 00:05:09.290
through some type of a boundary controller allowing certain activities

00:05:09.290 --> 00:05:13.050
in and certainly blocking others as well.

00:05:14.350 --> 00:05:19.340
Many organizations have looked at things like an on‑site private cloud.

00:05:19.940 --> 00:05:22.980
That means that I take my own equipment,

00:05:23.090 --> 00:05:28.370
but I now use it as a type of cloud‑based deployment using some of the

00:05:28.370 --> 00:05:34.550
advantages of having things that are more shared resources,

00:05:34.840 --> 00:05:39.300
and we can see here in this case, in the case of a private cloud,

00:05:39.740 --> 00:05:45.950
that all of that equipment is inside the security perimeter of the organization.

00:05:46.540 --> 00:05:46.890
Now,

00:05:46.890 --> 00:05:50.280
we could also have a private cloud located at the

00:05:50.280 --> 00:05:53.560
facility of a cloud service provider.

00:05:54.040 --> 00:05:58.560
We can go to a CSP and we can then lease from them the

00:05:58.560 --> 00:06:04.660
space that our equipment runs on, perhaps in a protected cage at their facility.

00:06:05.140 --> 00:06:10.860
And so a private cloud really refers to a cloud for the use of one customer,

00:06:11.540 --> 00:06:13.110
and in this case,

00:06:13.110 --> 00:06:19.160
since this private cloud is located within the facility of the cloud consumer,

00:06:19.840 --> 00:06:24.030
then they control access all within their perimeter,

00:06:24.140 --> 00:06:28.430
but they may allow outside access as well through some type

00:06:28.430 --> 00:06:31.460
of approved and legitimate access path.

00:06:32.140 --> 00:06:33.960
When we look at the cloud,

00:06:34.090 --> 00:06:38.860
it's important to understand the roles of the various entities involved.

00:06:39.440 --> 00:06:42.860
Let's do a quick overview of what those main ones are.

00:06:43.340 --> 00:06:48.490
You have the cloud consumer or a customer who is using cloud‑based services.

00:06:49.140 --> 00:06:49.760
Now,

00:06:50.540 --> 00:06:53.240
I will point out that throughout this course and

00:06:53.240 --> 00:06:55.700
the certification by ISC squared,

00:06:55.870 --> 00:06:59.100
we often have a little bit of a bias towards the

00:06:59.100 --> 00:07:01.460
perspective of the cloud consumer.

00:07:02.040 --> 00:07:04.930
So very often when we look at things, we're looking at,

00:07:04.950 --> 00:07:08.360
if I am the cloud consumer, what do I need to do?

00:07:08.740 --> 00:07:12.060
And that's one thing to remember that we still obviously have to

00:07:12.060 --> 00:07:16.360
consider the perspective of the cloud provider as well,

00:07:16.840 --> 00:07:20.460
but the natural default tends to be with the consumer.

00:07:21.440 --> 00:07:25.660
You have clients or users that are using cloud‑based services,

00:07:25.660 --> 00:07:28.250
they could be employees of the cloud consumer.

00:07:28.740 --> 00:07:32.010
You have the actual, you have cloud provider,

00:07:32.200 --> 00:07:35.190
the cloud service provider that is providing the

00:07:35.190 --> 00:07:38.970
facility for cloud‑based services, and of course,

00:07:38.970 --> 00:07:39.880
you have the carriers,

00:07:39.890 --> 00:07:45.000
the networks that are enabling access even to remote locations.

00:07:46.960 --> 00:07:49.880
Some of the things we need to remember as we now go

00:07:49.880 --> 00:07:53.220
deeper into this course is that this term,

00:07:53.220 --> 00:07:57.460
cloud computing, is not just referring to one thing.

00:07:57.940 --> 00:08:00.380
It's sort of like using the term a car.

00:08:00.940 --> 00:08:05.260
Well there is a big difference between, obviously, one type of car and another.

00:08:05.740 --> 00:08:09.000
A Chevrolet is not quite the same as a Maserati,

00:08:09.000 --> 00:08:11.950
for example, and yet they're both cars.

00:08:12.440 --> 00:08:17.530
So the term cloud computing may be used in many ways and is

00:08:17.530 --> 00:08:20.450
based on the way that cloud providers define,

00:08:20.450 --> 00:08:26.960
or let's say, market their services, and that cloud consumers use those services.
