WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.300 --> 00:00:10.400
In this video you are going to get the hands-on experience

1
00:00:10.400 --> 00:00:13.300
 of Performing Network scanning use an end map.

2
00:00:13.300 --> 00:00:14.900
 So let's dive on in.

3
00:00:16.400 --> 00:00:19.100
Network mapper who better known as endmap is

4
00:00:19.100 --> 00:00:22.400
 simply free network scanner that simply enables

5
00:00:22.400 --> 00:00:25.700
 cyber Security Professionals to discover live

6
00:00:25.700 --> 00:00:28.200
 systems owning Network scan for

7
00:00:28.200 --> 00:00:32.000
 open TCP ports and UDP ports perform

8
00:00:31.700 --> 00:00:34.300
 banana grabbing uneven series

9
00:00:34.300 --> 00:00:35.200
 enumeration.

10
00:00:35.800 --> 00:00:38.800
Furthermore and my parts are capabilities of

11
00:00:38.800 --> 00:00:42.000
 detecting the host operating system and

12
00:00:41.400 --> 00:00:45.900
 even common security vulnerabilities online

13
00:00:44.900 --> 00:00:46.400
 host.

14
00:00:47.100 --> 00:00:48.300
So don't forget you.

15
00:00:49.800 --> 00:00:53.000
Let's start off by detecting life hosts

16
00:00:52.100 --> 00:00:53.400
 on a network.

17
00:00:54.200 --> 00:00:57.500
For this exercise. We will need to pour on

18
00:00:57.500 --> 00:01:00.400
 three or four virtual machines. We need to pour on

19
00:01:00.400 --> 00:01:03.700
 our cardi Linux virtual machine the metasploitable to

20
00:01:03.700 --> 00:01:06.500
 Virtual Machine and even a metasploitable tree

21
00:01:06.500 --> 00:01:07.300
 virtual machine.

22
00:01:08.100 --> 00:01:11.500
So let's pull on the two metasploitable machines

23
00:01:11.500 --> 00:01:14.300
 first so we can run these in the background.

24
00:01:14.300 --> 00:01:17.600
 But before we do, so let's ensure that each

25
00:01:17.600 --> 00:01:20.900
 virtual machine is connected to the right virtual

26
00:01:20.900 --> 00:01:23.600
 Network. Simply select metasploitable 2

27
00:01:23.600 --> 00:01:27.200
 VM click on settings, then simply

28
00:01:26.200 --> 00:01:29.300
 click on network and ensure it

29
00:01:29.300 --> 00:01:33.000
 is connected to the pen test Network and promiscuous

30
00:01:32.200 --> 00:01:34.300
 mode is set to allow all

31
00:01:35.100 --> 00:01:39.000
Next let's check the network settings on metasloidable tree

32
00:01:38.500 --> 00:01:40.700
 the Windows Virtual Machine.

33
00:01:41.400 --> 00:01:42.500
Let's click on settings.

34
00:01:43.500 --> 00:01:46.300
Click on network and here you can see it's

35
00:01:46.300 --> 00:01:48.500
 also connected to the pen test Network.

36
00:01:49.700 --> 00:01:52.500
We can start this virtual machines by simply clicking

37
00:01:52.500 --> 00:01:55.400
 a start button. However, let's run them

38
00:01:55.400 --> 00:01:58.500
 in the background to do so, simply click this little

39
00:01:58.500 --> 00:02:01.200
 icon here that points down

40
00:02:01.200 --> 00:02:04.800
 next to start button and simply select headless start.

41
00:02:04.800 --> 00:02:07.500
 This will simply run the virtual machine in

42
00:02:07.500 --> 00:02:10.500
 the background for us. So let's give this a few

43
00:02:10.500 --> 00:02:13.500
 seconds to boot up once it's booted. We

44
00:02:13.500 --> 00:02:17.400
 will then power on the metasploitable tree Windows VM.

45
00:02:19.400 --> 00:02:22.800
Okay, great. Let's do the same for metasploitable

46
00:02:22.800 --> 00:02:25.300
 tree Windows VM. Simply select it

47
00:02:25.300 --> 00:02:27.100
 click this down.

48
00:02:28.300 --> 00:02:31.500
menu, then select headlight start like

49
00:02:31.500 --> 00:02:31.700
 so

50
00:02:36.400 --> 00:02:39.600
as you notice on a virtualbox manager, we

51
00:02:39.600 --> 00:02:42.300
 can see a preview of the desktop interface.

52
00:02:45.100 --> 00:02:48.400
Okay, great. So the metasploitable tree virtual machine is

53
00:02:48.400 --> 00:02:51.500
 powered on now. Let's pull on our Kali Linux

54
00:02:51.500 --> 00:02:54.300
 virtual machine. Simply select Kali Linux

55
00:02:54.300 --> 00:02:55.400
 and click Start.

56
00:02:58.400 --> 00:03:01.900
Ensure that you log on with your user credentials. The username

57
00:03:01.900 --> 00:03:04.400
 is Kali and the password that

58
00:03:04.400 --> 00:03:05.900
 you are set in the previous videos.

