WEBVTT 1 00:00.000 --> 00:04.960 Now, it could be where an organization that has sensitive information that's 2 00:04.960 --> 00:05.680 required to be 3 00:05.680 --> 00:09.430 stored on site. This could be because of corporate policy. It could be 4 00:09.430 --> 00:12.080 something as complex as 5 00:12.080 --> 00:16.140 jurisdiction requirements, or you could be in the Department of Defense, which 6 00:16.140 --> 00:17.120 technically is a 7 00:17.120 --> 00:21.150 jurisdiction. Now, I'll give you an example from when I was still in because I 8 00:21.150 --> 00:21.920 just retired a 9 00:21.920 --> 00:26.710 couple of years ago. And we would have cloud infrastructures on our unclass 10 00:26.710 --> 00:27.360 ified side, 11 00:27.360 --> 00:31.470 but when it came to actually dealing with soldier information and certain WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:27.360 --> 00:31.470 but when it came to actually dealing with soldier information and certain 12 00:31.470 --> 00:33.200 aspects of soldier 13 00:33.200 --> 00:38.710 information, we were required by federal law in the United States Code Title 10 14 00:38.710 --> 00:39.200 to be able to 15 00:39.200 --> 00:44.320 keep some of those servers on site within DOD custody, meaning we couldn't have 16 00:44.320 --> 00:46.480 data stored on that 17 00:46.480 --> 00:51.040 cloud infrastructure. So if that cloud infrastructure fell apart, we would 18 00:51.040 --> 00:52.640 still have all the information 19 00:52.640 --> 00:58.230 retained physically on site for us to be able to access. Now, that data doesn't 20 00:58.230 --> 00:59.120 necessarily stay 21 00:59.120 --> 01:03.600 there forever. It can be transmitted from point A to point B. But the incorpor WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 21 00:59.120 --> 01:03.600 there forever. It can be transmitted from point A to point B. But the incorpor 22 01:03.600 --> 01:04.560 ation of physical 23 01:04.560 --> 01:09.970 servers and all the environment that is physical on one site integrated with 24 01:09.970 --> 01:11.520 infrastructure as a 25 01:11.520 --> 01:18.780 service does bring up the hybrid environment scenario because we were able to 26 01:18.780 --> 01:19.440 keep all of our 27 01:19.440 --> 01:25.410 physical servers on site for specific reasons, whether they be required or not. 28 01:25.410 --> 01:26.560 And we are able to 29 01:26.560 --> 01:31.830 integrate different resources and utilization inside of infrastructure as a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 01:26.560 --> 01:31.830 integrate different resources and utilization inside of infrastructure as a 30 01:31.830 --> 01:35.040 service. So let's say 31 01:35.040 --> 01:40.650 that we have a web front that allows us our and our organization to be able to 32 01:40.650 --> 01:42.240 have clients access 33 01:42.880 --> 01:48.610 let's say a storefront and we want to be able to have all of our listings of 34 01:48.610 --> 01:50.320 inventory inside of 35 01:50.320 --> 01:54.790 that high infrastructure as a service environment. We have database servers 36 01:54.790 --> 01:55.680 that keep track of 37 01:55.680 --> 02:00.420 inventory of our organization and all that other great stuff. But we're in a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 37 01:55.680 --> 02:00.420 inventory of our organization and all that other great stuff. But we're in a 38 02:00.420 --> 02:02.000 jurisdiction that requires 39 02:02.000 --> 02:08.790 any kind of financial transaction to be maintained on site for that requirement 40 02:08.790 --> 02:10.800 . We don't want all 41 02:10.800 --> 02:15.600 of that private PII to be able to get loose. And if somebody were able to break 42 02:15.600 --> 02:16.640 in or hack into 43 02:16.640 --> 02:22.490 that infrastructure as a service, we can still maintain PII and financial 44 02:22.490 --> 02:24.720 information on site. 45 02:24.720 --> 02:28.500 Again, we're just making up a scenario as we go, but I'm trying to keep it 46 02:28.500 --> 02:30.320 realistic in terms of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 02:28.500 --> 02:30.320 realistic in terms of 47 02:30.320 --> 02:36.540 jurisdiction and regulations. So our hybrid environment allows us to be able to 48 02:36.540 --> 02:38.400 keep database servers 49 02:38.400 --> 02:43.040 and resources that are in physical form inside of our organization and we're 50 02:43.040 --> 02:44.240 utilizing a network 51 02:44.240 --> 02:49.280 connection and integration to be able to have our infrastructure as a service 52 02:49.280 --> 02:51.440 access that database 53 02:51.440 --> 02:56.770 information that's on site. Now our web front are servers that are being hosted 54 02:56.770 --> 02:57.600 by the infrastructure 55 02:57.600 --> 03:02.600 as a service because it's clients responsibility bus in order to maintain those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 55 02:57.600 --> 03:02.600 as a service because it's clients responsibility bus in order to maintain those 56 03:02.600 --> 03:03.840 servers. And we build 57 03:03.840 --> 03:08.960 a connection from those virtual servers to the physical ones on our site using 58 03:08.960 --> 03:11.760 TLS SSL IPsec and 59 03:11.760 --> 03:14.940 all the other wonderful security measures that we've learned about previous to 60 03:14.940 --> 03:17.200 this. Now to go a 61 03:17.200 --> 03:21.360 little bit more in depth to that with everything that we've learned so far, if 62 03:21.360 --> 03:22.880 we have a physical 63 03:22.880 --> 03:26.570 environment on site within our organization, there has to be a network 64 03:26.570 --> 03:28.880 infrastructure to that as well 65 03:28.880 --> 03:33.280 in order to tie into infrastructure as a service. And that's where Nest Comp WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 65 03:28.880 --> 03:33.280 in order to tie into infrastructure as a service. And that's where Nest Comp 66 03:33.280 --> 03:34.880 and Rest Comp come into play 67 03:34.880 --> 03:40.310 at and along with the other API calls and configuration methods that we can 68 03:40.310 --> 03:42.400 utilize to be able to manage 69 03:42.400 --> 03:47.830 all of those network resources, whether they be physical or virtual, we can go 70 03:47.830 --> 03:49.600 through and maintain 71 03:49.600 --> 03:55.330 oversight configuration security compliance both with the physical and virtual 72 03:55.330 --> 03:56.800 from one management 73 03:56.800 --> 04:03.120 point and be able to implement Nest Comp, Rest Comp, whatever the flavor that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 73 03:56.800 --> 04:03.120 point and be able to implement Nest Comp, Rest Comp, whatever the flavor that 74 04:03.120 --> 04:04.160 you refer is. 75 04:04.160 --> 04:08.240 And to make sure that we don't have to go to every device individually.