WEBVTT

00:00:00.940 --> 00:00:05.700
Let's look at the building blocks that make up cloud implementations.

00:00:06.740 --> 00:00:09.270
Building the cloud is a combination of many

00:00:09.270 --> 00:00:11.660
different components working together.

00:00:12.300 --> 00:00:13.810
It's based, for example,

00:00:13.810 --> 00:00:19.460
on software, as in applications; as well as operating system and virtualization,

00:00:19.460 --> 00:00:20.250
for example,

00:00:20.840 --> 00:00:25.310
and this includes the applications that face the customer, as

00:00:25.310 --> 00:00:29.840
well as the applications used to operate the various operations

00:00:30.070 --> 00:00:34.850
such as application program interfaces, drivers and utilities,

00:00:35.340 --> 00:00:38.060
operating systems, and hypervisors.

00:00:39.240 --> 00:00:43.810
We, of course, rely a lot today on databases and the database management

00:00:43.810 --> 00:00:49.260
system that is provided by many of the cloud providers; the hardware that

00:00:49.270 --> 00:00:54.900
all of these systems run on, and that of course includes both compute and

00:00:54.900 --> 00:00:57.460
storage type of hardware systems.

00:00:58.940 --> 00:01:04.340
We rely a lot on networks for all of this to work, broad network access

00:01:04.340 --> 00:01:07.360
being one of the essential characteristics of the cloud.

00:01:08.240 --> 00:01:11.590
We can understand that the larger the attack surface,

00:01:11.590 --> 00:01:15.810
the more difficult it is to defend, and we can see that a cloud

00:01:15.810 --> 00:01:19.860
implementation has actually a fairly large attack surface.

00:01:20.190 --> 00:01:24.420
There are many different angles of attack that could be used just

00:01:24.420 --> 00:01:28.570
from a perspective of equipment and software,

00:01:28.820 --> 00:01:31.620
not even looking at things like physical security

00:01:31.620 --> 00:01:33.680
and people on top of all of this.

00:01:35.440 --> 00:01:39.540
A lot of the advantage that comes from a cloud implementation is

00:01:39.540 --> 00:01:42.480
getting all the pieces working well together.

00:01:42.940 --> 00:01:46.260
We can call that service orchestration,

00:01:46.720 --> 00:01:50.520
that is the arrangement, coordination, and management of all of

00:01:50.520 --> 00:01:54.990
these system components that are used by the cloud provider to

00:01:54.990 --> 00:01:57.950
provide services to the cloud consumer.

00:01:58.740 --> 00:02:03.370
We can see that we've divided this up into three major levels.

00:02:03.520 --> 00:02:04.670
The service layer,

00:02:04.670 --> 00:02:10.500
which provides access interfaces to the cloud consumer, or user, and of course

00:02:10.500 --> 00:02:13.600
that varies a little bit depending on the type of model,

00:02:13.600 --> 00:02:17.360
whether it's Software, Platform or Infrastructure as a Service.

00:02:18.040 --> 00:02:23.300
We then have the whole idea of the cloud is really resource abstraction.

00:02:24.240 --> 00:02:30.150
The user does not need to know or even be aware of the type of hardware

00:02:30.150 --> 00:02:34.560
being used to support cloud services. They don't need to know the

00:02:34.560 --> 00:02:39.890
operating system, because there's a level of abstraction there that

00:02:39.900 --> 00:02:44.460
really insulates and isolates the user,

00:02:44.460 --> 00:02:50.000
the cloud consumer, from the cloud service provider, and this resource

00:02:50.010 --> 00:02:53.560
abstraction and control layer is an important thing.

00:02:54.040 --> 00:02:59.010
We are no longer bound by the type of operating system or

00:02:59.010 --> 00:03:01.340
the piece of hardware we're connected to.

00:03:01.740 --> 00:03:04.450
Instead, we can be connected to many,

00:03:04.450 --> 00:03:09.350
many different pieces of hardware and easily move from

00:03:09.350 --> 00:03:11.660
using this piece of hardware to another,

00:03:11.880 --> 00:03:13.460
storing our data here,

00:03:13.460 --> 00:03:18.860
to storing data somewhere else, and the cloud user doesn't really care

00:03:18.860 --> 00:03:23.550
or have any knowledge of where their data is being stored in that

00:03:23.560 --> 00:03:27.900
perspective. They may know the geographic location, but not

00:03:27.900 --> 00:03:31.350
necessarily the piece of hardware itself.

00:03:32.040 --> 00:03:37.120
And this allows the flexibility, this allows us to ensure

00:03:37.120 --> 00:03:39.780
that even if one piece of hardware fails,

