WEBVTT

00:03.160 --> 00:09.580
The big joke about simple network management protocol used to be security.

00:09.730 --> 00:11.230
Not my problem.

00:11.410 --> 00:11.770
Yeah.

00:12.040 --> 00:19.810
Simple network management protocol has been a wonder for network managers because the graphical user

00:19.810 --> 00:25.920
interface often time based programs that make it function for them.

00:25.930 --> 00:27.160
It's a godsend.

00:27.490 --> 00:30.430
The network management station.

00:30.430 --> 00:33.950
And you need to know these S&amp;P terms.

00:34.000 --> 00:36.010
Otherwise, I wouldn't be covering them with you.

00:36.490 --> 00:42.540
So the network management station is where the network manager is located.

00:42.550 --> 00:51.340
Of course, this is a nice graphical user interface and it is sending S&amp;P commands down to agent software.

00:52.300 --> 00:59.260
And the agent software communicates with a database called the Management Information Base.

00:59.980 --> 01:06.250
I used to make a men and black joke here, but I can no longer do that because Will Smith slapped Chris

01:06.250 --> 01:06.700
Rock.

01:06.940 --> 01:09.550
And now I don't mention Will Smith movies.

01:09.730 --> 01:10.720
Oh, wait, I just did.

01:10.960 --> 01:11.950
All right, well, whatever.

01:12.370 --> 01:12.820
All right.

01:12.820 --> 01:18.340
So, yeah, the agent is communicating with the management information base.

01:18.370 --> 01:23.440
Now, keep in mind, these two things are on the network.

01:23.890 --> 01:25.090
The network node.

01:25.090 --> 01:33.070
And I say node here, not necessarily like device, because I just want you to know that it is flexible

01:33.070 --> 01:36.900
as far as what the agent and Mitb can be installed on.

01:36.910 --> 01:40.690
So I want to be very broad here and just say a network node.

01:40.690 --> 01:45.310
It could be a client, could be a server, could be a router, could be a firewall.

01:45.730 --> 01:48.400
The list just goes on and on.

01:49.150 --> 02:00.370
So one of the problems and why we used to refer to this protocol as security's not my problem is the

02:00.370 --> 02:08.740
classically used versions of one end to see both of these versions, which we were stuck with for decades.

02:08.980 --> 02:12.550
Both of them are clear text based.

02:13.300 --> 02:14.110
That's right.

02:14.210 --> 02:14.810
Yuck.

02:15.040 --> 02:16.630
I mean, impossible.

02:16.630 --> 02:17.440
No way.

02:17.470 --> 02:18.310
Can't deal with that.

02:18.550 --> 02:25.870
They use community strings as passwords and there's no real security.

02:26.380 --> 02:29.380
So that's why the joke has always been security.

02:29.380 --> 02:30.310
Not my problem.

02:30.670 --> 02:36.870
You can configure a read only password called a community string.

02:36.910 --> 02:37.930
Let me write that.

02:38.320 --> 02:41.920
So it's just kind of burned in your brain.

02:42.310 --> 02:44.680
The passwords are called community strings.

02:44.920 --> 02:50.080
And then there's a read write community string, otherwise known as a password.

02:50.680 --> 02:58.570
And that's it really for the security mechanisms of version one and two.

02:58.600 --> 02:59.950
See, that's a nightmare.

02:59.950 --> 03:03.490
And we want to try and get that stuff out of our network, by the way.

03:03.520 --> 03:04.780
Sorry, I'm writing Crooked.

03:05.050 --> 03:06.070
I'll stop doing that.

03:06.100 --> 03:06.730
That's weird.

03:07.120 --> 03:07.600
All right.

03:07.930 --> 03:09.340
So, what else?

03:09.580 --> 03:16.210
Well, SMP version three can no longer be easily joked about as far as security goes.

03:16.210 --> 03:23.320
And that's because we now have version three and version three.

03:23.470 --> 03:28.780
It's like they were insulted for being made fun of for so long.

03:29.080 --> 03:32.230
This thing has robust security.

03:32.470 --> 03:39.880
You can configure it like with no security, some security, more security.

03:40.030 --> 03:45.970
And then you could go crazy security and know those aren't the official terms.

03:46.270 --> 03:48.820
It's just that there's a bunch of different modes.

03:48.970 --> 03:56.620
You don't need to know them all at this point, but just understand that there is like auth no priv

03:56.620 --> 04:01.180
which means there's authentication done but no encryption.

04:01.510 --> 04:07.300
And then you can do strong authentication and strong encryption which would be auth priv.

04:07.660 --> 04:15.700
So there's all these different, you know, interestingly named modes and that gives you varying levels

04:15.700 --> 04:20.290
of security and varying levels of authentication and encryption.

04:20.290 --> 04:23.650
And as I said, it can get crazy secure now.

04:23.950 --> 04:32.620
So as an MP, version three is definitely where we want to be pushing for when it comes to S&amp;P usage.

04:32.860 --> 04:40.360
That's because everything could be securely authenticated and encrypted and would be nearly impossible

04:40.390 --> 04:42.610
to enumerate in any way.

04:43.000 --> 04:43.710
Think about it.

04:43.960 --> 04:54.820
This nib that the agent is next to contains just hundreds of thousands of variables.

04:55.090 --> 05:00.010
These variables give all kinds of information about that node.

05:00.220 --> 05:02.620
That's the whole point of SMP by the.

05:02.660 --> 05:05.720
Way is for all these probes.

05:05.720 --> 05:09.740
And by the way, we should know this term traps.

05:10.100 --> 05:13.040
Traps are sent by the agent.

05:13.370 --> 05:17.390
They're non requested, so they just happen.

05:17.660 --> 05:20.570
And these are great for network administrators.

05:20.810 --> 05:27.470
They might go in and say if the temperature in the data center ever hits 80 degrees.

05:27.770 --> 05:28.160
Right.

05:28.160 --> 05:34.190
If it ever hits 80 degrees Fahrenheit, then absolutely sound off an alarm.

05:34.190 --> 05:37.340
And that would be a simple network management protocol trap.

05:38.180 --> 05:47.780
So these kinds of mechanisms, they're going to contain a lot of information by design about these devices.

05:47.780 --> 05:50.630
This information must be kept secure.

05:51.080 --> 05:58.160
Otherwise great enumeration could be done against S&amp;P and S&amp;P systems.
