WEBVTT

00:00:01.040 --> 00:00:05.510
An important part of any security program is to ensure that

00:00:05.510 --> 00:00:08.260
roles and responsibilities have been assigned.

00:00:08.840 --> 00:00:12.650
If it's nobody's job, then often nobody does it.

00:00:13.240 --> 00:00:15.010
In a world of cloud computing,

00:00:15.010 --> 00:00:19.810
we have a few roles different from a normal business operation,

00:00:19.810 --> 00:00:23.880
but the assignment of a role creates accountability.

00:00:24.340 --> 00:00:27.810
It means a person is responsible to do certain tasks,

00:00:27.810 --> 00:00:31.060
and therefore, they are accountable to make sure that they are done.

00:00:31.700 --> 00:00:37.110
We only have accountability when it's clearly defined whose job it is.

00:00:37.950 --> 00:00:43.380
Everyone assigned a role must understand the requirements that what

00:00:43.380 --> 00:00:46.680
are they accountable or responsible for doing,

00:00:46.680 --> 00:00:51.270
and then they must execute their tasks in a responsible,

00:00:51.270 --> 00:00:52.950
thorough manner as well.

00:00:53.340 --> 00:00:56.420
This also means they have to have the skills to be

00:00:56.420 --> 00:00:58.860
able to execute their tasks as well.

00:01:00.040 --> 00:01:02.400
When it comes to cloud‑based roles,

00:01:02.430 --> 00:01:06.690
roles and responsibilities become more complex when there's a

00:01:06.690 --> 00:01:09.160
relationship between different parties.

00:01:09.740 --> 00:01:12.060
When it's all within one company,

00:01:12.070 --> 00:01:16.240
a senior manager can assign roles and those are in effect,

00:01:16.240 --> 00:01:20.060
but when we're dealing with a cloud service provider,

00:01:20.440 --> 00:01:24.930
there is a difference here where roles and responsibilities can be shared,

00:01:25.160 --> 00:01:28.860
and in fact they can be shared in different ways depending

00:01:28.860 --> 00:01:31.660
on the deployment model or the contract.

00:01:33.290 --> 00:01:38.510
The cloud service provider is responsible for providing cloud

00:01:38.510 --> 00:01:42.900
services to customers according to the contract terms under

00:01:42.900 --> 00:01:45.750
various deployments and service models.

00:01:46.640 --> 00:01:52.520
They purchase and maintain hardware, the building; they manage access control,

00:01:52.520 --> 00:01:56.960
both physically and logically; they manage the network,

00:01:56.970 --> 00:01:59.510
as well as, of course, the various building elements,

00:01:59.510 --> 00:02:03.340
such as power, heating, ventilation, and air conditioning.

00:02:03.340 --> 00:02:07.550
They also manage the staffing of the cloud service

00:02:07.550 --> 00:02:11.540
provider staff help desk operations, and so on.

00:02:12.710 --> 00:02:15.790
The cloud consumer, or cloud customer,

00:02:16.090 --> 00:02:22.600
is an individual or an organization that consumes or uses cloud services.

00:02:23.140 --> 00:02:25.850
Now, they could also be a cloud provider.

00:02:26.180 --> 00:02:29.850
We have situations where one company can offer or sell

00:02:29.850 --> 00:02:32.160
software as a service to their customers,

00:02:32.540 --> 00:02:35.940
but they at the same time are purchasing platform as a

00:02:35.940 --> 00:02:38.380
service from another cloud provider.

00:02:40.140 --> 00:02:45.190
We see that, for example, in the area of things like streaming media.

00:02:45.340 --> 00:02:49.800
Very often you can purchase a streaming media that is a

00:02:49.800 --> 00:02:54.580
software as a service type of offering, but being hosted by,

00:02:54.580 --> 00:02:57.820
then, a large provider on platform as a service.

00:02:59.030 --> 00:03:00.800
Some cloud services are free.

00:03:00.980 --> 00:03:04.380
We've seen a lot of different offerings of email,

00:03:04.380 --> 00:03:07.540
for example, that's free for people to use,

00:03:07.540 --> 00:03:11.560
but in other cases there is a contracted price,

00:03:11.940 --> 00:03:15.470
and even the free services quite often have a contracted price

00:03:15.470 --> 00:03:17.960
if you go above a certain storage level.

00:03:19.640 --> 00:03:25.450
The cloud carrier plays an important role because all of this requires stable,

00:03:25.450 --> 00:03:26.960
reliable networks.

