WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.500 --> 00:00:10.500
Hello everyone in this lesson. We will analyze the host

1
00:00:10.500 --> 00:00:13.500
 information over the hcp and

2
00:00:13.500 --> 00:00:15.700
 net bios and curbers.

3
00:00:17.400 --> 00:00:20.500
Firstly let's talk about the DHCP protocol

4
00:00:20.500 --> 00:00:23.900
 DCP protocol means Dynamic host

5
00:00:23.900 --> 00:00:26.500
 configuration protocol and it's a

6
00:00:26.500 --> 00:00:29.500
 protocol used to dynamically assign IP addresses to

7
00:00:29.500 --> 00:00:32.300
 devices on a network the hcp is

8
00:00:32.300 --> 00:00:36.000
 a client server protocol where the hcp

9
00:00:35.200 --> 00:00:38.500
 store will maintains a pool of available IP

10
00:00:38.500 --> 00:00:41.800
 addresses and assign them to thcp clients

11
00:00:41.800 --> 00:00:42.800
 upon request.

12
00:00:43.800 --> 00:00:46.800
So when a device such as a computer is

13
00:00:46.800 --> 00:00:49.700
 connected to a network. It sends

14
00:00:49.700 --> 00:00:52.700
 a broadcast message requesting an IP

15
00:00:52.700 --> 00:00:55.500
 address and the DHCP server receives

16
00:00:55.500 --> 00:00:58.500
 this request and assigns unavailable IP address

17
00:00:58.500 --> 00:01:01.200
 to the device along with the subnet mask

18
00:01:01.200 --> 00:01:04.300
 default gateway and DNS server information.

19
00:01:05.400 --> 00:01:09.100
As you know, this process is called phcp leasing.

20
00:01:08.100 --> 00:01:11.900
 The hcp release time is

21
00:01:11.900 --> 00:01:14.600
 the amount of time for which the

22
00:01:14.600 --> 00:01:17.800
 DHCP server resides an IP address line.

23
00:01:18.400 --> 00:01:21.700
After the least time expires declined must

24
00:01:21.700 --> 00:01:24.000
 request a new IP address assignment.

25
00:01:24.700 --> 00:01:28.100
Gcp also allows for the automatic renewal

26
00:01:27.100 --> 00:01:31.400
 of IP address leases before they expire.

27
00:01:32.200 --> 00:01:35.900
So DHCP also includes a feature called the hcp

28
00:01:35.900 --> 00:01:38.500
 reservation which allows the administrator to

29
00:01:38.500 --> 00:01:41.700
 permanently assign a specific IP address to

30
00:01:41.700 --> 00:01:44.600
 a specific device based on its Mac

31
00:01:44.600 --> 00:01:44.700
 address.

32
00:01:45.400 --> 00:01:49.000
This is useful for devices that need to be accessible at

33
00:01:48.700 --> 00:01:51.000
 a known IP address such as

34
00:01:51.800 --> 00:01:53.000
 servers or parenters.

35
00:01:53.600 --> 00:01:56.200
In summary DHCP is a protocol used to

36
00:01:56.200 --> 00:01:59.300
 dynamically assign IP addresses to devices on

37
00:01:59.300 --> 00:01:59.700
 a network.

38
00:02:00.600 --> 00:02:04.100
And it provides IP subnet mask

39
00:02:03.100 --> 00:02:06.900
 default gateway and DNS server

40
00:02:06.900 --> 00:02:10.100
 information to the client upon request and also

41
00:02:09.100 --> 00:02:13.200
 allows for DHCP reservation to

42
00:02:12.200 --> 00:02:16.100
 assign specific IP addresses to

43
00:02:15.100 --> 00:02:17.300
 specific devices.

44
00:02:18.600 --> 00:02:21.600
Now, let's look at a known DHCP conversation

45
00:02:21.600 --> 00:02:24.200
 with an example Network traffic in Wireshark.

46
00:02:26.500 --> 00:02:29.100
In this PK file, the first picket is a

47
00:02:29.100 --> 00:02:31.000
 broadcast packet.

48
00:02:31.700 --> 00:02:34.400
As you can see the destination IP address

49
00:02:34.400 --> 00:02:38.400
 and the destination Mac address are broadcast addresses.

50
00:02:39.100 --> 00:02:42.200
So the IP address of the source device sending the

51
00:02:42.200 --> 00:02:46.700
 broadcast is 0.0.0.0 because

52
00:02:46.700 --> 00:02:49.600
 it has joined the network and doesn't have

53
00:02:49.600 --> 00:02:50.600
 an IP address yet.

54
00:02:51.400 --> 00:02:54.100
Sends a broadcast in order to get an IP address

55
00:02:54.100 --> 00:02:57.900
 and the device sending the broadcast as a

56
00:02:57.900 --> 00:03:02.100
 MAC address like this and include FC

57
00:03:00.100 --> 00:03:03.100
 and 42.

58
00:03:04.100 --> 00:03:07.700
This is the MAC address of the device sending broadcast.

59
00:03:07.700 --> 00:03:10.600
 Now, let's expand the dynamic host

60
00:03:10.600 --> 00:03:14.100
 configuration protocol DHCP protocol field in

61
00:03:13.100 --> 00:03:16.600
 here. The first information that

62
00:03:16.600 --> 00:03:19.700
 we can see is this is a discover packet,

63
00:03:19.700 --> 00:03:20.300
 so

64
00:03:21.500 --> 00:03:24.800
Then scrolling down and and we

65
00:03:24.800 --> 00:03:27.200
 can see again the IP address of the

66
00:03:27.200 --> 00:03:30.300
 device. It has no iPad. It has

67
00:03:30.300 --> 00:03:34.500
 no IP address now and the Really

68
00:03:33.500 --> 00:03:36.700
 agent IP address also is

69
00:03:36.700 --> 00:03:37.200
 the same.

70
00:03:38.400 --> 00:03:40.100
and declined mechanics

71
00:03:41.200 --> 00:03:41.900
as you know

