WEBVTT

1
00:00.000 --> 00:05.000
So our next topic here is cloud deployment models.

2
00:05.000 --> 00:10.720
NIST actually defines several different models

3
00:10.720 --> 00:12.400
that we wanna be aware of.

4
00:12.400 --> 00:15.960
And what this is really related to is sort of

5
00:15.960 --> 00:17.960
who's running the cloud?

6
00:17.960 --> 00:21.160
Where is your data and how is it being deployed

7
00:21.160 --> 00:23.120
and being accessed?

8
00:23.120 --> 00:26.020
We'll talk here a little bit about the pros and cons

9
00:26.020 --> 00:28.640
of some of the more popular models,

10
00:28.640 --> 00:31.480
but overall this is really about covering
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:28.640 --> 00:31.480
but overall this is really about covering

11
00:31.480 --> 00:35.920
the different deployment models as defined by NIST.

12
00:35.920 --> 00:38.400
So let's go ahead and jump in and take a look

13
00:38.400 --> 00:40.040
at the various models.

14
00:40.040 --> 00:44.440
So as we mentioned during the introduction,

15
00:44.440 --> 00:47.200
we're going to be covering several different

16
00:47.200 --> 00:51.960
deployment models that are defined by NIST.

17
00:51.960 --> 00:55.720
The first of which is simply the private cloud.

18
00:55.720 --> 00:58.000
What is private cloud?

19
00:58.000 --> 01:01.560
Well, first this is a cloud that's going to be used
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:58.000 --> 01:01.560
Well, first this is a cloud that's going to be used

20
01:01.560 --> 01:04.200
by a single organization.

21
01:04.200 --> 01:07.160
Now that doesn't necessarily mean they're running it,

22
01:07.160 --> 01:10.800
but it's being used just by that one organization.

23
01:10.800 --> 01:14.640
Again, it could be managed by that organization,

24
01:14.640 --> 01:18.040
a third party or possibly even both.

25
01:18.040 --> 01:22.480
So there's no real restriction as far as who's managing it.

26
01:22.480 --> 01:25.800
There's also really no restriction on whether it's

27
01:25.800 --> 01:28.640
on their premises, off their premises,

28
01:28.640 --> 01:31.320
or once again, maybe both.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:28.640 --> 01:31.320
or once again, maybe both.

29
01:31.320 --> 01:35.680
Now, like most things, private cloud has pros and cons

30
01:35.680 --> 01:37.720
to the deployment model.

31
01:37.720 --> 01:39.560
First, the pros.

32
01:39.560 --> 01:44.480
Number one, you have complete control over the resources.

33
01:44.480 --> 01:48.160
Again, it's being used by a single organization,

34
01:48.160 --> 01:51.120
which means that you are going to have total control

35
01:51.120 --> 01:52.720
over the resources.

36
01:52.720 --> 01:55.600
That also means you're going to have total control

37
01:55.600 --> 01:57.520
over any changes.

38
01:57.520 --> 02:01.640
That could mean anything from updating the operating systems
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:57.520 --> 02:01.640
That could mean anything from updating the operating systems

39
02:01.640 --> 02:08.480
on the cloud devices to deleting data to updating applications.

40
02:08.480 --> 02:12.440
It really means any changes that are going to happen,

41
02:12.440 --> 02:16.040
including maintenance schedules, scheduled downtime,

42
02:16.040 --> 02:18.360
all of that kind of information.

43
02:18.360 --> 02:21.840
We of course also have total control of the information

44
02:21.840 --> 02:24.920
on whatever type of private cloud we're talking about.

45
02:24.920 --> 02:28.120
Again, since it's private, we have total control

46
02:28.120 --> 02:29.680
over everything.

47
02:29.680 --> 02:32.120
We can of course also include encryption on this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:29.680 --> 02:32.120
We can of course also include encryption on this

48
02:32.120 --> 02:34.720
just in case it were to get compromised.

49
02:34.720 --> 02:39.080
So these are all things that we can do in a private cloud.

50
02:39.080 --> 02:42.400
Now, some of the cons to the private cloud.

51
02:42.400 --> 02:45.840
Well, it is generally going to be a higher cost,

52
02:45.840 --> 02:49.840
because as we mentioned in the previous video,

53
02:49.840 --> 02:53.400
this means that you're entirely responsible for the resources.

54
02:53.400 --> 02:56.680
If you want control of them, that means you own them.

55
02:56.680 --> 03:01.520
That means you paid for them and therefore the higher cost.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:56.680 --> 03:01.520
That means you paid for them and therefore the higher cost.