59
00:03:07.900 --> 00:03:15.500
Okay, great.

60
00:03:15.500 --> 00:03:18.300
 So we are logged into our Kali Linux.

61
00:03:18.300 --> 00:03:18.900
 Which on machine?

62
00:03:19.500 --> 00:03:22.400
Before we perform any network scans on a system.

63
00:03:23.400 --> 00:03:26.300
It's highly recommended that you change or spoof your

64
00:03:26.300 --> 00:03:29.500
 Mac address simply to prevent your identity

65
00:03:29.500 --> 00:03:32.900
 from being revealed as in your devices Market

66
00:03:32.900 --> 00:03:35.600
 address to do this. Let's open a

67
00:03:35.600 --> 00:03:36.200
 terminal like so

68
00:03:41.500 --> 00:03:44.300
And before we proceed further, let's check the number

69
00:03:44.300 --> 00:03:47.500
 of interfaces. We have and their Mac addresses. So

70
00:03:47.500 --> 00:03:50.600
 simply type I have config like so and press

71
00:03:50.600 --> 00:03:50.800
 enter.

72
00:03:51.600 --> 00:03:55.000
As you can see, we have a few ethernet

73
00:03:54.500 --> 00:03:57.400
 interfaces. If you recall one of

74
00:03:57.400 --> 00:04:00.500
 the ethernet interface is connected to your physical Network.

75
00:04:00.500 --> 00:04:03.200
 That's this network interface.

76
00:04:05.400 --> 00:04:08.900
Then we have another interface that is connected to all pen

77
00:04:08.900 --> 00:04:11.500
 test Network which is ethernet 2

78
00:04:11.500 --> 00:04:14.800
 and you can see that it has an IP address on the

79
00:04:14.800 --> 00:04:17.500
 pen test Network. And also there is

80
00:04:17.500 --> 00:04:19.100
 the MAC address now.

81
00:04:20.100 --> 00:04:23.400
Let's say the Security Professionals were able to capture some

82
00:04:23.400 --> 00:04:27.000
 of the pockets that were leaving your system that will scanning

83
00:04:26.300 --> 00:04:29.300
 their assets. They can

84
00:04:29.300 --> 00:04:32.700
 simply use the MAC address and the two

85
00:04:32.700 --> 00:04:36.200
 men what type of system is on their Network. So to

86
00:04:35.200 --> 00:04:38.400
 spoof the market address. Let's follow these steps.

87
00:04:39.800 --> 00:04:41.500
Firstly let's type sudo.

88
00:04:42.300 --> 00:04:44.000
I have config like so

89
00:04:45.200 --> 00:04:48.600
etch one because eth one is

90
00:04:48.600 --> 00:04:51.500
 connected to Penthouse Network and let's type down

91
00:04:51.500 --> 00:04:54.600
 simply enter your Kali Linux

92
00:04:54.600 --> 00:04:55.800
 password like so

93
00:04:56.600 --> 00:04:56.900
and

94
00:04:58.100 --> 00:05:01.200
we got back a new prompt. So let's type. I've conflict one

95
00:05:01.200 --> 00:05:04.600
 more time. And now you can see ethe21 is

96
00:05:04.600 --> 00:05:07.300
 no longer available simply because we have

97
00:05:07.300 --> 00:05:11.200
 logically shut down this interface and that's one

98
00:05:10.200 --> 00:05:13.700
 of the most important steps needed when

99
00:05:13.700 --> 00:05:16.200
 you're changing the MAC address on your system.

100
00:05:16.200 --> 00:05:18.200
 You need to know the interface.

101
00:05:19.200 --> 00:05:22.200
Let's check to see what type of commands we could

102
00:05:22.200 --> 00:05:25.400
 use with Mark changer. Mark changer is

103
00:05:25.400 --> 00:05:28.300
 simply pre-installing Carly Linux and this

104
00:05:28.300 --> 00:05:32.000
 allows us to change our Mark address. So as

105
00:05:31.100 --> 00:05:34.300
 you can see we can view all current market

106
00:05:34.300 --> 00:05:37.600
 address. We could change it to another Market address. We

107
00:05:37.600 --> 00:05:40.800
 could round my super recess we can even select

108
00:05:40.800 --> 00:05:44.100
 from a list of particular types of devices, but

109
00:05:43.100 --> 00:05:46.500
 let's keep it simple. Let's use

110
00:05:46.500 --> 00:05:49.700
 a dash capital E parameter to set

111
00:05:49.700 --> 00:05:51.600
 a random Mac address of any kind.

112
00:05:53.100 --> 00:05:55.100
So we can use sudo.

113
00:05:55.800 --> 00:05:56.800
Mark changer

114
00:05:57.800 --> 00:06:01.600
Dash capital e eth one

115
00:06:02.700 --> 00:06:04.800
Here you can see the current market address.

116
00:06:05.700 --> 00:06:08.100
The permanent Mark address and now we can

117
00:06:08.100 --> 00:06:11.000
 see the New randomized Market address.

118
00:06:12.600 --> 00:06:14.700
Next let's type sudo.