72
00:03:42.600 --> 00:03:45.500
And focus on the option 50 we see

73
00:03:45.500 --> 00:03:50.900
 that the IP address just requested is 0.0.0.

74
00:03:52.200 --> 00:03:55.700
And so the requested IP address hasn't

75
00:03:55.700 --> 00:03:56.800
 been specified yet.

76
00:03:57.500 --> 00:04:00.400
After this cover packet the device

77
00:04:00.400 --> 00:04:04.500
 that has the IP address and with 0.1 is

78
00:04:03.500 --> 00:04:06.900
 sending a response to

79
00:04:06.900 --> 00:04:08.900
 the this IP address.

80
00:04:09.600 --> 00:04:13.100
And it is sending an over and over packet

81
00:04:12.100 --> 00:04:14.600
 as you can see in here.

82
00:04:15.400 --> 00:04:18.500
and when we click on the offer packet

83
00:04:20.600 --> 00:04:22.900
You can see the details in the packet details again.

84
00:04:24.100 --> 00:04:27.400
This device can be our router in the network or

85
00:04:27.400 --> 00:04:30.300
 just a server with TCP function. It doesn't

86
00:04:30.300 --> 00:04:33.600
 matter and we see that DHCP server

87
00:04:33.600 --> 00:04:37.000
 sends an offer packet in response.

88
00:04:37.900 --> 00:04:40.300
And when we look at the packet details

89
00:04:40.300 --> 00:04:43.400
 we see that a subnet mask in here.

90
00:04:44.900 --> 00:04:47.900
You can see in here. The option one

91
00:04:47.900 --> 00:04:50.900
 is representing subnet mask

92
00:04:50.900 --> 00:04:51.300
 information.

93
00:04:52.400 --> 00:04:56.500
And the subnet mask has been offered is ending

94
00:04:55.500 --> 00:04:59.200
 with 255.0.

95
00:05:00.200 --> 00:05:03.500
And we also see that renewable time value in

96
00:05:03.500 --> 00:05:03.500
 here.

97
00:05:04.200 --> 00:05:05.600
When we expand it.

98
00:05:06.200 --> 00:05:10.300
We can see the renewable time value is

99
00:05:09.300 --> 00:05:11.200
 30 minutes.

100
00:05:12.200 --> 00:05:15.600
And it is specified as 30 minutes

101
00:05:15.600 --> 00:05:21.300
 which corresponds to 1,800 seconds.

102
00:05:22.700 --> 00:05:25.200
And the renewal time value specifies the

103
00:05:25.200 --> 00:05:28.600
 time in seconds from other assignment until the

104
00:05:28.600 --> 00:05:30.800
 client enters the renewing state.

105
00:05:31.600 --> 00:05:34.600
And we can see in option 51 that

106
00:05:34.600 --> 00:05:37.000
 the IP address lease time.

107
00:05:38.400 --> 00:05:41.300
So the IP address list time is one hour.

108
00:05:42.200 --> 00:05:45.600
And DHCP packets can provide information about the

109
00:05:45.600 --> 00:05:48.900
 duration of thcp leases choose. The

110
00:05:48.900 --> 00:05:51.600
 amount of time that a device

111
00:05:51.600 --> 00:05:54.400
 is allowed to use a specific IP address

112
00:05:54.400 --> 00:05:57.800
 before it must request anyone.

113
00:05:57.800 --> 00:06:00.200
 So this information can be

114
00:06:00.200 --> 00:06:04.300
 used to identify devices that have long thcp lasers.

115
00:06:04.800 --> 00:06:07.300
and in option 54

116
00:06:08.500 --> 00:06:11.300
when we expanded we can see

117
00:06:11.300 --> 00:06:11.500
 that.

118
00:06:12.700 --> 00:06:15.600
the IP address of the DHCP

119
00:06:15.600 --> 00:06:16.000
 server

120
00:06:16.800 --> 00:06:19.800
So it ends with 0.1. So

121
00:06:19.800 --> 00:06:22.900
 in response to this offer, the client sends

122
00:06:22.900 --> 00:06:25.700
 a request packet as you

123
00:06:25.700 --> 00:06:29.200
 can see here. We see that the requested IP

124
00:06:28.200 --> 00:06:29.700
 address.

125
00:06:31.400 --> 00:06:34.700
And with 0.10 now we

126
00:06:34.700 --> 00:06:38.300
 can see the requested IP address as well

127
00:06:38.300 --> 00:06:41.300
 and this information wasn't included in the

128
00:06:41.300 --> 00:06:42.800
 offer before.

129
00:06:44.400 --> 00:06:47.400
We couldn't see the requested IP address

130
00:06:47.400 --> 00:06:50.400
 in here because it wasn't a request

131
00:06:50.400 --> 00:06:53.600
 a peckant but in the request packet,

132
00:06:53.600 --> 00:06:56.700
 we can see the request IP address. So this

133
00:06:56.700 --> 00:06:59.600
 IP address has been requested by

134
00:06:59.600 --> 00:07:02.800
 the client that has no IP

135
00:07:02.800 --> 00:07:06.300
 address yet. And in addition other parameters

136
00:07:05.300 --> 00:07:09.600
 requested in the request are subnet mask

137
00:07:09.600 --> 00:07:12.600
 and then router information and

138
00:07:12.600 --> 00:07:16.800
 the domain name server information are requested

139
00:07:15.800 --> 00:07:17.700
 by the client.

140
00:07:18.500 --> 00:07:21.900
At this moment so and the

141
00:07:21.900 --> 00:07:24.600
 network time protocol service also has

142
00:07:24.600 --> 00:07:27.300
 been requested by the client in this

143
00:07:27.300 --> 00:07:30.300
 packet. And these parameters are the

144
00:07:30.300 --> 00:07:33.200
 information the client needs to

145
00:07:33.200 --> 00:07:37.400
 establish a successful connection successful network

146
00:07:36.400 --> 00:07:39.900
 connection. So then the sap

147
00:07:39.900 --> 00:07:43.100
 is server responds with an

