WEBVTT

1
00:00.000 --> 00:04.240
To help us reinforce the concept of a gateway firewall on one of our gateways

2
00:04.240 --> 00:05.040
in NSX,

3
00:05.040 --> 00:09.280
I'd like to propose this scenario for you and here it is. The customer had a

4
00:09.280 --> 00:09.760
tech

5
00:09.760 --> 00:14.880
configuring a gateway firewall policy on gateway B that is right there.

6
00:14.880 --> 00:18.960
And as part of that policy, the intention was to have a rule that permitted all

7
00:18.960 --> 00:20.240
HTTP traffic

8
00:20.240 --> 00:24.320
if it's sourced from over here on the 1020 zero network and destined over here

9
00:24.320 --> 00:24.880
to the 1010

10
00:24.880 --> 00:29.060
zero network. They wanted that traffic to be denied. However, unfortunately,

11
00:29.060 --> 00:30.320
when clients try here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.060 --> 00:30.320
when clients try here

12
00:30.320 --> 00:34.600
from the segment 20 to access a web server over here on segment 10,

13
00:34.600 --> 00:36.720
unfortunately it is still working

14
00:36.720 --> 00:41.510
with HTTP. So your challenge should you choose to accept it is to think for a

15
00:41.510 --> 00:42.800
moment about what

16
00:42.800 --> 00:48.790
could possibly be wrong and why isn't that control at gateway B being enforced

17
00:48.790 --> 00:49.920
is the actual rule

18
00:49.920 --> 00:53.810
written incorrectly or is the rule disabled, etc. I'd like you to think just

19
00:53.810 --> 00:54.720
for a moment about

20
00:54.720 --> 00:58.960
what would cause that rule not to be matched on and not to deny that traffic.

21
00:58.960 --> 00:59.920
And then secondly,

22
00:59.920 --> 01:03.350
I'd like you to use the screenshots following this video. And in those
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.920 --> 01:03.350
I'd like you to use the screenshots following this video. And in those

23
01:03.350 --> 01:04.240
screenshots, I'm going to

24
01:04.240 --> 01:08.860
have information about various aspects of our configuration in NSX. And based

25
01:08.860 --> 01:10.000
on those screenshots

26
01:10.000 --> 01:12.920
and what we've been through together in this skill, I'd like you to identify

27
01:12.920 --> 01:13.600
what you think

28
01:13.600 --> 01:17.990
the problem is with the current configuration that is still permitting HTTP

29
01:17.990 --> 01:19.680
traffic from 1020

30
01:19.680 --> 01:24.970
zero to HTTP services over here on 10 10. So go ahead now and take a few

31
01:24.970 --> 01:26.480
minutes and consider

32
01:26.480 --> 01:30.240
based on the screenshots, what you think is incorrect. And when you are ready,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:26.480 --> 01:30.240
based on the screenshots, what you think is incorrect. And when you are ready,

33
01:30.240 --> 01:33.850
join me in the next video and we'll do a walk through together and we'll

34
01:33.850 --> 01:34.880
compare notes.

35
01:34.880 --> 01:37.760
So I'll see you in that next video when you are ready.

36
01:37.760 --> 01:47.760
[BLANK_AUDIO]