WEBVTT

1
00:00.000 --> 00:08.780
So, let's begin our discussion on cloud security just by taking a look at some

2
00:08.780 --> 00:09.820
of the advantages

3
00:09.820 --> 00:15.460
and disadvantages we have when dealing with the public cloud providers.

4
00:15.460 --> 00:20.580
There are some advantages even to security that moving to the cloud brings to

5
00:20.580 --> 00:21.420
the table.

6
00:21.420 --> 00:26.250
But there are of course some semi-obvious disadvantages as well when we're

7
00:26.250 --> 00:26.980
taking our

8
00:26.980 --> 00:31.280
private data and putting it on a public service provider.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:26.980 --> 00:31.280
private data and putting it on a public service provider.

9
00:31.280 --> 00:35.830
So let's go ahead and jump in, take a look at some of those pros and cons

10
00:35.830 --> 00:36.820
mostly from

11
00:36.820 --> 00:38.940
a networking perspective.

12
00:38.940 --> 00:44.460
Now keep in mind from a data protection perspective, there's other things that

13
00:44.460 --> 00:45.540
have to be considered

14
00:45.540 --> 00:50.620
as well such as encryption on storage and things like that.

15
00:50.620 --> 00:54.340
That's a little bit beyond the scope of what we're going to be discussing here.

16
00:54.340 --> 01:00.710
We're trying to discuss cloud security again from the perspective of networking
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:54.340 --> 01:00.710
We're trying to discuss cloud security again from the perspective of networking

17
01:00.710 --> 01:01.420
and getting

18
01:01.420 --> 01:07.140
our equipment, specifically our Cisco equipment connected into that cloud.

19
01:07.140 --> 01:12.300
And as we said during the skill introduction, we do have to have a basic

20
01:12.300 --> 01:14.020
understanding of

21
01:14.020 --> 01:18.950
the different components of the cloud security particularly in regards to

22
01:18.950 --> 01:20.060
networking if we're

23
01:20.060 --> 01:23.060
going to connect our equipment into the cloud.

24
01:23.060 --> 01:27.440
So let's just start off by taking a look at some of those advantages and

25
01:27.440 --> 01:28.500
disadvantages

26
01:28.500 --> 01:33.340
of security in the cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:28.500 --> 01:33.340
of security in the cloud.

27
01:33.340 --> 01:39.360
So to start off with, like we said, there are a lot of positive aspects when we

28
01:39.360 --> 01:39.940
're talking

29
01:39.940 --> 01:44.500
about moving over to our cloud security features.

30
01:44.500 --> 01:46.980
It's not all bad news.

31
01:46.980 --> 01:53.360
In fact, there's actually quite a few good things about using cloud security

32
01:53.360 --> 01:54.660
particularly

33
01:54.660 --> 01:57.500
for a smaller business.

34
01:57.500 --> 02:03.060
Now the reason I say particularly for a smaller business, we'll see as we go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:57.500 --> 02:03.060
Now the reason I say particularly for a smaller business, we'll see as we go

35
02:03.060 --> 02:04.100
down this list,

36
02:04.100 --> 02:09.720
a lot of these things are features that a large enterprise would have

37
02:09.720 --> 02:11.780
traditionally had

38
02:11.780 --> 02:14.180
in their IT department.

39
02:14.180 --> 02:19.840
However, smaller or even mid-sized companies generally wouldn't be able to

40
02:19.840 --> 02:20.820
afford to do

41
02:20.820 --> 02:26.650
a lot of the things on this list, but we get them because we're putting our

42
02:26.650 --> 02:27.500
stuff in the

43
02:27.500 --> 02:28.820
cloud.

44
02:28.820 --> 02:33.560
So just as an example, let's get started with our first one here, having a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:28.820 --> 02:33.560
So just as an example, let's get started with our first one here, having a

45
02:33.560 --> 02:34.460
specialized

46
02:34.460 --> 02:36.140
staff.

47
02:36.140 --> 02:43.460
People who are specifically trained in things like security or storage

48
02:43.460 --> 02:46.220
management or networking.

49
02:46.220 --> 02:51.510
A lot of times with a mid to small company, you might only have a handful of

50
02:51.510 --> 02:52.300
people in

51
02:52.300 --> 02:54.100
the IT department.

52
02:54.100 --> 02:58.840
And with that, they sort of have to be a jack of all trades, meaning they're

53
02:58.840 --> 03:00.100
not specializing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:58.840 --> 03:00.100
not specializing

54
03:00.100 --> 03:03.940
in any one focus of IT.

55
03:03.940 --> 03:06.260
For example, security.

56
03:06.260 --> 03:12.760
So this allows us to have people that are better trained in this particular

57
03:12.760 --> 03:13.140
focus.