119
00:06:15.200 --> 00:06:18.900
I have config e the each and type

120
00:06:18.900 --> 00:06:20.800
 up like so and hit enter.

121
00:06:21.700 --> 00:06:24.700
So at this point ethernet 1 should

122
00:06:24.700 --> 00:06:27.100
 be up unavailable with a new market address.

123
00:06:27.100 --> 00:06:28.200
 Let's check.

124
00:06:29.200 --> 00:06:31.200
Let's do ifconfig and hit enter.

125
00:06:32.100 --> 00:06:32.300
and look

126
00:06:33.400 --> 00:06:36.200
The interface is now available and it

127
00:06:36.200 --> 00:06:40.000
 is using the new randomly generated Market address. Great.

128
00:06:40.900 --> 00:06:43.700
Now that we have a new Mac address. Let's proceed

129
00:06:43.700 --> 00:06:45.400
 to actually scan our Network.

130
00:06:46.300 --> 00:06:46.800
firstly

131
00:06:47.500 --> 00:06:51.200
let's check the ifconfig once more and

132
00:06:50.200 --> 00:06:54.000
 we are already on the 172 TT

133
00:06:53.300 --> 00:06:56.500
 1.0 Network simply by the

134
00:06:56.500 --> 00:06:59.200
 class subnet mask. So let's assume that

135
00:06:59.200 --> 00:07:02.500
 there are live fools on this network. What can

136
00:07:02.500 --> 00:07:05.400
 we do? Well, there's a few tools that we could use but

137
00:07:05.400 --> 00:07:07.100
 we are sticking to enemap.

138
00:07:07.600 --> 00:07:10.900
Would end up we can perform a port scan

139
00:07:10.900 --> 00:07:13.100
 we could perform a ping scan. We

140
00:07:13.100 --> 00:07:17.500
 could perform different types of scans. So let's use a

141
00:07:17.500 --> 00:07:19.900
 simple scan but before doing the scan.

142
00:07:20.900 --> 00:07:23.300
Let me show you a few syntax that

143
00:07:23.300 --> 00:07:26.900
 you could use with end map on how to learn more stuff using MMA

144
00:07:26.900 --> 00:07:28.400
 we can type and map.

145
00:07:29.600 --> 00:07:32.300
Let's type man then and map so

146
00:07:32.300 --> 00:07:36.200
 we can see the manual feature and map hit enter and

147
00:07:35.200 --> 00:07:38.000
 you get a full description of nmap.

148
00:07:38.800 --> 00:07:42.000
Going on Twitter. We can see their various

149
00:07:41.400 --> 00:07:44.700
 syntax that you can use an examples

150
00:07:44.700 --> 00:07:47.100
 of the type of output that you will see.

151
00:07:48.200 --> 00:07:51.800
Going on filter. We have a lot more different parameters that

152
00:07:51.800 --> 00:07:54.700
 we could use and most important thing is we

153
00:07:54.700 --> 00:07:57.900
 have so many different syntax or

154
00:07:57.900 --> 00:08:00.200
 what we might call switches to use it and

155
00:08:00.200 --> 00:08:00.700
 map.

156
00:08:01.300 --> 00:08:04.400
The first thing that we are going to use is let's perform a ping

157
00:08:04.400 --> 00:08:04.700
 scan.

158
00:08:05.200 --> 00:08:08.800
Some hosts only network will have the icmp

159
00:08:08.800 --> 00:08:11.900
 enabled by default. However, some Network

160
00:08:11.900 --> 00:08:15.100
 professionals aren't even systems administrators. Will

161
00:08:14.100 --> 00:08:17.400
 this evil icmp messages

162
00:08:17.400 --> 00:08:18.100
 from?

163
00:08:18.900 --> 00:08:21.500
Being Santa Crossing into it and also preventing

164
00:08:21.500 --> 00:08:24.100
 the assets from responding to any ping messages.

165
00:08:25.200 --> 00:08:28.600
But we are still going to do it to see what is the expected result

166
00:08:28.600 --> 00:08:32.000
 or what results that will get before. We

167
00:08:31.300 --> 00:08:34.400
 actually perform any network scans.

168
00:08:39.500 --> 00:08:42.300
So let's do ifconfig one more time to get

169
00:08:42.300 --> 00:08:43.800
 our own IP address.

170
00:08:44.700 --> 00:08:47.100
So during our Network scan we can

171
00:08:47.100 --> 00:08:50.600
 scan the entire IP subnet. However, we'll

172
00:08:50.600 --> 00:08:53.500
 also be scanning our own system. So let's

173
00:08:53.500 --> 00:08:55.900
 exclude our own device from the scan.

174
00:08:56.400 --> 00:08:59.500
So I'm going to copy the IP address of

175
00:08:59.500 --> 00:09:01.100
 my device like so.

176
00:09:04.300 --> 00:09:06.200
Let's do I have config?

177
00:09:06.700 --> 00:09:08.800
Let's copy our IP address.

178
00:09:10.200 --> 00:09:10.600
Just this one.