148
00:07:42.100 --> 00:07:45.900
 egg packet with an egg message. And

149
00:07:45.900 --> 00:07:49.700
 if you have noticed from here on declines

150
00:07:48.700 --> 00:07:51.500
 IP address is now the

151
00:07:51.500 --> 00:07:55.200
 requested IP address the client requested this

152
00:07:54.200 --> 00:07:57.500
 IP address the in the packet

153
00:07:57.500 --> 00:08:00.200
 in the previous packet in here.

154
00:08:00.200 --> 00:08:03.900
 Now, it has this IP address that has

155
00:08:03.900 --> 00:08:07.700
 been requested by the client and it

156
00:08:06.700 --> 00:08:09.600
 has received the IP address

157
00:08:09.600 --> 00:08:13.000
 and link with 0.10 as

158
00:08:12.100 --> 00:08:15.500
 you can see now it has an IP

159
00:08:15.500 --> 00:08:18.100
 address as a result now, I will

160
00:08:18.500 --> 00:08:22.400
You a filter expiration to analyze

161
00:08:21.400 --> 00:08:24.500
 unusual DHCP requests

162
00:08:24.500 --> 00:08:25.700
 in our Network.

163
00:08:29.600 --> 00:08:32.900
Now I am typing the filter expression.

164
00:08:40.500 --> 00:08:42.100
so in this filter

165
00:08:43.100 --> 00:08:46.100
As you can see we see that the code of the

166
00:08:46.100 --> 00:08:49.500
 option parameter is equal to

167
00:08:49.500 --> 00:08:52.400
 3. So this code is

168
00:08:52.400 --> 00:08:56.600
 used to create request packets. Maybe we

169
00:08:56.600 --> 00:08:59.800
 can see in the request in a request packet,

170
00:08:59.800 --> 00:09:00.900
 Discord.

171
00:09:03.300 --> 00:09:05.600
Let's look at in the packet details.

172
00:09:06.800 --> 00:09:10.100
And as you can see the request packets

173
00:09:09.100 --> 00:09:13.200
 as the DHCP value a

174
00:09:12.200 --> 00:09:15.300
 DHCP value as three.

175
00:09:16.100 --> 00:09:20.100
So this code is used to create and

176
00:09:19.100 --> 00:09:21.600
 request packet. So.

177
00:09:24.300 --> 00:09:27.900
so if you want to filter out the request packets

178
00:09:27.900 --> 00:09:30.100
 in the DHCP protocol you can

179
00:09:30.100 --> 00:09:33.500
 use this parameter directly and you

180
00:09:33.500 --> 00:09:36.900
 know that you can hold this

181
00:09:36.900 --> 00:09:39.800
 information and direct

182
00:09:39.800 --> 00:09:40.400
 into the

183
00:09:42.600 --> 00:09:45.200
display filter field and you can drop it

184
00:09:45.200 --> 00:09:45.800
 in here.

185
00:09:47.200 --> 00:09:50.700
And we are choosing the selected one as you

186
00:09:50.700 --> 00:09:53.700
 can see the same filter has been applied

187
00:09:53.700 --> 00:09:54.500
 in here.

188
00:09:56.200 --> 00:09:57.300
With the previous one.

189
00:09:57.900 --> 00:10:00.600
And you can see the

190
00:10:00.600 --> 00:10:03.600
 request packet only with this filtering

191
00:10:03.600 --> 00:10:04.600
 expression.

192
00:10:05.800 --> 00:10:08.400
So as a result DCP packets can provide

193
00:10:08.400 --> 00:10:11.700
 information about behavior of the hcp

194
00:10:11.700 --> 00:10:14.200
 clients and such as the number

195
00:10:14.200 --> 00:10:17.200
 of DHCP requests and the time

196
00:10:17.200 --> 00:10:18.200
 between requests.

197
00:10:18.900 --> 00:10:21.300
So this information can be used to identify

198
00:10:21.300 --> 00:10:24.800
 clients that are misconfigured or that have

199
00:10:24.800 --> 00:10:27.700
 some network issues and you

200
00:10:27.700 --> 00:10:30.700
 can find the network issues with

201
00:10:30.700 --> 00:10:35.100
 investigating and discovering

202
00:10:33.100 --> 00:10:36.800
 some DHCP

203
00:10:36.800 --> 00:10:37.800
 packets on your network.

204
00:10:40.300 --> 00:10:44.000
And let's talk about gcp attacks gcp

205
00:10:43.400 --> 00:10:46.700
 packets can be used to detect the SCP

206
00:10:46.700 --> 00:10:50.000
 starvation tax or DHCP. Superfic

207
00:10:49.500 --> 00:10:52.200
 attacks. TCP starvation attack is

208
00:10:52.200 --> 00:10:55.400
 a type of Daniel of service, you know,

209
00:10:55.400 --> 00:10:58.500
 those attack where an attacker

210
00:10:58.500 --> 00:11:01.300
 sense a large number of thcp requests

211
00:11:01.300 --> 00:11:04.500
 to exhaust the sap service IP

212
00:11:04.500 --> 00:11:05.000
 address pool.

213
00:11:05.600 --> 00:11:07.900
And the ACP superfink attack?

214
00:11:08.700 --> 00:11:11.200
Anticipating attack is a type

215
00:11:11.200 --> 00:11:14.700
 of men in the middle attack where an attacker sends fake

216
00:11:14.700 --> 00:11:17.500
 DHCP responses to clients in an

217
00:11:17.500 --> 00:11:21.200
 attempt to redirect their traffic to

218
00:11:20.200 --> 00:11:24.000
 a different network to detect

219
00:11:23.700 --> 00:11:26.200
 DHCP records forward. You can

220
00:11:26.200 --> 00:11:29.400
 filter for DHCP request packets that have a

221
00:11:29.400 --> 00:11:32.100
 high number of requests from the

222
00:11:32.100 --> 00:11:35.500
 same client or from multiple clients in a

223
00:11:35.500 --> 00:11:36.700
 short period of time.

