WEBVTT 1 00:00.000 --> 00:03.040 Starting off, we have NIST 800-145. 2 00:03.040 --> 00:06.880 And this is our standard or basic application guide 3 00:06.880 --> 00:09.760 for implementing our cloud platform 4 00:09.760 --> 00:12.240 and everything related to that cloud platform 5 00:12.240 --> 00:14.480 and suggested security requirements. 6 00:14.480 --> 00:16.720 This is not necessarily a Cisco thing, 7 00:16.720 --> 00:20.960 but an overall standard for the community of IT 8 00:20.960 --> 00:24.000 so that way we can be all on the same page. 9 00:24.000 --> 00:28.160 And Cisco goes even further by delving into some of the tools 10 00:28.160 --> 00:29.840 which we'll be getting into later. 11 00:29.840 --> 00:31.520 But I do want to touch on some of the things WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:29.840 --> 00:31.520 But I do want to touch on some of the things 12 00:31.520 --> 00:34.080 that are covered inside of this special publication. 13 00:34.080 --> 00:36.000 For instance, one of the first things that we cover 14 00:36.000 --> 00:38.160 is on-demand self-service, 15 00:38.160 --> 00:39.840 where we're basically allowing users 16 00:39.840 --> 00:42.720 to automatically provision things like server time 17 00:42.720 --> 00:45.920 and storage requirements without human interaction 18 00:45.920 --> 00:48.480 so that way it's as seamless as possible 19 00:48.480 --> 00:49.840 with each service provider. 20 00:49.840 --> 00:51.840 Now some of this can be things like 21 00:51.840 --> 00:55.840 a user has maxed out their storage requirements 22 00:55.840 --> 00:59.120 and there's a macro setup or some sort of configuration 23 00:59.120 --> 01:01.120 inside of that cloud environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:59.120 --> 01:01.120 inside of that cloud environment 24 01:01.120 --> 01:03.680 that automatically expands storage 25 01:03.680 --> 01:04.960 in certain increments. 26 01:04.960 --> 01:07.360 So that way the user doesn't necessarily think 27 01:07.360 --> 01:08.800 they're running out of storage. 28 01:08.800 --> 01:11.040 It just keeps expanding so that way 29 01:11.040 --> 01:13.120 their requirements are met. 30 01:13.120 --> 01:15.040 Now we're not going to be covering the cost 31 01:15.040 --> 01:16.800 or anything like that because that varies 32 01:16.800 --> 01:19.760 based on who the actual cloud provider is. 33 01:19.760 --> 01:22.160 We're just saying that in this particular skill 34 01:22.160 --> 01:26.320 and course that that can be configured automatically 35 01:26.320 --> 01:28.240 through different configuration points 36 01:28.240 --> 01:30.240 and as we go through we'll be looking WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:28.240 --> 01:30.240 and as we go through we'll be looking 37 01:30.240 --> 01:32.400 at some of those different methods for Cisco 38 01:32.400 --> 01:34.560 outside of the NIST standard. 39 01:34.560 --> 01:37.760 Then we have broad network access which is basically 40 01:37.760 --> 01:40.560 saying that cloud services are accessible over the network 41 01:40.560 --> 01:43.040 and can be used through standard devices 42 01:43.040 --> 01:45.760 like laptops, regular desktop computers 43 01:45.760 --> 01:47.200 and mobile devices. 44 01:47.200 --> 01:51.120 Because as we start to expand on our cellular devices 45 01:51.120 --> 01:53.840 the capabilities of those also expand. 46 01:53.840 --> 01:55.760 You can do more on a cellular device now 47 01:55.760 --> 01:57.760 than you've ever been able to do before 48 01:57.760 --> 01:59.280 and it makes it a little bit easier 49 01:59.280 --> 02:01.520 to access some of those cloud resources. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 01:59.280 --> 02:01.520 to access some of those cloud resources. 50 02:01.520 --> 02:05.120 So if you're working on let's say a tablet 51 02:05.120 --> 02:07.760 and you're accessing a cloud storage device 52 02:07.760 --> 02:09.600 or let's say a server farm 53 02:09.600 --> 02:12.000 and you want to be able to implement a new server 54 02:12.000 --> 02:13.520 and you run out of storage 55 02:13.520 --> 02:16.080 that automatic configuration we just went over 56 02:16.080 --> 02:17.520 should be able to handle that for you 57 02:17.520 --> 02:20.400 according to our NIST standard of usability. 58 02:20.400 --> 02:23.520 800-145 also covers resource pooling 59 02:23.520 --> 02:26.400 and where we provide computer resources 60 02:26.400 --> 02:28.960 in a pooled environment for that cloud environment 61 02:28.960 --> 02:30.160 to be able to operate. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 02:28.960 --> 02:30.160 to be able to operate. 62 02:30.160 --> 02:32.800 So you have many physical systems out there 63 02:32.800 --> 02:34.880 or many virtual machines out there 64 02:34.880 --> 02:36.320 pooling their resources together 65 02:36.320 --> 02:38.080 to be able to provide what looks like 66 02:38.080 --> 02:41.840 one specified service for the actual user. 67 02:41.840 --> 02:45.760 So instead of having 10 different hard drives out there 68 02:45.760 --> 02:46.880 for that storage requirement 69 02:46.880 --> 02:49.200 that we're trying to expand on the fly 70 02:49.200 --> 02:52.560 we have one setup, a virtual setup 71 02:52.560 --> 02:56.560 to where the user sees that one storage space 72 02:56.560 --> 03:00.400 let's say a drive letter D or something like that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 72 02:56.560 --> 03:00.400 let's say a drive letter D or something like that 73 03:00.400 --> 03:01.680 and it just keeps expanding 74 03:01.680 --> 03:03.920 using those multiple physical devices 75 03:03.920 --> 03:06.240 and allows for those different servers 76 03:06.240 --> 03:09.120 or virtual machines to be able to pull the resources together 77 03:09.120 --> 03:10.640 to provide that capability. 78 03:10.640 --> 03:12.480 This means that the data may be spread out 79 03:12.480 --> 03:14.480 over multiple physical devices 80 03:14.480 --> 03:17.840 but for the purposes of the actual user looking 81 03:17.840 --> 03:20.480 at the resource or utilize that resource 82 03:20.480 --> 03:24.480 we're talking about just one in terms of visibility. 83 03:24.480 --> 03:26.240 Now I do want to point out this also works 84 03:26.240 --> 03:28.240 into that multi-tinet model 85 03:28.240 --> 03:31.040 where we're basically using a single system WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 85 03:28.240 --> 03:31.040 where we're basically using a single system 86 03:31.040 --> 03:33.840 physical or virtual machine like we just covered 87 03:33.840 --> 03:35.920 and serving multiple users. 88 03:35.920 --> 03:38.120 So that physical or virtual machine 89 03:38.120 --> 03:41.120 might be able to pool together different resources 90 03:41.120 --> 03:42.520 for multiple different places 91 03:42.520 --> 03:45.200 or systems on the actual cloud environment 92 03:45.200 --> 03:48.560 and pull them together in that one system 93 03:48.560 --> 03:51.320 whether it be a virtual machine or a physical system 94 03:51.320 --> 03:54.920 and provide it to that user and that's multi-tinet. 95 03:54.920 --> 03:58.000 We also want to be able to provide rapid response 96 03:58.000 --> 04:01.480 to the actual user when we do this resource expansion WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 96 03:58.000 --> 04:01.480 to the actual user when we do this resource expansion 97 04:01.480 --> 04:06.160 or making sure that different aspects of cloud usage 98 04:06.160 --> 04:08.000 is made available to the user 99 04:08.000 --> 04:10.160 and that's done through rapid elasticity. 100 04:10.160 --> 04:13.520 Rapid elasticity is allowing us to quickly 101 04:13.520 --> 04:17.280 and easily scale up or down as in terms of a rubber band 102 04:17.280 --> 04:21.400 how much resources or how many different types of resources 103 04:21.400 --> 04:25.000 that we're using based on the actual utilization metrics 104 04:25.000 --> 04:28.320 that the user is either meeting or providing. 105 04:28.320 --> 04:29.600 Think of it like this. 106 04:29.600 --> 04:32.280 If you have a user that has a virtual system WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 106 04:29.600 --> 04:32.280 If you have a user that has a virtual system 107 04:32.280 --> 04:35.960 within that your cloud environment running 200 gigs of RAM 108 04:35.960 --> 04:40.800 and they're only utilizing let's say 25 gigs of it, 109 04:40.800 --> 04:45.000 rapid elasticity will allow you to be able to lower the amount 110 04:45.000 --> 04:48.120 of RAM allocated to that particular usage 111 04:48.120 --> 04:50.480 and allocated somewhere else that's needed 112 04:50.480 --> 04:52.680 inside of that cloud environment. 113 04:52.680 --> 04:54.360 And it also works the other way around 114 04:54.360 --> 04:58.120 if you're limited to 200 gigs of RAM on that particular system 115 04:58.120 --> 05:00.400 and for whatever reason you need more WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 115 04:58.120 --> 05:00.400 and for whatever reason you need more 116 05:00.400 --> 05:03.840 the resource pooling will allow us to be able to expand 117 05:03.840 --> 05:07.640 the amount of RAM allocated to that particular system service 118 05:07.640 --> 05:11.840 or device virtualized within the cloud 119 05:11.840 --> 05:15.200 and expand it on the fly to make it as easy as possible 120 05:15.200 --> 05:16.720 for the user to be able to commit 121 05:16.720 --> 05:20.040 to their resource allocation requirements. 122 05:20.040 --> 05:23.680 Whole point behind that is as much uninterrupted use 123 05:23.680 --> 05:27.320 as possible so that way the user doesn't have any downtime. 124 05:27.320 --> 05:29.840 If you've been through some of our other courses together 125 05:29.840 --> 05:32.680 you know that we're always banging on about the five nines WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 125 05:29.840 --> 05:32.680 you know that we're always banging on about the five nines 126 05:32.680 --> 05:36.120 to 99.99% availability rate. 127 05:36.120 --> 05:39.440 And rapid elasticity allows us to be able to run by that 128 05:39.440 --> 05:40.840 with ease of use. 129 05:40.840 --> 05:44.240 Now all this is done under a measured service 130 05:44.240 --> 05:47.880 and we're taking account of everything that the user 131 05:47.880 --> 05:51.960 or organization that is using our cloud resources 132 05:51.960 --> 05:54.520 is needing or is currently using 133 05:54.520 --> 05:57.520 and maintain an automatic control over those systems 134 05:57.520 --> 06:00.080 to enable things like rapid elasticity WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 134 05:57.520 --> 06:00.080 to enable things like rapid elasticity 135 06:00.080 --> 06:03.960 or the resource pooling or the actual network access 136 06:03.960 --> 06:07.440 for those different systems that way we know 137 06:07.440 --> 06:09.480 and we have accountability of the different things 138 06:09.480 --> 06:11.320 we may or may not need. 139 06:11.320 --> 06:15.920 So we're not just using macros or pre-programmed measures 140 06:15.920 --> 06:19.040 to be able to go out and give organizations 141 06:19.040 --> 06:22.320 or users extra resources or take them away 142 06:22.320 --> 06:24.920 without having some sort of accountability mechanism 143 06:24.920 --> 06:28.800 in place to make sure that that's actually the type of tool 144 06:28.800 --> 06:32.040 or service that we need to do for those different users. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 144 06:28.800 --> 06:32.040 or service that we need to do for those different users. 145 06:32.040 --> 06:34.000 So just keep this in mind as we start going through 146 06:34.000 --> 06:35.520 the rest of the skills together 147 06:35.520 --> 06:39.200 that are basic background and kind of regulation, 148 06:39.200 --> 06:43.600 if you will, is missed 800-145 to make sure 149 06:43.600 --> 06:47.320 that we're staying in line with all the cloud needs 150 06:47.320 --> 06:51.480 of our actual servers, platforms, organizations 151 06:51.480 --> 06:53.040 and individual users.