WEBVTT

00:00:01.140 --> 00:00:03.730
When we take a look at security of course,

00:00:03.730 --> 00:00:07.100
that's general for most things, but when we take

00:00:07.100 --> 00:00:10.020
specifically a look at cloud security,

00:00:10.070 --> 00:00:13.180
we have a few other concerns, certainly, we have to pay

00:00:13.180 --> 00:00:17.460
attention to. The cloud is a multi‑tenant model.

00:00:17.840 --> 00:00:20.840
We have all sorts of different customers that could

00:00:20.840 --> 00:00:22.780
be in there, both corporations,

00:00:22.780 --> 00:00:26.790
but also just people, and many of them can have different

00:00:26.790 --> 00:00:31.550
security even requirements or security practices.

00:00:32.040 --> 00:00:35.160
Could I be attacked from one of them?

00:00:35.840 --> 00:00:39.400
Could a competitor see my data? So there are things

00:00:39.400 --> 00:00:41.210
we do have to consider in this.

00:00:41.360 --> 00:00:42.470
In most cases,

00:00:42.470 --> 00:00:46.860
cloud service providers do a good job of isolation, but that

00:00:46.860 --> 00:00:49.940
probably depends a little bit on the quality of the cloud

00:00:49.940 --> 00:00:52.050
service provider we choose as well.

00:00:53.540 --> 00:00:56.260
We of course have concerns with jurisdiction.

00:00:56.640 --> 00:01:01.480
There can be laws regarding privacy that require data to be kept

00:01:01.480 --> 00:01:05.770
within our country or region. There can be problems to deal with

00:01:05.770 --> 00:01:08.250
legal issues, if there's a problem,

00:01:08.250 --> 00:01:12.250
where will any dispute be heard in the courts of our country or of

00:01:12.250 --> 00:01:15.450
another, and those are things we have to consider.

00:01:15.630 --> 00:01:19.950
We also have to consider, where are my backups. For example,

00:01:19.960 --> 00:01:23.350
maybe my data is being stored in my own country,

00:01:23.840 --> 00:01:27.960
but does the cloud service provider back it up to another part

00:01:27.960 --> 00:01:31.660
of the world, and is it therefore secure?

00:01:32.240 --> 00:01:36.730
We also have to worry about end of life, data destruction,

00:01:36.740 --> 00:01:40.170
especially when we look at memory, for example,

00:01:40.740 --> 00:01:43.540
that has stored very sensitive data.

00:01:43.670 --> 00:01:49.280
We want to make sure that that hardware is properly then cleared so there's

00:01:49.280 --> 00:01:53.080
no chance of recovery of my data at the end, as well.

00:01:54.540 --> 00:01:57.350
We also have to worry about secure development.

00:01:57.660 --> 00:02:03.290
That means that we build security in as part of the actual plan,

00:02:03.290 --> 00:02:07.700
the design, but we all know that things can be designed, but

00:02:07.700 --> 00:02:09.759
that's not how they're actually built.

00:02:10.240 --> 00:02:14.260
There's often a large difference between as‑designed and as‑built.

00:02:14.840 --> 00:02:19.470
So are the things that are important for us actually being

00:02:19.480 --> 00:02:23.560
implemented and are the security controls, for example,

00:02:23.570 --> 00:02:26.360
being operated correctly as well.

00:02:27.840 --> 00:02:32.400
We want to ensure that we have security all the way through things

00:02:32.400 --> 00:02:35.550
like systems development and software development,

00:02:35.550 --> 00:02:41.680
the SDLC. We want to make sure that when different projects are done,

00:02:41.680 --> 00:02:42.600
say, for example,

00:02:42.600 --> 00:02:48.040
we could use a methodology like DevOps, was security considered in

00:02:48.040 --> 00:02:54.780
that? Is it truly DevSecOps, as we sometimes hear? We want to be

00:02:54.780 --> 00:02:57.250
sure we're secure at the network level.

00:02:57.740 --> 00:03:02.290
We can see that the cloud has many different attack vectors,

00:03:02.300 --> 00:03:05.260
more than a traditional type of operation.

00:03:06.040 --> 00:03:10.830
We rely on the networks, and to ensure availability of those networks through

00:03:10.830 --> 00:03:16.630
things like redundancy. We want to ensure that our data is protected while it's

00:03:16.630 --> 00:03:20.430
in transit so that we have encryption, for example,

00:03:20.430 --> 00:03:24.460
but also protection against errors or lost data.

00:03:25.240 --> 00:03:27.900
Part of this will ensure protection of data from

00:03:27.900 --> 00:03:32.400
re‑transmission or maybe some other type of unauthorized

00:03:32.410 --> 00:03:36.340
alteration. When we look at network security,

00:03:36.340 --> 00:03:40.600
it's important that we review what traffic we have on our

00:03:40.600 --> 00:03:46.000
networks to make sure that all of that traffic is, for example,

00:03:46.000 --> 00:03:51.050
properly protected and that we're not exceeding the actual

00:03:51.050 --> 00:03:53.560
bandwidth limitations that we have.

00:03:54.640 --> 00:04:00.040
We very often today hear the term zero‑trust network, and this is

00:04:00.040 --> 00:04:04.180
used, of course, in many cases where we talk about zero‑trust that

00:04:04.190 --> 00:04:09.570
everything must be protected. And we know the network can be two

00:04:09.570 --> 00:04:12.760
things, it can be the target of an attack,