224
00:11:37.600 --> 00:11:40.300
So to detect the SCP is proving attack.

225
00:11:40.300 --> 00:11:43.900
 You can filter for DCP over packets

226
00:11:43.900 --> 00:11:47.200
 that come from unexpected TCP

227
00:11:46.200 --> 00:11:47.600
 servers.

228
00:11:48.100 --> 00:11:51.900
Or that have unusual values for the DHCP options

229
00:11:51.900 --> 00:11:55.100
 to do this. You can use that

230
00:11:54.100 --> 00:11:57.200
 filter expression like this.

231
00:12:12.100 --> 00:12:16.200
And when you apply this filter, you will see only

232
00:12:15.200 --> 00:12:19.100
 offer packets only the sap

233
00:12:18.100 --> 00:12:21.800
 offer packets and you can investigate

234
00:12:21.800 --> 00:12:24.500
 the DHCP offer packets

235
00:12:24.500 --> 00:12:28.000
 applying this filter expression. So you

236
00:12:27.100 --> 00:12:31.300
 can search for the some attack

237
00:12:30.300 --> 00:12:33.400
 patterns in the ACP terrific

238
00:12:33.400 --> 00:12:37.300
 and you can use that to find

239
00:12:38.600 --> 00:12:41.200
some malicious activities on your network.

240
00:12:43.600 --> 00:12:46.600
Okay. Now we are going to investigate the net bios

241
00:12:46.600 --> 00:12:47.100
 protocol.

242
00:12:49.500 --> 00:12:52.100
So over this PK file in order

243
00:12:52.100 --> 00:12:55.400
 to see on the net bios traffic we can type this

244
00:12:55.400 --> 00:12:56.400
 filter.

245
00:12:59.900 --> 00:13:02.500
N b and s is a

246
00:13:02.500 --> 00:13:05.700
 filtering expression in order to see only the

247
00:13:05.700 --> 00:13:08.400
 net buyers traffic and click on the enter.

248
00:13:09.300 --> 00:13:13.100
As you can see now we only see the ambience

249
00:13:12.100 --> 00:13:15.500
 which means net bios

250
00:13:15.500 --> 00:13:18.100
 packets net buyers traffic.

251
00:13:21.100 --> 00:13:24.600
So net bios, which means Network basic input

252
00:13:24.600 --> 00:13:27.400
 output system is a protocol

253
00:13:27.400 --> 00:13:30.200
 that provides services for applications on a

254
00:13:30.200 --> 00:13:33.200
 local area network to communicate with

255
00:13:33.200 --> 00:13:33.800
 each other.

256
00:13:34.600 --> 00:13:37.400
Maybe you know net buyers provides

257
00:13:37.400 --> 00:13:40.600
 three main services and these services are

258
00:13:40.600 --> 00:13:43.500
 name servers and these services

259
00:13:43.500 --> 00:13:47.100
 are names service session service and

260
00:13:46.100 --> 00:13:49.400
 datagram service. So what

261
00:13:49.400 --> 00:13:52.000
 is the name service? Let's talk about

262
00:13:52.600 --> 00:13:55.600
 a little bit the name service allows devices

263
00:13:55.600 --> 00:13:58.700
 on a network to register their names and IP

264
00:13:58.700 --> 00:14:02.000
 addresses and to resolve the names of other device

265
00:14:01.400 --> 00:14:02.700
 on the network.

266
00:14:04.500 --> 00:14:08.100
And this errors applications to identify and

267
00:14:07.100 --> 00:14:11.100
 connect to other devices by name rather

268
00:14:10.100 --> 00:14:13.500
 than by IP address in order

269
00:14:13.500 --> 00:14:17.300
 to get details. We can look at queries in packet

270
00:14:16.300 --> 00:14:17.600
 details.

271
00:14:18.800 --> 00:14:22.100
So let's look at in a packet tail

272
00:14:21.100 --> 00:14:24.300
 details on a packet.

273
00:14:27.500 --> 00:14:30.400
And let me show you net bios name

274
00:14:30.400 --> 00:14:32.800
 service information in here.

275
00:14:34.300 --> 00:14:37.200
So in order to get details, we can look at the

276
00:14:37.200 --> 00:14:41.100
 queries in packet details

277
00:14:40.100 --> 00:14:44.100
 and when we look at the queries, we

278
00:14:43.100 --> 00:14:47.600
 see the name of the mission.

279
00:14:48.300 --> 00:14:51.900
And its name is ECI domain.

280
00:14:51.900 --> 00:14:55.400
 So again expanding and

281
00:14:54.400 --> 00:14:57.700
 as you can see, the name

282
00:14:57.700 --> 00:15:00.900
 information is ECI domain

283
00:15:00.900 --> 00:15:03.700
 and this mission is a

284
00:15:03.700 --> 00:15:04.800
 domain controller.

285
00:15:05.500 --> 00:15:08.500
So we can learn this information

286
00:15:08.500 --> 00:15:12.700
 from this queries information and

287
00:15:11.700 --> 00:15:14.500
 the type value and

288
00:15:14.500 --> 00:15:16.900
 the class value are also in here.

289
00:15:17.700 --> 00:15:20.200
So and we can look

290
00:15:20.200 --> 00:15:22.000
 at another machine.

291
00:15:23.400 --> 00:15:26.800
In detailed and in here this

292
00:15:26.800 --> 00:15:29.800
 machine has a name with work

293
00:15:29.800 --> 00:15:29.900
 group.

294
00:15:30.500 --> 00:15:34.000
And this machine is a domain Master browser.

295
00:15:33.800 --> 00:15:36.900
 We can learn it from here.

296
00:15:39.100 --> 00:15:44.100
Thanks to net bios. We can get detailed such as

297
00:15:44.100 --> 00:15:47.700
 like this we can get detailed

298
00:15:47.700 --> 00:15:50.700
 information about the machines in our local network

299
00:15:50.700 --> 00:15:51.500
 in this way.

300
00:15:52.400 --> 00:15:56.100
And we can analyze the traffic between them. So