58
03:13.140 --> 03:18.900
Also having secure and uniform infrastructure.

59
03:18.900 --> 03:24.190
This is important because as we move things in our cloud between say, regions

60
03:24.190 --> 03:25.420
or availability

61
03:25.420 --> 03:30.140
zones and so on, which we'll get into more in a little bit, but as we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
03:25.420 --> 03:30.140
zones and so on, which we'll get into more in a little bit, but as we're

62
03:30.140 --> 03:31.100
working with

63
03:31.100 --> 03:35.670
these cloud providers, it's important that we have a very uniform

64
03:35.670 --> 03:37.140
infrastructure.

65
03:37.140 --> 03:41.260
And of course, along with that, it's going to be secure as well.

66
03:41.260 --> 03:46.140
But this is important because everything is going to be the same in all the

67
03:46.140 --> 03:47.100
locations.

68
03:47.100 --> 03:50.620
That makes it far easier to secure as well.

69
03:50.620 --> 03:56.940
And one of our big ones here is of course the availability of resources.

70
03:56.940 --> 04:02.700
The cloud of course can scale with in reason as large as we need it to be,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:56.940 --> 04:02.700
The cloud of course can scale with in reason as large as we need it to be,

71
04:02.700 --> 04:04.100
which means they're

72
04:04.100 --> 04:10.040
not going to get overwhelmed by something like a distributed denial of service

73
04:10.040 --> 04:10.860
attack.

74
04:10.860 --> 04:16.890
This is going to be very difficult to overwhelm the resources of your major

75
04:16.890 --> 04:18.660
cloud providers.

76
04:18.660 --> 04:23.300
Nothing is impossible, of course, but it's going to be far more difficult just

77
04:23.300 --> 04:24.020
based on

78
04:24.020 --> 04:30.020
the availability of resources for networking, for compute, for storage.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
04:24.020 --> 04:30.020
the availability of resources for networking, for compute, for storage.

79
04:30.020 --> 04:35.700
And again, also to a certain extent, having again the staff to deal with it.

80
04:35.700 --> 04:40.640
They're going to have the resources from a staffing perspective to be able to

81
04:40.640 --> 04:41.180
handle

82
04:41.180 --> 04:46.740
any security breaches that do occur in a much more efficient manner.

83
04:46.740 --> 04:48.380
Another big advantage.

84
04:48.380 --> 04:54.910
Our cloud services often offer backup and recovery features as well that may be

85
04:54.910 --> 04:55.580
better

86
04:55.580 --> 04:59.460
than again what you can provide as an individual company.

87
04:59.460 --> 05:03.250
Now, again, of course, we've been doing backups and recoveries pretty much
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
04:59.460 --> 05:03.250
Now, again, of course, we've been doing backups and recoveries pretty much

88
05:03.250 --> 05:04.180
since the beginning

89
05:04.180 --> 05:05.580
of IT.

90
05:05.580 --> 05:10.540
But again, they're going to have much better, more streamlined and more

91
05:10.540 --> 05:11.780
reliable systems

92
05:11.780 --> 05:15.460
than we generally have at a single company.

93
05:15.460 --> 05:19.660
This can also help with things like endpoint mobility.

94
05:19.660 --> 05:25.900
We can access the cloud from almost anywhere, which means we have that mobility

95
05:25.900 --> 05:26.780
in place.

96
05:26.780 --> 05:32.720
Plus, if we're talking about resources in the cloud itself, those can also be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
05:26.780 --> 05:32.720
Plus, if we're talking about resources in the cloud itself, those can also be

97
05:32.720 --> 05:33.300
mobile

98
05:33.300 --> 05:38.820
because of that secure and uniform infrastructure that we talked about before,

99
05:38.820 --> 05:39.460
we can move things

100
05:39.460 --> 05:43.860
around in the cloud and they will still be accessible.

101
05:43.860 --> 05:49.540
And along with that sort of goes the idea of the cloud based data access where

102
05:49.540 --> 05:50.100
we can

103
05:50.100 --> 05:55.010
access our data from anywhere as long as we generally have an internet

104
05:55.010 --> 05:56.140
connection.

105
05:56.140 --> 06:01.020
So the availability of that data is going to generally be far better if it's in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
05:56.140 --> 06:01.020
So the availability of that data is going to generally be far better if it's in

106
06:01.020 --> 06:01.340
the

107
06:01.340 --> 06:05.700
cloud than if it's housed with an individual company.

108
06:05.700 --> 06:10.540
Now these together are also really good reasons to move to the cloud.

109
06:10.540 --> 06:14.610
And again, we're not even focusing yet on any of the specific security features

110
06:14.610 --> 06:14.900
.

111
06:14.900 --> 06:18.140
We're going to be doing that in the upcoming videos here.

112
06:18.140 --> 06:22.580
This is just some general advantages to moving to the cloud.