179
00:09:12.700 --> 00:09:14.300
Now, let's specify it here.

180
00:09:15.300 --> 00:09:19.000
So this command will do it will perform a ping scan

181
00:09:18.300 --> 00:09:24.700
 or the entire network, which is 254 IP

182
00:09:23.700 --> 00:09:26.500
 addresses to check received. There

183
00:09:26.500 --> 00:09:29.900
 are any devices online that are responding to icmp messages.

184
00:09:29.900 --> 00:09:33.000
 However, it is going to exclude our

185
00:09:32.400 --> 00:09:35.500
 system which is a Kali Linux system from the actual

186
00:09:35.500 --> 00:09:35.800
 scan.

187
00:09:36.300 --> 00:09:39.300
Hit enter and we actually need two.

188
00:09:41.800 --> 00:09:44.900
Specify the right words actually

189
00:09:44.900 --> 00:09:47.700
 made a typo when typing nmap.

190
00:09:48.300 --> 00:09:51.700
So now the scan it should take us a few seconds the pops

191
00:09:51.700 --> 00:09:54.800
 a few minutes. Oh, look, it's actually finished quickly. So

192
00:09:54.800 --> 00:09:57.800
 currently we can see there are two devices online, which

193
00:09:57.800 --> 00:09:58.100
 is

194
00:09:59.100 --> 00:10:03.800
172 Tut 1.37 and 17230

195
00:10:02.800 --> 00:10:05.500
 1.t.

196
00:10:06.700 --> 00:10:09.800
So let's start scanning one device at

197
00:10:09.800 --> 00:10:09.900
 a time.

198
00:10:10.700 --> 00:10:13.900
So now that we tuman that there

199
00:10:13.900 --> 00:10:16.800
 are two live systems next we can start proving

200
00:10:16.800 --> 00:10:19.800
 for any sort of silver Sports running services

201
00:10:19.800 --> 00:10:21.900
 and even operating systems.

202
00:10:23.400 --> 00:10:26.100
So great. Let's check for any sort of

203
00:10:26.100 --> 00:10:29.500
 open ports on both systems. Let's Ivan.

204
00:10:31.400 --> 00:10:33.300
So now that we're back on our Carly learns machine.

205
00:10:34.400 --> 00:10:37.100
Let's type and map and let's specify.

206
00:10:38.500 --> 00:10:41.200
One of the IP addresses Let's scan this

207
00:10:41.200 --> 00:10:44.400
 particular system. What is scan will do it will perform

208
00:10:44.400 --> 00:10:47.700
 a scan for the top 1000 most

209
00:10:47.700 --> 00:10:51.500
 commonly used ports and silver

210
00:10:50.500 --> 00:10:52.700
 Sports horny system.

211
00:10:53.300 --> 00:10:56.400
That's it. Enter and sometimes scan will

212
00:10:56.400 --> 00:10:57.100
 happen very quickly.

213
00:10:57.900 --> 00:11:00.400
So currently we can see there's a list

214
00:11:00.400 --> 00:11:04.100
 of open ports we can see it's TCB ports

215
00:11:03.100 --> 00:11:06.900
 the status as opan and the

216
00:11:06.900 --> 00:11:08.000
 associated service

217
00:11:09.100 --> 00:11:11.500
Let's scan the next device

218
00:11:13.100 --> 00:11:16.600
Let's press up and let's change this to IP address

219
00:11:16.600 --> 00:11:19.100
 of the another host. Let's hit enter.

220
00:11:20.900 --> 00:11:23.400
So currently we can see this other hose

221
00:11:23.400 --> 00:11:26.600
 has less Sports open but looking at

222
00:11:26.600 --> 00:11:29.700
 it we seem to be able to identify some common

223
00:11:29.700 --> 00:11:32.700
 services for example, there's FTP. So

224
00:11:32.700 --> 00:11:36.000
 pop says a file server, there's

225
00:11:35.500 --> 00:11:38.900
 SSE is HTTP a

226
00:11:38.900 --> 00:11:39.400
 web server.

227
00:11:39.900 --> 00:11:43.400
And look these ports provide some

228
00:11:42.400 --> 00:11:45.400
 type of indication that most likely it's

229
00:11:45.400 --> 00:11:46.700
 a windows-based system.

230
00:11:47.400 --> 00:11:50.500
However, we could take a deeper dive and even go further into

231
00:11:50.500 --> 00:11:53.700
 discovering what exactly is being

232
00:11:53.700 --> 00:11:56.300
 hosted on these particular ports.

233
00:11:57.600 --> 00:12:01.000
So now that we find open ports, let's

234
00:12:00.400 --> 00:12:03.100
 actually start discovering the

235
00:12:03.100 --> 00:12:07.400
 operating system and together will enumerate

236
00:12:06.400 --> 00:12:09.600
 these services on

237
00:12:09.600 --> 00:12:10.400
 these systems.

238
00:12:14.100 --> 00:12:17.300
So let's dive in and checking for the operating

239
00:12:17.300 --> 00:12:20.900
 system version and enumerating and grabbing