301
00:15:55.100 --> 00:15:59.000
 if there are errors or anomalies we

302
00:15:58.100 --> 00:16:03.900
 can discover them in discovering

303
00:16:01.900 --> 00:16:05.700
 and identifying

304
00:16:04.700 --> 00:16:07.800
 some problems on

305
00:16:07.800 --> 00:16:10.400
 our Network. So, of course

306
00:16:10.400 --> 00:16:13.500
 we can filter by name to see the traffic

307
00:16:13.500 --> 00:16:16.400
 of a particular client. So let's

308
00:16:16.400 --> 00:16:20.300
 say I want to see only this Mission traffic

309
00:16:19.300 --> 00:16:22.500
 on our Network and I want

310
00:16:22.500 --> 00:16:26.000
 to use the name information to filter

311
00:16:25.300 --> 00:16:28.600
 out you can do that

312
00:16:28.600 --> 00:16:32.000
 in two ways one way,

313
00:16:31.400 --> 00:16:34.900
 you know preparing as filter.

314
00:16:36.200 --> 00:16:40.300
Like this you can use this method to

315
00:16:39.300 --> 00:16:42.100
 filter out and the other

316
00:16:42.100 --> 00:16:46.700
 one as you can guess we

317
00:16:45.700 --> 00:16:49.100
 have used before we can

318
00:16:48.100 --> 00:16:51.700
 we can take the name

319
00:16:51.700 --> 00:16:54.500
 information and drag into

320
00:16:54.500 --> 00:16:57.100
 the display filter and drop it.

321
00:16:57.700 --> 00:17:01.000
So when we do that, you can

322
00:17:00.500 --> 00:17:04.400
 see the only traffic which

323
00:17:03.400 --> 00:17:07.900
 associated with the mission as

324
00:17:06.900 --> 00:17:09.400
 the name work group.

325
00:17:09.900 --> 00:17:13.100
So now I can see the only

326
00:17:12.100 --> 00:17:15.800
 packets associated with this measure.

327
00:17:18.200 --> 00:17:21.700
So that's all about the net buyers traffic.

328
00:17:24.300 --> 00:17:26.800
Okay, let's jump to the kerberus now.

329
00:17:29.500 --> 00:17:32.700
So gerberus is a network Authentication Protocol that

330
00:17:32.700 --> 00:17:35.500
 is designed to provide secure authentication for

331
00:17:35.500 --> 00:17:39.200
 clients and service on a computer network and

332
00:17:38.200 --> 00:17:42.200
 it was developed by the MIT in

333
00:17:41.200 --> 00:17:43.500
 the 1980s.

334
00:17:44.200 --> 00:17:48.500
And it is widely used in windows-based networks,

335
00:17:48.500 --> 00:17:51.300
 as you know, and other environments that

336
00:17:51.300 --> 00:17:53.300
 require secure Authentication.

337
00:17:54.900 --> 00:17:57.700
Covers is the default authentication Service

338
00:17:57.700 --> 00:18:00.100
 for Microsoft Windows domains.

339
00:18:00.600 --> 00:18:04.400
And in an active directory domains,

340
00:18:03.400 --> 00:18:06.300
 maybe you know, so it is

341
00:18:06.300 --> 00:18:09.100
 widely used in windows-based networks and

342
00:18:09.100 --> 00:18:12.500
 it is used in Unix environments as well

343
00:18:12.500 --> 00:18:15.700
 and covers uses a combination

344
00:18:15.700 --> 00:18:19.400
 of secret K cryptography and

345
00:18:19.400 --> 00:18:22.600
 a centralized authentication server

346
00:18:22.600 --> 00:18:25.300
 to provide secure or the indication

347
00:18:25.300 --> 00:18:29.300
 the key component of the covers protocol

348
00:18:29.300 --> 00:18:32.500
 is the curves or the indication servers, which is

349
00:18:32.500 --> 00:18:36.100
 responsible for organicating clients and

350
00:18:35.100 --> 00:18:37.500
 servers on the network.

351
00:18:38.700 --> 00:18:41.400
A Nicholas such as a computer or a

352
00:18:41.400 --> 00:18:44.700
 user wants to access a network resource. It

353
00:18:44.700 --> 00:18:47.800
 sends a request to the terrible authentication

354
00:18:47.800 --> 00:18:50.900
 server and the authentication server

355
00:18:50.900 --> 00:18:53.400
 checks the client's credential and if it

356
00:18:53.400 --> 00:18:56.400
 is valid generates a unique session

357
00:18:56.400 --> 00:19:00.100
 key for the client. So the session

358
00:18:59.100 --> 00:19:02.400
 key is then encrypted with the

359
00:19:02.400 --> 00:19:05.800
 clients secret key and encrypted session

360
00:19:05.800 --> 00:19:09.000
 key is sent back to the client and

361
00:19:08.900 --> 00:19:11.400
 decline then uses the session key

362
00:19:11.400 --> 00:19:14.200
 to encrypt a request for the network

363
00:19:14.200 --> 00:19:15.000
 resource.

364
00:19:15.600 --> 00:19:18.500
And sent the encrypted request to

365
00:19:18.500 --> 00:19:21.900
 the server that hosts the resource

366
00:19:21.900 --> 00:19:24.800
 and the server which also has

367
00:19:24.800 --> 00:19:28.200
 a copy of the session key decrypts the

368
00:19:28.200 --> 00:19:31.100
 request and grants access to the

369
00:19:31.100 --> 00:19:35.600
 resource. And one of the key benefits of servers

370
00:19:34.600 --> 00:19:37.500
 is that it doesn't send

371
00:19:37.500 --> 00:19:41.100
 plain text password over the network. So another

372
00:19:40.100 --> 00:19:43.700
 benefit is that it uses ticket

373
00:19:43.700 --> 00:19:47.200
 which are encrypted and have limited

374
00:19:46.200 --> 00:19:49.700
 lifetime in this way. Even

375
00:19:49.700 --> 00:19:53.500
 if the ticket is intercepted or leaked

