WEBVTT 1 00:00.000 --> 00:04.480 Now going over all those different ways to actually add security may beg the 2 00:04.480 --> 00:09.220 question of inside of our platform as a service model that we have inside of 3 00:09.220 --> 00:10.160 our sandbox. 4 00:10.160 --> 00:14.040 How do we take care of it? Well, I'm glad you asked again as we move over to 5 00:14.040 --> 00:14.920 the side screen. 6 00:14.920 --> 00:21.160 Down there. And as you can see here, we're back to where we actually started in 7 00:21.160 --> 00:25.560 the actual catalyst center sandbox inside of our demo here. 8 00:25.760 --> 00:31.440 But one of the things that we have that we have really touched on yet is the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:25.760 --> 00:31.440 But one of the things that we have that we have really touched on yet is the 9 00:31.440 --> 00:38.560 ice server ice ice baby. And we're taking a look at the ISE here for Cisco. 10 00:38.560 --> 00:43.350 And as we know already, we ice is more of our secure platform in order to 11 00:43.350 --> 00:46.520 implement many, many different things. 12 00:46.520 --> 00:52.000 We can normally use it to manage different network devices, implement security 13 00:52.000 --> 00:54.680 and also apply things like 8021x. 14 00:55.080 --> 00:59.390 But as we're sitting here in inside of the dashboard, I also want to point out 15 00:59.390 --> 01:03.430 real quick that you can actually select the device and go down and see the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:59.390 --> 01:03.430 real quick that you can actually select the device and go down and see the 16 01:03.430 --> 01:06.200 different attributes to this actual device. 17 01:06.200 --> 01:11.240 So even the point to where you can see the VMDK that it's running right there, 18 01:11.240 --> 01:14.870 because that'll give you more information as you start to enter that 19 01:14.870 --> 01:19.170 infrastructure as a service and see what this is actually sitting that on those 20 01:19.170 --> 01:23.680 actual physical servers inside of either the type one or type two. 21 01:24.960 --> 01:30.330 A hypervisor and virtualization infrastructure. So if we go back to just click WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 21 01:24.960 --> 01:30.330 A hypervisor and virtualization infrastructure. So if we go back to just click 22 01:30.330 --> 01:34.960 anywhere else, you can go back to the access details and see where all the 23 01:34.960 --> 01:38.720 information is to be able to access these different systems. 24 01:38.720 --> 01:44.400 Find the IP address, log in and password information for your actual ice. And 25 01:44.400 --> 01:49.360 do remember that we still have to be connected to our VPN that this is for in 26 01:49.360 --> 01:51.160 order to be able to access all this. 27 01:51.880 --> 01:57.070 And I already have my ice opened up here. Now, this doesn't have a lot of 28 01:57.070 --> 02:01.120 different things inside of it because we're in a sandbox environment and there WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 01:57.070 --> 02:01.120 different things inside of it because we're in a sandbox environment and there 29 02:01.120 --> 02:03.040 's not that many devices on here. 30 02:03.040 --> 02:07.470 My fact, we go back to our catalyst center. And I'll show you how I got to this 31 02:07.470 --> 02:12.400 in just a second, but we only have four switches inside of our mock network. 32 02:12.400 --> 02:18.370 And I get went to the top left. I went to provision and then the inventory. And 33 02:18.370 --> 02:20.440 that's where these four switches came up at. 34 02:20.920 --> 02:26.230 Switching back over to our ice, we can actually go in here and use this to be 35 02:26.230 --> 02:31.740 able to identify key points of different endpoints and their configurations and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 02:26.230 --> 02:31.740 able to identify key points of different endpoints and their configurations and 36 02:31.740 --> 02:33.080 security measures. 37 02:33.080 --> 02:37.490 And we'll take a look at how we can actually dive in on the security. Now on 38 02:37.490 --> 02:41.640 our top left, where we have the Cisco ice label, we're going to click on the 39 02:41.640 --> 02:43.160 three little lines there. 40 02:43.600 --> 02:47.080 And make sure it'll start off with context visibility, but we're going to go 41 02:47.080 --> 02:51.060 over to the administration tab. Now in here, you can see where we have a lot of 42 02:51.060 --> 02:55.170 what we were talking about while ago as far as like the actual prevention of 43 02:55.170 --> 03:00.940 access to inside the API and on those different devices for overall access in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 02:55.170 --> 03:00.940 access to inside the API and on those different devices for overall access in 44 03:00.940 --> 03:01.640 general. 45 03:02.000 --> 03:05.680 And we can go in here and look at how we want to kind of configure some of 46 03:05.680 --> 03:10.370 these things. We can actually go into device portal management and see our 47 03:10.370 --> 03:16.580 block list, bring your devices certificate, prevention, provisioning and also 48 03:16.580 --> 03:22.760 go up into the actual radius servers, radius server sequences. 49 03:22.760 --> 03:26.420 Now the reason that we're not really diving into these too much is because 50 03:26.420 --> 03:29.780 based on our sandbox mode, we're very much limited on the amount of 51 03:29.780 --> 03:31.240 availability that we have. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 03:29.780 --> 03:31.240 availability that we have. 52 03:31.720 --> 03:35.990 See, in full implementation, we'd have multiple devices implemented and we'd be 53 03:35.990 --> 03:39.000 able to go through and configure a lot of these things. 54 03:39.000 --> 03:42.760 But this is just a quick overview to show you that some of the things that we 55 03:42.760 --> 03:46.780 mentioned in our API security concerns and just overall security concerns in 56 03:46.780 --> 03:51.600 general can be addressed inside of our ice server inside of our platform. 57 03:51.960 --> 03:56.580 And this is still inside of our platform as a service model because we're 58 03:56.580 --> 04:01.750 actually in the application of it instead of the actual hardware, which is more WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 03:56.580 --> 04:01.750 actually in the application of it instead of the actual hardware, which is more 59 04:01.750 --> 04:04.200 in line with the infrastructure as a service. 60 04:04.200 --> 04:08.890 Yes, we're still using that actual browser to get to where we're at right here, 61 04:08.890 --> 04:13.160 but we can actually go through and make changes inside the actual program 62 04:13.160 --> 04:18.860 itself to implement for software as a service, which is more at the user end of 63 04:18.860 --> 04:21.160 our infrastructure, our excuse me, our 64 04:21.400 --> 04:25.640 cloud service modeling that we have implemented within our organization 65 04:25.640 --> 04:26.560 currently. 66 04:26.560 --> 04:31.070 So we're able to go in and actually take a look at policy sets, make sure it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 66 04:26.560 --> 04:31.070 So we're able to go in and actually take a look at policy sets, make sure it 67 04:31.070 --> 04:32.800 makes some policy changes. 68 04:32.800 --> 04:37.240 And one thing I want to also point out too is if I close this right here, I 69 04:37.240 --> 04:42.280 want to hone in on the fact that this could also do vulnerability and threat. 70 04:42.280 --> 04:45.080 But we're going to come back to that here in just a little bit.