240
00:12:20.900 --> 00:12:24.000
 the banner of each of those ports found

241
00:12:23.300 --> 00:12:26.400
 on both devices. So, let's Dive In

242
00:12:28.500 --> 00:12:30.200
So great. We are back at all Kali machine.

243
00:12:30.800 --> 00:12:33.700
Let's press up a couple of times and we'll

244
00:12:33.700 --> 00:12:36.700
 start with the 2d7, which is obvious machine.

245
00:12:36.700 --> 00:12:38.000
 We wanted to man.

246
00:12:39.100 --> 00:12:42.800
What type of service versions are providing

247
00:12:42.800 --> 00:12:45.700
 those Services found on the

248
00:12:45.700 --> 00:12:48.400
 37 together it we wanted to in

249
00:12:48.400 --> 00:12:51.900
 the operating system so we can use Dash capital A

250
00:12:51.900 --> 00:12:54.400
 which is used to perform a series of

251
00:12:54.400 --> 00:12:57.600
 scans Force Dash e will simply

252
00:12:57.600 --> 00:13:00.700
 tell and map to identify the operating system

253
00:13:00.700 --> 00:13:03.500
 the service versions of any running services

254
00:13:03.500 --> 00:13:06.400
 and perform B6 script scanning together

255
00:13:06.400 --> 00:13:07.800
 with a tree throws.

256
00:13:08.500 --> 00:13:11.600
Next we can use a dash capital T command

257
00:13:11.600 --> 00:13:14.400
 followed by 4 and this command will

258
00:13:14.400 --> 00:13:17.200
 simply specify the timing options for the scan

259
00:13:17.200 --> 00:13:20.800
 and the ranges are usually between 0 to

260
00:13:20.800 --> 00:13:23.500
 5 and 0 is very slow

261
00:13:23.500 --> 00:13:26.100
 and fives very fast on a

262
00:13:26.100 --> 00:13:29.200
 real Network. You don't want to perform a very fast scan at all

263
00:13:29.200 --> 00:13:32.500
 simply because any sort of thread detection

264
00:13:32.500 --> 00:13:35.800
 systems me trigger an alarm, but because

265
00:13:35.800 --> 00:13:38.500
 we're doing this within all personal lab Network,

266
00:13:38.500 --> 00:13:41.600
 we could scan us quickly as we want. So therefore we

267
00:13:41.600 --> 00:13:43.700
 get a lot of results very quickly.

268
00:13:44.500 --> 00:13:47.600
However, since and map usually scans the

269
00:13:47.600 --> 00:13:50.700
 top 1000 ports by default, let's specify

270
00:13:50.700 --> 00:13:53.500
 and tell nmap. Hey scan all

271
00:13:53.500 --> 00:13:56.500
 65,535 ports

272
00:13:56.500 --> 00:13:59.700
 to do this. We can simply use a dash

273
00:13:59.700 --> 00:14:02.400
 P command with another Dash like

274
00:14:02.400 --> 00:14:02.800
 so

275
00:14:03.400 --> 00:14:06.300
so the dash P command allows it to specify

276
00:14:06.300 --> 00:14:09.400
 our Port let's say you want to scan Port 80

277
00:14:09.400 --> 00:14:12.700
 we can specify Port 80, but if we

278
00:14:12.700 --> 00:14:15.700
 put on another Dash after the dash P command

279
00:14:15.700 --> 00:14:18.600
 like so we're simply specifying scan

280
00:14:18.600 --> 00:14:21.900
 for all silver sports with the

281
00:14:21.900 --> 00:14:22.600
 non operating system.

282
00:14:23.500 --> 00:14:27.100
Now to get a scan going we can simply press enter and

283
00:14:26.100 --> 00:14:29.300
 because we're scanning all the ports this

284
00:14:29.300 --> 00:14:32.600
 meeting sometime. So I'm going to pause the video Once

285
00:14:32.600 --> 00:14:34.800
 the results are completed. We will retain.

286
00:14:35.800 --> 00:14:38.100
After a few minutes the scan was completed.

287
00:14:38.700 --> 00:14:42.100
Here you can see we get a lot more information and this

288
00:14:41.100 --> 00:14:44.400
 information could help us create a profile

289
00:14:44.400 --> 00:14:47.600
 and tell us specific details about the type

290
00:14:47.600 --> 00:14:52.400
 of system that has IP address of 172 tt1.t5.

291
00:14:53.100 --> 00:14:56.600
For example, we can see yes, it did scan

292
00:14:56.600 --> 00:14:59.900
 Port 21 again. It shows it is open and it

293
00:14:59.900 --> 00:15:02.100
 is running FTP but looking through that

294
00:15:02.100 --> 00:15:05.800
 we can see the specific version of FTP on

295
00:15:05.800 --> 00:15:08.600
 the system. For example, we can take

296
00:15:08.600 --> 00:15:11.600
 this information Let's see. We open our web browser like

297
00:15:11.600 --> 00:15:11.800
 so

298
00:15:13.700 --> 00:15:16.100
arcade had water Google once we had a

