WEBVTT 1 00:00.000 --> 00:04.400 As we start to wrap up this skill together, I wanted to do a slight review and 2 00:04.400 --> 00:07.940 make sure that we covered some of the bigger points and remember what we 3 00:07.940 --> 00:09.000 learned along the way. 4 00:09.000 --> 00:13.990 So when it comes to Cisco and looking at software as a service and the things 5 00:13.990 --> 00:18.250 that we are provided across that public network, this is a cloud-based 6 00:18.250 --> 00:24.380 application provided by Cisco or somebody hosting that Cisco application that's 7 00:24.380 --> 00:29.000 fully managed and developed, delivered over the internet by a service provider. 8 00:29.000 --> 00:32.940 See, there's that different that will come back to here in a minute of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:29.000 --> 00:32.940 See, there's that different that will come back to here in a minute of the 9 00:32.940 --> 00:37.350 difference between the customers' responsibilities and the providers' 10 00:37.350 --> 00:39.000 responsibilities. 11 00:39.000 --> 00:42.800 Think of this as an application that we can access very easily with just an 12 00:42.800 --> 00:44.000 internet browser. 13 00:44.000 --> 00:48.940 And that's one of the distinguishing factors behind software as a service in 14 00:48.940 --> 00:53.960 general is that it's readily accessible and doesn't require much setup on the 15 00:53.960 --> 00:56.000 actual clients end of everything. 16 00:56.000 --> 01:00.690 So the customer's access and used software without needing to manage the under WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:56.000 --> 01:00.690 So the customer's access and used software without needing to manage the under 17 01:00.690 --> 01:05.000 lining infrastructure operating system and application updates. 18 01:05.000 --> 01:10.010 So as a user, there's not that much downtime noticed and there's not that many 19 01:10.010 --> 01:12.000 updates that are sent out. 20 01:12.000 --> 01:15.700 See, we're using things like a workstation, let's say like this one that I'm 21 01:15.700 --> 01:20.380 working on right now, we would normally get notifications for updates every so 22 01:20.380 --> 01:21.000 often. 23 01:21.000 --> 01:26.020 But for software as a service in that Cisco environment and we're accessed and 24 01:26.020 --> 01:31.080 over generally that browser and not responsible for any of the server and under WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:26.020 --> 01:31.080 over generally that browser and not responsible for any of the server and under 25 01:31.080 --> 01:36.500 applications end, it's kind of seamless and transparent to the user that's 26 01:36.500 --> 01:40.000 accessing those services and doesn't really come up as an issue. 27 01:40.000 --> 01:46.580 Now the owner/IT manager of the organization is going to be kept afloat of some 28 01:46.580 --> 01:52.880 of these down times by the actual service provider and that's where we as those 29 01:52.880 --> 01:57.540 professionals in the IT field need to make sure that we're doing that service 30 01:57.540 --> 02:01.160 level agreement between us and the organization that we're utilizing for this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 30 01:57.540 --> 02:01.160 level agreement between us and the organization that we're utilizing for this 31 02:01.160 --> 02:02.000 software as a service. 32 02:02.000 --> 02:06.180 This also means that the service provider is also going to be responsible 33 02:06.180 --> 02:11.000 primarily responsible for security patches and infrastructure management. 34 02:11.000 --> 02:14.860 Now when we talk about infrastructure management, we're not talking about 35 02:14.860 --> 02:17.000 internal to the organization itself. 36 02:17.000 --> 02:22.260 So anything happens inside of the building as far as like network upgrades and 37 02:22.260 --> 02:26.440 system upgrades to the overall system that's sitting on our desk does not 38 02:26.440 --> 02:30.790 involve the actual provider and the applications and infrastructure that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 02:26.440 --> 02:30.790 involve the actual provider and the applications and infrastructure that's 39 02:30.790 --> 02:31.000 running inside of the organization itself. 40 02:31.000 --> 02:34.080 So that's running inside of that cloud environment. Those are two completely 41 02:34.080 --> 02:35.000 separate things. 42 02:35.000 --> 02:39.870 One thing that we are responsible for as a client within that software as a 43 02:39.870 --> 02:44.350 service provider is making sure that user access control and data security is 44 02:44.350 --> 02:50.180 maintained and dealt with because whoever we're getting this service from, they 45 02:50.180 --> 02:53.590 're from providers themselves, they don't know who we need have access to 46 02:53.590 --> 02:58.590 whatever data is out there and they don't know what kind of information that we 47 02:58.590 --> 03:00.000 need classified based on the contents of that service provider. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 03:00.000 --> 03:06.330 It's not up to them. They're just the host and make sure that everything 49 03:06.330 --> 03:11.200 matches their terms of service or user level agreements or whatever 50 03:11.200 --> 03:13.000 jurisdiction that they're in. 51 03:13.000 --> 03:17.450 Now I do want to point out obviously that if there's something, let's say we're 52 03:17.450 --> 03:21.650 here in Texas right now and if there's a law in Texas and states that you can't 53 03:21.650 --> 03:26.190 store illegal information on a cloud based server, the cloud infrastructure is 54 03:26.190 --> 03:29.000 responsible to a certain extent to make sure that illegal information is 55 03:29.000 --> 03:29.000 available. 56 03:29.000 --> 03:32.100 That illegal information isn't stored on their services and if they notice WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 56 03:29.000 --> 03:32.100 That illegal information isn't stored on their services and if they notice 57 03:32.100 --> 03:34.000 something they have to call law enforcement. 58 03:34.000 --> 03:37.790 I don't want to get into the nitty gritty as far as like determining what is or 59 03:37.790 --> 03:41.000 isn't illegal information, but I do want to put that out. 60 03:41.000 --> 03:47.480 And the proper identification falls on us as the client to maintain and use 61 03:47.480 --> 03:52.830 stuff like IAM, identity access management, data classification, auditing of 62 03:52.830 --> 03:57.000 services to maintain that security and threat identification in response. 63 03:57.000 --> 04:01.770 And that's what we're going to kind of start to close out on is our shortened WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 03:57.000 --> 04:01.770 And that's what we're going to kind of start to close out on is our shortened 64 04:01.770 --> 04:06.810 review because identity identifying those threats is something that we have 65 04:06.810 --> 04:11.000 limited scope and ability to do as far as the actual client is concerned 66 04:11.000 --> 04:16.630 because we're only responsible for those users and people are excuse me users 67 04:16.630 --> 04:17.000 and data. 68 04:17.000 --> 04:21.960 And the actual infrastructure from applications, the hardware, the actual 69 04:21.960 --> 04:26.260 software that's running in the background can't be really tested or 70 04:26.260 --> 04:32.000 vulnerability assessed except for the owners of that actual system itself. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 70 04:26.260 --> 04:32.000 vulnerability assessed except for the owners of that actual system itself. 71 04:32.000 --> 04:35.050 So the only thing that we're going to be keeping track of is things that are 72 04:35.050 --> 04:37.000 going in and outside of our organization. 73 04:37.000 --> 04:42.500 Let's say there's a Millignnet file that's going in and out of our data network 74 04:42.500 --> 04:46.000 that's going to that cloud infrastructure. 75 04:46.000 --> 04:51.580 Hopefully we as the security technicians and service managers inside of that 76 04:51.580 --> 04:57.000 client responsibility realm identified that and have a work and arrangement 77 04:57.000 --> 05:02.000 with the actual provider to make sure that we can identify those threats. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 04:57.000 --> 05:02.000 with the actual provider to make sure that we can identify those threats. 78 05:02.000 --> 05:06.650 Because something that's stored inside the cloud that's malicious in nature can 79 05:06.650 --> 05:10.760 infect our host systems, even though we're just using something as simple as a 80 05:10.760 --> 05:13.000 web browser to access those services. 81 05:13.000 --> 05:16.000 Now to close this out and I'm going to put this on screen. 82 05:16.000 --> 05:19.430 And we're going to take a look at it for just a second and see if we can 83 05:19.430 --> 05:25.500 identify where our client responsibilities and provider responsibilities split 84 05:25.500 --> 05:26.000 off at. 85 05:26.000 --> 05:29.600 Because we started this off at the skill by identifying that this is what 86 05:29.600 --> 05:32.000 uniquely identifies software as a service. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 86 05:29.600 --> 05:32.000 uniquely identifies software as a service. 87 05:32.000 --> 05:35.390 So I'm going to give you just a second and then I'll go ahead and put it on the 88 05:35.390 --> 05:38.000 screen. Ready? Right there. 89 05:38.000 --> 05:42.900 Because the customer's responsibility, that's you and I, we're responsible for 90 05:42.900 --> 05:47.000 the people in data and the provider is responsible for applications, runtime, 91 05:47.000 --> 05:51.160 middleware, OS, virtual network and all the hardware that is involved with 92 05:51.160 --> 05:52.000 everything that we do. 93 05:52.000 --> 05:56.110 We're trying to make this as simple as possible and deliver it as easily as 94 05:56.110 --> 06:00.690 possible to the actual client, which is why software as a service provides that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 94 05:56.110 --> 06:00.690 possible to the actual client, which is why software as a service provides that 95 06:00.690 --> 06:04.000 quick and easy adaptability for an organization overall. 96 06:04.000 --> 06:07.780 I hope this has been informative for you and I'd like to thank you for doing it 97 06:07.780 --> 06:08.000 .