WEBVTT

00:00:01.140 --> 00:00:05.960
It's interesting how we entitled this section Business Continuity? with

00:00:05.960 --> 00:00:09.320
a question mark. Because when we look at the cloud,

00:00:09.330 --> 00:00:14.960
we are relying on another organization to store and process our data, we're

00:00:14.960 --> 00:00:19.360
relying on another company to handle our network communications.

00:00:19.740 --> 00:00:24.430
And one of the things we need to do is to ensure that those

00:00:24.440 --> 00:00:29.460
dependencies we have will support our business needs,

00:00:29.730 --> 00:00:33.520
that we can continue our critical business functions.

00:00:34.340 --> 00:00:37.960
Business continuity planning is, as its name says,

00:00:38.440 --> 00:00:41.880
trying to make sure that we can continue business.

00:00:42.070 --> 00:00:45.820
Not just that the cloud provider can continue to operate,

00:00:45.940 --> 00:00:50.570
but know that they can provide support for our business functions.

00:00:51.310 --> 00:00:56.110
The cloud service provider is, for many organizations and many

00:00:56.110 --> 00:01:00.980
different systems today, a critical dependency for operations

00:01:00.980 --> 00:01:03.550
and mission of the cloud consumer.

00:01:04.840 --> 00:01:08.260
The way we must determine this is by doing an analysis.

00:01:08.640 --> 00:01:14.710
What would the impact of an outage of, say, the cloud service be on our

00:01:14.710 --> 00:01:19.530
business? And we call this, therefore, business impact analysis,

00:01:19.800 --> 00:01:26.720
the analysis of the impact on our business. As a consumer, we need

00:01:26.720 --> 00:01:29.550
to take this into account because this is a risk.

00:01:30.040 --> 00:01:35.660
We have to make sure that the cloud service provider we deal with has a plan

00:01:35.660 --> 00:01:40.270
for business continuity in the event of a serious incident.

00:01:40.570 --> 00:01:41.810
Say, for example,

00:01:41.810 --> 00:01:45.650
they had a fire, or what would happen even if we had a

00:01:45.660 --> 00:01:49.250
cut network cable? Do they have a plan?

00:01:49.840 --> 00:01:52.900
And this is where I've heard people say in the past,

00:01:52.900 --> 00:01:56.060
well, the cloud will never go down. Well,

00:01:56.070 --> 00:01:58.230
yes, the cloud has gone down.

00:01:58.230 --> 00:02:02.370
We've had a number of cases where even some of the largest cloud

00:02:02.370 --> 00:02:06.550
service providers have had outages of 8 hours or more.

00:02:07.140 --> 00:02:13.160
And in this case, we find that companies naively thought that while the

00:02:13.160 --> 00:02:19.160
cloud service provider has a plan and they didn't realize it was necessary

00:02:19.160 --> 00:02:25.590
for them as a consumer to purchase the additional protection to ensure that

00:02:25.590 --> 00:02:31.450
the cloud service provider would keep their services running during some

00:02:31.450 --> 00:02:33.260
type of a serious incident.

00:02:34.140 --> 00:02:36.800
Some of the options for the cloud service provider is

00:02:36.800 --> 00:02:38.440
that they could have multiple sites.

00:02:38.680 --> 00:02:41.030
If one goes down, we can move to another.

00:02:41.640 --> 00:02:46.060
Now ideally, those sites should be geographically dispersed so there's

00:02:46.060 --> 00:02:49.050
not a chance of both going down at the same time.

00:02:49.840 --> 00:02:53.720
But in other cases where we have a smaller cloud service provider,

00:02:53.890 --> 00:02:57.850
it could be that they have an arrangement with another cloud provider.

00:02:58.180 --> 00:03:01.860
So they provide backup facilities to each other.

00:03:03.540 --> 00:03:07.950
Some of the options for us as a consumer is to go to a hybrid model

00:03:08.150 --> 00:03:11.450
to have, of course, multiple cloud providers.

00:03:11.940 --> 00:03:14.480
But then we have to make sure we have portability.

00:03:14.670 --> 00:03:18.290
We can easily move our data from one provider to another.

00:03:18.840 --> 00:03:21.460
We have the ability to transfer data.

00:03:21.760 --> 00:03:25.120
Now this is important because one thing that the cloud is not

00:03:25.130 --> 00:03:29.190
good at is bulk uploads and bulk downloads.

00:03:29.640 --> 00:03:32.760
They're very good at processing and storing data.

00:03:33.140 --> 00:03:38.870
But if I have to move a huge amount of data onto a cloud provider or

00:03:38.880 --> 00:03:42.500
off of a cloud provider, that could take, as we saw,

00:03:42.500 --> 00:03:46.270
for example with Glacier, it could take months.

00:03:46.840 --> 00:03:51.360
And so the challenge here is making sure we have a data

00:03:51.360 --> 00:03:55.760
transfer capability that will allow us to resume business

00:03:55.760 --> 00:03:58.150
within that required length of time.

00:03:59.640 --> 00:04:03.520
We also have to make sure that if we're dealing with multiple cloud providers

00:04:03.720 --> 00:04:08.610
that they're using the same type of systems that would be interoperable and I

00:04:08.610 --> 00:04:12.360
can easily port my data over to the other one.

00:04:14.640 --> 00:04:15.860
Key point to review.

00:04:17.140 --> 00:04:20.860
Each organization is responsible for its own risk.

00:04:21.440 --> 00:04:22.470
Therefore,

00:04:22.520 --> 00:04:28.390
each organization must exercise due care and due diligence to

00:04:28.390 --> 00:04:31.000
protect the assets of the organization.

00:04:31.950 --> 00:04:36.700
This means that we have to ensure we provide adequate

00:04:36.700 --> 00:04:40.960
security, and we do this through the implementation of

00:04:40.960 --> 00:04:44.660
appropriate controls based on our risk.

00:04:45.340 --> 00:04:50.130
But then controls sometimes don't work, and that's why we need

00:04:50.130 --> 00:04:54.480
monitoring to make sure the controls are effective, and the risk

00:04:54.490 --> 00:04:57.050
has been reduced to an acceptable level.
