WEBVTT

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


2
00:00.500 --> 00:02.790 align:middle line:90%
The first and most basic
way that we can actually

3
00:02.790 --> 00:05.610 align:middle line:90%
allow devices onto our
network is using something

4
00:05.610 --> 00:07.710 align:middle line:84%
called network profiling.

5
00:07.710 --> 00:10.410 align:middle line:90%
That's where we gather
some basic information just

6
00:10.410 --> 00:12.360 align:middle line:90%
by looking at the
type of device that's

7
00:12.360 --> 00:15.810 align:middle line:90%
trying to access our network,
make some assumptions about it

8
00:15.810 --> 00:17.760 align:middle line:90%
based on what we
know, and then we

9
00:17.760 --> 00:20.143 align:middle line:90%
decide if we want to
allow it in or not.

10
00:20.143 --> 00:22.560 align:middle line:90%
So get ready where we're going
to be talking about network

11
00:22.560 --> 00:23.770 align:middle line:84%
profiling in this Nugget.

12
00:23.770 --> 00:24.640 align:middle line:84%
Let's get going.

13
00:24.640 --> 00:27.450 align:middle line:90%
So before we dig really
deep into what this is,

14
00:27.450 --> 00:29.850 align:middle line:90%
what profiling is,
keep in mind what

15
00:29.850 --> 00:31.380 align:middle line:84%
we're trying to do right now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:29.850 --> 00:31.380 align:middle line:84%
we're trying to do right now.

16
00:31.380 --> 00:35.590 align:middle line:90%
What we're trying to do is allow
endpoints onto the network,

17
00:35.590 --> 00:38.490 align:middle line:90%
or, at least, stop malicious
endpoints from entering network

18
00:38.490 --> 00:39.760 align:middle line:84%
in the first place.

19
00:39.760 --> 00:41.550 align:middle line:90%
So what we're going
to talk about first

20
00:41.550 --> 00:44.430 align:middle line:90%
is how we can just
make assumptions

21
00:44.430 --> 00:47.160 align:middle line:90%
based on characteristics
of the devices that

22
00:47.160 --> 00:49.800 align:middle line:90%
are trying to enter the
network and then beyond that,

23
00:49.800 --> 00:53.190 align:middle line:90%
dynamically place them
into the correct subnet.

24
00:53.190 --> 00:55.140 align:middle line:84%
Here's how profiling works.

25
00:55.140 --> 00:57.750 align:middle line:90%
Consider for a moment that
we may have a telephone.

26
00:57.750 --> 00:59.700 align:middle line:90%
It's going to be a
voice over IP phone.

27
00:59.700 --> 01:02.820 align:middle line:90%
So I'll draw a little phone
here and a little cord.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:59.700 --> 01:02.820 align:middle line:90%
So I'll draw a little phone
here and a little cord.

28
01:02.820 --> 01:05.820 align:middle line:84%
And it plugs into a switch.

29
01:05.820 --> 01:09.510 align:middle line:90%
Now, the way we want our
secure environment to work

30
01:09.510 --> 01:12.720 align:middle line:90%
is we don't want anything
that plugs into our switch

31
01:12.720 --> 01:15.990 align:middle line:90%
to be automatically handed an
IP address and on the network

32
01:15.990 --> 01:17.410 align:middle line:84%
with total keys to the kingdom.

33
01:17.410 --> 01:19.770 align:middle line:90%
That's what we're
trying to avoid now

34
01:19.770 --> 01:22.140 align:middle line:90%
when we're talking
about endpoint security

35
01:22.140 --> 01:25.110 align:middle line:90%
and specifically
endpoint network access.

36
01:25.110 --> 01:28.590 align:middle line:90%
That's the key phrase
here is network access.

37
01:28.590 --> 01:32.170 align:middle line:90%
Who was allowed access
onto the network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:28.590 --> 01:32.170 align:middle line:90%
Who was allowed access
onto the network.

38
01:32.170 --> 01:34.080 align:middle line:90%
So what we can do
is we can leverage

39
01:34.080 --> 01:36.930 align:middle line:90%
tools that can identify
these devices that

40
01:36.930 --> 01:40.260 align:middle line:90%
are trying to enter the
network and then assign them

