WEBVTT - This file was automatically generated by VIMEO

0
00:00:04.800 --> 00:00:06.000
Hello, everyone.

1
00:00:07.400 --> 00:00:10.300
So in this video we are going to see one of

2
00:00:10.300 --> 00:00:13.400
 the most interesting script of

3
00:00:13.400 --> 00:00:16.000
 nmap, which is firewalk.

4
00:00:17.400 --> 00:00:20.800
So when we are running a firewalk scan onto

5
00:00:20.800 --> 00:00:24.000
 a Target we can identify that.

6
00:00:25.700 --> 00:00:29.300
Is the firewall blocking some

7
00:00:28.300 --> 00:00:31.900
 of the ports or not. So

8
00:00:31.900 --> 00:00:34.400
 basically you will not be able

9
00:00:34.400 --> 00:00:37.900
 to get the correct output or

10
00:00:37.900 --> 00:00:40.500
 the response when you hit request on

11
00:00:40.500 --> 00:00:41.800
 some of the ports.

12
00:00:43.100 --> 00:00:47.600
The reason may be because the firewall is basically blocking.

13
00:00:48.400 --> 00:00:51.400
You to identify the status of those types

14
00:00:51.400 --> 00:00:52.200
 of ports?

15
00:00:52.900 --> 00:00:55.900
You can identify those ports onto

16
00:00:55.900 --> 00:00:59.400
 a server where the firewall

17
00:00:58.400 --> 00:01:01.300
 is configured to block.

18
00:01:03.300 --> 00:01:06.700
So, let's see how we can identify if any

19
00:01:06.700 --> 00:01:09.800
 web server is blocking any particular Port

20
00:01:09.800 --> 00:01:11.700
 using this scan.

21
00:01:13.100 --> 00:01:16.500
The syntax of doing this scan is nmap the target

22
00:01:16.500 --> 00:01:19.600
 IP address followed by hyphen hyphen

23
00:01:19.600 --> 00:01:22.900
 script equals to firewalk and we can also see

24
00:01:22.900 --> 00:01:25.100
 the trace route wherein you

25
00:01:25.100 --> 00:01:28.700
 will understand how your request is going to that particular Target.

26
00:01:30.400 --> 00:01:33.300
You can always add hyphen V to see the output in

27
00:01:33.300 --> 00:01:36.400
 verbose mode the example to run. This

28
00:01:36.400 --> 00:01:38.100
 scan is given below.

29
00:01:39.800 --> 00:01:42.600
Let's jump to the Practical and let's

30
00:01:42.600 --> 00:01:44.200
 see how you can run this.

31
00:01:48.400 --> 00:01:51.400
As you can see on the screen here. I have given

32
00:01:51.400 --> 00:01:55.100
 the command which is nmap -script equals

33
00:01:54.100 --> 00:01:57.500
 to firewalk and I'll

34
00:01:57.500 --> 00:02:00.900
 also I'm giving trace route to see the Hops.

35
00:02:03.800 --> 00:02:06.600
And I will give the target which is scan Dot

36
00:02:06.600 --> 00:02:08.100
 nmap.org.

37
00:02:10.400 --> 00:02:14.000
As you can see this particular scan requires

38
00:02:13.500 --> 00:02:16.300
 root privileges, so I will

39
00:02:16.300 --> 00:02:19.800
 just quickly become root and I will again run

40
00:02:19.800 --> 00:02:20.500
 this scan.

41
00:02:26.200 --> 00:02:28.400
As you can see the scan has successfully started.

42
00:02:29.800 --> 00:02:32.500
I will just skip the scan so we can directly

43
00:02:32.500 --> 00:02:33.400
 jump to the output.

44
00:02:41.600 --> 00:02:44.600
As you can see we have got the output and let's understand

45
00:02:44.600 --> 00:02:45.500
 the output.

46
00:02:47.500 --> 00:02:50.900
As you can see over here the particular host.

47
00:02:52.300 --> 00:02:55.900
Has some of the ports which are blocked as

48
00:02:55.900 --> 00:02:58.700
 you can see, these are the ports which

49
00:02:58.700 --> 00:03:01.700
 are blocked by the firewall, which

50
00:03:01.700 --> 00:03:04.600
 you if you scan will not be able to identify

51
00:03:04.600 --> 00:03:05.800
 the correct status.

52
00:03:06.500 --> 00:03:10.400
So we are able to identify this ports

53
00:03:09.400 --> 00:03:13.700
 are blocked because of firewalk script

54
00:03:13.700 --> 00:03:17.200
 as you can see we have got four ports

55
00:03:16.200 --> 00:03:19.400
 which are block ports by

56
00:03:19.400 --> 00:03:20.200
 the firewall.

57
00:03:21.500 --> 00:03:24.200
Now you can see this is the output of the trace route.

58
00:03:25.100 --> 00:03:28.300
Wherein we are able to identify each request that has

59
00:03:28.300 --> 00:03:29.300
 been hopped.

60
00:03:30.100 --> 00:03:31.700
in the trace route output

61
00:03:33.100 --> 00:03:34.200
So I hope you guys understood.

62
00:03:35.200 --> 00:03:38.000
This particular scan, which is firewalk scan.

63
00:03:38.700 --> 00:03:39.100
Thank you.
