WEBVTT 1 00:00.000 --> 00:03.840 For those of you that have been in my skills or courses before, you know that I 2 00:03.840 --> 00:07.500 like to hone in on data security and overall cyber security. 3 00:07.500 --> 00:12.520 And that's because sometimes I do nefarious things on that side of the house in 4 00:12.520 --> 00:16.500 terms of pin testing, all in the name of security. Am I right? 5 00:16.500 --> 00:21.270 But here in the cloud infrastructure and especially in software as a service 6 00:21.270 --> 00:25.890 where we have limited access inside of the main components of the services 7 00:25.890 --> 00:27.000 being provided, 8 00:27.000 --> 00:30.880 security is one of the most highlighted concerns that we have as an WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:27.000 --> 00:30.880 security is one of the most highlighted concerns that we have as an 9 00:30.880 --> 00:35.000 administrator, especially in Cisco Cloud environment. 10 00:35.000 --> 00:38.570 One of the things you may hear me reiterate a good bit inside of the 11 00:38.570 --> 00:43.000 cybersecurity courses here at CWT Nogins is data classification. 12 00:43.000 --> 00:46.790 And because this allows us to be able to highlight the importance of protecting 13 00:46.790 --> 00:51.190 sensitive data such as personally identifiable information or even financial 14 00:51.190 --> 00:52.000 records. 15 00:52.000 --> 00:56.250 We want to be able to classify data based on its sensitivity and apply the 16 00:56.250 --> 01:00.000 appropriate security controls when needed or necessary. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 01:00.000 --> 01:05.090 And that's especially important inside of software as a service in our cloud, 18 01:05.090 --> 01:07.000 Cisco Cloud environment. 19 01:07.000 --> 01:11.120 And that's because remember it's the clients responsibility to maintain 20 01:11.120 --> 01:15.120 oversight of data and the people, but it's the provider's responsibility to 21 01:15.120 --> 01:17.000 maintain application and beyond. 22 01:17.000 --> 01:22.180 So it's really important for us to make sure that the information going in and 23 01:22.180 --> 01:27.180 out of that actual infrastructure that's being handled by the provider is 24 01:27.180 --> 01:32.660 maintained and properly classified within not only organizational specs for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:27.180 --> 01:32.660 maintained and properly classified within not only organizational specs for 25 01:32.660 --> 01:37.240 security classifications, but also any kind of jurisdiction requirements as we 26 01:37.240 --> 01:42.000 've mentioned before, HIPAA, GDR, GDPR, and whatever the like. 27 01:42.000 --> 01:47.010 Now being that we are using that cloud environment, it goes without saying that 28 01:47.010 --> 01:51.570 the infrastructure in the applications and even the hardware that we're 29 01:51.570 --> 01:56.460 utilizing through our web access is not on site at our current location within 30 01:56.460 --> 01:58.000 the organization. 31 01:58.000 --> 02:02.350 That means that any data going in and out of our processing for that cloud WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 31 01:58.000 --> 02:02.350 That means that any data going in and out of our processing for that cloud 32 02:02.350 --> 02:06.980 environment is going to be on the internet or whatever public network that we 33 02:06.980 --> 02:09.000 used to be able to get there. 34 02:09.000 --> 02:13.450 And that's why it's also important to make sure that that security layer is 35 02:13.450 --> 02:16.000 around that data going back and forth. 36 02:16.000 --> 02:21.220 Now even though it's the provider's responsibility to maintain oversight of the 37 02:21.220 --> 02:27.140 application and beyond, it's as we mentioned inside identity access management 38 02:27.140 --> 02:29.000 earlier in the skill. 39 02:29.000 --> 02:34.230 It's our responsibility as an organization to make sure that let's say we have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 02:29.000 --> 02:34.230 It's our responsibility as an organization to make sure that let's say we have 40 02:34.230 --> 02:39.860 data encryption either through IP, SAC, TLS, going back and forth, making sure 41 02:39.860 --> 02:44.920 that we're getting rid of all those plain text lines of communication going 42 02:44.920 --> 02:46.000 back and forth. 43 02:46.000 --> 02:50.480 And we want to make sure that we take advantage of every security measure 44 02:50.480 --> 02:54.900 possible to us within our organization and that cloud infrastructure 45 02:54.900 --> 02:56.000 environment. 46 02:56.000 --> 03:00.300 Now we would be using things like the Cisco Secure Network Analytics to be able WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 02:56.000 --> 03:00.300 Now we would be using things like the Cisco Secure Network Analytics to be able 47 03:00.300 --> 03:06.110 to track that information going back and forth and also keep an alarm going up 48 03:06.110 --> 03:11.000 anytime that there's a plain text piece of information leaving the organization 49 03:11.000 --> 03:13.000 or coming back inside. 50 03:13.000 --> 03:18.450 We could even set up rules to where we can screen for that PIA, PIA, personally 51 03:18.450 --> 03:23.970 identifiable information or let's say that we have a piece of information that 52 03:23.970 --> 03:29.000 is classified secret or top secret for those inside the DOD realm. 53 03:29.000 --> 03:34.040 See that's exactly what we do or what I used to do inside a DOD. I'm recently WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 03:29.000 --> 03:34.040 See that's exactly what we do or what I used to do inside a DOD. I'm recently 54 03:34.040 --> 03:36.000 retired. Remember that. 55 03:36.000 --> 03:40.530 But whenever we would process information and we wanted to make sure that it 56 03:40.530 --> 03:45.110 had the proper classifications on it, not only would we classify it based on 57 03:45.110 --> 03:49.400 what network it was actually generated on, but the type of information that was 58 03:49.400 --> 03:50.000 put into it. 59 03:50.000 --> 03:54.250 Now a lot of this has to do with the actual policy of data classification 60 03:54.250 --> 04:00.990 within the organization, but it also helps prevent common threats to the people WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 60 03:54.250 --> 04:00.990 within the organization, but it also helps prevent common threats to the people 61 04:00.990 --> 04:03.000 in data inside of our cloud. 62 04:03.000 --> 04:06.810 Now a couple of those common threats may include like fishing and social 63 04:06.810 --> 04:11.080 engineering because if everyday folks are outside of our organization are able 64 04:11.080 --> 04:14.000 to get into our information and read what's going on. 65 04:14.000 --> 04:17.840 As you are able to get let's say one piece of information here, another piece 66 04:17.840 --> 04:21.520 of information there, another piece of information up there and piece it all 67 04:21.520 --> 04:22.000 together. 68 04:22.000 --> 04:27.460 You could potentially piece something together that could damage the our 69 04:27.460 --> 04:31.000 organization if it's you put in wrong hands. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 04:27.460 --> 04:31.000 organization if it's you put in wrong hands. 70 04:31.000 --> 04:35.790 Social engineering does just that even if they're using stuff like open source 71 04:35.790 --> 04:41.000 intelligence or something like fishing sending emails out to the organization. 72 04:41.000 --> 04:45.670 But where does the threat get those emails from? Well, that's where we have to 73 04:45.670 --> 04:50.370 figure out as the customer and the administrator within our organization, what 74 04:50.370 --> 04:53.000 kind of information that we want to protect going in and out. 75 04:53.000 --> 04:58.040 Because we can have all the scripts and all the different measures of adapt 76 04:58.040 --> 05:01.000 ability within this software as a service. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 04:58.040 --> 05:01.000 ability within this software as a service. 77 05:01.000 --> 05:05.550 But at the end of it, it still comes down on us security administrators to make 78 05:05.550 --> 05:11.060 sure that we're maintaining everything within our policy and whatever else is 79 05:11.060 --> 05:14.000 required of us based on the type of information being handled. 80 05:14.000 --> 05:17.370 Now like it or not, one of the biggest threats that's always going to be out 81 05:17.370 --> 05:20.000 there as a potential is going to be an insider threat. 82 05:20.000 --> 05:25.840 So as a security administrator within the cloud infrastructure, we always have 83 05:25.840 --> 05:30.560 to maintain oversight as to making sure that insiders are doing everything that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 05:25.840 --> 05:30.560 to maintain oversight as to making sure that insiders are doing everything that 84 05:30.560 --> 05:35.130 they're supposed to be doing and not doing things that they're not supposed to 85 05:35.130 --> 05:36.000 be doing. 86 05:36.000 --> 05:42.470 So making sure that we explain that internal users must have legitimate access 87 05:42.470 --> 05:47.000 to the data and the people within the organization. 88 05:47.000 --> 05:52.360 But any kind of accident, whether it be on purpose or intentional, could cause 89 05:52.360 --> 05:55.000 a reprimal damage to the organization. 90 05:55.000 --> 05:58.550 And you wouldn't want your own personal information getting out there or your 91 05:58.550 --> 06:02.100 businesses information getting out there, especially if you had something WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 91 05:58.550 --> 06:02.100 businesses information getting out there, especially if you had something 92 06:02.100 --> 06:03.000 proprietary. 93 06:03.000 --> 06:06.530 Regardless of the cloud model that we are utilizing, whether it be software as 94 06:06.530 --> 06:09.000 a service or some of the others will cover later on. 95 06:09.000 --> 06:12.750 A lot of everything that we've been discussing inside of this particular area 96 06:12.750 --> 06:15.000 of our skill falls within data governance. 97 06:15.000 --> 06:20.490 And it's the tools and the responsibilities combined together that allow us to 98 06:20.490 --> 06:25.000 be able to govern our data properly within the organization.