41
01:40.260 --> 01:42.000 align:middle line:90%
the correct
permissions and so on.

42
01:42.000 --> 01:46.440 align:middle line:90%
Cisco offers an amazing
industry-standard amazing

43
01:46.440 --> 01:49.980 align:middle line:90%
identity, access,
and control system

44
01:49.980 --> 01:53.790 align:middle line:90%
called the Identity Services
Engine or ISE for short.

45
01:53.790 --> 01:56.010 align:middle line:90%
So the idea is that
if we're trying

46
01:56.010 --> 01:58.800 align:middle line:90%
to implement a
profiling strategy, when

47
01:58.800 --> 02:01.350 align:middle line:90%
this device plugs
into the network,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:58.800 --> 02:01.350 align:middle line:90%
this device plugs
into the network,

48
02:01.350 --> 02:05.670 align:middle line:90%
the switch and other services
can communicate back to ISE

49
02:05.670 --> 02:10.199 align:middle line:90%
and say a device with
this Mac address has just

50
02:10.199 --> 02:11.700 align:middle line:84%
plugged into the network.

51
02:11.700 --> 02:14.400 align:middle line:90%
ISE can check its
internal database

52
02:14.400 --> 02:17.460 align:middle line:90%
for any information on
that specific Mac address.

53
02:17.460 --> 02:19.560 align:middle line:90%
If it already knows
about this Mac address,

54
02:19.560 --> 02:21.420 align:middle line:90%
maybe because we've
configured it too,

55
02:21.420 --> 02:23.370 align:middle line:90%
it could allow it
in using something

56
02:23.370 --> 02:25.350 align:middle line:84%
like Mac authentication bypass.

57
02:25.350 --> 02:27.750 align:middle line:90%
You're going to learn about
Mac authentication bypass

58
02:27.750 --> 02:30.060 align:middle line:90%
later on in this
series of Nuggets.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:27.750 --> 02:30.060 align:middle line:90%
later on in this
series of Nuggets.

59
02:30.060 --> 02:33.720 align:middle line:90%
But if it doesn't specifically
know about that exact device,

60
02:33.720 --> 02:37.740 align:middle line:90%
it can start requesting or
gathering more information

61
02:37.740 --> 02:40.110 align:middle line:84%
about our voice over IP phone.

62
02:40.110 --> 02:42.180 align:middle line:90%
For instance, it
can determine, first

63
02:42.180 --> 02:43.920 align:middle line:90%
of all, what kind
of device is it?

64
02:43.920 --> 02:45.330 align:middle line:84%
Is it a phone?

65
02:45.330 --> 02:46.710 align:middle line:84%
Is it a tablet?

66
02:46.710 --> 02:48.030 align:middle line:84%
Is it a desktop?

67
02:48.030 --> 02:50.550 align:middle line:90%
What kind of operating
system is it running?

68
02:50.550 --> 02:52.770 align:middle line:84%
Who is the manufacturer?

69
02:52.770 --> 02:55.560 align:middle line:90%
And once it determines
that this is a phone

70
02:55.560 --> 02:58.290 align:middle line:90%
and its manufacturer
is Cisco, it

71
02:58.290 --> 03:03.180 align:middle line:90%
can create a profile for
Cisco voice products.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
02:58.290 --> 03:03.180 align:middle line:90%
can create a profile for
Cisco voice products.

72
03:03.180 --> 03:07.080 align:middle line:90%
And if we've instructed ISE
to behave this specific way,

73
03:07.080 --> 03:10.360 align:middle line:90%
something very cool
and dynamic can happen.

74
03:10.360 --> 03:13.680 align:middle line:90%
We can tell ISE if the
Cisco Voice over IP phone

75
03:13.680 --> 03:15.600 align:middle line:90%
were to plug into
the network, it's

76
03:15.600 --> 03:17.950 align:middle line:90%
OK to allow it to
access the network

77
03:17.950 --> 03:22.110 align:middle line:90%
but specifically put
it in the voice VLAN.

78
03:22.110 --> 03:25.860 align:middle line:90%
So Cisco ISE can return back
to this specific switchboard

79
03:25.860 --> 03:28.900 align:middle line:90%
and say, yes, allow them
access to the network.