376
00:19:52.500 --> 00:19:55.500
 it will be users after the

377
00:19:55.500 --> 00:19:56.200
 lifetime.

378
00:19:57.500 --> 00:20:00.300
Since keys are used in

379
00:20:00.300 --> 00:20:03.400
 this way in communication with turbulence. It

380
00:20:03.400 --> 00:20:05.700
 is necessary to decode the traffic.

381
00:20:06.500 --> 00:20:10.100
So to decode curbs traffic we must

382
00:20:09.100 --> 00:20:12.200
 have the keys used in the traffic.

383
00:20:12.900 --> 00:20:15.500
And if we have a key type file

384
00:20:15.500 --> 00:20:18.600
 that contains key values in this

385
00:20:18.600 --> 00:20:20.700
 way, our job is easy.

386
00:20:21.400 --> 00:20:25.000
And if you have a key type file in that

387
00:20:24.200 --> 00:20:28.000
 situation you can use it to record the

388
00:20:27.000 --> 00:20:28.200
 traffic.

389
00:20:28.900 --> 00:20:31.500
And when we look at the current traffic

390
00:20:31.500 --> 00:20:34.600
 at the first glance, you can

391
00:20:34.600 --> 00:20:37.600
 use a filtering expiration like

392
00:20:37.600 --> 00:20:38.000
 this.

393
00:20:41.400 --> 00:20:44.400
When you type this filtering expiration

394
00:20:44.400 --> 00:20:47.100
 as covers, you will

395
00:20:47.100 --> 00:20:51.300
 see the only purpose traffic on your PK

396
00:20:50.300 --> 00:20:54.200
 file click on the enter as

397
00:20:53.200 --> 00:20:57.800
 you can see now we have the only curbs

398
00:20:56.800 --> 00:21:00.500
 traffic and associated

399
00:20:59.500 --> 00:21:02.700
 with it some traffic

400
00:21:02.700 --> 00:21:05.000
 associated with the covers traffic.

401
00:21:05.600 --> 00:21:09.500
For example, there's an HTTP packet after

402
00:21:08.500 --> 00:21:13.000
 performing servers authentication

403
00:21:12.800 --> 00:21:15.600
 process in a Converse traffic

404
00:21:15.600 --> 00:21:19.000
 in a Converse conversation first. The

405
00:21:18.600 --> 00:21:21.400
 user sends a packet

406
00:21:21.400 --> 00:21:23.300
 to the curve cover server.

407
00:21:25.500 --> 00:21:28.500
Our user has an IP address and

408
00:21:28.500 --> 00:21:31.700
 Suite 12 and 12 and the

409
00:21:31.700 --> 00:21:34.700
 curb is server has an IP address and with

410
00:21:34.700 --> 00:21:35.800
 3.1.

411
00:21:36.500 --> 00:21:39.400
So this is our turbo server and this

412
00:21:39.400 --> 00:21:42.300
 is our client or you can think of

413
00:21:42.300 --> 00:21:46.000
 an user in our Network and user

414
00:21:45.300 --> 00:21:48.100
 is sending a request packet.

415
00:21:48.600 --> 00:21:52.400
To inform the Kerber server

416
00:21:52.400 --> 00:21:54.200
 about its client name.

417
00:21:55.300 --> 00:21:59.000
Client client name information has been

418
00:21:58.900 --> 00:22:01.400
 sent by the client.

419
00:22:02.200 --> 00:22:05.800
So we can see in a curbs field in

420
00:22:05.800 --> 00:22:09.700
 the covers field. The cname information

421
00:22:09.700 --> 00:22:11.700
 is administrator.

422
00:22:12.500 --> 00:22:16.800
So this is the client name information of

423
00:22:15.800 --> 00:22:19.200
 the client and we

424
00:22:18.200 --> 00:22:22.000
 can think of as a sea

425
00:22:21.200 --> 00:22:24.700
 information and the

426
00:22:24.700 --> 00:22:29.000
 client sent the username

427
00:22:27.700 --> 00:22:31.200
 as administrator to

428
00:22:30.200 --> 00:22:33.500
 the curb your server in this pack

429
00:22:33.500 --> 00:22:34.400
 in the first pack.

430
00:22:35.100 --> 00:22:35.400
So

431
00:22:36.500 --> 00:22:39.900
after the client send its

432
00:22:39.900 --> 00:22:42.900
 client name as administrator the

433
00:22:42.900 --> 00:22:46.800
 cover server will respond with

434
00:22:45.800 --> 00:22:48.100
 a response packet.

435
00:22:48.900 --> 00:22:51.800
To the client and in this packet,

436
00:22:51.800 --> 00:22:54.600
 we can see a ticket.

437
00:22:55.600 --> 00:22:59.300
We can we are called as

438
00:22:58.300 --> 00:23:02.500
 TGs this ticket

439
00:23:02.500 --> 00:23:05.200
 and the server is going to respond

440
00:23:05.200 --> 00:23:08.400
 to back with a ticket at TGs like

441
00:23:08.400 --> 00:23:11.300
 this, but we can we can't see the ticket.

442
00:23:12.900 --> 00:23:15.500
As a plain text because

443
00:23:15.500 --> 00:23:19.200
 the we haven't decrypt

444
00:23:18.200 --> 00:23:22.800
 our traffic yet. We should

445
00:23:22.800 --> 00:23:26.300
 use the keyfile to decrypt

446
00:23:25.300 --> 00:23:28.900
 this traffic and in order

447
00:23:28.900 --> 00:23:32.200
 to see the ticket information in

448
00:23:31.200 --> 00:23:35.200
 a plane text. So there

449
00:23:34.200 --> 00:23:36.100
 is a ticket

450
00:23:37.200 --> 00:23:39.600
in the response packet

451
00:23:40.300 --> 00:23:41.500
and now

452
00:23:43.100 --> 00:23:48.200
Here the client are talking

453
00:23:47.200 --> 00:23:50.900
 to the covers interface

454
00:23:50.900 --> 00:23:53.700
 in the Kerber server. So