56
03:01.520 --> 03:04.000
Now, although we have control over it,

57
03:04.000 --> 03:08.120
it also means that we do in fact have to actually do that maintenance.

58
03:08.120 --> 03:10.040
We're the ones who have to update things.

59
03:10.040 --> 03:13.760
We're the ones who have to do the maintenance on these devices.

60
03:13.760 --> 03:16.200
And in a lot of cases, what's going to happen

61
03:16.200 --> 03:20.880
is this is ultimately going to end up being underutilized.

62
03:20.880 --> 03:23.240
Clearly, you don't want your customers

63
03:23.240 --> 03:25.640
to end up with bad performance.

64
03:25.640 --> 03:30.680
So you're probably going to overbuild your private cloud, if you will,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:25.640 --> 03:30.680
So you're probably going to overbuild your private cloud, if you will,

65
03:30.680 --> 03:35.760
which means a lot of the resources will go underutilized.

66
03:35.760 --> 03:37.960
Now, if you have the other problem,

67
03:37.960 --> 03:41.520
and maybe your cloud devices are too small,

68
03:41.520 --> 03:44.560
well, you also have a problem here with scaling.

69
03:44.560 --> 03:48.160
We can't do infinite scaling with the private cloud,

70
03:48.160 --> 03:51.440
because once again, we're the ones who own the equipment.

71
03:51.440 --> 03:55.240
Therefore, we have to actually have the equipment.

72
03:55.240 --> 03:59.320
So again, there's pros and cons to the private cloud.

73
03:59.320 --> 04:05.200
Now, sort of opposite of the private cloud would be the public cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:59.320 --> 04:05.200
Now, sort of opposite of the private cloud would be the public cloud.

74
04:05.200 --> 04:08.560
And truth be told, this is probably the model

75
04:08.560 --> 04:13.040
that most people think about if you just generically say,

76
04:13.040 --> 04:16.720
we're putting this in the cloud, or you just refer to the cloud.

77
04:16.720 --> 04:20.240
Most people are probably referring to the public cloud.

78
04:20.240 --> 04:24.160
This, again, is going to be used by the general public.

79
04:24.160 --> 04:29.560
So again, this would be things like Amazon AWS, and Google,

80
04:29.560 --> 04:32.040
and Microsoft Azure.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:29.560 --> 04:32.040
and Microsoft Azure.

81
04:32.040 --> 04:35.200
So there's different providers for this.

82
04:35.200 --> 04:38.720
But again, this is generally what most people are referring to.

83
04:38.720 --> 04:44.280
Now again, this can be managed by maybe a business,

84
04:44.280 --> 04:47.040
an academic, like a school or a college,

85
04:47.040 --> 04:50.240
possibly even a governmental organization.

86
04:50.240 --> 04:53.200
It doesn't really, again, matter who's managing it.

87
04:53.200 --> 04:56.040
Most of them, of course, are going to be business.

88
04:56.040 --> 04:57.840
That would be the examples I just gave,

89
04:57.840 --> 05:00.680
such as Amazon, Google, and Microsoft.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
04:57.840 --> 05:00.680
such as Amazon, Google, and Microsoft.

90
05:00.680 --> 05:03.440
But there are these other options as well.

91
05:03.440 --> 05:05.720
Of course, one of the biggest factors of this

92
05:05.720 --> 05:09.720
is it's generally going to be located on-prem,

93
05:09.720 --> 05:12.560
but not the customer's premises,

94
05:12.560 --> 05:15.720
on the premises of the provider.

95
05:15.720 --> 05:18.480
Of course, in their data centers.

96
05:18.480 --> 05:22.280
Honestly, that's sort of the main point of public cloud,

97
05:22.280 --> 05:26.360
is that you don't have the resources as the customer.

98
05:26.360 --> 05:30.760
The provider has all the resources at their location
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
05:26.360 --> 05:30.760
The provider has all the resources at their location

99
05:30.760 --> 05:34.480
with all of the redundancy and geographical diversity

100
05:34.480 --> 05:37.520
and everything else that that comes with.

101
05:37.520 --> 05:40.200
Now, once again, just like private cloud,

102
05:40.200 --> 05:42.880
there are pros and cons here as well.

103
05:42.880 --> 05:45.680
So starting off with the pros.

104
05:45.680 --> 05:49.360
First, it is definitely a lower cost,

105
05:49.360 --> 05:53.440
particularly for capital expenditures.