80
03:28.900 --> 03:32.460 align:middle line:90%
But this switchboard
should belong on VLAN,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:28.900 --> 03:32.460 align:middle line:90%
But this switchboard
should belong on VLAN,

81
03:32.460 --> 03:36.360 align:middle line:90%
make up something like 100,
which is our voice VLAN.

82
03:36.360 --> 03:40.410 align:middle line:90%
Extrapolate this times any of
the other devices or services

83
03:40.410 --> 03:41.640 align:middle line:84%
that you can work with.

84
03:41.640 --> 03:44.170 align:middle line:90%
That's exactly what
profiling is all about.

85
03:44.170 --> 03:46.830 align:middle line:90%
We're all about
gathering information

86
03:46.830 --> 03:50.100 align:middle line:90%
on the types of devices that
are trying to access our network

87
03:50.100 --> 03:52.830 align:middle line:90%
and then placing them
into the correct VLAN.

88
03:52.830 --> 03:54.810 align:middle line:90%
So you could do things
outside of voice.

89
03:54.810 --> 04:00.120 align:middle line:90%
You could do things like
printers, IoT devices, servers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
03:54.810 --> 04:00.120 align:middle line:90%
You could do things like
printers, IoT devices, servers.

90
04:00.120 --> 04:04.800 align:middle line:90%
Or even guest access devices
would bring your own devices,

91
04:04.800 --> 04:06.780 align:middle line:84%
like tablets and cell phones.

92
04:06.780 --> 04:08.410 align:middle line:90%
And look, I know
what you're thinking.

93
04:08.410 --> 04:11.100 align:middle line:90%
You're thinking, hey, this
is really cool and all--

94
04:11.100 --> 04:12.030 align:middle line:84%
prove it.

95
04:12.030 --> 04:13.830 align:middle line:90%
One of the best
things about Cisco

96
04:13.830 --> 04:16.260 align:middle line:90%
and these really expensive
platforms for us,

97
04:16.260 --> 04:18.300 align:middle line:90%
the learners is
that we can still

98
04:18.300 --> 04:22.290 align:middle line:90%
get hands on with each of these
devices leveraging the DevNet

99
04:22.290 --> 04:23.130 align:middle line:84%
Sandbox.

100
04:23.130 --> 04:27.390 align:middle line:90%
So go to
devnetsandbox.cisco.com.

101
04:27.390 --> 04:31.230 align:middle line:90%
And you'll be able to reserve
your own instance of Cisco ISE
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
04:27.390 --> 04:31.230 align:middle line:90%
And you'll be able to reserve
your own instance of Cisco ISE

102
04:31.230 --> 04:33.600 align:middle line:90%
with end points that you
can validate and click

103
04:33.600 --> 04:34.920 align:middle line:84%
around and play around with.

104
04:34.920 --> 04:38.130 align:middle line:90%
For instance, I'm setting up
my environment right now so

105
04:38.130 --> 04:41.680 align:middle line:90%
that we can log in to
Cisco's DevNet sandbox.

106
04:41.680 --> 04:43.500 align:middle line:90%
Now, for each of the
security platforms--

107
04:43.500 --> 04:45.030 align:middle line:90%
I'm going to write
security here--

108
04:45.030 --> 04:48.940 align:middle line:90%
you do have to reserve each
one of these instances.

109
04:48.940 --> 04:51.960 align:middle line:90%
So once you're clicking
around in these sandbox labs,

110
04:51.960 --> 04:54.030 align:middle line:90%
you'll be able to filter
them down by security.

111
04:54.030 --> 04:56.880 align:middle line:90%
And you'll see the
Identity Services Engine

112
04:56.880 --> 04:59.880 align:middle line:90%
sandboxes, which is what
I've reserved right here.

113
04:59.880 --> 05:01.920 align:middle line:90%
If I scroll over
just a hair, you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
04:59.880 --> 05:01.920 align:middle line:90%
If I scroll over
just a hair, you

114
05:01.920 --> 05:04.490 align:middle line:90%
can see the exact environment
that we're working with.

115
05:04.490 --> 05:06.030 align:middle line:84%
Here's the IP addresses.

116
05:06.030 --> 05:08.820 align:middle line:90%
Here's some servers
and end point devices

