WEBVTT

00:00:01.540 --> 00:00:04.390
When it comes to securing data in the cloud,

00:00:05.040 --> 00:00:07.920
we know that there are a number of things we have to do to

00:00:07.920 --> 00:00:10.740
ensure our data is properly protected.

00:00:11.020 --> 00:00:13.830
And, in fact, domain two of this course,

00:00:13.840 --> 00:00:17.920
Data Security in the Cloud, is the most heavily weighted domain.

00:00:18.340 --> 00:00:21.780
But let's look at this from a high‑level overview before we get

00:00:21.780 --> 00:00:26.030
into more detail in the next module of the course.

00:00:27.040 --> 00:00:33.510
One of the things that leads to security of our data is to do planning,

00:00:33.510 --> 00:00:37.150
a well architected framework, for example,

00:00:37.540 --> 00:00:40.790
and to follow some of the practices out there,

00:00:40.790 --> 00:00:45.340
say from the cloud security alliance, their enterprise architecture.

00:00:46.340 --> 00:00:49.670
We know that SANS also has put out a number of good

00:00:49.670 --> 00:00:51.950
security principles we can follow.

00:00:54.240 --> 00:00:59.550
The cloud security alliance has defined the data lifecycle in this way.

00:01:00.540 --> 00:01:06.660
Create, store, use, share, archive, and delete.

00:01:07.340 --> 00:01:12.050
So we need to pay attention to the protection of data

00:01:12.060 --> 00:01:14.260
all the way through the lifecycle.

00:01:14.940 --> 00:01:18.940
That includes ensuring the secure deletion of the

00:01:18.940 --> 00:01:21.660
data at the end of life as well.

00:01:22.440 --> 00:01:26.580
But we secure it when we store it, classifying it,

00:01:26.580 --> 00:01:33.280
for example, and we make sure that only authorized people can use it or share it.

00:01:33.740 --> 00:01:37.020
We keep it as long as we're required with archiving.

00:01:38.640 --> 00:01:42.510
In order to protect data, it's important that we,

00:01:42.510 --> 00:01:44.750
first of all, know what data we have,

00:01:45.140 --> 00:01:48.190
and those are the various types of data elements.

00:01:48.200 --> 00:01:51.500
Which of those data elements are sensitive or

00:01:51.500 --> 00:01:54.010
critical and need additional protection?

00:01:54.640 --> 00:01:59.940
Where they used and what is the location where that data could be found,

00:02:00.210 --> 00:02:04.020
not only physically but on various types of reports,

00:02:04.030 --> 00:02:09.720
systems, access according to roles and responsibilities as well?

00:02:09.720 --> 00:02:14.990
A big part of protecting data is to determine who is accountable.

00:02:15.000 --> 00:02:16.960
In other words, the data owner.

00:02:17.800 --> 00:02:23.260
Then the data owner will oversee the creation of a data classification scheme.

00:02:23.720 --> 00:02:27.250
The purpose of data classification is to specify

00:02:27.260 --> 00:02:30.410
how a data must be then handled.

00:02:30.420 --> 00:02:37.050
How we set in place the rules for the handling, use, and deletion of the data.

00:02:38.140 --> 00:02:42.840
Securing data consistently means we protect it all the way

00:02:42.840 --> 00:02:45.850
through that data lifecycle we looked at.

00:02:46.440 --> 00:02:50.770
This includes data in all forms, electronic data,

00:02:50.780 --> 00:02:55.710
paper, and things like logs, data when it's being stored,

00:02:56.140 --> 00:02:58.970
when it's being transmitted, and of course,

00:02:58.970 --> 00:03:00.600
when it's being displayed.

00:03:00.600 --> 00:03:06.800
We must protect data consistently in all of those and then at end

00:03:06.800 --> 00:03:10.670
of life have what we call secure destruction.

00:03:10.950 --> 00:03:15.700
This is also known as defensible destruction because it refers to the

00:03:15.700 --> 00:03:21.030
fact that we are able to defend or make that statement.

