WEBVTT

1
00:00.000 --> 00:01.090 align:middle line:84%


2
00:01.090 --> 00:02.740 align:middle line:90%
One of the challenges
that can come up

3
00:02.740 --> 00:05.500 align:middle line:90%
as we may want to have different
policies for different subnets

4
00:05.500 --> 00:06.820 align:middle line:84%
inside our organization.

5
00:06.820 --> 00:08.590 align:middle line:90%
But as they all go
out to the internet,

6
00:08.590 --> 00:10.540 align:middle line:90%
they all appear as
just one IP address.

7
00:10.540 --> 00:14.620 align:middle line:90%
And so how do you take 1,000
users on different subnets

8
00:14.620 --> 00:17.192 align:middle line:90%
that all appear as one IP
address for DNS requests?

9
00:17.192 --> 00:19.150 align:middle line:90%
And how do you enforce
different policies based

10
00:19.150 --> 00:20.470 align:middle line:84%
on which subnet they came from?

11
00:20.470 --> 00:22.750 align:middle line:90%
Well, one solution to
that is to go ahead

12
00:22.750 --> 00:25.480 align:middle line:90%
and use the Umbrella
virtual appliance

13
00:25.480 --> 00:26.643 align:middle line:84%
inside of our network.

14
00:26.643 --> 00:28.060 align:middle line:90%
So in this video,
I'd like to chat

15
00:28.060 --> 00:32.000 align:middle line:90%
with you about what that is,
how to get it, and how it works.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:28.060 --> 00:32.000 align:middle line:90%
with you about what that is,
how to get it, and how it works.

16
00:32.000 --> 00:34.870 align:middle line:90%
So let's imagine inside of our
network, we've got some VLANs

17
00:34.870 --> 00:36.340 align:middle line:84%
and associated IP subnets.

18
00:36.340 --> 00:39.610 align:middle line:90%
Let's say Bob is on one
of them and that Lois

19
00:39.610 --> 00:41.670 align:middle line:84%
is on yet a different one.

20
00:41.670 --> 00:47.890 align:middle line:90%
So maybe this is VLAN 10
and this is 192.168.10.01

21
00:47.890 --> 00:49.000 align:middle line:84%
with a 24-bye mask.

22
00:49.000 --> 00:54.940 align:middle line:90%
And maybe Lois is
at 192.168.20.0.

23
00:54.940 --> 00:58.975 align:middle line:90%
So for VLAN 10 and VLAN 20
with their associate layer

24
00:58.975 --> 01:00.520 align:middle line:84%
3 addresses.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:58.975 --> 01:00.520 align:middle line:84%
3 addresses.

25
01:00.520 --> 01:02.440 align:middle line:90%
And as our traffic goes
out to the internet,

26
01:02.440 --> 01:04.690 align:middle line:90%
if everything's being
padded to this one IP

27
01:04.690 --> 01:06.970 align:middle line:90%
address or a single
address out here,

28
01:06.970 --> 01:09.087 align:middle line:90%
then when those DNS
requests go to the cloud,

29
01:09.087 --> 01:11.170 align:middle line:90%
if we've identified through
the Umbrella interface

30
01:11.170 --> 01:12.820 align:middle line:90%
that this is the IP
address to expect,

31
01:12.820 --> 01:14.890 align:middle line:84%
we can still apply policy.

32
01:14.890 --> 01:17.125 align:middle line:90%
But we won't be able to
differentiate traffic,

33
01:17.125 --> 01:20.020 align:middle line:90%
if it's coming from this subnet,
from this subnet, because it

34
01:20.020 --> 01:22.250 align:middle line:90%
all looks like it's coming
from one IP address.

35
01:22.250 --> 01:23.270 align:middle line:84%
So let me clear off the screen.

36
01:23.270 --> 01:24.620 align:middle line:90%
Let's talk about a
solution to that.

37
01:24.620 --> 01:25.420 align:middle line:84%
So here's what we would do.

38
01:25.420 --> 01:27.190 align:middle line:90%
We'd download the
virtual appliance.