117
05:08.820 --> 05:10.650 align:middle line:90%
like a Linux device
and a Windows device

118
05:10.650 --> 05:11.970 align:middle line:84%
that we can click around with.

119
05:11.970 --> 05:13.620 align:middle line:90%
And once you've
reserved this, you

120
05:13.620 --> 05:15.420 align:middle line:90%
will need to connect
to the AnyConnect

121
05:15.420 --> 05:16.950 align:middle line:90%
VPN, which we're
going to talk about

122
05:16.950 --> 05:18.750 align:middle line:84%
later in this exact skill.

123
05:18.750 --> 05:20.850 align:middle line:90%
So you get connected
to the AnyConnect VPN.

124
05:20.850 --> 05:23.910 align:middle line:90%
And now you can hover
over the ISE device

125
05:23.910 --> 05:25.530 align:middle line:90%
and click on the
little menu item

126
05:25.530 --> 05:27.550 align:middle line:90%
here-- this little
three-tier menu item.

127
05:27.550 --> 05:29.340 align:middle line:90%
It'll pop out a
screen, and it shows

128
05:29.340 --> 05:31.770 align:middle line:90%
you the username and
password that you can use
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
05:29.340 --> 05:31.770 align:middle line:90%
you the username and
password that you can use

129
05:31.770 --> 05:33.670 align:middle line:84%
to get logged into the device.

130
05:33.670 --> 05:35.700 align:middle line:90%
So at this point,
what I'm going to do

131
05:35.700 --> 05:37.680 align:middle line:90%
is I'm going to get
connected to AnyConnect

132
05:37.680 --> 05:40.320 align:middle line:90%
so that we can access
ISE from the front end.

133
05:40.320 --> 05:42.720 align:middle line:90%
And you'll be able to
follow along and see

134
05:42.720 --> 05:45.305 align:middle line:90%
at least where Cisco ISE
can implement profiles.

135
05:45.305 --> 05:47.430 align:middle line:90%
Now, again, we're going to
cover this in a lot more

136
05:47.430 --> 05:49.380 align:middle line:90%
when Keith Barker
gets to the Cisco ISE

137
05:49.380 --> 05:51.150 align:middle line:90%
content towards the
end of this playlist.

138
05:51.150 --> 05:52.590 align:middle line:90%
But this is setting
up, at least,

139
05:52.590 --> 05:55.110 align:middle line:90%
how profiling works
within Cisco ISE.

140
05:55.110 --> 05:55.860 align:middle line:84%
So here we go.

141
05:55.860 --> 05:57.240 align:middle line:84%
I've typed in my password.

142
05:57.240 --> 05:58.830 align:middle line:84%
I'm clicking OK.

143
05:58.830 --> 06:01.230 align:middle line:90%
And it shows me that I am
established and connected
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
05:58.830 --> 06:01.230 align:middle line:90%
And it shows me that I am
established and connected

144
06:01.230 --> 06:02.280 align:middle line:84%
to the VPN.

145
06:02.280 --> 06:05.700 align:middle line:90%
So at this point, I should be
able to browse to 10.10.20.70.

146
06:05.700 --> 06:08.280 align:middle line:90%
Let's do it over HTTPS
just to make sure--

147
06:08.280 --> 06:12.300 align:middle line:84%
https://10.10.20.70.

148
06:12.300 --> 06:14.070 align:middle line:84%
And so far, it's looking good.

149
06:14.070 --> 06:15.960 align:middle line:90%
This should take me
to the ISE login.

150
06:15.960 --> 06:16.930 align:middle line:84%
And there we go.

151
06:16.930 --> 06:18.990 align:middle line:90%
There's Identity
Services Engine.

152
06:18.990 --> 06:20.880 align:middle line:90%
So jumping back to
the DevNet sandbox,

153
06:20.880 --> 06:22.620 align:middle line:84%
I see the username is admin.

154
06:22.620 --> 06:27.550 align:middle line:90%
And the password
is this C1sco12345!

155
06:27.550 --> 06:33.840 align:middle line:90%
So I'll type admin
and C1sco12345!
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
06:27.550 --> 06:33.840 align:middle line:90%
So I'll type admin
and C1sco12345!