106
05:53.440 --> 05:55.280
There are no capital expenditures here

107
05:55.280 --> 05:59.600
because the cloud provider owns everything.

108
05:59.600 --> 06:03.720
Next is effectively infinite scaling.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
05:59.600 --> 06:03.720
Next is effectively infinite scaling.

109
06:03.720 --> 06:06.600
Of course, by the strictest definition of the word,

110
06:06.600 --> 06:09.640
obviously, resources are not infinite.

111
06:09.640 --> 06:13.240
However, they're as infinite as we need them to be

112
06:13.240 --> 06:17.520
in almost any business environment we could imagine.

113
06:17.520 --> 06:21.080
Also, what's nice here is we have zero-day deployment.

114
06:21.080 --> 06:23.680
As I mentioned in our previous video,

115
06:23.680 --> 06:28.120
you can go to Amazon, AWS, or Google, or Microsoft,

116
06:28.120 --> 06:29.880
or any of the providers,

117
06:29.880 --> 06:33.560
and you can fire up a bunch of servers this afternoon
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
06:29.880 --> 06:33.560
and you can fire up a bunch of servers this afternoon

118
06:33.560 --> 06:35.960
and have them running before dinner.

119
06:35.960 --> 06:37.400
So very easy to do.

120
06:37.400 --> 06:39.280
We can get everything up and running

121
06:39.280 --> 06:41.240
right from the very beginning.

122
06:41.240 --> 06:43.800
And the other big advantage is,

123
06:43.800 --> 06:47.760
this is all enterprise class services.

124
06:47.760 --> 06:50.200
So that means the redundancy,

125
06:50.200 --> 06:55.080
the geographical diversity, fault tolerance, recovery,

126
06:55.080 --> 06:57.240
all the different things that we generally have

127
06:57.240 --> 06:59.280
in an enterprise environment.

128
06:59.280 --> 07:04.080
And we're providing this for storage, networking,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:59.280 --> 07:04.080
And we're providing this for storage, networking,

129
07:04.080 --> 07:07.240
security, and honestly, some other things as well,

130
07:07.240 --> 07:09.040
but those are sort of the big ones.

131
07:09.040 --> 07:12.040
You could put CPU on here as well.

132
07:12.040 --> 07:15.400
But overall, we're getting enterprise class services

133
07:15.400 --> 07:17.480
for all of these things.

134
07:17.480 --> 07:20.280
Now, the cons, you're gonna notice

135
07:20.280 --> 07:22.640
all have something in common.

136
07:22.640 --> 07:27.640
We have very little control over specific things.

137
07:27.640 --> 07:30.720
Now, of course, we have control over
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

137
07:27.640 --> 07:30.720
Now, of course, we have control over

138
07:30.720 --> 07:32.840
what resources we're using.

139
07:32.840 --> 07:35.160
That, of course, we have control over.

140
07:35.160 --> 07:38.320
But what we generally don't have control over

141
07:38.320 --> 07:42.400
is the provider's data retention policy.

142
07:42.400 --> 07:46.000
When they decide to do updates to their environment,

143
07:46.000 --> 07:50.000
when and what security fixes they decide to roll out.

144
07:50.000 --> 07:51.800
What happens if you're using a feature

145
07:51.800 --> 07:53.880
and they decide to change that feature?

146
07:53.880 --> 07:56.200
You don't have any control over that.

147
07:56.200 --> 07:58.560
Technology implementation.

148
07:58.560 --> 08:02.520
Just as an example, maybe the service provider decides
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
07:58.560 --> 08:02.520
Just as an example, maybe the service provider decides

149
08:02.520 --> 08:05.960
to offer OSPF routing in their environment.

150
08:05.960 --> 08:10.560
But they decide not to offer stub or not-so-subbe areas.

151
08:10.560 --> 08:12.520
They'll only do normal areas.

152
08:12.520 --> 08:13.760
You're not gonna have any control

153
08:13.760 --> 08:18.440
over what they choose to support as far as technology goes.

154
08:18.440 --> 08:22.400
Again, maybe you wanna run HSRP for first-hop redundancy

155
08:22.400 --> 08:25.160
and they only support VRRP.

156
08:25.160 --> 08:27.720
You're not going to have control over that sort of thing.

157
08:27.720 --> 08:30.680
You're going to have to work within their parameters.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
08:27.720 --> 08:30.680
You're going to have to work within their parameters.

158
08:30.680 --> 08:32.880
Next up is legal issues.