39
01:27.190 --> 01:30.070 align:middle line:90%
We'd boot it up, launch
it in our hypervisor.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:27.190 --> 01:30.070 align:middle line:90%
We'd boot it up, launch
it in our hypervisor.

40
01:30.070 --> 01:31.690 align:middle line:90%
And then we'd give
it an IP address.

41
01:31.690 --> 01:33.727 align:middle line:84%
In my topology, I just have .41.

42
01:33.727 --> 01:35.560 align:middle line:90%
And then we would train
all of our computers

43
01:35.560 --> 01:40.000 align:middle line:90%
to go ahead and use that IP
address as their DNS server.

44
01:40.000 --> 01:41.740 align:middle line:90%
We can also in our
Umbrella, specify.

45
01:41.740 --> 01:44.433 align:middle line:84%
Let's say this is ogit.com.

46
01:44.433 --> 01:46.600 align:middle line:90%
And we can specify that
this is our internal domain,

47
01:46.600 --> 01:48.410 align:middle line:84%
and everything else is external.

48
01:48.410 --> 01:52.060 align:middle line:90%
So when clients make requests
to this virtual appliance,

49
01:52.060 --> 01:55.030 align:middle line:90%
if it's for ogit.com,
those requests

50
01:55.030 --> 01:56.560 align:middle line:90%
can go to our
internal DNS server.

51
01:56.560 --> 01:59.300 align:middle line:90%
And if they're for something
outside of our domain,

52
01:59.300 --> 02:01.540 align:middle line:90%
the virtual appliance can
then make the request up
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
01:59.300 --> 02:01.540 align:middle line:90%
the virtual appliance can
then make the request up

53
02:01.540 --> 02:03.645 align:middle line:84%
to the Umbrella DNS servers.

54
02:03.645 --> 02:05.020 align:middle line:90%
And because the
virtual appliance

55
02:05.020 --> 02:06.460 align:middle line:90%
can differentiate
and communicate

56
02:06.460 --> 02:08.915 align:middle line:90%
where they're coming from,
then based on the policy,

57
02:08.915 --> 02:11.290 align:middle line:90%
if we have different policies
for those internal subnets,

58
02:11.290 --> 02:13.233 align:middle line:90%
the correct policy
can be deployed.

59
02:13.233 --> 02:14.900 align:middle line:90%
So in this video, let
me share with you,

60
02:14.900 --> 02:18.490 align:middle line:90%
first of all, how do I
download this virtual appliance

61
02:18.490 --> 02:20.560 align:middle line:84%
as part of my Umbrella license?

62
02:20.560 --> 02:22.020 align:middle line:84%
Let me show you that first.

63
02:22.020 --> 02:23.020 align:middle line:84%
So here is what we'd do.

64
02:23.020 --> 02:25.930 align:middle line:90%
In the Umbrella Client, we
would go to Deployments.

65
02:25.930 --> 02:27.520 align:middle line:90%
And so under Core
Identities, here's

66
02:27.520 --> 02:29.260 align:middle line:90%
where we can specify
our network devices

67
02:29.260 --> 02:31.030 align:middle line:90%
and carve them all
out independently.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:29.260 --> 02:31.030 align:middle line:90%
and carve them all
out independently.

68
02:31.030 --> 02:33.970 align:middle line:90%
But under Configuration,
we'd go to Domain Management.

69
02:33.970 --> 02:37.510 align:middle line:90%
And here's where I specify
my local domain of ogit.com.

70
02:37.510 --> 02:40.870 align:middle line:90%
And then other Sites and
Active Directory, this

71
02:40.870 --> 02:44.500 align:middle line:90%
is where we can download the
virtual appliance, the Umbrella

72
02:44.500 --> 02:45.430 align:middle line:84%
virtual appliance.

73
02:45.430 --> 02:47.240 align:middle line:90%
And to do that up, here
on the right-hand corner,

74
02:47.240 --> 02:48.573 align:middle line:84%
we have the option for download.

75
02:48.573 --> 02:49.737 align:middle line:84%
We'll click on Download.

76
02:49.737 --> 02:51.820 align:middle line:90%
Then we have some options
for downloading a script