00:03:21.280 --> 00:03:23.520
This data has been destroyed.

00:03:23.700 --> 00:03:28.550
We have then reviewed the practices used for that.

00:03:30.440 --> 00:03:33.850
Another important part of protecting data of course is

00:03:33.850 --> 00:03:35.860
protecting who has access to it.

00:03:36.090 --> 00:03:40.320
And identity and access management is a key part of

00:03:40.330 --> 00:03:42.950
any type of IT system security.

00:03:43.640 --> 00:03:48.160
We must make sure that only authorized entities have access,

00:03:48.640 --> 00:03:53.560
but also that they only have the appropriate level of access as well.

00:03:54.510 --> 00:03:58.160
The problem can come when the person's access continues to

00:03:58.160 --> 00:04:01.530
grow as they longer in the organization,

00:04:01.530 --> 00:04:05.260
they move from department to department or from system to system.

00:04:05.640 --> 00:04:08.770
And we have what we could call then access creep,

00:04:08.970 --> 00:04:11.780
a level of access that goes far beyond what a

00:04:11.780 --> 00:04:14.060
person needs for their current job.

00:04:14.940 --> 00:04:19.570
We also have to look at who manages the access and how up to

00:04:19.570 --> 00:04:22.350
date and current are they in that management?

00:04:22.740 --> 00:04:27.660
We have to make sure that we have differentiation between the various users,

00:04:27.670 --> 00:04:31.830
what a user could do as compared to what a manager can do.

00:04:31.920 --> 00:04:36.960
What are the levels of access actually then granted to these people?

00:04:38.140 --> 00:04:44.200
One of the areas that's always a concern is the person who has higher levels

00:04:44.200 --> 00:04:48.290
of privilege and the person who's the administrator is,

00:04:48.290 --> 00:04:52.480
of course, the person where the highest risk also lies.

00:04:52.940 --> 00:04:55.060
Who has administrator access?

00:04:55.090 --> 00:04:58.930
Are we keeping on top of whether or not that access is

00:04:58.930 --> 00:05:01.090
removed when they no longer need it?

00:05:02.040 --> 00:05:02.880
Now,

00:05:02.930 --> 00:05:07.760
one of the things we saw in the earlier module is that

00:05:07.760 --> 00:05:10.050
we have shared responsibilities,

00:05:10.640 --> 00:05:15.690
and responsibilities for many things could be shared depending on whether we're

00:05:15.690 --> 00:05:19.170
dealing with Platform as a Service or Software as a Service,

00:05:19.170 --> 00:05:19.960
for example.

00:05:20.740 --> 00:05:26.420
We know though that in all cases whereas some of the things like user

00:05:26.420 --> 00:05:31.620
permissions might be managed by the consumer and the cloud service

00:05:31.620 --> 00:05:35.070
provider deal with the administrators, that's not always the case.

00:05:35.640 --> 00:05:36.490
And therefore,

00:05:36.490 --> 00:05:41.050
we have to know who is responsible for the protection of our systems,

00:05:41.200 --> 00:05:46.160
system access, and data access depending on the model we are dealing with.

00:05:48.540 --> 00:05:52.030
When we look at the idea of access control,

00:05:52.040 --> 00:05:56.110
we often call this the IAAA, the identification,

00:05:56.120 --> 00:05:59.720
authentication, authorization, and accounting,

00:05:59.720 --> 00:06:02.160
or sometimes accounting is called auditing.

00:06:02.940 --> 00:06:04.820
We will look at this in more detail,

00:06:04.830 --> 00:06:08.990
but we want to make sure that we identify who is

00:06:08.990 --> 00:06:11.560
able to access our data or systems,

00:06:11.730 --> 00:06:14.940
we prove their identity through authentication,

00:06:15.210 --> 00:06:18.770
we only grant them the correct level of authorization,

00:06:18.890 --> 00:06:22.710
and of course with practices like need to know and least privilege,