00:04:13.240 --> 00:04:17.160
but also it can be the conduit used in an attack.

00:04:17.640 --> 00:04:21.220
So, therefore, we have to make sure that not only

00:04:21.220 --> 00:04:23.960
is the network secure in itself,

00:04:24.540 --> 00:04:29.400
but also we have protection in there to ensure the network is

00:04:29.400 --> 00:04:33.730
not a channel that can be used to attack endpoints and our

00:04:33.730 --> 00:04:35.850
systems or our customer systems.

00:04:36.740 --> 00:04:38.260
Everything must be protected.

00:04:39.120 --> 00:04:44.460
In other words, nothing is trusted, truly a zero‑trust network.

00:04:45.540 --> 00:04:48.240
The other thing is that we quite often will try to limit

00:04:48.240 --> 00:04:51.040
things according to geographic areas.

00:04:51.170 --> 00:04:56.860
Maybe we only allow access to our networks or systems from certain

00:04:56.860 --> 00:05:04.140
registered or common places, and the idea of course behind that, also,

00:05:04.170 --> 00:05:10.440
is where we get into the challenge today of using marketing tools to try

00:05:10.440 --> 00:05:17.060
and target our advertising and our outreach to certain areas and people

00:05:17.060 --> 00:05:18.860
in their current location.

00:05:19.840 --> 00:05:24.420
The virtual level is, of course, another area of an attack,

00:05:24.500 --> 00:05:27.860
and virtualization security, whether or not we're talking

00:05:27.860 --> 00:05:29.860
about security of containers,

00:05:30.240 --> 00:05:36.880
security of the data that we store, even temporarily, and serverless

00:05:36.880 --> 00:05:42.780
technology, are areas that are used a lot in the cloud. We have a

00:05:42.780 --> 00:05:47.000
lot, for example, of containers that are self‑contained units, but

00:05:47.000 --> 00:05:49.460
must be configured to be secure.

00:05:50.040 --> 00:05:55.290
We want to make sure that any data we store, even temporarily, was protected.

00:05:55.940 --> 00:05:59.190
And of course it's kind of funny to use a term like serverless

00:05:59.190 --> 00:06:03.420
technology, because it's not truly serverless, it's just not a

00:06:03.430 --> 00:06:05.620
dedicated server for our use.

00:06:06.140 --> 00:06:11.660
And the idea, of course, behind this is that we want to have that level of

00:06:11.660 --> 00:06:17.110
abstraction that we're not worried about the servers underneath. We're quite

00:06:17.110 --> 00:06:22.880
simply just trusting that the cloud service provider is properly storing and

00:06:22.880 --> 00:06:26.160
processing our data on the servers they have.

00:06:26.640 --> 00:06:32.490
So the question for us is, are these attack points? Are there ways

00:06:32.490 --> 00:06:36.610
that a person could get in and disclose our data,

00:06:36.620 --> 00:06:43.430
corrupt our data or make systems unavailable as well? Linked into, of

00:06:43.430 --> 00:06:47.450
course, virtualization security is the hypervisor itself.

00:06:47.840 --> 00:06:53.360
We know that a key component of the cloud is the use of hypervisors.

00:06:53.740 --> 00:06:57.960
It is that layer of abstraction between hardware and

00:06:57.970 --> 00:07:04.840
our presentation and applications, but it also can be an attack surface.

00:07:05.040 --> 00:07:08.870
The hypervisor itself must be secured through things like keeping the

00:07:08.870 --> 00:07:15.600
patches up to date and making sure it's correctly configured as well. In

00:07:15.600 --> 00:07:18.660
conjunction with all of this are the virtual machines.

00:07:19.140 --> 00:07:24.040
These, of course, are the configurations of the systems that we will

00:07:24.040 --> 00:07:30.260
then power up and run on the platforms we have, and we've often said

00:07:30.260 --> 00:07:33.720
that a virtual machine should be something that is considered an

00:07:33.730 --> 00:07:35.480
asset of the organization.

00:07:36.040 --> 00:07:39.500
Any time somebody needs to spin up a virtual machine,

00:07:39.560 --> 00:07:45.410
they should use a trusted and approved configuration, so therefore, that should

00:07:45.410 --> 00:07:48.900
also be included in the configuration management database.

00:07:49.540 --> 00:07:55.260
This will ensure that all VMs follow that correct standard configuration.

00:07:56.140 --> 00:07:57.650
As we mentioned earlier,

00:07:57.650 --> 00:08:01.710
one of the problems with this is the fact that we could have VM

00:08:01.710 --> 00:08:07.180
sprawl. Virtual machine sprawl, where we are paying for all kinds of

00:08:07.180 --> 00:08:13.000
resources that we're not even using, so this is why we need careful

00:08:13.000 --> 00:08:15.260
management of these as well.

00:08:16.110 --> 00:08:21.760
This leads to, of course, not only wasted resources, but excessive billing.

00:08:23.750 --> 00:08:25.160
The Key Points Review.

00:08:25.740 --> 00:08:28.160
Obviously, security is security,

00:08:28.640 --> 00:08:33.059
but cloud‑based systems have not only the same security

00:08:33.059 --> 00:08:38.250
challenges as a traditional system, but they also bring in some new challenges,

00:08:38.480 --> 00:08:43.230
especially since we're dealing with coordination between

00:08:43.240 --> 00:08:46.060
different entities that have to work together.