77
02:51.820 --> 02:53.560 align:middle line:90%
to use as part of
Active Directory.

78
02:53.560 --> 02:56.330 align:middle line:90%
And here we have the download
for the virtual appliance.

79
02:56.330 --> 02:58.840 align:middle line:90%
So there's one that runs
in Hyper-V Microsoft,

80
02:58.840 --> 03:02.830 align:middle line:90%
and there's one that runs in
VMware on their ESXI host.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
02:58.840 --> 03:02.830 align:middle line:90%
and there's one that runs in
VMware on their ESXI host.

81
03:02.830 --> 03:04.210 align:middle line:84%
So I simply clicked on Download.

82
03:04.210 --> 03:06.520 align:middle line:90%
And it just downloaded it
to my Downloads folder.

83
03:06.520 --> 03:08.660 align:middle line:90%
And then I open
up my hypervisor,

84
03:08.660 --> 03:10.400 align:middle line:84%
which is right here.

85
03:10.400 --> 03:12.610 align:middle line:90%
And I simply went to
Host, right-clicked,

86
03:12.610 --> 03:15.070 align:middle line:84%
and said I want to create a VM.

87
03:15.070 --> 03:17.440 align:middle line:90%
And then I said I've
got an OVA or OVF file.

88
03:17.440 --> 03:18.220 align:middle line:84%
I clicked on Next.

89
03:18.220 --> 03:19.450 align:middle line:84%
I point it to that file.

90
03:19.450 --> 03:21.100 align:middle line:84%
And it installed it for me.

91
03:21.100 --> 03:21.970 align:middle line:84%
And away I went.

92
03:21.970 --> 03:24.590 align:middle line:90%
And this is the virtual machine
here that's currently running.

93
03:24.590 --> 03:25.738 align:middle line:84%
So here is the IP address.

94
03:25.738 --> 03:27.280 align:middle line:90%
You can also manually
configure that.

95
03:27.280 --> 03:28.713 align:middle line:84%
It's just got to be a DHB.

96
03:28.713 --> 03:30.130 align:middle line:90%
In a production
environment, you'd
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:28.713 --> 03:30.130 align:middle line:90%
In a production
environment, you'd

97
03:30.130 --> 03:32.170 align:middle line:84%
want to hard-code so it sticks.

98
03:32.170 --> 03:34.420 align:middle line:90%
And then I configured it
to tell where my local DNS

99
03:34.420 --> 03:37.395 align:middle line:84%
server was, which is at .100.

100
03:37.395 --> 03:38.770 align:middle line:90%
It has the default
gateway, so it

101
03:38.770 --> 03:40.780 align:middle line:90%
knows how to get out
to the Umbrella cloud.

102
03:40.780 --> 03:43.300 align:middle line:90%
So here it says for
connectivity, this DNS server's

103
03:43.300 --> 03:44.110 align:middle line:84%
OK.

104
03:44.110 --> 03:45.880 align:middle line:84%
The local DNS server's OK.

105
03:45.880 --> 03:48.600 align:middle line:90%
And the Umbrella DNS
servers are all OK.

106
03:48.600 --> 03:50.350 align:middle line:90%
And what we can do is
take Bob's computer.

107
03:50.350 --> 03:54.190 align:middle line:90%
And I took the liberty of
removing the remote client off

108
03:54.190 --> 03:55.367 align:middle line:84%
of Bob's computer.

109
03:55.367 --> 03:56.950 align:middle line:90%
What we could do is
we could point Bob

110
03:56.950 --> 04:00.220 align:middle line:84%
to this server at 192.168.1.41.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
03:56.950 --> 04:00.220 align:middle line:84%
to this server at 192.168.1.41.

111
04:00.220 --> 04:01.990 align:middle line:84%
This is the virtual appliance.

112
04:01.990 --> 04:04.780 align:middle line:90%
And then if Bob is doing
a resolution for ogit.com,

113
04:04.780 --> 04:06.700 align:middle line:84%
it'll work locally.

114
04:06.700 --> 04:08.770 align:middle line:90%
If Bob does a resolution
for anything else,

