WEBVTT 1 00:00.000 --> 00:06.480 Finally, let's wrap up by looking at Google Cloud. 2 00:06.480 --> 00:13.110 Now, from a network hierarchy perspective, Google Cloud is almost identical to 3 00:13.110 --> 00:13.840 Amazon's 4 00:13.840 --> 00:19.880 AWS in that it has regions and availability zones and so on. 5 00:19.880 --> 00:25.640 So our main focus here is really just going to be on the Google Cloud firewall 6 00:25.640 --> 00:26.000 and the 7 00:26.000 --> 00:30.620 different features and versions that are available and what each of those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:26.000 --> 00:30.620 different features and versions that are available and what each of those 8 00:30.620 --> 00:31.360 offers. 9 00:31.360 --> 00:36.160 So let's just go ahead and jump in and take a look. 10 00:36.160 --> 00:43.320 So Google Cloud's firewall comes in two major offerings, Essentials and the 11 00:43.320 --> 00:45.600 standard version. 12 00:45.600 --> 00:51.000 So first, let's talk about what's included in both versions. 13 00:51.000 --> 00:57.000 Both versions include first, it is a distributed firewall service. 14 00:57.000 --> 01:01.740 This means that it's available across different regions and so on in Google WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:57.000 --> 01:01.740 This means that it's available across different regions and so on in Google 15 01:01.740 --> 01:02.480 Cloud, which is 16 01:02.480 --> 01:04.520 a really nice feature. 17 01:04.520 --> 01:08.200 It's very simple to configure, very simple to manage. 18 01:08.200 --> 01:10.680 That one pretty much speaks for itself. 19 01:10.680 --> 01:15.280 It supports micro segmentation, which as we mentioned is very important for 20 01:15.280 --> 01:16.080 controlling 21 01:16.080 --> 01:18.000 the East West traffic. 22 01:18.000 --> 01:20.960 So again, another nice feature. 23 01:20.960 --> 01:24.840 It supports context aware dynamic objects. 24 01:24.840 --> 01:30.780 So for example, you could put together a group that includes web servers and if WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:24.840 --> 01:30.780 So for example, you could put together a group that includes web servers and if 25 01:30.780 --> 01:31.760 you classify 26 01:31.760 --> 01:35.950 one of your servers as a web server, it will automatically put it into that 27 01:35.950 --> 01:36.920 group and treat 28 01:36.920 --> 01:38.400 it the same way. 29 01:38.400 --> 01:41.400 So again, some really cool features here. 30 01:41.400 --> 01:46.630 Now since it is distributed, it's also important to note that it does support 31 01:46.630 --> 01:48.120 both global and 32 01:48.120 --> 01:49.880 regional policies. 33 01:49.880 --> 01:54.820 So you don't have to have a global policy, but it is also supported if that's 34 01:54.820 --> 01:55.360 what you 35 01:55.360 --> 01:57.000 want to do. 36 01:57.000 --> 02:01.680 It also supports tags, like a lot of the other features we've been looking at. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:57.000 --> 02:01.680 It also supports tags, like a lot of the other features we've been looking at. 37 02:01.680 --> 02:07.600 It supports address groups, which are very similar to the content aware dynamic 38 02:07.600 --> 02:08.440 objects, 39 02:08.440 --> 02:12.490 but basically you're grouping things together by their address rather than 40 02:12.490 --> 02:14.680 their object type. 41 02:14.680 --> 02:20.920 And it supports VPC firewall rules within the VPCs themselves. 42 02:20.920 --> 02:25.710 Now what do we get in addition if we go with the standard version because the 43 02:25.710 --> 02:26.400 standard 44 02:26.400 --> 02:31.120 version is the upgraded version, so to speak. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 02:26.400 --> 02:31.120 version is the upgraded version, so to speak. 45 02:31.120 --> 02:33.440 Well, this is going to sound familiar. 46 02:33.440 --> 02:39.570 We get cloud threat intelligence, which sounds an awful lot like the Microsoft 47 02:39.570 --> 02:41.560 Azure feature, 48 02:41.560 --> 02:46.840 but it also adds the ability to do DNS based objects. 49 02:46.840 --> 02:53.660 So we can do things based on their FQDN or their fully qualified domain name 50 02:53.660 --> 02:54.960 and it adds 51 02:54.960 --> 02:56.720 geo location. 52 02:56.720 --> 03:02.290 So again, we can implement rules and such based on where these objects are in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 02:56.720 --> 03:02.290 So again, we can implement rules and such based on where these objects are in 53 03:02.290 --> 03:04.600 the world. 54 03:04.600 --> 03:08.780 So in this video, we looked at some of the features of the Google Cloud 55 03:08.780 --> 03:09.680 firewall. 56 03:09.680 --> 03:14.400 And as you can sort of tell, it's quite similar to the other offerings from our 57 03:14.400 --> 03:15.240 other cloud 58 03:15.240 --> 03:16.640 providers. 59 03:16.640 --> 03:21.200 And that's fair enough because they are all offering pretty much the same types 60 03:21.200 --> 03:22.840 of services. 61 03:22.840 --> 03:27.560 But that concludes everything that we need to discuss in this skill. 62 03:27.560 --> 03:31.800 So that leaves us with nothing more than to take the challenge. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 03:27.560 --> 03:31.800 So that leaves us with nothing more than to take the challenge. 63 03:31.800 --> 03:34.440 So go ahead and work through that challenge. 64 03:34.440 --> 03:38.160 And I'll see you in the solution video on the other side. 65 03:38.160 --> 03:48.160 [BLANK_AUDIO]