299
00:15:16.100 --> 00:15:20.200
 lot of Google we can simply start doing some research to determine

300
00:15:19.200 --> 00:15:22.400
 the weather this particular service has

301
00:15:22.400 --> 00:15:25.600
 any sort of security flows so we can

302
00:15:25.600 --> 00:15:28.700
 piece the information there and we can either type

303
00:15:28.700 --> 00:15:31.100
 vulnerability or we can even

304
00:15:31.100 --> 00:15:32.000
 type exploit

305
00:15:32.900 --> 00:15:35.200
So look at this the first few

306
00:15:35.200 --> 00:15:38.600
 results include that there's a backdoor command

307
00:15:38.600 --> 00:15:39.100
 execution.

308
00:15:39.800 --> 00:15:41.900
If we click on exploit DB.

309
00:15:42.400 --> 00:15:45.800
And let's say we also open the rapid7 link. We

310
00:15:45.800 --> 00:15:48.500
 should be able to get more details about the

311
00:15:48.500 --> 00:15:51.400
 security flow on how it can be exploited.

312
00:15:52.100 --> 00:15:56.200
For instance, we can see this security flow. It

313
00:15:55.200 --> 00:15:58.400
 was disclose a very long time ago

314
00:15:58.400 --> 00:16:01.600
 and we get a full description. So this

315
00:16:01.600 --> 00:16:04.900
 system that you just scanned it is vulnerable

316
00:16:04.900 --> 00:16:07.700
 and there's an exploit module

317
00:16:07.700 --> 00:16:10.100
 that curated back door access in that particular

318
00:16:10.100 --> 00:16:11.100
 service Force.

319
00:16:11.800 --> 00:16:14.600
So if we are lucky we'll be able to exploit it

320
00:16:14.600 --> 00:16:17.300
 and check this out. It shows how to use some

321
00:16:17.300 --> 00:16:20.600
 Metasploit module to compromise the actual Target

322
00:16:20.600 --> 00:16:23.300
 which will take a look at any later video

323
00:16:23.300 --> 00:16:25.700
 when we reach the exploitation fees.

324
00:16:26.400 --> 00:16:29.300
If you check the exploit D to base link

325
00:16:29.300 --> 00:16:30.400
 we can also see.

326
00:16:31.500 --> 00:16:34.100
The specific details and the code that is

327
00:16:34.100 --> 00:16:38.000
 used to actually exploit that security flow on.

328
00:16:39.100 --> 00:16:40.100
our Target system

329
00:16:40.800 --> 00:16:43.500
But we'll come back to exploiting this at a

330
00:16:43.500 --> 00:16:46.700
 later time for now. We are trying to determine what type

331
00:16:46.700 --> 00:16:49.700
 of system that we are looking at without seeing

332
00:16:49.700 --> 00:16:50.900
 the physical system. That is

333
00:16:51.800 --> 00:16:54.800
we can even see that end map capture the

334
00:16:54.800 --> 00:16:57.800
 banner information Force automatically simply because

335
00:16:57.800 --> 00:17:00.300
 we use a dash a parameter like so

336
00:17:01.900 --> 00:17:04.900
for SSH we can see open as

337
00:17:04.900 --> 00:17:07.900
 a Siege 4.7 P1 is a

338
00:17:07.900 --> 00:17:11.700
 version that is being used on the target

339
00:17:10.700 --> 00:17:13.400
 system, but let's scroll down

340
00:17:13.400 --> 00:17:14.300
 way down.

341
00:17:15.400 --> 00:17:18.000
There's something particular we need to take a look

342
00:17:18.000 --> 00:17:18.100
 at.

343
00:17:25.500 --> 00:17:27.700
Let's look at a service information.

344
00:17:28.900 --> 00:17:31.300
For whose the name of the horse is

345
00:17:31.300 --> 00:17:32.300
 metasploitable.

346
00:17:33.500 --> 00:17:36.800
However, if you look at the operating system

347
00:17:36.800 --> 00:17:40.100
 types here we can see the specifying Linux.

348
00:17:40.900 --> 00:17:43.400
And nothing else. So most likely this

349
00:17:43.400 --> 00:17:46.400
 system is a Lennox Beast operating system.

350
00:17:46.400 --> 00:17:49.700
 So so far we were able to identify at

351
00:17:49.700 --> 00:17:52.700
 least one security flow, but we must

352
00:17:52.700 --> 00:17:55.400
 go through each port and do research

353
00:17:55.400 --> 00:17:58.600
 to determen what it is any sort of security weaknesses

354
00:17:58.600 --> 00:18:01.500
 on any of the services that will found

355
00:18:01.500 --> 00:18:04.100
 running on the system so far. We were able to

356
00:18:04.100 --> 00:18:07.500
 find one security flow that seems to be exploitable. We know

357
00:18:07.500 --> 00:18:10.400
 the operating system is a Lennox bass operating system.

358
00:18:10.400 --> 00:18:13.800
 Okay, great while you are capturing. Oh

359
00:18:13.800 --> 00:18:16.200
 while you're performing all of this scanning on

