WEBVTT 1 00:00.000 --> 00:04.760 Now, when we deploy the NSX application platform or as its friends call it, NAP 2 00:04.760 --> 00:05.360 , there's actually 3 00:05.360 --> 00:10.550 four major categories or features that we can get as a result of having that 4 00:10.550 --> 00:11.600 platform in place. 5 00:11.600 --> 00:17.360 And one of those is NSX Intelligence. A second benefit is the feature of NSX 6 00:17.360 --> 00:22.670 network detection and response. Another benefit is NSX Malware Prevention. And 7 00:22.670 --> 00:23.280 a fourth major 8 00:23.280 --> 00:27.450 component and feature is NSX Metrics. So in this set of videos and in the skill 9 00:27.450 --> 00:28.400 , I like to focus on 10 00:28.400 --> 00:32.720 this specific feature first and that is NSX Intelligence. What exactly does WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 10 00:28.400 --> 00:32.720 this specific feature first and that is NSX Intelligence. What exactly does 11 00:32.720 --> 00:33.680 that bring to the table? 12 00:33.680 --> 00:38.240 Why would we want this? So that is a great question. Let's consider what a lot 13 00:38.240 --> 00:38.880 of networks 14 00:38.880 --> 00:43.390 are doing by default. They've got network segments and these could be inside of 15 00:43.390 --> 00:44.080 an NSX 16 00:44.080 --> 00:48.240 environment or traditional networking. So let's say we have network A up here 17 00:48.240 --> 00:49.280 and network B and 18 00:49.280 --> 00:53.210 network C and we have some hosts that are connected to all those networks. Then 19 00:53.210 --> 00:54.000 we have some routing 20 00:54.000 --> 00:58.000 functions between those networks. So we have a connection here and a connection 21 00:58.000 --> 00:58.480 here and a 22 00:58.480 --> 01:02.390 connection here. These could be physical or logical routers either way. And WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 00:58.480 --> 01:02.390 connection here. These could be physical or logical routers either way. And 23 01:02.390 --> 01:02.720 then one of the 24 01:02.720 --> 01:05.540 benefits of networking in general is to be able to communicate across those 25 01:05.540 --> 01:06.960 networks. So maybe over 26 01:06.960 --> 01:11.190 here we have front-end web servers and maybe over here we have some database 27 01:11.190 --> 01:12.320 servers and over here 28 01:12.320 --> 01:15.330 we have yet another type of application server or maybe over here instead of 29 01:15.330 --> 01:16.320 application servers 30 01:16.320 --> 01:19.830 maybe we have a network of clients. And also of course, it's very likely we 31 01:19.830 --> 01:20.800 have connectivity 32 01:20.800 --> 01:24.240 out to the public internet as well. And we want to permit traffic that needs to 33 01:24.240 --> 01:24.560 go out to the 34 01:24.560 --> 01:27.600 internet to be allowed to go through. So here's my question for you. How do we 35 01:27.600 --> 01:28.800 know what the actual 36 01:28.800 --> 01:32.630 traffic patterns are across these network segments? Now we could use things WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:28.800 --> 01:32.630 traffic patterns are across these network segments? Now we could use things 37 01:32.630 --> 01:33.760 like netflow and we could 38 01:33.760 --> 01:37.720 analyze the traffic that way to get a ballpark picture of the traffic patterns 39 01:37.720 --> 01:38.400 and so forth. 40 01:38.400 --> 01:42.350 But if we really want to lock this down and only permit the protocols and 41 01:42.350 --> 01:43.600 services that are needed 42 01:43.600 --> 01:47.670 by the business and then filter or tonight everything else, we need some really 43 01:47.670 --> 01:48.720 good insight as to 44 01:48.720 --> 01:52.570 what's happening. And that's what NSX Intelligence brings to the table. It 45 01:52.570 --> 01:54.160 allows us to visualize 46 01:54.160 --> 01:57.850 the actual network traffic flows about what's really happening between our 47 01:57.850 --> 01:58.640 segments and between 48 01:58.640 --> 02:02.840 our devices in our network. So instead of the NSX Manager using the NSX WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 01:58.640 --> 02:02.840 our devices in our network. So instead of the NSX Manager using the NSX 49 02:02.840 --> 02:04.400 Intelligence as part of the 50 02:04.400 --> 02:10.080 NSX application platform, we can bring up a pane within the NSX Manager and see 51 02:10.080 --> 02:11.680 exactly what's 52 02:11.680 --> 02:15.050 happening and what our traffic flows are. But not only will it help us see 53 02:15.050 --> 02:16.000 exactly what's happening 54 02:16.000 --> 02:19.820 what the traffic flows are, it'll also make recommendations for us regarding 55 02:19.820 --> 02:20.720 security policy 56 02:20.720 --> 02:24.290 rules for a firewall that we can then implement to help improve our micro 57 02:24.290 --> 02:25.280 segmentation and our 58 02:25.280 --> 02:29.180 security controls between devices inside of our network. And the other third 59 02:29.180 --> 02:29.920 main benefit 60 02:29.920 --> 02:33.970 that NSX Intelligence brings to the table is it can help us identify suspicious WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 60 02:29.920 --> 02:33.970 that NSX Intelligence brings to the table is it can help us identify suspicious 61 02:33.970 --> 02:34.800 activity. And all 62 02:34.800 --> 02:38.230 those features are part of the NSX Intelligence, which once again is one of 63 02:38.230 --> 02:39.360 these sub features as 64 02:39.360 --> 02:43.820 part of the NSX application platform. Now one of the challenges by default is 65 02:43.820 --> 02:44.880 that once we have the 66 02:44.880 --> 02:50.250 NSX application platform deployed and functioning in our network, the feature 67 02:50.250 --> 02:51.680 for the NSX Intelligence 68 02:51.680 --> 02:56.590 is not, I repeat, it is not enabled by default. So that's going to be one of 69 02:56.590 --> 02:57.760 our first steps. 70 02:57.760 --> 03:01.890 And that's also where we get to continue our journey in the very next video as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 02:57.760 --> 03:01.890 And that's also where we get to continue our journey in the very next video as 71 03:01.890 --> 03:02.320 we start 72 03:02.320 --> 03:06.120 enabling and then putting NSX Intelligence to work. So I'll see you in the next 73 03:06.120 --> 03:07.360 video in just a moment.