115
04:08.770 --> 04:11.890 align:middle line:90%
his request will be forwarded
by this virtual appliance up

116
04:11.890 --> 04:13.030 align:middle line:84%
to the Umbrella servers.

117
04:13.030 --> 04:15.070 align:middle line:90%
And we can still enforce
the policy that way.

118
04:15.070 --> 04:16.630 align:middle line:84%
Oh, and one other thing.

119
04:16.630 --> 04:19.329 align:middle line:90%
If you do need to log on
to this virtual appliance

120
04:19.329 --> 04:21.640 align:middle line:90%
to configure it, which
I did, the password

121
04:21.640 --> 04:23.588 align:middle line:90%
is umbrella followed
by a series of numbers.

122
04:23.588 --> 04:25.630 align:middle line:90%
And let me show you how
to find that because that

123
04:25.630 --> 04:26.750 align:middle line:84%
was kind of tricky for me.

124
04:26.750 --> 04:28.600 align:middle line:90%
If you go to Admin
and Accounts, it's

125
04:28.600 --> 04:31.450 align:middle line:90%
going to have in the
string this set of numbers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
04:28.600 --> 04:31.450 align:middle line:90%
going to have in the
string this set of numbers.

126
04:31.450 --> 04:33.760 align:middle line:84%
Mine's 502, yada, yada, yada.

127
04:33.760 --> 04:37.090 align:middle line:90%
And the password for
the virtual appliance

128
04:37.090 --> 04:38.830 align:middle line:90%
is going to be
Umbrella with a capital

129
04:38.830 --> 04:42.267 align:middle line:90%
U followed by those series of
numbers regarding your account.

130
04:42.267 --> 04:44.350 align:middle line:90%
And that's how you log
into that virtual appliance

131
04:44.350 --> 04:45.800 align:middle line:84%
to modify and tweak it.

132
04:45.800 --> 04:48.370 align:middle line:90%
So what I propose we do,
let's verify on Bob's computer

133
04:48.370 --> 04:50.260 align:middle line:90%
that we're not using
Umbrella at the moment.

134
04:50.260 --> 04:55.510 align:middle line:90%
Let's do an ipconfig
-all or /all, either way.

135
04:55.510 --> 04:57.670 align:middle line:90%
So we're using a
DNS server 8.8.8.8.

136
04:57.670 --> 05:00.280 align:middle line:90%
And if we opened
up a browser and we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
04:57.670 --> 05:00.280 align:middle line:90%
And if we opened
up a browser and we

137
05:00.280 --> 05:03.150 align:middle line:90%
went to alcohol
websites, this is all

138
05:03.150 --> 05:06.140 align:middle line:90%
going to work because we don't
have a policy stopping it.

139
05:06.140 --> 05:08.730 align:middle line:90%
So let's go ahead and grab
one that we did previously

140
05:08.730 --> 05:09.990 align:middle line:84%
to make it consistent.

141
05:09.990 --> 05:11.310 align:middle line:84%
Liquorama will do.

142
05:11.310 --> 05:12.940 align:middle line:90%
And it's allowing
us to go through.

143
05:12.940 --> 05:16.650 align:middle line:90%
And if we tried to
go to www.acme.com,

144
05:16.650 --> 05:18.900 align:middle line:90%
that's going to work as well
because we're not sending

145
05:18.900 --> 05:21.413 align:middle line:84%
any requests up to Umbrella.

146
05:21.413 --> 05:23.080 align:middle line:90%
So I'm going to go
ahead and close that.

147
05:23.080 --> 05:24.910 align:middle line:84%
And let's change our settings.

148
05:24.910 --> 05:27.360 align:middle line:90%
So if we change our
network adapter settings

149
05:27.360 --> 05:30.093 align:middle line:90%
by right-clicking on that
adapter and going to IPv4,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
05:27.360 --> 05:30.093 align:middle line:90%
by right-clicking on that
adapter and going to IPv4,

150
05:30.093 --> 05:32.010 align:middle line:90%
now, if I just pointed
to the Umbrella servers