00:06:22.960 --> 00:06:26.110
and we have a record of all the access and what they did,

00:06:26.110 --> 00:06:28.450
and that, of course, is accounting.

00:06:29.840 --> 00:06:34.550
The concepts behind access control is to ensure that a person

00:06:34.550 --> 00:06:36.950
has the access they need to do their job.

00:06:37.640 --> 00:06:40.460
Denying access is easy, just turn the system off.

00:06:41.040 --> 00:06:44.650
Know the challenge of access control is to provide

00:06:44.650 --> 00:06:46.760
the appropriate level of access.

00:06:47.440 --> 00:06:52.310
In alignment with principles such as only giving a person the lowest

00:06:52.310 --> 00:06:56.130
level of access or privilege they need to do their job,

00:06:56.140 --> 00:06:58.260
we'll call that least privilege,

00:06:58.340 --> 00:07:02.860
and we could say even only for the time they require that access.

00:07:03.440 --> 00:07:06.990
We also bring in the ideas of separation or

00:07:06.990 --> 00:07:09.650
sometimes called segregation of duties.

00:07:10.240 --> 00:07:14.040
No one person controls a sensitive transaction right

00:07:14.040 --> 00:07:16.560
from its initiation to its completion.

00:07:17.010 --> 00:07:17.290
No,

00:07:17.290 --> 00:07:20.940
instead we have others that must review and approve to

00:07:20.940 --> 00:07:23.490
try to prevent mistakes or even fraud.

00:07:24.740 --> 00:07:30.830
This applies not only to our employees as a cloud consumer,

00:07:30.980 --> 00:07:35.150
but also very much to the staff of the cloud service provider.

00:07:35.740 --> 00:07:40.860
Do they make sure that their employees can't access data they shouldn't see?

00:07:41.240 --> 00:07:46.730
And maybe they're limited to only being able to see access data for

00:07:46.730 --> 00:07:49.610
certain companies and not for their competitors.

00:07:51.140 --> 00:07:53.860
We also bring in the idea of need to know.

00:07:54.340 --> 00:07:58.630
And this is where sometimes obfuscation tokenization is good,

00:07:58.660 --> 00:08:01.620
where a person doesn't know the real data,

00:08:01.680 --> 00:08:04.860
they don't need to, so therefore, we hide it from them.

00:08:05.740 --> 00:08:06.720
And this, of course,

00:08:06.720 --> 00:08:12.100
includes the protection or storage of sensitive data if we

00:08:12.100 --> 00:08:14.470
deal with something like a payment card,

00:08:14.470 --> 00:08:19.590
a credit card, debit card, other types of personal information,

00:08:19.720 --> 00:08:24.660
we want to make sure that is protected from unauthorized disclosure as well.

00:08:26.140 --> 00:08:29.130
One of the ways we protect our data is through encryption.

00:08:29.480 --> 00:08:34.289
Encryption can do two main benefits for us and that is one,

00:08:34.400 --> 00:08:37.059
protect it from unauthorized disclosure,

00:08:37.539 --> 00:08:42.460
but also protect our data from unauthorized or improper modification.

00:08:43.440 --> 00:08:45.890
But when we deal with encryption,

00:08:46.340 --> 00:08:50.480
the secret to encryption is the protection of the key

00:08:50.830 --> 00:08:52.850
according to Kirchoff's principle.

00:08:53.340 --> 00:08:54.170
Therefore,

00:08:54.170 --> 00:08:59.360
one of the most important things here is that we have good key management.

00:09:00.040 --> 00:09:03.120
That means we know who holds the keys,

00:09:03.130 --> 00:09:06.980
and maybe we keep them in escrow with a trusted third‑party,

00:09:07.000 --> 00:09:11.760
or maybe we have them on something like a hardware security module,

00:09:11.830 --> 00:09:15.660
though many hardware security modules are now software as well.

00:09:16.840 --> 00:09:20.760
But we also can use the idea of cryptographic erase.

00:09:21.240 --> 00:09:24.560
We encrypt all the data we store on the cloud,