113
06:22.580 --> 06:28.530
But like most things, everything that has positive aspects is also going to

114
06:28.530 --> 06:30.660
have, unfortunately,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
06:28.530 --> 06:30.660
have, unfortunately,

115
06:30.660 --> 06:35.460
some negative aspects or concerns as well.

116
06:35.460 --> 06:41.700
The first concern for a lot of customers is these are some rather complex

117
06:41.700 --> 06:42.860
systems.

118
06:42.860 --> 06:49.790
There's going to be a bit of a learning curve as you go to things like AWS,

119
06:49.790 --> 06:51.380
Azure, Google

120
06:51.380 --> 06:53.100
Cloud.

121
06:53.100 --> 06:56.020
These are some rather complex systems.

122
06:56.020 --> 06:58.340
There's several different moving parts.

123
06:58.340 --> 07:01.580
Now that of course adds to the scalability.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

123
06:58.340 --> 07:01.580
Now that of course adds to the scalability.

124
07:01.580 --> 07:05.740
That's what makes these cloud providers so powerful and flexible.

125
07:05.740 --> 07:09.960
But at the same time, it does mean that we are going to have to learn how these

126
07:09.960 --> 07:10.580
systems

127
07:10.580 --> 07:14.620
work in order to secure our network properly.

128
07:14.620 --> 07:20.550
Also at the end of the day, there is no denying whatsoever that a cloud just by

129
07:20.550 --> 07:21.500
its nature

130
07:21.500 --> 07:25.500
is going to be a multi-tenant environment.

131
07:25.500 --> 07:31.170
Needless to say, Amazon has not built their entire cloud environment just for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
07:25.500 --> 07:31.170
Needless to say, Amazon has not built their entire cloud environment just for

132
07:31.170 --> 07:31.740
you and

133
07:31.740 --> 07:33.180
your company.

134
07:33.180 --> 07:36.220
Neither is Azure or Google Cloud.

135
07:36.220 --> 07:39.500
These are definitely multi-tenant.

136
07:39.500 --> 07:43.460
You could argue probably about as multi-tenant as it gets.

137
07:43.460 --> 07:49.220
They have millions of customers all on the same cloud environment.

138
07:49.220 --> 07:51.180
So that is going to be a concern.

139
07:51.180 --> 07:55.030
Now they've addressed these concerns and we'll again talk about these things in

140
07:55.030 --> 07:55.820
more detail

141
07:55.820 --> 07:57.340
as we go.

142
07:57.340 --> 08:02.670
But of course it tends to be a concern for a company that this is ultimately a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
07:57.340 --> 08:02.670
But of course it tends to be a concern for a company that this is ultimately a

143
08:02.670 --> 08:03.660
multi-tenant

144
08:03.660 --> 08:04.660
environment.

145
08:04.660 --> 08:07.220
There's just no two ways about it.

146
08:07.220 --> 08:12.450
Also almost everything that we're going to be putting in the cloud has some

147
08:12.450 --> 08:13.280
sort of internet

148
08:13.280 --> 08:15.780
facing services.

149
08:15.780 --> 08:20.760
Maybe that a web server or possibly remote desktop, there's a lot of different

150
08:20.760 --> 08:21.300
things

151
08:21.300 --> 08:26.630
we put in the cloud and some of it may be reachable only through a VPN but

152
08:26.630 --> 08:27.420
there are

153
08:27.420 --> 08:32.040
going to be internet facing services and our overall configuration and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
08:27.420 --> 08:32.040
going to be internet facing services and our overall configuration and

154
08:32.040 --> 08:33.260
management is going

155
08:33.260 --> 08:36.500
to be through a web interface as well.

156
08:36.500 --> 08:41.480
So there are definitely internet facing aspects when we're dealing with the

157
08:41.480 --> 08:42.180
cloud.

158
08:42.180 --> 08:44.980
There's just no two ways about that one either.

159
08:44.980 --> 08:49.960
And possibly the biggest concern for a lot of IT departments in a lot of

160
08:49.960 --> 08:51.220
companies would

161
08:51.220 --> 08:59.080
be the last one and that is the loss of administrative control over the systems

162
08:59.080 --> 08:59.180
.

163
08:59.180 --> 09:04.420
At the end of the day we don't have control over the services and systems that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
08:59.180 --> 09:04.420
At the end of the day we don't have control over the services and systems that

164
09:04.420 --> 09:05.220
are being

165
09:05.220 --> 09:11.780
deployed by Amazon or Microsoft or Google or any other cloud provider.

166
09:11.780 --> 09:14.980
We don't control how they run their firewalls.

167
09:14.980 --> 09:17.540
We don't control when they do updates.

168
09:17.540 --> 09:22.180
We don't control their outage windows which they don't generally have from a