151
05:32.010 --> 05:34.020 align:middle line:90%
here, if I wasn't
registered or didn't

152
05:34.020 --> 05:36.390 align:middle line:90%
have the remote client
running on this device,

153
05:36.390 --> 05:39.253 align:middle line:90%
it wouldn't recognize that Bob
is part of our organization.

154
05:39.253 --> 05:41.670 align:middle line:90%
So what I'm going to do is I'm
going to go ahead and point

155
05:41.670 --> 05:45.000 align:middle line:84%
to 192.168.1.41.

156
05:45.000 --> 05:46.565 align:middle line:84%
That's the virtual appliance.

157
05:46.565 --> 05:47.940 align:middle line:90%
And because the
virtual appliance

158
05:47.940 --> 05:51.150 align:middle line:90%
is registered with
Umbrella, its request

159
05:51.150 --> 05:53.430 align:middle line:90%
is it forwards request
up to the Umbrella cloud.

160
05:53.430 --> 05:55.282 align:middle line:90%
We can then have
our policy applied

161
05:55.282 --> 05:57.240 align:middle line:90%
because Umbrella knows
that those requests came

162
05:57.240 --> 05:58.810 align:middle line:84%
from our organization.

163
05:58.810 --> 06:01.620 align:middle line:90%
So we'll go ahead and
click on OK and OK.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
05:58.810 --> 06:01.620 align:middle line:90%
So we'll go ahead and
click on OK and OK.

164
06:01.620 --> 06:04.810 align:middle line:90%
And let's flush the
cache real quick.

165
06:04.810 --> 06:07.873 align:middle line:90%
So I'll do an ipconfig
-flushdns just

166
06:07.873 --> 06:09.540 align:middle line:90%
to make sure we're
not caching anything.

167
06:09.540 --> 06:10.542 align:middle line:84%
We'll minimize that.

168
06:10.542 --> 06:11.980 align:middle line:84%
We'll close that.

169
06:11.980 --> 06:13.690 align:middle line:84%
And let's open up a browser.

170
06:13.690 --> 06:17.160 align:middle line:90%
Let's go out to google.com
just to make sure we

171
06:17.160 --> 06:18.240 align:middle line:84%
have basic connectivity.

172
06:18.240 --> 06:20.210 align:middle line:84%
And that seems to be working.

173
06:20.210 --> 06:22.620 align:middle line:90%
Let's do a search
for alcohol websites.

174
06:22.620 --> 06:25.110 align:middle line:90%
And let's go ahead
and grab one again.

175
06:25.110 --> 06:26.360 align:middle line:84%
And that is--

176
06:26.360 --> 06:29.160 align:middle line:84%
[LAUGHING] All right.

177
06:29.160 --> 06:30.330 align:middle line:84%
All right, pause the track.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
06:29.160 --> 06:30.330 align:middle line:84%
All right, pause the track.

178
06:30.330 --> 06:31.020 align:middle line:84%
That's working.

179
06:31.020 --> 06:32.020 align:middle line:84%
Why is that working?

180
06:32.020 --> 06:34.050 align:middle line:90%
Let's just go check
our work real quick.

181
06:34.050 --> 06:37.830 align:middle line:84%
So we do an ipconfig -all.

182
06:37.830 --> 06:39.900 align:middle line:90%
I want to see how our
current settings are.

183
06:39.900 --> 06:44.420 align:middle line:84%
Our DNS server is 192.168.1.41.

184
06:44.420 --> 06:46.100 align:middle line:90%
And let me verify
that's our address.

185
06:46.100 --> 06:48.380 align:middle line:84%
192.168.1.41.

186
06:48.380 --> 06:50.450 align:middle line:90%
It says from the
virtual appliance

187
06:50.450 --> 06:52.040 align:middle line:84%
that everything looks good.

188
06:52.040 --> 06:55.790 align:middle line:90%
And also because I was
able to go to those sites,

189
06:55.790 --> 06:57.050 align:middle line:84%
that means DNS was working.

190
06:57.050 --> 06:58.580 align:middle line:84%
Let's do an nslookup real quick.