00:03:39.840 --> 00:03:45.770
we can still have service through the other pieces. And, of course,

00:03:45.780 --> 00:03:50.900
this resource abstraction is done by the cloud provider in order to

00:03:50.900 --> 00:03:54.930
manage the various system components, and they can do this through

00:03:54.930 --> 00:03:59.620
things like a hypervisor, for example, and the use of different virtual machines.

00:04:00.940 --> 00:04:03.870
Then we have the physical resource layer,

00:04:04.160 --> 00:04:08.060
the actual hardware that our system runs on, as well as

00:04:08.060 --> 00:04:10.530
the building it runs in, the facility.

00:04:10.940 --> 00:04:14.730
And this level includes things like the central processing unit,

00:04:14.740 --> 00:04:19.550
networks, firewalls, storage, and heating ventilation and air conditioning.

00:04:20.140 --> 00:04:24.760
And this is a diagram used by NIST to try to give an

00:04:24.770 --> 00:04:28.160
overview of service orchestration.

00:04:29.740 --> 00:04:34.150
We use many different terms when you talk about cloud services, and these

00:04:34.150 --> 00:04:36.680
are things you'll see as we go through the course here,

00:04:36.860 --> 00:04:42.360
the idea of portability, vendor lock‑in, cloud migration,

00:04:42.740 --> 00:04:47.160
cloud backup, hypervisor, virtual machines,

00:04:47.540 --> 00:04:53.950
containers, and all of these are different tools used in the

00:04:53.950 --> 00:04:58.420
implementation and operations of the cloud, and ones that we should

00:04:58.420 --> 00:05:02.150
certainly be familiar with that we will look at in more detail.

00:05:03.140 --> 00:05:05.150
So the building blocks of the cloud,

00:05:05.940 --> 00:05:13.580
the building that our systems are running in, and of course that requires clean,

00:05:13.590 --> 00:05:16.710
reliable power; heating, ventilation,

00:05:16.710 --> 00:05:19.950
air conditioning; and of course physical access controls.

00:05:20.640 --> 00:05:25.860
We have the hardware that our systems run on, as well as the operating systems,

00:05:26.240 --> 00:05:31.120
the hypervisor, network, application program interfaces,

00:05:31.130 --> 00:05:36.080
applications, and of course the most important part of all this, the whole

00:05:36.080 --> 00:05:43.240
reason for all of this, is data, so we can process and store our data so it

00:05:43.240 --> 00:05:46.160
can support business and legal requirements.

00:05:47.240 --> 00:05:51.080
Then we have the users. The users may be our employees,

00:05:51.100 --> 00:05:55.560
but also the users could be our customers, people we have no control over,

00:05:55.560 --> 00:05:55.960
really.

00:05:57.840 --> 00:06:00.690
One of the things that's important with all of this is that

00:06:00.690 --> 00:06:03.680
we have a well‑architected framework.

00:06:03.990 --> 00:06:10.460
In other words, we build all these components so they work well together.

00:06:11.640 --> 00:06:15.570
The goal of a well‑architected framework, as defined actually in

00:06:15.570 --> 00:06:19.020
this case by Amazon, is operational excellence,

00:06:19.370 --> 00:06:26.860
security, reliability, performance efficiency, and cost optimization.

00:06:28.040 --> 00:06:33.840
It is important that we can continue to use our cloud services, and

00:06:33.840 --> 00:06:37.260
therefore, sustainability is important as well.

00:06:38.040 --> 00:06:43.260
So this is how, for example, a good cloud implementation should work.

00:06:44.220 --> 00:06:52.660
It works operationally, securely, reliably, for example. The Key Points Review.

00:06:54.240 --> 00:06:55.690
In many cases,

00:06:55.770 --> 00:07:01.050
it is only when a business uses a cloud access security broker,

00:07:01.050 --> 00:07:06.160
or CASB, that they may become aware of how many pieces of cloud

00:07:06.170 --> 00:07:08.250
services they're already using.

00:07:09.040 --> 00:07:14.410
Many businesses don't actually know how much of the cloud they already are

00:07:14.410 --> 00:07:19.290
using, and that of course means that they may not be as aware of some of

00:07:19.290 --> 00:07:22.450
the security implications of that as well.

00:07:23.540 --> 00:07:27.260
We know that migrating to the cloud is definitely an

00:07:27.260 --> 00:07:30.260
excellent option for many organizations,

00:07:30.640 --> 00:07:35.190
but not all, and things have to be carefully thought out, what

00:07:35.190 --> 00:07:39.640
are the risks, what are the business requirements, before I do

00:07:39.640 --> 00:07:41.650
a mass migration to the cloud.