169
09:22.180 --> 09:22.860
customer

170
09:22.860 --> 09:24.660
facing perspective.

171
09:24.660 --> 09:30.580
But the point is we're losing control over a lot of the aspects when we go to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
09:24.660 --> 09:30.580
But the point is we're losing control over a lot of the aspects when we go to

172
09:30.580 --> 09:31.780
the cloud.

173
09:31.780 --> 09:37.290
Now in truth, this is also probably one of the biggest selling points of the

174
09:37.290 --> 09:37.900
cloud as

175
09:37.900 --> 09:38.900
well.

176
09:38.900 --> 09:44.570
As a company, we don't need to have as much administrative staff to have the

177
09:44.570 --> 09:45.220
control

178
09:45.220 --> 09:51.670
over these systems and we're actually purposefully offloading a lot of that to

179
09:51.670 --> 09:52.860
the cloud.

180
09:52.860 --> 09:58.940
So again, although this is a concern, it's also one of the primary selling

181
09:58.940 --> 09:59.580
points.

182
09:59.580 --> 10:04.740
Just as an example of this, I had a friend of mine who used to work for a very
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

182
09:59.580 --> 10:04.740
Just as an example of this, I had a friend of mine who used to work for a very

183
10:04.740 --> 10:05.260
small

184
10:05.260 --> 10:07.260
private school.

185
10:07.260 --> 10:10.700
And he was the only person in the IT department.

186
10:10.700 --> 10:12.500
It was just him.

187
10:12.500 --> 10:17.600
And he was in charge of all the PCs for the students, all of the PCs for the

188
10:17.600 --> 10:18.260
faculty

189
10:18.260 --> 10:19.340
and staff.

190
10:19.340 --> 10:21.740
He was in charge of their back end database.

191
10:21.740 --> 10:23.540
He was in charge of their network.

192
10:23.540 --> 10:25.380
He was in charge of printers.

193
10:25.380 --> 10:30.330
He was in charge of literally everything that pretty much took electricity in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
10:25.380 --> 10:30.330
He was in charge of literally everything that pretty much took electricity in

194
10:30.330 --> 10:31.460
that school

195
10:31.460 --> 10:36.140
that had any form of technology in it, including the phone system.

196
10:36.140 --> 10:40.790
And at one point, they wanted to add some more things to his responsibilities,

197
10:40.790 --> 10:41.260
including

198
10:41.260 --> 10:45.820
things like video editing for the school plays and things like this.

199
10:45.820 --> 10:47.460
And of course, he came to me.

200
10:47.460 --> 10:49.980
He's like, "I don't know how I'm going to handle all of this."

201
10:49.980 --> 10:53.760
And I'm like, "Well, maybe it's time that we start moving some of these things

202
10:53.760 --> 10:54.220
out to

203
10:54.220 --> 10:55.420
the cloud."

204
10:55.420 --> 11:00.140
And ultimately, we ended up moving a lot of things, file and print services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

204
10:55.420 --> 11:00.140
And ultimately, we ended up moving a lot of things, file and print services.

205
11:00.140 --> 11:02.620
We moved his databases out to the cloud.

206
11:02.620 --> 11:07.650
We moved quite a few things to free up his schedule to be able to do some of

207
11:07.650 --> 11:08.300
these other

208
11:08.300 --> 11:09.940
responsibilities.

209
11:09.940 --> 11:14.260
Of course, hiring somebody else was not on that list.

210
11:14.260 --> 11:19.270
So the solution offloaded to the cloud and give some of that administrative

211
11:19.270 --> 11:20.420
responsibility

212
11:20.420 --> 11:26.500
and control over to, in his case, he ended up using AWS.

213
11:26.500 --> 11:30.780
But again, any of the cloud providers would have been just fine.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

213
11:26.500 --> 11:30.780
But again, any of the cloud providers would have been just fine.

214
11:30.780 --> 11:35.320
So in this video, we took a look at some of the basic features that we're

215
11:35.320 --> 11:36.100
looking for

216
11:36.100 --> 11:40.140
for security when it comes to the cloud providers.

217
11:40.140 --> 11:42.980
Now once again, this is not a detailed list.

218
11:42.980 --> 11:47.260
We'll be hitting some more things in more detail as we move forward.

219
11:47.260 --> 11:51.260
But we also took a look here at some of our concerns as well.

220
11:51.260 --> 11:56.740
So next up, let's take a more detailed look at exactly what type of traffic it

221
11:56.740 --> 11:57.380
is that

222
11:57.380 --> 12:01.940
we're talking about trying to secure and control in our cloud environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

222
11:57.380 --> 12:01.940
we're talking about trying to secure and control in our cloud environment.

223
12:01.940 --> 12:10.940
[BLANK_AUDIO]