455
00:23:53.700 --> 00:23:57.100
 there are two interfaces in the

456
00:23:56.100 --> 00:23:59.500
 turbo server. We can think of

457
00:23:59.500 --> 00:24:03.200
 that there are two interfaces

458
00:24:02.200 --> 00:24:05.600
 in our server and one

459
00:24:05.600 --> 00:24:08.800
 of them is called turbos interface. And

460
00:24:08.800 --> 00:24:12.300
 the first two packets is associated

461
00:24:11.300 --> 00:24:14.900
 with the talking to

462
00:24:14.900 --> 00:24:18.700
 the first interface covers

463
00:24:17.700 --> 00:24:21.300
 interface. And then

464
00:24:20.300 --> 00:24:24.100
 in the step three

465
00:24:23.100 --> 00:24:27.300
 client again set is

466
00:24:26.300 --> 00:24:29.800
 sanding a packet a request

467
00:24:29.800 --> 00:24:32.700
 packet and in this

468
00:24:32.700 --> 00:24:33.800
 packet we can see

469
00:24:37.300 --> 00:24:40.300
A request meaning that

470
00:24:40.300 --> 00:24:43.000
 the server that I want

471
00:24:43.200 --> 00:24:43.700
 to talk to.

472
00:24:44.800 --> 00:24:47.500
Is this a client say this?

473
00:24:47.500 --> 00:24:49.600
 I want to I want to talk.

474
00:24:51.300 --> 00:24:53.900
With a server in our Network.

475
00:24:54.800 --> 00:24:57.800
And let's say

476
00:24:57.800 --> 00:25:00.500
 and an nftp server.

477
00:25:00.500 --> 00:25:03.900
 I want to talk and FTP server, or I want

478
00:25:03.900 --> 00:25:06.200
 to talk to the printer.

479
00:25:06.900 --> 00:25:09.600
and in this packet with this packet,

480
00:25:09.600 --> 00:25:11.200
 the client says that

481
00:25:11.700 --> 00:25:14.600
hey curb yourself. I want to talk a

482
00:25:14.600 --> 00:25:15.900
 server in our Network.

483
00:25:16.800 --> 00:25:20.000
And I want to request request making make

484
00:25:19.300 --> 00:25:21.600
 a rocket request about this.

485
00:25:23.300 --> 00:25:27.000
in this request you can see the server name

486
00:25:26.000 --> 00:25:28.500
 the

487
00:25:30.200 --> 00:25:33.500
Server name that the user want to talk

488
00:25:33.500 --> 00:25:33.900
 to.

489
00:25:34.700 --> 00:25:34.800
so

490
00:25:35.700 --> 00:25:38.700
In here, we can see the s name

491
00:25:38.700 --> 00:25:40.100
 server name String.

492
00:25:40.700 --> 00:25:43.200
HTTP so we can understand

493
00:25:43.200 --> 00:25:46.500
 that the client want to talk to

494
00:25:46.500 --> 00:25:49.800
 the HTTP server and

495
00:25:49.800 --> 00:25:52.600
 this server name sittering. Is this

496
00:25:52.600 --> 00:25:54.600
 deny dc.com

497
00:25:55.300 --> 00:25:56.700
so

498
00:25:58.900 --> 00:26:02.200
we can't we can't see some detailed information

499
00:26:01.200 --> 00:26:02.900
 in here.

500
00:26:03.700 --> 00:26:06.400
Because as I told

501
00:26:06.400 --> 00:26:09.500
 you before we haven't decrypt

502
00:26:09.500 --> 00:26:12.800
 our traffic yet traffic yet and in

503
00:26:12.800 --> 00:26:15.500
 this packet in the third packet.

504
00:26:18.600 --> 00:26:22.900
As I said server informed about

505
00:26:22.900 --> 00:26:25.200
 the server that it wants

506
00:26:25.200 --> 00:26:29.700
 to talk and this conversation

507
00:26:28.700 --> 00:26:31.900
 between the user and

508
00:26:31.900 --> 00:26:34.900
 the interface of TGC.

509
00:26:35.500 --> 00:26:38.800
So sorry the interface

510
00:26:38.800 --> 00:26:40.300
 of the TGs.

511
00:26:41.900 --> 00:26:45.700
There is a there's an another interface

512
00:26:44.700 --> 00:26:48.200
 on the cover server

513
00:26:47.200 --> 00:26:51.200
 and it's called as TGs.

514
00:26:52.000 --> 00:26:52.300
so

515
00:26:54.900 --> 00:26:56.100
and to respond

516
00:26:59.600 --> 00:27:01.400
And the curb your server?

517
00:27:03.800 --> 00:27:06.300
sending anti-curable server is sending

518
00:27:06.300 --> 00:27:09.800
 a response to this request about

519
00:27:09.800 --> 00:27:12.600
 talking to a

520
00:27:12.600 --> 00:27:15.200
 server from the client and

521
00:27:16.300 --> 00:27:20.000
In this response, you can see another ticket

522
00:27:19.000 --> 00:27:21.300
 data.

523
00:27:22.200 --> 00:27:23.100
So this ticket

524
00:27:23.800 --> 00:27:28.100
Is for talking with

525
00:27:26.100 --> 00:27:28.700
 the server?

526
00:27:31.400 --> 00:27:35.200
the talking with the servers by client

527
00:27:36.200 --> 00:27:39.700
So the declined will use this ticket

528
00:27:39.700 --> 00:27:42.400
 in order to talk to the

529
00:27:42.400 --> 00:27:44.700
 server that it wants.

530
00:27:46.100 --> 00:27:49.300
And if you have a key type file, you can use it to

531
00:27:49.300 --> 00:27:52.600
 decrypt the curb traffic by

532
00:27:52.600 --> 00:27:53.100
 going to

533
00:27:54.200 --> 00:27:56.900
edit menu and preferences

534
00:28:00.100 --> 00:28:04.300
and covers protocol. We will go to the service

535
00:28:03.300 --> 00:28:04.700
 protocol.