191
06:58.580 --> 07:01.280 align:middle line:90%
Yeah, so that's the DNS
server that we're using.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

191
06:58.580 --> 07:01.280 align:middle line:90%
Yeah, so that's the DNS
server that we're using.

192
07:01.280 --> 07:04.330 align:middle line:84%
Let's do a cisco.com.

193
07:04.330 --> 07:05.627 align:middle line:84%
Yeah, so DNS is working.

194
07:05.627 --> 07:06.710 align:middle line:84%
It's working through that.

195
07:06.710 --> 07:09.590 align:middle line:90%
What is going on with
that virtual appliance?

196
07:09.590 --> 07:11.358 align:middle line:90%
So let's go back to
the interface here.

197
07:11.358 --> 07:12.650 align:middle line:84%
On the Overview page, it says--

198
07:12.650 --> 07:13.880 align:middle line:84%
Oh, right there.

199
07:13.880 --> 07:18.110 align:middle line:90%
192.168.1.41 is in
a state of error.

200
07:18.110 --> 07:19.820 align:middle line:84%
Hmm.

201
07:19.820 --> 07:22.850 align:middle line:90%
This morning, there was
an icon for an update.

202
07:22.850 --> 07:23.780 align:middle line:84%
I did it.

203
07:23.780 --> 07:26.450 align:middle line:84%
This says it's OK, though.

204
07:26.450 --> 07:27.150 align:middle line:84%
Let me do this.

205
07:27.150 --> 07:28.740 align:middle line:90%
Let's go ahead and reboot
the virtual appliance,

206
07:28.740 --> 07:30.290 align:middle line:90%
because I just
did do an upgrade.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

206
07:28.740 --> 07:30.290 align:middle line:90%
because I just
did do an upgrade.

207
07:30.290 --> 07:32.250 align:middle line:90%
And I will leave
the camera rolling.

208
07:32.250 --> 07:32.750 align:middle line:84%
All right.

209
07:32.750 --> 07:36.200 align:middle line:90%
So here, let me bring this up so
we can see a little bit better.

210
07:36.200 --> 07:37.850 align:middle line:90%
All right, down at
the bottom it says

211
07:37.850 --> 07:41.280 align:middle line:90%
control plus s, which
I will go ahead and do.

212
07:41.280 --> 07:44.830 align:middle line:90%
And then I have an
option here for Poweroff

213
07:44.830 --> 07:46.080 align:middle line:84%
in the upper left-hand corner.

214
07:46.080 --> 07:49.370 align:middle line:90%
I'm going to go ahead and
power this off with an OK.

215
07:49.370 --> 07:51.380 align:middle line:90%
And then I will
go ahead in power

216
07:51.380 --> 07:53.660 align:middle line:84%
it on here on the ESXI host.

217
07:53.660 --> 07:56.060 align:middle line:90%
So I think after
the update, that

218
07:56.060 --> 07:57.440 align:middle line:84%
may be causing us some grief.

219
07:57.440 --> 07:58.858 align:middle line:84%
That seems reasonable.

220
07:58.858 --> 08:00.650 align:middle line:90%
Let me give it a moment
and I'll reboot it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

220
07:58.858 --> 08:00.650 align:middle line:90%
Let me give it a moment
and I'll reboot it.

221
08:00.650 --> 08:02.025 align:middle line:90%
All right, so
that's powered off.

222
08:02.025 --> 08:04.460 align:middle line:90%
Let me go ahead and
power that baby back on.

223
08:04.460 --> 08:05.330 align:middle line:84%
Here it goes.

224
08:05.330 --> 08:07.070 align:middle line:90%
All right, so as
that boots up, let's

225
08:07.070 --> 08:08.630 align:middle line:84%
go back to Bob's computer.

226
08:08.630 --> 08:11.840 align:middle line:90%
And let's go to a command
prompt and just verify

227
08:11.840 --> 08:12.950 align:middle line:84%
a couple of things.

228
08:12.950 --> 08:13.490 align:middle line:84%
Yeah.

229
08:13.490 --> 08:17.850 align:middle line:84%
Well, let's flush the DNS cache.