00:03:27.340 --> 00:03:30.270
And the cloud carrier, could be a telco,

00:03:30.280 --> 00:03:35.820
could be satellite, they are the ones providing some form of network access,

00:03:36.240 --> 00:03:39.240
and quite often we work with them to ensure we have

00:03:39.240 --> 00:03:42.330
redundancy so that if there was a cut cable,

00:03:42.330 --> 00:03:46.460
there would still be another alternate route for traffic to take.

00:03:47.240 --> 00:03:50.960
Now, that could be, let's say for example, if a fiber was cut.

00:03:51.340 --> 00:03:54.710
We could have another fiber that went a different direction,

00:03:54.720 --> 00:03:55.660
different path,

00:03:56.640 --> 00:04:01.700
or it could be that we have a completely diverse type of routing where,

00:04:01.710 --> 00:04:04.390
instead of just having a redundant fiber,

00:04:04.400 --> 00:04:07.480
they might have a microwave or some type of satellite

00:04:07.480 --> 00:04:12.020
communication in case of a problem with the fiber or

00:04:12.020 --> 00:04:14.760
traditional telecommunications network.

00:04:16.040 --> 00:04:18.730
One of the things that's important here is to have sufficient

00:04:18.730 --> 00:04:22.720
bandwidth to be able to support all the needs of the various

00:04:22.720 --> 00:04:25.250
consumers of the cloud services.

00:04:27.040 --> 00:04:29.730
In some cases it's best to work with a broker.

00:04:30.050 --> 00:04:33.850
A broker manages the relationship between the cloud

00:04:33.850 --> 00:04:36.210
consumer and the service provider.

00:04:36.640 --> 00:04:38.250
They might, first of all,

00:04:38.260 --> 00:04:42.810
try to determine which is the best cloud offering to use.

00:04:43.120 --> 00:04:45.410
They would then negotiate the contracts,

00:04:45.420 --> 00:04:49.750
and of course they could represent several different cloud service providers.

00:04:50.440 --> 00:04:53.540
That's a little different from, of course, another reseller.

00:04:53.750 --> 00:04:57.660
A reseller is just someone who sells the services of a

00:04:57.660 --> 00:04:59.760
particular cloud service provider.

00:05:01.540 --> 00:05:07.140
One of the tools that's been useful for organizations is to use a CASB,

00:05:07.140 --> 00:05:10.360
a cloud access security broker.

00:05:10.840 --> 00:05:15.710
And the purpose of a CASB is to do exactly as it says,

00:05:15.840 --> 00:05:23.330
monitor cloud access and, therefore, give us a glimpse into the security we have.

00:05:23.740 --> 00:05:29.080
So it monitors cloud usage and allows the IT department to be able to

00:05:29.080 --> 00:05:33.320
see what cloud services are currently being used.

00:05:33.550 --> 00:05:35.750
As we talked about earlier in this course,

00:05:35.750 --> 00:05:38.740
many organizations don't even know how many

00:05:38.740 --> 00:05:41.050
different cloud services they are using.

00:05:42.440 --> 00:05:46.820
The CASB can also help us then manage that relationship,

00:05:46.830 --> 00:05:51.950
the communications, between the cloud service provider and the cloud consumer.

00:05:53.240 --> 00:05:56.530
One of the things that is then brought in through part of that

00:05:56.530 --> 00:06:00.870
administrative management is the management of access controls,

00:06:00.940 --> 00:06:05.810
that only the correct people are able to access those cloud services and,

00:06:05.820 --> 00:06:07.850
hopefully, only in the right way.

00:06:09.240 --> 00:06:12.910
One of the things that's been necessary for many organizations when

00:06:12.910 --> 00:06:15.490
they're considering a transition to the cloud,

00:06:15.840 --> 00:06:19.200
is to have someone who is able to architect,

00:06:19.200 --> 00:06:22.630
or plan, the various types of implementations,

00:06:22.630 --> 00:06:24.450
and this is the cloud architect.

00:06:25.040 --> 00:06:27.840
They are a specialist that designs the cloud

00:06:27.840 --> 00:06:32.640
implementations and ensures that the right cloud solution

00:06:32.640 --> 00:06:35.520
is chosen to meet business requirements.

00:06:36.640 --> 00:06:39.990
We also have cloud auditors and regulators.

00:06:40.440 --> 00:06:45.450
A cloud auditor provides independent assessment of cloud providers.

00:06:45.840 --> 00:06:47.160
And they are important,

00:06:47.160 --> 00:06:50.730
as we'll look at especially in the third part of this course where

