WEBVTT - This file was automatically generated by VIMEO

0
00:00:12.300 --> 00:00:15.800
Hello everyone and welcome to this nmap

1
00:00:15.800 --> 00:00:16.000
 course.

2
00:00:16.600 --> 00:00:20.500
In this video we are going to learn about nmap

3
00:00:19.500 --> 00:00:21.000
 scan types.

4
00:00:22.100 --> 00:00:25.500
So there are many type of scan types which

5
00:00:25.500 --> 00:00:28.400
 are used for our scanning in

6
00:00:28.400 --> 00:00:32.000
 and map like sin act zombie

7
00:00:31.200 --> 00:00:35.300
 scan null scan. Xmascan TCP

8
00:00:34.300 --> 00:00:38.000
 scan UDP scan and fence can.

9
00:00:39.500 --> 00:00:42.900
So let's start with the first scan, which

10
00:00:42.900 --> 00:00:46.600
 is TCP connectscan. The syntax

11
00:00:45.600 --> 00:00:49.400
 of this scan is nmap hyphen

12
00:00:48.400 --> 00:00:51.900
 St. The target IP and

13
00:00:51.900 --> 00:00:53.300
 the port you want to scan.

14
00:00:54.200 --> 00:00:57.700
the TCP connect scan completes the three-way

15
00:00:57.700 --> 00:00:58.300
 handshake

16
00:00:59.100 --> 00:01:03.200
if a port is open the operating system completes the

17
00:01:03.200 --> 00:01:06.900
 tcp-3 way handshake and the port scanner immediately

18
00:01:06.900 --> 00:01:10.100
 closes the connection to avoid dos.

19
00:01:11.400 --> 00:01:14.500
This scan is noisy because the services can

20
00:01:14.500 --> 00:01:17.700
 lock the sender's IP address and they might

21
00:01:17.700 --> 00:01:19.200
 trigger IDs.

22
00:01:19.800 --> 00:01:22.300
And IPS on the systems.

23
00:01:23.900 --> 00:01:26.700
So what actually happens in

24
00:01:26.700 --> 00:01:27.800
 this scan?

25
00:01:29.100 --> 00:01:32.800
As you can see on the left hand side is the unmarked

26
00:01:32.800 --> 00:01:35.100
 machine and on the right hand side is the

27
00:01:35.100 --> 00:01:37.000
 server which we are going to scan.

28
00:01:38.600 --> 00:01:41.700
The first request our nmap is going to send is

29
00:01:41.700 --> 00:01:44.200
 the send request then the server

30
00:01:44.200 --> 00:01:47.600
 is going to reply for that with a syntax.

31
00:01:48.600 --> 00:01:51.600
And finally and map will send an

32
00:01:51.600 --> 00:01:54.900
 acknowledge package to the server to acknowledge

33
00:01:54.900 --> 00:01:57.800
 it and then will reset the packet.

34
00:01:59.800 --> 00:02:03.000
Let's understand the Wireshark packet breakdown

35
00:02:02.500 --> 00:02:05.000
 of TCP connect scan.

36
00:02:06.200 --> 00:02:10.100
As you can see there is syn, Packet synac

37
00:02:09.100 --> 00:02:13.200
 and AC which is happening successfully

38
00:02:12.200 --> 00:02:15.300
 after that a reset has

39
00:02:15.300 --> 00:02:15.800
 been sent.

40
00:02:16.500 --> 00:02:19.700
So here we can conclude that TCP connect

41
00:02:19.700 --> 00:02:23.200
 scan utilizes TCP 3-way

42
00:02:22.200 --> 00:02:25.700
 handshake in background as we

43
00:02:25.700 --> 00:02:27.600
 saw into this packet.

44
00:02:29.500 --> 00:02:32.400
So what are the pros and cons of this scam?

45
00:02:33.800 --> 00:02:37.200
The advantage is it is quite reliable scan

46
00:02:36.200 --> 00:02:38.800
 on TCP ports.

47
00:02:39.800 --> 00:02:42.600
The disadvantage is it is less still

48
00:02:42.600 --> 00:02:45.700
 the as the connection attempts will be logged by

49
00:02:45.700 --> 00:02:48.400
 the server and it takes longer time to

50
00:02:48.400 --> 00:02:49.900
 send more packets.

51
00:02:52.200 --> 00:02:55.600
So it is the Practical time and let's see the Practical