230
08:17.850 --> 08:20.360 align:middle line:84%
So the ipconfig -flushdns.

231
08:20.360 --> 08:21.210 align:middle line:84%
Great, great, great.

232
08:21.210 --> 08:22.335 align:middle line:84%
And then we'll do nslookup.

233
08:22.335 --> 08:27.080 align:middle line:90%
up And let's look
for cbtnuggets.com

234
08:27.080 --> 08:30.690 align:middle line:90%
Yeah, DNS seems to
be working great.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

234
08:27.080 --> 08:30.690 align:middle line:90%
Yeah, DNS seems to
be working great.

235
08:30.690 --> 08:31.190 align:middle line:84%
All right.

236
08:31.190 --> 08:34.640 align:middle line:90%
And that says it's all coming
back from the server too.

237
08:34.640 --> 08:35.150 align:middle line:84%
All right.

238
08:35.150 --> 08:38.020 align:middle line:84%
So let's type exit.

239
08:38.020 --> 08:39.380 align:middle line:84%
So I've got green lights.

240
08:39.380 --> 08:40.110 align:middle line:84%
That looks good.

241
08:40.110 --> 08:41.640 align:middle line:84%
Let's go to Bob's computer.

242
08:41.640 --> 08:43.260 align:middle line:84%
I'll open up a browser.

243
08:43.260 --> 08:45.590 align:middle line:84%
We'll go to google.com.

244
08:45.590 --> 08:49.460 align:middle line:84%
And let's just try www.acme.com.

245
08:49.460 --> 08:51.590 align:middle line:84%
That'll be a quick test.

246
08:51.590 --> 08:53.520 align:middle line:84%
[LAUGHING]

247
08:53.520 --> 08:54.020 align:middle line:84%
All right.

248
08:54.020 --> 08:55.640 align:middle line:90%
So we've verified
that DNS is working.

249
08:55.640 --> 08:57.140 align:middle line:90%
It's going to the
virtual appliance.

250
08:57.140 --> 09:01.010 align:middle line:90%
Why are we not getting
the policy enforced?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

250
08:57.140 --> 09:01.010 align:middle line:90%
Why are we not getting
the policy enforced?

251
09:01.010 --> 09:01.640 align:middle line:84%
Oh, yeah.

252
09:01.640 --> 09:03.260 align:middle line:84%
That would be why.

253
09:03.260 --> 09:05.340 align:middle line:84%
Check this out.

254
09:05.340 --> 09:08.420 align:middle line:90%
If we go to Policies,
All Policies,

255
09:08.420 --> 09:11.090 align:middle line:90%
we have zero identities
in our custom policy

256
09:11.090 --> 09:13.290 align:middle line:90%
because I removed
the remote client.

257
09:13.290 --> 09:15.950 align:middle line:90%
And so basically, our custom
policy applies to no one.

258
09:15.950 --> 09:18.880 align:middle line:90%
And the default policy is
applying to everything else.

259
09:18.880 --> 09:20.780 align:middle line:90%
So there's our
problem right there.

260
09:20.780 --> 09:23.240 align:middle line:90%
I'm going to apply it to
all networks and all sites.

261
09:23.240 --> 09:25.670 align:middle line:84%
And that's all I have to find.

262
09:25.670 --> 09:26.540 align:middle line:84%
So that'll catch it.

263
09:26.540 --> 09:29.490 align:middle line:90%
So with those selected,
I'll click on Set & Return.

264
09:29.490 --> 09:32.450 align:middle line:90%
And now I have two identities
included in this custom policy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

264
09:29.490 --> 09:32.450 align:middle line:90%
And now I have two identities
included in this custom policy.

265
09:32.450 --> 09:33.620 align:middle line:84%
Click on Save.

266
09:33.620 --> 09:36.200 align:middle line:90%
And there we go, two identities
associated with that.

267
09:36.200 --> 09:37.820 align:middle line:84%
All right.

268
09:37.820 --> 09:39.020 align:middle line:84%
So we're not going crazy.

269
09:39.020 --> 09:40.850 align:middle line:90%
So let's go back
to Bob's computer.