00:06:50.730 --> 00:06:53.550
we'll look at the evaluation of cloud providers.

00:06:54.140 --> 00:06:55.280
We also have, then,

00:06:55.280 --> 00:06:59.210
the regulators that can review and make sure that

00:06:59.210 --> 00:07:00.950
things are being done correctly.

00:07:01.340 --> 00:07:04.120
There are a number of different standards we can use,

00:07:04.120 --> 00:07:07.030
such as STAR from the Cloud Security Alliance,

00:07:07.640 --> 00:07:09.720
the SSAE 18,

00:07:09.730 --> 00:07:14.110
though many organizations have already transitioned to the next version,

00:07:14.110 --> 00:07:20.900
the SSAE 20, and the International Standard ISAE 3402.

00:07:21.940 --> 00:07:24.880
In the US government, we have FISMA, which,

00:07:24.880 --> 00:07:29.460
of course, is the Federal Information Security Management Act,

00:07:29.930 --> 00:07:30.740
though, of course,

00:07:30.740 --> 00:07:34.080
in some cases today with a revision to it it's called the

00:07:34.080 --> 00:07:37.460
Federal Information Security Modernization Act.

00:07:39.540 --> 00:07:44.600
One of the things that becomes more complex in a cloud relationship

00:07:44.610 --> 00:07:47.850
is where is the division of responsibilities?

00:07:48.340 --> 00:07:52.910
The one thing we should remember is that there are certain responsibilities

00:07:52.910 --> 00:07:56.060
that are always going to be those of the cloud customer.

00:07:56.540 --> 00:07:58.750
There are others that are always going to be the

00:07:58.750 --> 00:08:00.560
responsibility of the cloud provider.

00:08:01.240 --> 00:08:01.860
But,

00:08:02.240 --> 00:08:06.590
there is a gray area in between that varies according

00:08:06.590 --> 00:08:08.360
to the type of service we're using.

00:08:09.040 --> 00:08:13.690
One of the things that it's good to remember from a security perspective is

00:08:13.690 --> 00:08:17.160
that we see that data governance and data rights management,

00:08:17.640 --> 00:08:22.160
as well as client endpoints and account and access management,

00:08:22.170 --> 00:08:25.650
are always the responsibility of the cloud customer.

00:08:26.640 --> 00:08:30.310
The cloud provider always looks after the building,

00:08:30.310 --> 00:08:34.159
the physical host, physical network, and physical data center.

00:08:35.039 --> 00:08:39.390
But, depending on whether or not we're using software as a service,

00:08:39.390 --> 00:08:42.650
platform as a service, or infrastructure as a service,

00:08:42.650 --> 00:08:48.560
the responsibilities could be those of the customer or of the cloud provider,

00:08:48.560 --> 00:08:52.250
or they could even be shared when we look at things such as,

00:08:52.260 --> 00:08:55.830
well, applications, network controls, and,

00:08:55.870 --> 00:09:00.900
even we can say here, to identity and set up directory management.

00:09:02.840 --> 00:09:04.250
The key point to review.

00:09:04.840 --> 00:09:07.980
It's only possible to establish accountability and

00:09:07.980 --> 00:09:11.560
responsibility when roles are clearly defined.

00:09:11.940 --> 00:09:14.330
I have not gone into, in depth here,

00:09:14.330 --> 00:09:18.080
the differentiation between accountability and responsibility.

00:09:18.540 --> 00:09:21.100
Accountability is the person who's ultimately

00:09:21.100 --> 00:09:24.020
accountable to make sure something's done,

00:09:24.020 --> 00:09:27.660
responsibility is the person who actually does the work,

00:09:27.660 --> 00:09:30.850
and each person may be, of course,

00:09:30.850 --> 00:09:34.360
responsible for certain tasks and accountable for what they did.

00:09:34.940 --> 00:09:38.610
Or we could have a situation where a manager delegates

00:09:38.620 --> 00:09:40.920
a responsibility to an employee,

00:09:41.040 --> 00:09:44.860
but the manager remains accountable for what that employee does.

00:09:45.440 --> 00:09:49.560
But that's part of our RACI models and something that we will

00:09:49.560 --> 00:09:52.060
look at in more detail later in the course.

00:09:53.640 --> 00:09:58.450
As we know, this whole area of, we could say here,

00:09:59.140 --> 00:10:04.950
roles, responsibilities, accountability becomes even more important,

00:10:04.960 --> 00:10:10.260
but also more complex, when several different organizations are involved.
