WEBVTT 1 00:00.000 --> 00:03.550 In our previous skill, kicking off this domain, we went over a brief 2 00:03.550 --> 00:09.500 introduction of the three different types of as a service models that are out 3 00:09.500 --> 00:11.000 there within that cloud environment. 4 00:11.000 --> 00:15.880 And the first one that we're going to be diving into in more detail, especially 5 00:15.880 --> 00:21.000 when it comes to that Cisco methodology, is software as a service. 6 00:21.000 --> 00:25.280 Now I'm going to be going through these in order and working our way up to more 7 00:25.280 --> 00:31.090 responsibility overall based on who the customer and provider cover as far as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:25.280 --> 00:31.090 responsibility overall based on who the customer and provider cover as far as 8 00:31.090 --> 00:34.020 the different services and roles to those different users that are 9 00:34.020 --> 00:36.000 participating in that cloud service. 10 00:36.000 --> 00:40.410 Now up on the screen, we have our first model where we're going to take a look 11 00:40.410 --> 00:44.000 at SAS, our software as a service and the shared responsibility model. 12 00:44.000 --> 00:48.320 Generally in this model, we're going to be dealing with people and data more 13 00:48.320 --> 00:52.720 than we are the actual applications and everything else that's involved with 14 00:52.720 --> 00:56.000 the actual infrastructure of a cloud environment. 15 00:56.000 --> 00:59.720 It's going to be the provider's responsibility to maintain the physical 16 00:59.720 --> 01:03.500 infrastructure, including the servers and the storage and all around oper WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:59.720 --> 01:03.500 infrastructure, including the servers and the storage and all around oper 17 01:03.500 --> 01:07.660 ability of the equipment that backs everything that we're trying to do for the 18 01:07.660 --> 01:11.000 data and the people that is the customer's responsibility. 19 01:11.000 --> 01:14.510 And we're going to be securing application settings and ensuring compliance 20 01:14.510 --> 01:16.000 with industry regulations. 21 01:16.000 --> 01:20.830 This could mean that we're working with GDPR if we're inside of the European 22 01:20.830 --> 01:25.000 Union or HIPAA for example if we're here in the United States. 23 01:25.000 --> 01:28.490 Now there's some definite advantages to being able to utilize a software as a 24 01:28.490 --> 01:31.000 service, especially in that Cisco environment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:28.490 --> 01:31.000 service, especially in that Cisco environment. 25 01:31.000 --> 01:34.000 Primarily, it's going to come down to a cost factor. 26 01:34.000 --> 01:38.440 When we're dealing with software as a service, one of the primary 27 01:38.440 --> 01:43.000 responsibilities of the organization is to maintain a budget. 28 01:43.000 --> 01:48.110 The cost efficiency side of this is accomplished through reducing the need for 29 01:48.110 --> 01:51.000 extensive hardware and IT maintenance. 30 01:51.000 --> 01:55.210 A lot of the maintenance and actual hardware requirements and let's say 31 01:55.210 --> 01:59.700 something breaks and it has to get replaced is going to be taken care of by the 32 01:59.700 --> 02:02.000 actual provider in this scenario. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:59.700 --> 02:02.000 actual provider in this scenario. 33 02:02.000 --> 02:06.250 So we could be running, let's say for example inside of the Cisco world, a VoIP 34 02:06.250 --> 02:12.840 environment where for the end user, for the software as a service, we're going 35 02:12.840 --> 02:19.000 to be using the VoIP software client on the actual end point workstations. 36 02:19.000 --> 02:23.190 So who's responsible for fixing the actual VoIP system if the phone service 37 02:23.190 --> 02:24.000 goes down? 38 02:24.000 --> 02:28.110 Well, that's on the provider where we're responsible for just maintaining the 39 02:28.110 --> 02:31.800 phone book, making sure the users get their connectivity on the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 02:28.110 --> 02:31.800 phone book, making sure the users get their connectivity on the actual 40 02:31.800 --> 02:36.730 application itself through our provider and maintaining the phone book and user 41 02:36.730 --> 02:38.000 registration. 42 02:38.000 --> 02:42.240 Now there's way more in-depth this that we'll cover as we go throughout, but 43 02:42.240 --> 02:46.570 that's just a quick overview of software as a service as we're considering the 44 02:46.570 --> 02:48.000 Cisco environment. 45 02:48.000 --> 02:52.550 But the advantages don't just stop at the affordability, respectively depending 46 02:52.550 --> 02:55.000 on what kind of service we're utilizing. 47 02:55.000 --> 02:58.000 It also goes into actual software updates. 48 02:58.000 --> 03:02.580 As we took a look at our model since we're focusing in on the actual data and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 02:58.000 --> 03:02.580 As we took a look at our model since we're focusing in on the actual data and 49 03:02.580 --> 03:07.760 users, the software updates that are in the application are maintained also by 50 03:07.760 --> 03:09.000 that provider. 51 03:09.000 --> 03:13.980 We still have a responsibility as we'll go through throughout the skill in 52 03:13.980 --> 03:19.530 making sure that vulnerabilities are addressed and found if there are any that 53 03:19.530 --> 03:21.000 exist out there. 54 03:21.000 --> 03:24.650 But if something needs to be taken care of on that particular end, it's going 55 03:24.650 --> 03:29.210 to be the provider that's responsible for it, whereas we're more of a physical 56 03:29.210 --> 03:32.000 security maintainer in this aspect. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 03:29.210 --> 03:32.000 security maintainer in this aspect. 57 03:32.000 --> 03:35.880 It kind of leads us to one of the key security concerns of what's actually 58 03:35.880 --> 03:39.800 going on in software as a service, and it's ensuring that the data of the 59 03:39.800 --> 03:42.000 customer is protected at all cost. 60 03:42.000 --> 03:46.910 One of the ways that we do this is by encryption and making sure that the data, 61 03:46.910 --> 03:51.880 whether it be at-rested motion, is encrypted to make sure that we are 62 03:51.880 --> 03:58.000 maintaining that CIA triad of confidentiality integrity and accessibility. 63 03:58.000 --> 04:02.340 Because even though the infrastructure of everything is being ran by the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 03:58.000 --> 04:02.340 Because even though the infrastructure of everything is being ran by the 64 04:02.340 --> 04:06.730 provider, we are still held responsible for ensuring that the CIA triad in 65 04:06.730 --> 04:09.000 software as a service is maintained. 66 04:09.000 --> 04:13.480 Because if we get rid of the access to that actual software platform, then we 67 04:13.480 --> 04:16.000 're kind of cutting off accessibility. 68 04:16.000 --> 04:22.000 And in security, we do maintain practice through encryption and also through 69 04:22.000 --> 04:25.000 hashing for that integrity as well. 70 04:25.000 --> 04:29.630 In more detail, we get into the identity and access management of what's 71 04:29.630 --> 04:34.570 actually going on because us as the actual administrators in the software as a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 04:29.630 --> 04:34.570 actually going on because us as the actual administrators in the software as a 72 04:34.570 --> 04:39.840 service platform, we're maintaining who has access and who has rights and who 73 04:39.840 --> 04:44.000 has basically every permission that they need, even though we're not 74 04:44.000 --> 04:47.000 maintaining the actual service themselves, if that makes sense. 75 04:47.000 --> 04:53.340 Because while the application and above in our model is being dealt with by the 76 04:53.340 --> 04:57.490 actual provider, who is it that's going to relay that information to the 77 04:57.490 --> 05:01.790 provider that has a, let's say we have a new employee come in and has to have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 04:57.490 --> 05:01.790 provider that has a, let's say we have a new employee come in and has to have 78 05:01.790 --> 05:03.000 certain access. 79 05:03.000 --> 05:09.180 It's going to be us as the, on the ground technicians, maintaining oversight of 80 05:09.180 --> 05:14.090 the data and people. And although we don't have too much dealings with the 81 05:14.090 --> 05:19.310 actual applications as hosting our services, we do have a little bit of deal 82 05:19.310 --> 05:21.000 ings with the API. 83 05:21.000 --> 05:26.470 And we'll begin the API a little bit more as the skill unfolds. Just know that 84 05:26.470 --> 05:31.980 right now that most SaaS platforms provide APIs for integration as far as what WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 84 05:26.470 --> 05:31.980 right now that most SaaS platforms provide APIs for integration as far as what 85 05:31.980 --> 05:37.910 kind of programs we're using to incorporate that data and also making an API 86 05:37.910 --> 05:42.000 security, a critical concern. 87 05:42.000 --> 05:45.750 So let's go ahead and strap in and do it to it and start looking at Cisco 88 05:45.750 --> 05:49.880 inside of that software as a service and getting into some of the details and 89 05:49.880 --> 05:52.000 more importantly some examples.