360
00:18:16.200 --> 00:18:19.600
 all of these techniques on using all of these tools. Be sure

361
00:18:19.600 --> 00:18:22.400
 to start taking notes simply because

362
00:18:22.400 --> 00:18:25.400
 at the end of a pantry shantas, you need to compile your

363
00:18:25.400 --> 00:18:28.800
 notes and create a very good executive any

364
00:18:28.800 --> 00:18:31.500
 technical report. Once you start performing any

365
00:18:31.500 --> 00:18:34.700
 sort of technical stuff start creating your

366
00:18:34.700 --> 00:18:38.100
 notes. I highly recommend to use any new

367
00:18:37.100 --> 00:18:40.600
 tea can up you can use Google Docs you

368
00:18:40.600 --> 00:18:40.800
 can use

369
00:18:40.900 --> 00:18:43.900
Microsoft OneNote you could

370
00:18:43.900 --> 00:18:46.200
 use Microsoft Word you could even

371
00:18:46.200 --> 00:18:49.600
 use notion if you want, but please ensure your notes are

372
00:18:49.600 --> 00:18:51.500
 backed up and secured all times.

373
00:18:52.400 --> 00:18:55.300
So now that we have an idea on what this system

374
00:18:55.300 --> 00:18:58.300
 is Let's scan the not a

375
00:18:58.300 --> 00:19:01.300
 system or the next system. So let's changes the

376
00:19:01.300 --> 00:19:04.200
 dot tte. Like so hit enter

377
00:19:04.200 --> 00:19:07.900
 and once again, I'm going to pause the video because this

378
00:19:07.900 --> 00:19:10.300
 usually takes quite some time to complete.

379
00:19:13.300 --> 00:19:17.200
After a few minutes the sky is finally completed similarly to

380
00:19:16.200 --> 00:19:19.400
 the type of results. We got in the previous scan

381
00:19:19.400 --> 00:19:22.300
 by scanning Delano space machine. We can see

382
00:19:22.300 --> 00:19:25.100
 the same sort of four models use to scan

383
00:19:25.100 --> 00:19:28.500
 this system, which is that TT. This system is

384
00:19:28.500 --> 00:19:31.500
 also running FTP, but it is running in Microsoft

385
00:19:31.500 --> 00:19:32.600
 version of FTP.

386
00:19:33.400 --> 00:19:36.400
It is using open SSH 7.1. And

387
00:19:36.400 --> 00:19:40.400
 again, we can simply take all of these information and

388
00:19:39.400 --> 00:19:42.600
 do some research on Google to

389
00:19:42.600 --> 00:19:45.800
 determine what it is any sort of known security flaws

390
00:19:45.800 --> 00:19:48.800
 and what it is any sort of exploits for

391
00:19:48.800 --> 00:19:49.800
 these services.

392
00:19:50.700 --> 00:19:53.700
However, we can see that there are many Microsoft services.

393
00:19:53.700 --> 00:19:57.200
 But if we take a look at Port 445,

394
00:19:56.200 --> 00:20:00.000
 it's specifies exact

395
00:19:59.300 --> 00:20:02.200
 version of a Windows and it's a

396
00:20:02.200 --> 00:20:06.500
 Windows Server 2008 R2 standard width

397
00:20:05.500 --> 00:20:08.800
 this specific build

398
00:20:08.800 --> 00:20:11.200
 number 7601 that is

399
00:20:11.200 --> 00:20:14.400
 running so spark 1 so great. If we

400
00:20:14.400 --> 00:20:17.600
 screw it on some more we will see all the ports

401
00:20:17.600 --> 00:20:20.400
 are open. We could even see there's an SQL silver

402
00:20:20.400 --> 00:20:23.400
 running on this system, but screw only

403
00:20:23.400 --> 00:20:27.900
 one further way down. We don't almost

404
00:20:26.900 --> 00:20:30.100
 got screw

405
00:20:29.100 --> 00:20:30.600
 in way down.

406
00:20:34.400 --> 00:20:38.600
We can see that it performs a basic smb/os Discovery

407
00:20:37.600 --> 00:20:40.200
 scan by using the

408
00:20:40.200 --> 00:20:43.500
 script. Of course, it tells us the operating system which

409
00:20:43.500 --> 00:20:46.400
 we found earlier, but on this section

410
00:20:46.400 --> 00:20:50.000
 it verified operating system for us and

411
00:20:49.100 --> 00:20:52.400
 told us the actual CP is a

412
00:20:52.400 --> 00:20:55.600
 Windows to a 2008 series spark

413
00:20:55.600 --> 00:20:58.400
 1. Well, this is an odated operating

414
00:20:58.400 --> 00:21:02.900
 system, which means they are so many security weaknesses

415
00:21:01.900 --> 00:21:04.800
 on this version of

416
00:21:04.800 --> 00:21:07.300
 Windows. So when we reach on to

417
00:21:07.300 --> 00:21:10.800
 the section on exploitation, we'll take

418
00:21:10.800 --> 00:21:14.000
 a look at using different exploits to

419
00:21:13.900 --> 00:21:16.800
 compromise each of these security weaknesses