156
06:33.840 --> 06:35.070 align:middle line:84%
And login.

157
06:35.070 --> 06:37.278 align:middle line:90%
Of course, Cisco ISE
is a big product.

158
06:37.278 --> 06:38.820 align:middle line:90%
So it's going to
take a minute or two

159
06:38.820 --> 06:40.230 align:middle line:84%
to load the entire database.

160
06:40.230 --> 06:42.270 align:middle line:90%
Once we've got the
dashboard up in front of us,

161
06:42.270 --> 06:45.210 align:middle line:90%
we'll navigate to where the
endpoint profiles are really

162
06:45.210 --> 06:45.760 align:middle line:84%
set.

163
06:45.760 --> 06:46.570 align:middle line:84%
So here we are.

164
06:46.570 --> 06:49.158 align:middle line:90%
We're on the endpoint of
Identity Services Engine.

165
06:49.158 --> 06:49.950 align:middle line:84%
And check this out.

166
06:49.950 --> 06:51.840 align:middle line:90%
Under Work Centers,
this is where you see

167
06:51.840 --> 06:53.580 align:middle line:84%
where the real work gets done.

168
06:53.580 --> 06:56.020 align:middle line:90%
Look at all these categories
that are available to us.

169
06:56.020 --> 06:57.603 align:middle line:90%
A lot of these
categories, we're going

170
06:57.603 --> 06:59.378 align:middle line:90%
to be talking about
in this exact Nugget--

171
06:59.378 --> 07:00.670 align:middle line:84%
things like-- oop, there we go.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
06:59.378 --> 07:00.670 align:middle line:84%
things like-- oop, there we go.

172
07:00.670 --> 07:02.850 align:middle line:90%
I lost my pen-- things
like network access

173
07:02.850 --> 07:03.780 align:middle line:84%
which is over here.

174
07:03.780 --> 07:06.450 align:middle line:90%
We've got Guest Access
and Bring Your Own Device.

175
07:06.450 --> 07:07.980 align:middle line:84%
We'll be talking about that too.

176
07:07.980 --> 07:09.720 align:middle line:90%
TrustSec and
Posture-- yep, we're

177
07:09.720 --> 07:11.380 align:middle line:90%
talking about that
in this skill.

178
07:11.380 --> 07:13.530 align:middle line:90%
But profiling is
what we're talking

179
07:13.530 --> 07:15.300 align:middle line:84%
about in this particular Nugget.

180
07:15.300 --> 07:17.280 align:middle line:90%
And under the
Profiler, that's where

181
07:17.280 --> 07:20.430 align:middle line:90%
we can explore how to go
through the profiling process.

182
07:20.430 --> 07:22.830 align:middle line:90%
And look, it even gives
you like a little overview

183
07:22.830 --> 07:25.830 align:middle line:90%
of how you should set up
profiling in your environment.

184
07:25.830 --> 07:27.600 align:middle line:90%
If I go to Network
Devices real quick,

185
07:27.600 --> 07:29.910 align:middle line:90%
we can take a look at
what devices have already

186
07:29.910 --> 07:32.070 align:middle line:90%
been profiled by ISE
in this environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

186
07:29.910 --> 07:32.070 align:middle line:90%
been profiled by ISE
in this environment.

187
07:32.070 --> 07:35.040 align:middle line:90%
And we see the CentOS
box has already been

188
07:35.040 --> 07:37.380 align:middle line:84%
profiled given a name, Cisco.

189
07:37.380 --> 07:39.603 align:middle line:90%
We see thing, like
what services it's

190
07:39.603 --> 07:40.770 align:middle line:84%
going to be currently using.

191
07:40.770 --> 07:43.770 align:middle line:90%
Radius, TACACS,
TrustSEC, MAB, 802.1X,

192
07:43.770 --> 07:46.110 align:middle line:90%
and WebAuth are all
in the item here.

193
07:46.110 --> 07:48.987 align:middle line:90%
And it also uses something
called Change of Authorization

194
07:48.987 --> 07:51.570 align:middle line:90%
as part of this profile, which
we're going to be talking about

195
07:51.570 --> 07:52.680 align:middle line:84%
later in this Nugget.

196
07:52.680 --> 07:56.310 align:middle line:90%
But let's take a look at things
like the Policy Elements.