159
08:32.880 --> 08:35.040
This is talking about things like

160
08:35.040 --> 08:37.400
where your data is allowed to be.

161
08:37.400 --> 08:40.280
Speaking specifically here for the United States,

162
08:40.280 --> 08:44.720
with healthcare, we have something called HIPAA laws.

163
08:44.720 --> 08:49.720
The HIPAA laws control where and how data has to be maintained

164
08:49.720 --> 08:54.400
that contains patients' private information.

165
08:54.400 --> 08:56.760
Maybe that's allowed to be on the cloud.

166
08:56.760 --> 08:57.760
Maybe it's not.

167
08:57.760 --> 08:59.920
We're not here to discuss HIPAA laws.

168
08:59.920 --> 09:02.040
I'm just throwing out an example
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
08:59.920 --> 09:02.040
I'm just throwing out an example

169
09:02.040 --> 09:05.720
of where legal issues may become a problem.

170
09:05.720 --> 09:08.640
Another example would be, at least I hope,

171
09:08.640 --> 09:11.800
the military with top-secret information,

172
09:11.800 --> 09:15.880
they're probably not gonna go store that out on Amazon.

173
09:15.880 --> 09:19.080
That wouldn't necessarily be a legal issue so much

174
09:19.080 --> 09:22.880
as a practical issue, but the point being,

175
09:22.880 --> 09:26.760
we have to be careful what kind of data we're allowed to put

176
09:26.760 --> 09:28.280
in a public cloud.

177
09:28.280 --> 09:31.760
There may be legal issues where we can't do that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
09:28.280 --> 09:31.760
There may be legal issues where we can't do that.

178
09:31.760 --> 09:33.080
And all of this at the end of the day

179
09:33.080 --> 09:36.960
is gonna require that we have a certain level of trust

180
09:36.960 --> 09:39.120
in the service provider.

181
09:39.120 --> 09:41.680
We're going to have to trust that they're going to implement

182
09:41.680 --> 09:44.940
all of these things in a fashion that meets our needs.

183
09:44.940 --> 09:49.120
Now keep in mind, everything we just discussed

184
09:49.120 --> 09:52.000
on this list that we don't have control over,

185
09:52.000 --> 09:54.920
it is all going to be published information.

186
09:54.920 --> 09:56.880
They are going to put up notifications

187
09:56.880 --> 09:59.520
when they're going to do changes to technologies,

188
09:59.520 --> 10:01.680
changes to security policies.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
09:59.520 --> 10:01.680
changes to security policies.

189
10:01.680 --> 10:03.920
If any services are going to be unavailable

190
10:03.920 --> 10:08.200
at a certain time, they're going to post all of this information

191
10:08.200 --> 10:10.160
as well as their privacy policies

192
10:10.160 --> 10:11.720
and all of that kind of stuff.

193
10:11.720 --> 10:14.720
So it's not that any of this is going to be a surprise,

194
10:14.720 --> 10:17.000
again, as long as you do your research,

195
10:17.000 --> 10:20.520
but you should be aware that even though they're notifying us

196
10:20.520 --> 10:23.800
about this, that doesn't mean we have any control over it.

197
10:23.800 --> 10:26.560
If Amazon says they're doing X,

198
10:26.560 --> 10:29.040
you can't go back to Amazon and say,

199
10:29.040 --> 10:32.240
well, we'd actually prefer that you do it this other way
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

199
10:29.040 --> 10:32.240
well, we'd actually prefer that you do it this other way

200
10:32.240 --> 10:34.080
or at this other time.

201
10:34.080 --> 10:35.880
It's not going to go over real well.

202
10:35.880 --> 10:38.960
Again, they are acting as a service provider.

203
10:38.960 --> 10:40.720
They need to provide the same services

204
10:40.720 --> 10:42.400
to all of their customers.

205
10:42.400 --> 10:43.920
But again, at the end of the day,

206
10:43.920 --> 10:46.840
none of this should be a surprise to you.

207
10:46.840 --> 10:49.920
Just be aware of it and know what the different policies

208
10:49.920 --> 10:53.280
and procedures are for each different cloud provider.

209
10:53.280 --> 10:55.040
So you know what to expect.

210
10:55.040 --> 10:59.600
So that takes care of our private and our public clouds.

211
10:59.600 --> 11:02.760
In the next video, let's jump in and look at some
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

211
10:59.600 --> 11:02.760
In the next video, let's jump in and look at some

212
11:02.760 --> 11:07.200
of the other cloud deployment models that NIST defines.