52
00:02:55.600 --> 00:02:57.600
 of TCP connect scan.

53
00:03:00.100 --> 00:03:01.800
So as you can see over here.

54
00:03:05.200 --> 00:03:07.500
I'm going to write the command, which is nmap.

55
00:03:08.400 --> 00:03:12.300
And the flag hyphen s t and

56
00:03:11.300 --> 00:03:14.200
 the target IP address that I want

57
00:03:14.200 --> 00:03:14.500
 to scan.

58
00:03:18.500 --> 00:03:21.600
After giving the target IP address. I'm going

59
00:03:21.600 --> 00:03:24.900
 to add hyphen V to see the output in

60
00:03:24.900 --> 00:03:25.700
 verbose mode.

61
00:03:27.500 --> 00:03:28.200
Onto my screen.

62
00:03:30.300 --> 00:03:33.900
Remember in the background. I am running Wireshark to

63
00:03:33.900 --> 00:03:36.700
 capture all the packets to see what actually

64
00:03:36.700 --> 00:03:39.000
 and map is doing in the background.

65
00:03:46.100 --> 00:03:49.500
So as you can see I have started the scan.

66
00:03:50.600 --> 00:03:53.600
And it has already identified two

67
00:03:53.600 --> 00:03:56.700
 open ports, which is 445 and 7 0

68
00:03:56.700 --> 00:03:59.200
 7 0 as you can see over here and it

69
00:03:59.200 --> 00:04:02.000
 has also identified one more Port 808.

70
00:04:06.200 --> 00:04:09.900
If you notice closely, you can read over here initiating

71
00:04:09.900 --> 00:04:13.100
 and connect scan, which is a TCP connect

72
00:04:12.100 --> 00:04:13.500
 scan.

73
00:04:15.700 --> 00:04:18.400
It is also identified that the host is up.

74
00:04:18.400 --> 00:04:22.000
 Now. Let's see the analysis in Wireshark

75
00:04:21.200 --> 00:04:24.500
 that what actually happened. We have

76
00:04:24.500 --> 00:04:27.100
 already seen the packet image in the

77
00:04:27.100 --> 00:04:30.600
 previous slide. Now. Let's see the life packet

78
00:04:30.600 --> 00:04:32.800
 analysis of TCP connect scam.

79
00:04:36.900 --> 00:04:39.800
So in the Wireshark, I'm going to type

80
00:04:39.800 --> 00:04:43.000
 ip.edr equals equals

81
00:04:42.300 --> 00:04:45.200
 and the target IP address that I

82
00:04:45.200 --> 00:04:48.700
 want to see the packet for this is the filter in

83
00:04:48.700 --> 00:04:51.400
 which I just want to see the packets which are

84
00:04:51.400 --> 00:04:53.500
 sent to this particular IP address.

85
00:04:56.300 --> 00:04:57.700
I will just scroll down.

86
00:05:09.200 --> 00:05:12.900
Let me scroll more down to see a TCP three-way

87
00:05:12.900 --> 00:05:15.500
 handshake has been created with the

88
00:05:15.500 --> 00:05:16.600
 target IP address.

89
00:05:18.400 --> 00:05:22.200
Perfect, as you can see over here, we identified that

90
00:05:21.200 --> 00:05:24.700
 the port number 88 was open

91
00:05:24.700 --> 00:05:27.400
 and a tcp3 way handshake

92
00:05:27.400 --> 00:05:30.800
 has been successfully performed and the port status

93
00:05:30.800 --> 00:05:32.600
 was identified as open.

94
00:05:34.700 --> 00:05:37.900
If we look closely you can see first a

95
00:05:37.900 --> 00:05:41.100
 sin packet has been sent and then a synac

96
00:05:40.100 --> 00:05:43.800
 has been sent and finally an acknowledged has

97
00:05:43.800 --> 00:05:44.700
 been sent.

98
00:05:54.200 --> 00:05:57.700
As you can see over here Port 88 was identified

99
00:05:57.700 --> 00:06:00.800
 as open as we saw a complete

100
00:06:00.800 --> 00:06:03.400
 tcp3 way handshake was performed

101
00:06:03.400 --> 00:06:07.000
 and the status was identified by nmap.

102
00:06:08.400 --> 00:06:09.900
I hope you guys understood this.

103
00:06:11.300 --> 00:06:11.300
Thank you.