270
09:40.850 --> 09:42.560 align:middle line:84%
Let's close the browser.

271
09:42.560 --> 09:43.865 align:middle line:84%
Let's open up a command prompt.

272
09:43.865 --> 09:46.550 align:middle line:84%


273
09:46.550 --> 09:48.760 align:middle line:90%
And we'll run that
with admin privileges.

274
09:48.760 --> 09:51.220 align:middle line:90%
And let's do a couple of
verifications, number one,

275
09:51.220 --> 09:52.660 align:middle line:84%
that our DNS cache is flushed.

276
09:52.660 --> 09:59.500 align:middle line:90%
We'll do that with ipconfig
-flushdns and ipconfig -all.

277
09:59.500 --> 10:01.180 align:middle line:90%
And we are still
pointing to that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

277
09:59.500 --> 10:01.180 align:middle line:90%
And we are still
pointing to that.

278
10:01.180 --> 10:03.680 align:middle line:90%
Just to verify that we have
name resolution in general,

279
10:03.680 --> 10:08.590 align:middle line:84%
we'll do a nslookup cisco.com.

280
10:08.590 --> 10:10.370 align:middle line:84%
All right, great, great, great.

281
10:10.370 --> 10:12.840 align:middle line:90%
OK, so now we'll
open up a browser.

282
10:12.840 --> 10:14.840 align:middle line:90%
In fact, I'm just going
to go for incognito mode

283
10:14.840 --> 10:17.720 align:middle line:90%
to make sure we're
really free and clear.

284
10:17.720 --> 10:20.660 align:middle line:84%
Let's go to www.acme.com.

285
10:20.660 --> 10:23.240 align:middle line:84%
And thank goodness.

286
10:23.240 --> 10:24.450 align:middle line:84%
That's being blocked.

287
10:24.450 --> 10:26.690 align:middle line:90%
Let's go ahead and
do a Google search.

288
10:26.690 --> 10:28.560 align:middle line:84%
And Google seems to be working.

289
10:28.560 --> 10:29.180 align:middle line:84%
That's great.

290
10:29.180 --> 10:32.450 align:middle line:90%
If we click on the little lock,
it indicates under Certificate.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

290
10:29.180 --> 10:32.450 align:middle line:90%
If we click on the little lock,
it indicates under Certificate.

291
10:32.450 --> 10:34.460 align:middle line:90%
It's signed by our
Cisco Umbrella ACA.

292
10:34.460 --> 10:35.930 align:middle line:84%
That's fantastic.

293
10:35.930 --> 10:39.290 align:middle line:90%
And let's do a
search for liquor.

294
10:39.290 --> 10:42.720 align:middle line:90%
And let's go grab one
that we've done before.

295
10:42.720 --> 10:44.660 align:middle line:84%
How about liquor.com.

296
10:44.660 --> 10:46.130 align:middle line:84%
And that should be blocked.

297
10:46.130 --> 10:47.930 align:middle line:84%
And survey says, yes!

298
10:47.930 --> 10:49.220 align:middle line:84%
I saw the block.

299
10:49.220 --> 10:50.630 align:middle line:84%
That opened up DNS at the top.

300
10:50.630 --> 10:51.380 align:middle line:84%
It's been blocked.

301
10:51.380 --> 10:54.777 align:middle line:90%
Fantastic, that means our policy
is now successfully working.

302
10:54.777 --> 10:56.360 align:middle line:90%
So thanks for joining
me in this video

303
10:56.360 --> 10:58.550 align:middle line:90%
as we've taken a look at
the virtual appliance used

304
10:58.550 --> 11:00.680 align:middle line:90%
in conjunction with
Umbrella cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

304
10:58.550 --> 11:00.680 align:middle line:90%
in conjunction with
Umbrella cloud.

305
11:00.680 --> 11:02.460 align:middle line:84%
I'll see you in the next video.

306
11:02.460 --> 11:04.760 align:middle line:90%
Meanwhile, I hope this has
been informative for you.

307
11:04.760 --> 11:08.290 align:middle line:90%
And I'd like to thank
you for viewing.