536
00:28:13.900 --> 00:28:17.700
And we will choose the key rb5

537
00:28:16.700 --> 00:28:19.600
 because our current

538
00:28:19.600 --> 00:28:22.100
 protocol as the version 5.

539
00:28:22.800 --> 00:28:26.000
And in here you will choose your

540
00:28:25.200 --> 00:28:28.600
 keyfile, but before doing this,

541
00:28:28.600 --> 00:28:32.000
 you should choose this option.

542
00:28:31.700 --> 00:28:34.300
 You should check this option.

543
00:28:35.100 --> 00:28:38.600
To try to decrypt covers Bluffs to

544
00:28:38.600 --> 00:28:42.700
 obtain additional information and

545
00:28:41.700 --> 00:28:45.500
 some information that

546
00:28:44.500 --> 00:28:48.200
 has been encrypted. So now

547
00:28:47.200 --> 00:28:51.400
 let's choose our key

548
00:28:50.400 --> 00:28:53.600
 type file in here and we

549
00:28:53.600 --> 00:28:56.500
 have it in here. They deny

550
00:28:56.500 --> 00:28:58.000
 dc.com.key

551
00:29:00.200 --> 00:29:04.300
Your file can be in a format dot

552
00:29:03.300 --> 00:29:05.200
 tab.

553
00:29:06.200 --> 00:29:07.200
and open

554
00:29:08.200 --> 00:29:11.900
then you shouldn't change your

555
00:29:11.500 --> 00:29:14.200
 UDP Port TCP Port

556
00:29:14.200 --> 00:29:18.000
 information. If it is not necessary and

557
00:29:17.500 --> 00:29:20.000
 click on the okay button.

558
00:29:21.200 --> 00:29:23.800
Now as you can see there is

559
00:29:24.900 --> 00:29:28.300
such more additional information

560
00:29:27.300 --> 00:29:29.700
 we have

561
00:29:30.900 --> 00:29:34.000
after the decrypting process, we

562
00:29:33.200 --> 00:29:35.300
 have a lot of

563
00:29:36.200 --> 00:29:38.200
extraordinary and

564
00:29:39.200 --> 00:29:42.200
extra information about our traffic

565
00:29:42.800 --> 00:29:45.600
So now if we can look at

566
00:29:45.600 --> 00:29:48.200
 the ticket field, we can

567
00:29:48.200 --> 00:29:52.000
 see the ticket information ticket data as

568
00:29:51.200 --> 00:29:53.000
 a plain text.

569
00:29:54.200 --> 00:29:55.600
So let's look at this.

570
00:29:56.500 --> 00:29:57.000
and

571
00:29:58.600 --> 00:30:02.100
Let's look at these information in here.

572
00:30:01.100 --> 00:30:05.400
 You can see the

573
00:30:05.400 --> 00:30:08.700
 encrypted ticket part. Now, you can

574
00:30:08.700 --> 00:30:11.900
 see the key value now,

575
00:30:11.900 --> 00:30:14.300
 let's expand and

576
00:30:16.300 --> 00:30:18.900
learned encrypted ticket party

577
00:30:19.800 --> 00:30:20.100
and

578
00:30:21.300 --> 00:30:23.400
here it is. That is it.

579
00:30:24.200 --> 00:30:27.200
So now we can see the key value as you

580
00:30:27.200 --> 00:30:27.300
 can see.

581
00:30:28.500 --> 00:30:32.100
The circle and we have now key

582
00:30:31.100 --> 00:30:34.300
 value data information

583
00:30:34.300 --> 00:30:37.600
 and we can see the key value

584
00:30:37.600 --> 00:30:37.900
 now.

585
00:30:39.100 --> 00:30:43.100
So there are so much more information in

586
00:30:42.100 --> 00:30:45.900
 addition to key value and

587
00:30:45.900 --> 00:30:49.000
 you can see also authorization data

588
00:30:48.700 --> 00:30:50.200
 in here.

589
00:30:53.400 --> 00:30:55.900
And there are such more information.

590
00:30:57.900 --> 00:30:58.500
as you can see

591
00:30:59.600 --> 00:31:01.700
so you can analyze these data.

592
00:31:03.300 --> 00:31:06.300
if you need to this ones and

593
00:31:08.500 --> 00:31:11.200
some other information you can obtain.

594
00:31:12.200 --> 00:31:16.100
So that's all about curbs traffic and

595
00:31:15.100 --> 00:31:18.200
 the curves process.

596
00:31:19.600 --> 00:31:22.800
and after the curves negotiation

597
00:31:22.800 --> 00:31:25.800
 as you can see in this step,

598
00:31:25.800 --> 00:31:28.300
 the driver's negotiation

599
00:31:28.300 --> 00:31:31.800
 has been completed and after this step

600
00:31:31.800 --> 00:31:34.800
 now client can

601
00:31:35.800 --> 00:31:39.300
Access to the HTTP servers as

602
00:31:39.300 --> 00:31:43.700
 you can see now the client can send an

603
00:31:42.700 --> 00:31:45.900
 HTTP request to

604
00:31:45.900 --> 00:31:49.100
 the server. So you have learned how

605
00:31:48.100 --> 00:31:52.200
 the clients and the cover

606
00:31:51.200 --> 00:31:54.300
 servers talk to each

607
00:31:54.300 --> 00:31:58.500
 other and after this negotiation process

608
00:31:57.500 --> 00:32:01.200
 how the client access

609
00:32:00.200 --> 00:32:03.200
 to a server in our

610
00:32:03.200 --> 00:32:07.000
 Network just like in our example, it was an HTTP

611
00:32:06.600 --> 00:32:09.500
 server. So you can

612
00:32:09.500 --> 00:32:12.400
 analyze your PK files. You can

613
00:32:12.400 --> 00:32:16.700
 analyze your packets following these method.

614
00:32:19.300 --> 00:32:23.100
And that's all for covers protocol.

615
00:32:25.400 --> 00:32:28.300
So that's all for now. See you on the next video.