00:09:25.040 --> 00:09:27.800
and if we ever move to a different cloud provider,

00:09:27.810 --> 00:09:32.900
all we have to do to make that data inaccessible is to destroy the key.

00:09:33.340 --> 00:09:35.560
And that is cryptographic erase.

00:09:36.640 --> 00:09:41.260
Now, the way we protect data is different for each service model.

00:09:41.640 --> 00:09:43.160
In Software as a Service,

00:09:43.160 --> 00:09:47.350
for example the cloud service provider has full access to our data,

00:09:47.350 --> 00:09:48.750
they handle the encryption.

00:09:49.140 --> 00:09:51.390
Whereas in Platform as a Service,

00:09:51.400 --> 00:09:54.810
we might handle the encryption out to an endpoint,

00:09:54.930 --> 00:09:57.930
but the cloud service provider on say, for example,

00:09:58.270 --> 00:10:01.760
the actual storage units themselves.

00:10:03.940 --> 00:10:06.550
We use encryption in many places in the cloud.

00:10:07.040 --> 00:10:09.760
We use it within the applications themselves,

00:10:10.140 --> 00:10:15.040
within a database, and certainly when we're transmitting data over network,

00:10:15.050 --> 00:10:16.560
something like wireless.

00:10:17.940 --> 00:10:21.210
At the end of life, we need to make sure our data is,

00:10:21.210 --> 00:10:25.260
as we said, securely or defensively destroyed.

00:10:25.840 --> 00:10:29.990
That means that when it comes to hardware that's had sensitive data on it,

00:10:30.440 --> 00:10:33.060
there should be agreements in place to make sure that

00:10:33.060 --> 00:10:36.240
hardware has been properly destroyed.

00:10:36.440 --> 00:10:42.980
We know that the best way to protect data is to destroy the actual hardware,

00:10:43.190 --> 00:10:46.480
not to just overwrite or purge it, for example,

00:10:46.940 --> 00:10:52.150
because there are still opportunities to recover that data

00:10:52.150 --> 00:10:54.460
if we have enough resources available.

00:10:54.840 --> 00:11:00.360
So the best is, we can say here, the actual physical destruction of our hardware.

00:11:00.390 --> 00:11:04.210
This is where we need to know what is the arrangement we

00:11:04.210 --> 00:11:08.030
have in place with the cloud service provider to ensure the

00:11:08.030 --> 00:11:10.350
hardware is properly disposed of.

00:11:11.540 --> 00:11:14.440
The problem with overwriting in the cloud is we can say,

00:11:14.440 --> 00:11:16.240
well we'll just override our data yeah,

00:11:16.240 --> 00:11:19.250
but we have no control over where our data is being written.

00:11:19.840 --> 00:11:21.280
We might think we're overwriting,

00:11:21.280 --> 00:11:25.360
but not even into the place where our data originally was stored.

00:11:26.040 --> 00:11:29.500
And over the months that our data was on the cloud,

00:11:29.580 --> 00:11:32.810
it could have been on a number of different units moved

00:11:32.810 --> 00:11:35.060
around from this piece of hardware to another.

00:11:36.440 --> 00:11:40.930
So that is why the idea of cryptographic erase is good.

00:11:41.540 --> 00:11:45.360
Encrypt all the data we have in the cloud at all times,

00:11:45.740 --> 00:11:48.730
and then if we ever needed to destroy that data,

00:11:48.740 --> 00:11:51.260
all we have to do is destroy the key.

00:11:52.640 --> 00:11:53.960
The key points review.

00:11:54.940 --> 00:11:57.160
In the end, security is security.

00:11:57.640 --> 00:12:00.660
Information security is just information security.

00:12:01.240 --> 00:12:06.710
But in the cloud, there are some essential things that must be looked at.

00:12:06.870 --> 00:12:10.680
We need to acknowledge where these risks are and address

00:12:10.680 --> 00:12:12.950
those as part of our security plan.