420
00:21:16.800 --> 00:21:19.600
 phone both on the lanox system

421
00:21:19.600 --> 00:21:21.000
 on the window system.

422
00:21:25.400 --> 00:21:28.400
So great. Now that we have seen how to use and map

423
00:21:28.400 --> 00:21:31.600
 discover common ports identify earning Services

424
00:21:31.600 --> 00:21:34.800
 performed monograbbing unidentifying suits

425
00:21:34.800 --> 00:21:38.200
 Vision. Let's take a look at some common evasion

426
00:21:37.200 --> 00:21:40.700
 techniques that we can use it and map to avoid

427
00:21:40.700 --> 00:21:43.700
 being detected while performing Network scans

428
00:21:43.700 --> 00:21:44.400
 on a network.

429
00:21:46.300 --> 00:21:50.100
During and map scans, we could even spoof our Mac

430
00:21:49.100 --> 00:21:52.600
 address automatically by using and map so

431
00:21:52.600 --> 00:21:55.900
 you don't need to really change your Mac address directly on

432
00:21:55.900 --> 00:21:58.300
 our network adapter. We can simply use a command

433
00:21:58.300 --> 00:22:01.400
 such as nmap dash dash spoof like

434
00:22:01.400 --> 00:22:01.600
 so

435
00:22:02.500 --> 00:22:03.400
Dash mark

436
00:22:04.300 --> 00:22:07.000
zero for randomization and then we can

437
00:22:07.500 --> 00:22:10.200
 specify a targets IP address such as

438
00:22:10.200 --> 00:22:14.800
 let's see 172.t.1 dot.

439
00:22:13.800 --> 00:22:15.100
 Let's see.

440
00:22:16.900 --> 00:22:19.300
T6 just seeing right

441
00:22:19.300 --> 00:22:22.600
 so during this and map scan it will

442
00:22:22.600 --> 00:22:26.400
 actually spoof all Mac address automatically and if

443
00:22:25.400 --> 00:22:28.800
 any sort of Security Professionals with

444
00:22:28.800 --> 00:22:31.300
 the captured the network Pockets or even check the logs

445
00:22:31.300 --> 00:22:34.800
 will be using is simply randomly generated

446
00:22:34.800 --> 00:22:35.400
 Mac address.

447
00:22:36.100 --> 00:22:40.100
Another Technique we can use is we can simply specify

448
00:22:39.100 --> 00:22:42.500
 the dash capital S command to

449
00:22:42.500 --> 00:22:45.800
 spoof our IP address instead so we

450
00:22:45.800 --> 00:22:48.200
 can use let's say sudo.

451
00:22:49.300 --> 00:22:52.400
Just ensure we use administrative privileges to run these

452
00:22:52.400 --> 00:22:55.800
 commands sudo and map Dash capital

453
00:22:55.800 --> 00:22:58.300
 S. I'm going to specify a random

454
00:22:58.300 --> 00:23:01.600
 IP address within the actual Target Network.

455
00:23:01.600 --> 00:23:05.400
 So let's say we use tt.1.1 like

456
00:23:05.400 --> 00:23:08.400
 so or probably the 10 then we

457
00:23:08.400 --> 00:23:09.600
 can specify - e

458
00:23:10.400 --> 00:23:13.400
Ethernet and this is the specify our

459
00:23:13.400 --> 00:23:17.500
 ethernet adapter one and no we can specify the

460
00:23:16.500 --> 00:23:19.400
 actual Target IP address,

461
00:23:19.400 --> 00:23:22.200
 which is let's say one seven two

462
00:23:22.200 --> 00:23:25.400
 dot ct.1 dot. Let's

463
00:23:25.400 --> 00:23:28.100
 see TT it for example.

464
00:23:29.300 --> 00:23:32.700
So that's two techniques that we can use actually spoof or

465
00:23:32.700 --> 00:23:36.200
 Mac addresses and IP addresses when performing

466
00:23:35.200 --> 00:23:37.400
 Network scans.

467
00:23:40.600 --> 00:23:44.200
During this video. We have taken a look at detecting operating

468
00:23:43.200 --> 00:23:47.000
 systems and detecting service

469
00:23:46.300 --> 00:23:49.900
 versions using the end map tool on Kali

470
00:23:49.900 --> 00:23:52.200
 lancs. Furthermore. You have seen how to perform

471
00:23:52.200 --> 00:23:55.000
 Port scans using and map and we have taken a look at

472
00:23:55.600 --> 00:23:58.500
 common Vision techniques using and map simply by

473
00:23:58.500 --> 00:24:02.100
 spoofing the MAC address and IP addresses during

474
00:24:01.100 --> 00:24:03.300
 and end map scan.

475
00:24:05.300 --> 00:24:08.400
In the next video, we will take a look at performing in

476
00:24:08.400 --> 00:24:11.300
 network vulnerability scan only who's using

477
00:24:11.300 --> 00:24:14.600
 the necess tool. I hope this video has been informative for

478
00:24:14.600 --> 00:24:16.500
 you and I will see you in the next one.