197
07:56.310 --> 08:01.950 align:middle line:90%
These are the conditions against
which it can apply a profile.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

197
07:56.310 --> 08:01.950 align:middle line:90%
These are the conditions against
which it can apply a profile.

198
08:01.950 --> 08:03.600 align:middle line:84%
And you can see the system type.

199
08:03.600 --> 08:08.400 align:middle line:90%
These are all profiles that
Cisco provides with ISE.

200
08:08.400 --> 08:10.230 align:middle line:90%
So if I scroll down,
I can see things,

201
08:10.230 --> 08:12.840 align:middle line:90%
like here's a profile that
can check for Amazon Kindle

202
08:12.840 --> 08:13.650 align:middle line:84%
devices.

203
08:13.650 --> 08:16.410 align:middle line:90%
There's Android devices
and specific types

204
08:16.410 --> 08:19.080 align:middle line:90%
of Android devices,
like an HTC device

205
08:19.080 --> 08:21.540 align:middle line:90%
versus an LG device
versus a Lenovo

206
08:21.540 --> 08:24.000 align:middle line:84%
phone versus Samsung Galaxies.

207
08:24.000 --> 08:26.350 align:middle line:90%
I can scroll down into
the Apple devices.

208
08:26.350 --> 08:28.740 align:middle line:90%
We've got Apple TV's,
Mac books, watches.

209
08:28.740 --> 08:30.310 align:middle line:84%
We've got Aruba devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

209
08:28.740 --> 08:30.310 align:middle line:84%
We've got Aruba devices.

210
08:30.310 --> 08:31.950 align:middle line:90%
Now, we get into
the phone systems.

211
08:31.950 --> 08:34.950 align:middle line:90%
And I'm still in the A's before
I even get down into the B's.

212
08:34.950 --> 08:35.940 align:middle line:84%
You get the idea.

213
08:35.940 --> 08:40.409 align:middle line:90%
There are just a gagillion
different profiles

214
08:40.409 --> 08:43.950 align:middle line:90%
that ISE can use to identify
and make assumptions

215
08:43.950 --> 08:46.050 align:middle line:90%
based on what type
of device is trying

216
08:46.050 --> 08:47.220 align:middle line:84%
to connect to the network.

217
08:47.220 --> 08:49.830 align:middle line:90%
And with these
elements, we can create

218
08:49.830 --> 08:53.340 align:middle line:90%
policies about what
types of authentication

219
08:53.340 --> 08:55.690 align:middle line:90%
we can allow in
towards the network.

220
08:55.690 --> 08:58.680 align:middle line:90%
So here's the profiling
policies themselves.

221
08:58.680 --> 09:00.360 align:middle line:84%
Do we want to permit access?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

221
08:58.680 --> 09:00.360 align:middle line:84%
Do we want to permit access?

222
09:00.360 --> 09:02.820 align:middle line:90%
Do we want to place
them in a specific VLAN?

223
09:02.820 --> 09:06.220 align:middle line:90%
This is where you could start to
configure all of these devices

224
09:06.220 --> 09:10.500 align:middle line:90%
and use them in conjunction with
other authentication protocols,

225
09:10.500 --> 09:12.610 align:middle line:84%
like MAC Authentication Bypass.

226
09:12.610 --> 09:16.290 align:middle line:90%
So this sets up how profiling
works with your network access

227
09:16.290 --> 09:19.800 align:middle line:90%
environment and how Cisco ISE
could be the solution for you

228
09:19.800 --> 09:21.090 align:middle line:84%
when it comes to profiling.

229
09:21.090 --> 09:23.090 align:middle line:90%
Again, you're going to
see a lot more about this

230
09:23.090 --> 09:25.740 align:middle line:90%
when you start learning about
MAC Authentication Bypass

231
09:25.740 --> 09:27.872 align:middle line:90%
and how ISE works towards
the end of this playlist.

232
09:27.872 --> 09:29.580 align:middle line:90%
I hope this has been
informative for you,

233
09:29.580 --> 09:32.080 align:middle line:90%
and I'd like to thank
you for viewing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

233
09:29.580 --> 09:32.080 align:middle line:90%
and I'd like to thank
you for viewing.