WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.600 --> 00:00:10.500
Hello everyone in this lesson. We will

1
00:00:10.500 --> 00:00:13.700
 investigate the capturing techniques after inspecting

2
00:00:13.700 --> 00:00:16.600
 the techniques of the network terrific analysis.

3
00:00:16.600 --> 00:00:18.700
 We will make an analysis in practice.

4
00:00:20.400 --> 00:00:23.500
Now, let's look at the technical Network. Terrific

5
00:00:23.500 --> 00:00:26.500
 analysis. Here is a more detailed

6
00:00:26.500 --> 00:00:30.100
 breakdown of each of these types of analysis.

7
00:00:30.700 --> 00:00:34.100
And the first one is descriptive analysis.

8
00:00:35.100 --> 00:00:38.800
This type of analysis involves summarizing and describing

9
00:00:38.800 --> 00:00:41.800
 the characteristics of the network and its

10
00:00:41.800 --> 00:00:42.500
 components.

11
00:00:43.400 --> 00:00:46.500
This can include measures such as the size of

12
00:00:46.500 --> 00:00:49.400
 the network for example, the number of nodes

13
00:00:49.400 --> 00:00:53.200
 or vertise and edges

14
00:00:52.200 --> 00:00:55.300
 and the density of

15
00:00:55.300 --> 00:00:58.800
 the network. For example, the proportion of

16
00:00:58.800 --> 00:01:01.300
 the nodes that are connected by

17
00:01:01.300 --> 00:01:01.800
 age.

18
00:01:02.700 --> 00:01:05.600
And the centrality of

19
00:01:05.600 --> 00:01:09.000
 13 nodes for example their importance

20
00:01:08.400 --> 00:01:10.600
 or influence within the network.

21
00:01:11.400 --> 00:01:15.500
And descriptive analysis can also involved

22
00:01:14.500 --> 00:01:17.600
 identifying patterns and

23
00:01:17.600 --> 00:01:20.200
 Trends within the network such as

24
00:01:20.200 --> 00:01:23.600
 clusters or communities of notes that

25
00:01:23.600 --> 00:01:27.400
 are more closely connected to the connected to

26
00:01:27.400 --> 00:01:28.300
 one another.

27
00:01:29.400 --> 00:01:33.700
And the second one is diagnostic analysis.

28
00:01:34.500 --> 00:01:38.300
This type of analysis involves identifying issues

29
00:01:37.300 --> 00:01:41.200
 or problems within the network and this

30
00:01:40.200 --> 00:01:43.800
 can include identifying notes or

31
00:01:43.800 --> 00:01:47.500
 edges that are causing bottlenecks

32
00:01:46.500 --> 00:01:49.800
 or congestion within the

33
00:01:49.800 --> 00:01:52.700
 network or identifying notes that

34
00:01:52.700 --> 00:01:55.100
 are vulnerable to failure or

35
00:01:55.100 --> 00:01:55.600
 attack.

36
00:01:56.400 --> 00:01:59.500
And the diagnostic analysis can

37
00:01:59.500 --> 00:02:02.900
 also evolve identifying patterns of

38
00:02:02.900 --> 00:02:03.500
 behavior?

39
00:02:04.300 --> 00:02:07.300
That are indicative of problems within

40
00:02:07.300 --> 00:02:07.800
 the network.

41
00:02:08.800 --> 00:02:11.900
And such as suspicious activity or

42
00:02:11.900 --> 00:02:14.900
 unusual communication patterns.

43
00:02:16.300 --> 00:02:20.200
At the third one is predictive analysis this

44
00:02:19.200 --> 00:02:22.800
 type of analysis involves using data

45
00:02:22.800 --> 00:02:26.200
 and statistical techniques to make

46
00:02:26.200 --> 00:02:31.100
 predictions about feature Behavior or outcomes

47
00:02:29.100 --> 00:02:33.000
 within the network. This can

48
00:02:32.400 --> 00:02:36.000
 include predicting the likelihood

49
00:02:35.700 --> 00:02:40.300
 of certain events appearing

50
00:02:38.300 --> 00:02:41.300
 within the

51
00:02:41.300 --> 00:02:44.800
 network such as the failure of a particular note

52
00:02:44.800 --> 00:02:47.600
 or the spread of

53
00:02:47.600 --> 00:02:51.000
 a certain type of information and the

54
00:02:50.200 --> 00:02:54.900
 predictive analysis can also involve identifying

55
00:02:53.900 --> 00:02:56.900
 Trends and or

56
00:02:56.900 --> 00:02:59.700
 patterns within the

57
00:02:59.700 --> 00:03:02.900
 network that may indicate feature outcomes

58
00:03:02.900 --> 00:03:06.500
 such as chains in network structure

59
00:03:05.500 --> 00:03:08.800
 or behavior over time.

60
00:03:08.800 --> 00:03:12.100
 And the last one is the prescriptive

61
00:03:11.100 --> 00:03:13.400
 analysis.

62
00:03:14.300 --> 00:03:17.200
And prescriptive analysis is a type of

63
00:03:17.200 --> 00:03:20.700
 analysis that involves using data and

64
00:03:20.700 --> 00:03:23.800
 statistical techniques to recommend actions

65
00:03:23.800 --> 00:03:26.300
 or decisions based on the results of

66
00:03:26.300 --> 00:03:29.900
 the other one the another analysis.

67
00:03:30.700 --> 00:03:34.100
And the in the context of network

68
00:03:33.100 --> 00:03:36.800
 traffic analysis prescriptive analysis,

69
00:03:36.800 --> 00:03:40.200
 May might involve using data

70
00:03:39.200 --> 00:03:42.500
 on the past terrific patterns and

71
00:03:42.500 --> 00:03:46.800
 the trends to recommend strategies for

72
00:03:45.800 --> 00:03:49.400
 improving Network performance

73
00:03:48.400 --> 00:03:51.600
 or minimizing congestion.

74
00:03:52.400 --> 00:03:56.000
So for example prescriptive analysis might

75
00:03:55.900 --> 00:03:58.600
 involve analyzing data on

76
00:03:58.600 --> 00:03:59.500
 traffic volume.

77
00:04:00.200 --> 00:04:03.900
And patterns at different times of day and

78
00:04:03.900 --> 00:04:07.000
 using this information to recommend change

79
00:04:06.300 --> 00:04:09.700
 to network rating

80
00:04:09.700 --> 00:04:11.700
 or resource allocation.

81
00:04:12.500 --> 00:04:13.900
to improve performance

82
00:04:14.600 --> 00:04:17.900
during Peak usage times and it

83
00:04:17.900 --> 00:04:20.700
 might also involve analyzing data on

84
00:04:20.700 --> 00:04:24.100
 the types of traffic being transmitted over

85
00:04:23.100 --> 00:04:26.200
 the network and using this

86
00:04:26.200 --> 00:04:30.300
 information to recommend strategies for optimizing the

87
00:04:29.300 --> 00:04:32.600
 use of network resources or

88
00:04:32.600 --> 00:04:34.400
 improving security.

89
00:04:36.100 --> 00:04:39.700
So now we will investigate an example of

90
00:04:39.700 --> 00:04:42.400
 traffic. We will investigate

91
00:04:42.400 --> 00:04:44.600
 an SMB terrific.

92
00:04:46.200 --> 00:04:49.700
as you can see I have downloaded before

93
00:04:49.700 --> 00:04:52.600
 from the Wireshark website,

94
00:04:52.600 --> 00:04:55.500
 which has some sample capture

95
00:04:55.500 --> 00:04:58.500
 files, you know, we can access these example files

96
00:04:58.500 --> 00:05:04.800
 on the YG YT

97
00:05:01.800 --> 00:05:05.100
 dot

98
00:05:04.100 --> 00:05:07.800
 Wireshark dot Arc

99
00:05:08.700 --> 00:05:11.000
and you can access on the

100
00:05:11.700 --> 00:05:14.400
 internet this file or another example

101
00:05:14.400 --> 00:05:18.400
 another sample capturing files, but

102
00:05:17.400 --> 00:05:21.800
 I have downloaded the SMB

103
00:05:20.800 --> 00:05:24.300
 on Windows 10. This

104
00:05:23.300 --> 00:05:26.900
 is the this is

105
00:05:26.900 --> 00:05:29.600
 the one of the most known

106
00:05:29.600 --> 00:05:32.400
 sample sample capturing

107
00:05:32.400 --> 00:05:37.500
 file and we will investigate this capturing

108
00:05:36.500 --> 00:05:40.400
 file associated with

109
00:05:40.400 --> 00:05:43.700
 the SMB protocol. There is

110
00:05:43.700 --> 00:05:46.500
 a communication there's a network traffic between

111
00:05:46.500 --> 00:05:50.300
 some devices. You can see in here and

112
00:05:49.300 --> 00:05:53.100
 you can also download this

113
00:05:52.100 --> 00:05:55.300
 file this pickup NG file

114
00:05:55.300 --> 00:06:00.200
 if you want to investigate detailed.

115
00:06:02.400 --> 00:06:05.400
So let's begin with the

116
00:06:05.400 --> 00:06:09.200
 SMB protocol. And what

117
00:06:08.200 --> 00:06:11.700
 is SMB protocol? We can

118
00:06:11.700 --> 00:06:14.900
 talk about a little bit SMB means

119
00:06:14.900 --> 00:06:17.000
 server message block.

120
00:06:17.800 --> 00:06:21.200
And assembly protocol is a server

121
00:06:20.200 --> 00:06:23.700
 message block protocol. So it

122
00:06:23.700 --> 00:06:27.000
 is a network file sharing protocol

123
00:06:26.800 --> 00:06:29.800
 and it is used for sharing

124
00:06:29.800 --> 00:06:33.000
 files printers and other

125
00:06:32.600 --> 00:06:34.300
 resources on a network.

126
00:06:35.200 --> 00:06:38.800
And maybe you know, it is a client server protocol

127
00:06:38.800 --> 00:06:42.200
 and the which means that it

128
00:06:41.200 --> 00:06:44.800
 relies on a central server to

129
00:06:44.800 --> 00:06:48.400
 provide access to resources SMB is

130
00:06:48.400 --> 00:06:51.400
 a widely used protocol and it is supported by

131
00:06:51.400 --> 00:06:55.000
 many operating systems. It

132
00:06:54.700 --> 00:06:58.600
 is often used in Enterprise environments

133
00:06:57.600 --> 00:07:00.400
 to share resources on a

134
00:07:00.400 --> 00:07:01.800
 local area and Network.

135
00:07:02.600 --> 00:07:05.000
and versions

136
00:07:05.500 --> 00:07:08.300
anti versions of the SMB protocol

137
00:07:09.100 --> 00:07:12.100
have changed over years.

138
00:07:13.300 --> 00:07:16.400
Maybe you can see in here as well.

139
00:07:17.800 --> 00:07:21.300
the name of the protocol SMB

140
00:07:20.300 --> 00:07:23.100
 and if there is no

141
00:07:23.100 --> 00:07:26.400
 version number this means

142
00:07:26.400 --> 00:07:29.600
 the version of the SMB is

143
00:07:29.600 --> 00:07:32.700
 1 so this is the SMB version

144
00:07:32.700 --> 00:07:33.200
 1

145
00:07:34.200 --> 00:07:37.200
and the other ones you will

146
00:07:37.200 --> 00:07:39.700
 see as the smb2.

147
00:07:40.700 --> 00:07:41.000
so

148
00:07:43.200 --> 00:07:46.100
and the versions of the

149
00:07:46.100 --> 00:07:49.900
 SMB protocol have changed over the

150
00:07:49.900 --> 00:07:54.200
 years and after smb1 1.0.

151
00:07:52.200 --> 00:07:55.100
 Maybe you can

152
00:07:55.100 --> 00:07:59.300
 say and the second versions and the

153
00:07:58.300 --> 00:08:01.900
 finally the third versions

154
00:08:01.900 --> 00:08:03.400
 were the Great.

155
00:08:04.900 --> 00:08:07.900
And the third versions were declared

156
00:08:07.900 --> 00:08:11.100
 together with their

157
00:08:10.100 --> 00:08:13.500
 subversions and are still

158
00:08:13.500 --> 00:08:14.400
 being used.

159
00:08:15.200 --> 00:08:18.300
So now it is

160
00:08:18.300 --> 00:08:22.900
 it is being it is being used still the

161
00:08:21.900 --> 00:08:25.200
 version of one the

162
00:08:24.200 --> 00:08:27.400
 version 2 and the

163
00:08:27.400 --> 00:08:30.600
 version 3 and their subversions are

164
00:08:30.600 --> 00:08:31.900
 still being used.

165
00:08:32.800 --> 00:08:36.500
So that is the important you should

166
00:08:36.500 --> 00:08:40.300
 keep in you should keep in mind and the

167
00:08:39.300 --> 00:08:43.700
 developed at Modified by Microsoft.

168
00:08:42.700 --> 00:08:44.500
 So

169
00:08:46.900 --> 00:08:49.300
there therefore we can read the

170
00:08:49.300 --> 00:08:52.800
 documentation of the SMB protocol in detail on

171
00:08:52.800 --> 00:08:54.200
 the Microsoft website.

172
00:08:55.100 --> 00:08:58.900
and now we will talk about firstly

173
00:09:00.400 --> 00:09:03.300
on SMB and Shake

174
00:09:03.800 --> 00:09:06.800
Maybe you we can say to this

175
00:09:06.800 --> 00:09:10.400
 SMB handshake as such

176
00:09:09.400 --> 00:09:12.600
 as the TCP and Shake.

177
00:09:13.200 --> 00:09:16.700
The assembly handshake is called

178
00:09:16.700 --> 00:09:20.200
 as the assembly dialect.

179
00:09:20.800 --> 00:09:23.900
According to the SMB protocol based on

180
00:09:23.900 --> 00:09:26.800
 the SMB protocol. So

181
00:09:26.800 --> 00:09:29.500
 send me is also an

182
00:09:29.500 --> 00:09:32.100
 application layer protocol. We should

183
00:09:32.100 --> 00:09:35.700
 know this and the we are looking for an

184
00:09:35.700 --> 00:09:38.000
 application layer protocol here.

185
00:09:39.300 --> 00:09:43.300
Yeah, you should you should notice that in

186
00:09:42.300 --> 00:09:46.400
 order to establish a connection between

187
00:09:45.400 --> 00:09:48.800
 a client and the

188
00:09:48.800 --> 00:09:51.500
 server using SMB protocol.

189
00:09:51.500 --> 00:09:55.400
 You must first determine the dialect

190
00:09:54.400 --> 00:09:57.400
 with the highest level of the

191
00:09:57.400 --> 00:10:00.700
 functionality. If you want to have a communication between different

192
00:10:00.700 --> 00:10:04.300
 window systems, let's say between

193
00:10:03.300 --> 00:10:07.500
 Windows 10 and XP or

194
00:10:06.500 --> 00:10:11.000
 server server,

195
00:10:09.500 --> 00:10:13.200
 20 16

196
00:10:12.200 --> 00:10:15.600
 and the other

197
00:10:15.600 --> 00:10:18.300
 version of the windows. There must be a

198
00:10:18.300 --> 00:10:21.700
 negotiation on the protocol dialect

199
00:10:21.700 --> 00:10:22.000
 version.

200
00:10:22.800 --> 00:10:25.800
So after the TCP handshake

201
00:10:26.400 --> 00:10:30.400
We will see the SMB dialect

202
00:10:29.400 --> 00:10:33.300
 communication assembly dialect.

203
00:10:34.700 --> 00:10:37.800
messages so to do

204
00:10:37.800 --> 00:10:40.400
 this to to make

205
00:10:40.400 --> 00:10:40.600
 a

206
00:10:41.800 --> 00:10:43.100
to make it negotiation.

207
00:10:44.200 --> 00:10:49.000
On the devices between the devices client firstly

208
00:10:47.200 --> 00:10:51.100
 client offers client

209
00:10:50.100 --> 00:10:53.400
 offers an option of

210
00:10:53.400 --> 00:10:55.800
 available SMB dialects.

211
00:10:56.300 --> 00:10:59.700
I mean what dialects declined are supporting will

212
00:10:59.700 --> 00:11:02.400
 be presented by the client to the server?

213
00:11:03.100 --> 00:11:07.200
So then after the after the

214
00:11:07.200 --> 00:11:11.700
 offer offer message in here,

215
00:11:11.700 --> 00:11:14.000
 you can see the you can

216
00:11:14.200 --> 00:11:15.200
 see on the packet.

217
00:11:16.500 --> 00:11:19.700
854 on this packet

218
00:11:19.700 --> 00:11:22.500
 you can see the offer message over

219
00:11:22.500 --> 00:11:25.300
 packet or you or we can

220
00:11:25.300 --> 00:11:29.000
 we can call as the negotiate protocol

221
00:11:28.000 --> 00:11:29.600
 request.

222
00:11:30.500 --> 00:11:33.800
So it is known as negotiate protocol

223
00:11:33.800 --> 00:11:36.700
 request negotiate protocol request

224
00:11:36.700 --> 00:11:41.000
 packet means declined making

225
00:11:39.500 --> 00:11:44.000
 an offer

226
00:11:43.400 --> 00:11:45.400
 to the servers.

227
00:11:45.800 --> 00:11:49.700
on the on the SMB version

228
00:11:49.700 --> 00:11:52.800
 about the assembly version and then

229
00:11:53.700 --> 00:11:56.800
then the server will select

230
00:11:56.800 --> 00:11:58.600
 the highest common version.

231
00:11:59.900 --> 00:12:03.300
Client will offer some versions that

232
00:12:02.300 --> 00:12:05.500
 it has and after

233
00:12:05.500 --> 00:12:06.800
 this offer.

234
00:12:07.600 --> 00:12:10.300
The server will select the

235
00:12:10.300 --> 00:12:11.500
 highest common version.

236
00:12:12.600 --> 00:12:14.800
Let's take a look at the examples.

237
00:12:16.300 --> 00:12:19.400
Now on these packets firstly we

238
00:12:19.400 --> 00:12:23.200
 will look at the this example.

239
00:12:24.500 --> 00:12:25.300
Say example.

240
00:12:29.100 --> 00:12:29.600
Okay.

241
00:12:31.800 --> 00:12:32.700
and there is

242
00:12:35.300 --> 00:12:38.600
there is some conversation between the

243
00:12:38.600 --> 00:12:41.100
 devices on this MB protocol.

244
00:12:41.900 --> 00:12:44.900
and this is a negotiate

245
00:12:44.900 --> 00:12:48.900
 request from the client and

246
00:12:49.700 --> 00:12:51.600
let's look at the packet details now.

247
00:12:53.200 --> 00:12:55.300
negotiate protocol request packet

248
00:13:06.600 --> 00:13:09.300
in here in the packet details pane

249
00:13:09.800 --> 00:13:10.700
you can see the

250
00:13:13.200 --> 00:13:17.300
the knowledge the information about a

251
00:13:16.300 --> 00:13:18.500
 each layer.

252
00:13:19.800 --> 00:13:23.100
We have told before in the

253
00:13:22.100 --> 00:13:25.300
 on the pack details Pane

254
00:13:25.300 --> 00:13:29.900
 and every stage corresponds

255
00:13:28.900 --> 00:13:32.100
 to the a level

256
00:13:31.100 --> 00:13:34.100
 on the OSI model.

257
00:13:34.800 --> 00:13:37.400
So we will interest

258
00:13:37.400 --> 00:13:40.900
 it. We will be interested in the SMB protocol

259
00:13:40.900 --> 00:13:44.300
 in here. And before this

260
00:13:43.300 --> 00:13:46.800
 you can see the TCP protocol.

261
00:13:48.100 --> 00:13:52.000
And we should know this the SMB

262
00:13:51.500 --> 00:13:55.600
 protocol is running on

263
00:13:54.600 --> 00:13:57.300
 the is running

264
00:13:57.300 --> 00:14:00.700
 under the TCP transmission control

265
00:14:00.700 --> 00:14:04.000
 protocol so we can see the TCP

266
00:14:03.400 --> 00:14:07.000
 protocol in here after the transport

267
00:14:06.600 --> 00:14:09.400
 layer. You can see the higher level.

268
00:14:11.500 --> 00:14:14.300
Under the transmission control protocol and

269
00:14:14.300 --> 00:14:18.300
 the net bios session service

270
00:14:18.300 --> 00:14:21.600
 protocol is in

271
00:14:21.600 --> 00:14:24.700
 here on the session layer.

272
00:14:25.400 --> 00:14:28.500
So the net bios protocol

273
00:14:28.500 --> 00:14:30.800
 on the session layer.

274
00:14:31.300 --> 00:14:33.000
After the session layer.

275
00:14:33.500 --> 00:14:36.800
We can see the SMB protocol

276
00:14:36.800 --> 00:14:40.000
 on the application layer. So

277
00:14:39.400 --> 00:14:43.400
 we have expanded to expanded the

278
00:14:43.400 --> 00:14:45.300
 SMB protocol.

279
00:14:46.300 --> 00:14:49.600
field and the in this

280
00:14:49.600 --> 00:14:49.800
 field

281
00:14:51.100 --> 00:14:54.900
you'll see the dialect versions values.

282
00:14:58.400 --> 00:15:01.700
I'm going to the down on the details

283
00:15:01.700 --> 00:15:02.700
 and you can see.

284
00:15:03.600 --> 00:15:04.300
That's it.

285
00:15:05.400 --> 00:15:06.800
dialect version

286
00:15:08.100 --> 00:15:11.900
So you see the dialect version values line by

287
00:15:11.900 --> 00:15:12.500
 line.

288
00:15:13.600 --> 00:15:14.600
line by line

289
00:15:15.500 --> 00:15:19.300
the Soviet with this values declined

290
00:15:18.300 --> 00:15:21.700
 is offering the versions that

291
00:15:21.700 --> 00:15:23.300
 they can negotiate each other.

292
00:15:26.800 --> 00:15:29.800
This packet is the negotiate protocol request

293
00:15:29.800 --> 00:15:33.300
 pack packet and the client is

294
00:15:32.300 --> 00:15:35.800
 offering some versions

295
00:15:35.800 --> 00:15:38.700
 of the SMB. You can see in here.

296
00:15:38.700 --> 00:15:42.400
 There are some versions

297
00:15:41.400 --> 00:15:46.500
 as smb2 dot

298
00:15:45.500 --> 00:15:48.900
 zero to and

299
00:15:48.900 --> 00:15:52.600
 the other version is SMB 2.1

300
00:15:51.600 --> 00:15:57.700
 and the SMB 3.0.

301
00:15:59.400 --> 00:16:00.500
each of these

302
00:16:02.800 --> 00:16:06.700
SMB versions are being offered

303
00:16:05.700 --> 00:16:08.400
 by the client.

304
00:16:08.400 --> 00:16:09.000
 So

305
00:16:10.800 --> 00:16:15.900
they will they will negotiate on one

306
00:16:14.900 --> 00:16:17.700
 of the versions one

307
00:16:17.700 --> 00:16:20.900
 of these versions. And as I

308
00:16:20.900 --> 00:16:23.500
 told before the server will select

309
00:16:23.500 --> 00:16:27.000
 the highest common version. So in this

310
00:16:26.700 --> 00:16:29.600
 situation the server will

311
00:16:29.600 --> 00:16:30.500
 select the

312
00:16:32.100 --> 00:16:32.900
this version

313
00:16:34.500 --> 00:16:38.700
SMB 3 dot 1.1. So

314
00:16:38.700 --> 00:16:41.400
 let's look at what what the server

315
00:16:41.400 --> 00:16:44.800
 have selected as the

316
00:16:44.800 --> 00:16:47.600
 version of the SMB and we will

317
00:16:47.600 --> 00:16:50.400
 look at the next packet. The next

318
00:16:50.400 --> 00:16:54.200
 packet is the negotiate protocol

319
00:16:53.200 --> 00:16:54.800
 response.

320
00:16:55.500 --> 00:16:58.400
So in this packet when we look at

321
00:16:58.400 --> 00:17:01.300
 the packet details, we will see that

322
00:17:01.300 --> 00:17:02.400
 this server.

323
00:17:04.100 --> 00:17:07.800
Would would select the version

324
00:17:07.800 --> 00:17:09.500
 of the SMB?

325
00:17:10.100 --> 00:17:14.800
Now I'm I'm clicking on the negotiate protocol

326
00:17:14.800 --> 00:17:16.200
 response packet.

327
00:17:17.200 --> 00:17:21.400
and when we are looking when we

328
00:17:21.400 --> 00:17:21.600
 look at the

329
00:17:23.400 --> 00:17:24.600
packet details

330
00:17:26.200 --> 00:17:27.100
we will see.

331
00:17:28.800 --> 00:17:30.500
the version information

332
00:17:32.300 --> 00:17:34.200
so in this field

333
00:17:39.300 --> 00:17:39.500
so

334
00:17:40.300 --> 00:17:40.900
that's it.

335
00:17:42.800 --> 00:17:43.900
the dialect version

336
00:17:45.400 --> 00:17:51.400
has been selected by the server as the smb3.1.1.

337
00:17:52.300 --> 00:17:56.500
So we can understand that the server has

338
00:17:55.500 --> 00:17:58.900
 selected the highest common

339
00:17:58.900 --> 00:18:00.500
 version of the assembly.

340
00:18:01.400 --> 00:18:04.300
And after the negotiation you will

341
00:18:04.300 --> 00:18:07.900
 see the packet about on

342
00:18:07.900 --> 00:18:11.200
 the session setup request.

343
00:18:12.200 --> 00:18:16.200
And then you can see some errors.

344
00:18:15.200 --> 00:18:18.300
 Let's talk about these years.

345
00:18:19.500 --> 00:18:21.100
but first of all

346
00:18:23.500 --> 00:18:26.200
Before talking about the

347
00:18:26.200 --> 00:18:29.600
 errors we will investigate another conversation and

348
00:18:29.600 --> 00:18:33.500
 other negotiation conversation between

349
00:18:32.500 --> 00:18:34.100
 the devices.

350
00:18:35.300 --> 00:18:38.200
Let's go to the another example.

351
00:18:46.200 --> 00:18:50.100
So we can see yes. Okay. This

352
00:18:49.100 --> 00:18:53.400
 is the another example it starts

353
00:18:52.400 --> 00:18:54.100
 from here.

354
00:18:55.900 --> 00:18:58.400
It starts with this packet.

355
00:18:59.600 --> 00:19:03.000
And in this packet if he expand

356
00:19:02.400 --> 00:19:05.500
 the expand the

357
00:19:05.500 --> 00:19:07.100
 SMB field.

358
00:19:08.100 --> 00:19:10.700
You will see the sun.

359
00:19:12.100 --> 00:19:13.300
You will see the sum.

360
00:19:14.700 --> 00:19:15.400
offers

361
00:19:17.200 --> 00:19:17.400
so

362
00:19:19.400 --> 00:19:22.500
In here, we will we are looking at

363
00:19:22.500 --> 00:19:26.400
 the dialect information as

364
00:19:25.400 --> 00:19:32.100
 the SMB version 2.002

365
00:19:28.100 --> 00:19:32.900
 and

366
00:19:32.900 --> 00:19:36.900
 the other offer is smb2 Dot.

367
00:19:37.500 --> 00:19:40.900
Some question marks. So these

368
00:19:40.900 --> 00:19:45.100
 three question marks are meaning

369
00:19:44.100 --> 00:19:47.500
 the wild card and when we

370
00:19:47.500 --> 00:19:48.700
 look at the next packet.

371
00:19:49.400 --> 00:19:50.800
the response packet

372
00:19:51.500 --> 00:19:52.300
We can see.

373
00:19:53.400 --> 00:19:58.200
You can see the dialect the dialect

374
00:19:57.200 --> 00:20:00.300
 and the SMB version

375
00:20:00.300 --> 00:20:03.500
 that has been selected by the server is

376
00:20:03.500 --> 00:20:05.500
 smb2 wildcard.

377
00:20:06.900 --> 00:20:09.400
Because on the

378
00:20:09.400 --> 00:20:09.700
 request.

379
00:20:11.400 --> 00:20:14.900
because the highest version of the SMB has been accepted as

380
00:20:14.900 --> 00:20:17.900
 the wildcard version

381
00:20:17.900 --> 00:20:20.100
 and when we look

382
00:20:20.100 --> 00:20:23.200
 at the again, when we look at the game the

383
00:20:23.200 --> 00:20:26.300
 response packet we can see

384
00:20:26.300 --> 00:20:26.600
 the

385
00:20:28.600 --> 00:20:32.800
the dialect version is smb2 wire

386
00:20:32.800 --> 00:20:35.400
 card. So this time in this situation

387
00:20:35.400 --> 00:20:38.800
 to make a clear version

388
00:20:38.800 --> 00:20:41.900
 of the assembly the client

389
00:20:41.900 --> 00:20:45.100
 will offer new and higher values

390
00:20:44.100 --> 00:20:47.100
 again to the server.

391
00:20:48.200 --> 00:20:52.200
So because because of this situation we

392
00:20:51.200 --> 00:20:53.200
 are observing.

393
00:20:54.700 --> 00:20:57.600
The new request packed the next

394
00:20:57.600 --> 00:21:00.200
 packet is another request packet.

395
00:21:00.600 --> 00:21:03.600
and when we look at the another request packet

396
00:21:05.200 --> 00:21:08.800
We can see the other versions the higher

397
00:21:08.800 --> 00:21:10.700
 versions of the SMB.

398
00:21:12.400 --> 00:21:13.100
after the

399
00:21:14.600 --> 00:21:17.800
after the wild card version offering

400
00:21:17.800 --> 00:21:21.100
 declined make and

401
00:21:20.100 --> 00:21:23.800
 make an make a new offer the

402
00:21:23.800 --> 00:21:26.800
 client make a new offer to the

403
00:21:26.800 --> 00:21:27.100
 server.

404
00:21:29.400 --> 00:21:32.300
And with the higher that with

405
00:21:32.300 --> 00:21:35.800
 the higher versions of the assembly so

406
00:21:35.800 --> 00:21:38.700
 we can see the for example

407
00:21:38.700 --> 00:21:41.200
 at the

408
00:21:41.200 --> 00:21:46.700
 beginning smb202 and tsmb2.1

409
00:21:44.700 --> 00:21:49.700
 the higher

410
00:21:47.700 --> 00:21:51.600
 version and

411
00:21:50.600 --> 00:21:54.900
 the other one smb3.0 and

412
00:21:54.900 --> 00:21:59.000
 the last one is the smb3.1 dot

413
00:21:58.000 --> 00:22:00.000
 on.

414
00:22:00.700 --> 00:22:04.100
This means that the server will

415
00:22:03.100 --> 00:22:05.200
 select this version.

416
00:22:06.800 --> 00:22:09.000
3.1.1

417
00:22:09.700 --> 00:22:11.800
So let's look at the response packet.

418
00:22:13.100 --> 00:22:17.000
We can see the dialect information is

419
00:22:16.800 --> 00:22:19.900
 the highest version of

420
00:22:19.900 --> 00:22:20.800
 the SMB.

421
00:22:22.400 --> 00:22:24.400
in the previous packet

422
00:22:25.200 --> 00:22:28.500
In the last offer the assembly version

423
00:22:28.500 --> 00:22:31.300
 was the three dot one

424
00:22:31.300 --> 00:22:34.500
 dot one and the

425
00:22:34.500 --> 00:22:37.600
 server as a

426
00:22:37.600 --> 00:22:41.000
 server and server has selected this

427
00:22:40.000 --> 00:22:41.400
 version.

428
00:22:42.300 --> 00:22:43.100
the highest version

429
00:22:43.700 --> 00:22:47.000
So this is the dialect communication

430
00:22:46.600 --> 00:22:49.500
 dialect conversation between the

431
00:22:49.500 --> 00:22:51.600
 client and the server.

432
00:22:52.300 --> 00:22:52.600
and

433
00:22:54.200 --> 00:22:57.800
so the version 3 has been selected and using on

434
00:22:57.800 --> 00:23:00.300
 the conversation on the

435
00:23:00.300 --> 00:23:03.400
 following conversation, but we are

436
00:23:03.400 --> 00:23:07.000
 still observing these packets as smb2 packets.

437
00:23:08.700 --> 00:23:11.700
I mean after selecting version 2

438
00:23:11.700 --> 00:23:14.500
 we still observe that the version information

439
00:23:14.500 --> 00:23:15.300
 is too.

440
00:23:16.100 --> 00:23:19.800
Some B2. That's why smb2 and

441
00:23:19.800 --> 00:23:24.700
 smb3 use the same signature additionally

442
00:23:22.700 --> 00:23:25.900
 when we

443
00:23:25.900 --> 00:23:28.200
 are searching for smb3.

444
00:23:29.200 --> 00:23:32.300
On the filter on the filtering field

445
00:23:32.300 --> 00:23:35.200
 if you make a if we make a

446
00:23:35.200 --> 00:23:35.500
 filter.

447
00:23:37.100 --> 00:23:41.400
For the smb3 some B2

448
00:23:40.400 --> 00:23:44.000
 can be used as display filter.

449
00:23:43.500 --> 00:23:47.300
 So if if I write a filter

450
00:23:46.300 --> 00:23:50.100
 as SMB

451
00:23:49.100 --> 00:23:53.100
 3 we should

452
00:23:52.100 --> 00:23:57.200
 use we should write smb2 and

453
00:23:56.200 --> 00:23:59.500
 remind that the client and

454
00:23:59.500 --> 00:24:04.100
 the server will redo the negotiation

455
00:24:02.100 --> 00:24:05.500
 for the dialect.

456
00:24:06.900 --> 00:24:10.400
So after every TCP

457
00:24:09.400 --> 00:24:12.600
 handshake between the client

458
00:24:12.600 --> 00:24:15.500
 and the server you will see the negotiation

459
00:24:15.500 --> 00:24:18.800
 about the protocol

460
00:24:18.800 --> 00:24:20.400
 SMB.

461
00:24:21.500 --> 00:24:24.700
You might have an Enterprise Network and it

462
00:24:24.700 --> 00:24:28.200
 might be some multiple different versions

463
00:24:27.200 --> 00:24:29.300
 that servers have.

464
00:24:30.200 --> 00:24:33.700
In a cluster of Windows servers in that

465
00:24:33.700 --> 00:24:36.500
 situation the server might choose the highest

466
00:24:36.500 --> 00:24:39.700
 common dialect version among all other ones.

467
00:24:39.700 --> 00:24:42.500
 Not that not the highest version

468
00:24:42.500 --> 00:24:45.900
 but the highest common version. So this

469
00:24:45.900 --> 00:24:49.500
 is the important point they will

470
00:24:49.500 --> 00:24:52.900
 they will choose the highest common

471
00:24:52.900 --> 00:24:56.100
 version the highest common version

472
00:24:55.100 --> 00:24:58.200
 not the highest version.

473
00:25:01.100 --> 00:25:05.200
And why do multiple TCP handshakes

474
00:25:04.200 --> 00:25:08.500
 and sessions arise when

475
00:25:07.500 --> 00:25:10.800
 we are running on SMB protocol?

476
00:25:10.800 --> 00:25:13.400
 In fact, it might be that

477
00:25:13.400 --> 00:25:17.000
 one of the TCP session is used to open a

478
00:25:16.300 --> 00:25:20.600
 file and the second TCP session

479
00:25:19.600 --> 00:25:22.400
 is used to close the file.

480
00:25:22.900 --> 00:25:23.800
So that is why.

481
00:25:25.500 --> 00:25:28.800
Now, let's look at traffic in order to make an investigation.

482
00:25:31.700 --> 00:25:35.200
We see in here after the negotiation process the

483
00:25:34.200 --> 00:25:38.200
 client with the IP address and linked

484
00:25:37.200 --> 00:25:38.400
 with the

485
00:25:40.300 --> 00:25:45.200
ending with the 100 132 first

486
00:25:44.200 --> 00:25:47.300
 makes a login attempt here

487
00:25:47.300 --> 00:25:48.500
 as you can see.

488
00:25:50.100 --> 00:25:54.800
And login attempt in here and the

489
00:25:53.800 --> 00:25:57.400
 session request we

490
00:25:56.400 --> 00:26:00.100
 can see in here. So and this

491
00:25:59.100 --> 00:26:01.800
 attempt failed.

492
00:26:02.700 --> 00:26:06.200
After the login attempt, the

493
00:26:05.200 --> 00:26:08.100
 login attempt has

494
00:26:08.100 --> 00:26:11.800
 failed. So that is

495
00:26:11.800 --> 00:26:15.100
 why the status log on failure error

496
00:26:14.100 --> 00:26:18.100
 is received in here. And let's

497
00:26:17.100 --> 00:26:20.600
 also look at the user information of

498
00:26:20.600 --> 00:26:21.300
 this client.

499
00:26:22.300 --> 00:26:27.000
That has been made the request

500
00:26:25.300 --> 00:26:30.000
 for the login and when

501
00:26:28.100 --> 00:26:31.600
 we look at the user information.

502
00:26:33.400 --> 00:26:38.200
That you can see also an information summarizing

503
00:26:36.200 --> 00:26:40.000
 information in here

504
00:26:39.600 --> 00:26:42.200
 and we can look at the detail.

505
00:26:43.400 --> 00:26:46.700
Of the user information in here

506
00:26:46.700 --> 00:26:50.000
 as you can see on the session

507
00:26:49.500 --> 00:26:52.300
 ID field. The account field

508
00:26:52.300 --> 00:26:56.300
 is giving the username

509
00:26:55.300 --> 00:26:59.200
 as user then the

510
00:26:58.200 --> 00:27:02.200
 domain name is the important another

511
00:27:01.200 --> 00:27:05.400
 thing for us because this

512
00:27:04.400 --> 00:27:07.300
 is showing us

513
00:27:07.300 --> 00:27:10.300
 the domain name in this

514
00:27:10.300 --> 00:27:13.400
 situation multiple unsuccessful working

515
00:27:13.400 --> 00:27:16.400
 at hands with the same hostname.

516
00:27:17.600 --> 00:27:19.400
And the same username.

517
00:27:20.100 --> 00:27:21.400
are acceptable

518
00:27:22.300 --> 00:27:25.800
however, if we notice that the same client

519
00:27:26.400 --> 00:27:29.700
the same client with the same IP address

520
00:27:29.700 --> 00:27:32.900
 and the same username and

521
00:27:32.900 --> 00:27:34.500
 the same hostname.

522
00:27:35.400 --> 00:27:38.500
If you notice that the same client is trying to

523
00:27:38.500 --> 00:27:41.500
 login with different usernames.

524
00:27:42.400 --> 00:27:46.100
The other information will be

525
00:27:45.100 --> 00:27:50.300
 the same and the username

526
00:27:48.300 --> 00:27:51.300
 can be

527
00:27:51.300 --> 00:27:54.900
 might be a different username. So

528
00:27:54.900 --> 00:27:58.100
 in this situation, we have a suspicion that

529
00:27:57.100 --> 00:28:00.500
 this is suspicious activity.

530
00:28:01.500 --> 00:28:04.700
So let's take a look at the rest of

531
00:28:04.700 --> 00:28:05.200
 the traffic.

532
00:28:06.100 --> 00:28:10.400
This was the first on successful

533
00:28:09.400 --> 00:28:13.000
 login attempt and

534
00:28:12.300 --> 00:28:14.400
 it is acceptable.

535
00:28:15.200 --> 00:28:19.200
But let's move on the more. Let's

536
00:28:18.200 --> 00:28:22.800
 move on to the investigation on

537
00:28:22.800 --> 00:28:23.400
 the traffic.

538
00:28:27.300 --> 00:28:30.500
So when we come to

539
00:28:30.500 --> 00:28:34.000
 the another login attempt,

540
00:28:33.500 --> 00:28:36.000
 look the same

541
00:28:36.800 --> 00:28:38.200
 user the same user.

542
00:28:41.800 --> 00:28:44.200
Username is the same as you can

543
00:28:44.200 --> 00:28:45.200
 see in here.

544
00:28:46.800 --> 00:28:49.300
And the domain and hostname is the same

545
00:28:49.300 --> 00:28:52.500
 and the IP address

546
00:28:52.500 --> 00:28:53.500
 is the same as well.

547
00:28:54.300 --> 00:28:57.300
So the same user has

548
00:28:57.300 --> 00:29:01.300
 made another unsuccessful login attempt.

549
00:29:02.400 --> 00:29:06.500
So there is another error the

550
00:29:05.500 --> 00:29:08.900
 status log on favor.

551
00:29:10.900 --> 00:29:12.900
And okay move on the traffic.

552
00:29:15.900 --> 00:29:18.900
And here is the third unsuccessful login

553
00:29:18.900 --> 00:29:19.400
 attempt.

554
00:29:20.300 --> 00:29:20.400
so

555
00:29:22.100 --> 00:29:22.600
move on.

556
00:29:24.700 --> 00:29:26.600
and when we come to the

557
00:29:28.100 --> 00:29:28.900
packet

558
00:29:29.900 --> 00:29:33.900
740 here is

559
00:29:33.900 --> 00:29:37.100
 another unsuccessful login attempt

560
00:29:36.100 --> 00:29:39.800
 and the the user

561
00:29:39.800 --> 00:29:41.400
 is the same again.

562
00:29:43.300 --> 00:29:45.300
So let's move on again.

563
00:29:47.300 --> 00:29:50.100
And we are coming to the

564
00:29:50.100 --> 00:29:54.100
 another login attempt here. We

565
00:29:53.100 --> 00:29:55.700
 see that the same client.

566
00:29:56.500 --> 00:29:59.600
The same client with the same IP address

567
00:29:59.600 --> 00:30:03.400
 and with the same domain name

568
00:30:03.400 --> 00:30:05.000
 and the host name.

569
00:30:05.600 --> 00:30:05.900
but

570
00:30:07.200 --> 00:30:10.900
the username is different. So that

571
00:30:10.900 --> 00:30:11.500
 is interesting.

572
00:30:12.800 --> 00:30:15.500
And we see that the same client attempted

573
00:30:15.500 --> 00:30:18.200
 to login with an different username.

574
00:30:18.800 --> 00:30:21.600
Username is here team tester.

575
00:30:23.200 --> 00:30:27.300
And this login attempt also failed you

576
00:30:26.300 --> 00:30:29.400
 can see the error about

577
00:30:29.400 --> 00:30:32.400
 the login status log

578
00:30:32.400 --> 00:30:35.700
 on favor again. So that's interesting. That's

579
00:30:35.700 --> 00:30:40.400
 highly interesting and no

580
00:30:39.400 --> 00:30:41.000
 one the traffic.

581
00:30:42.500 --> 00:30:43.700
monitorific

582
00:30:44.900 --> 00:30:45.100
so

583
00:30:46.300 --> 00:30:48.800
when we come to the another packet.

584
00:30:50.500 --> 00:30:51.200
which might be

585
00:30:52.300 --> 00:30:56.300
interested with the same client

586
00:30:58.000 --> 00:30:58.300
and

587
00:31:00.700 --> 00:31:03.300
we see that we see that in here.

588
00:31:05.200 --> 00:31:05.600
again

589
00:31:06.800 --> 00:31:09.800
The same domain

590
00:31:09.800 --> 00:31:11.300
 name and the host name.

591
00:31:12.500 --> 00:31:12.700
Are the same?

592
00:31:13.700 --> 00:31:17.100
With the previous ones and

593
00:31:16.100 --> 00:31:19.400
 the account name is

594
00:31:19.400 --> 00:31:20.800
 different again.

595
00:31:21.600 --> 00:31:21.700
so

596
00:31:22.800 --> 00:31:26.100
the same client then attends

597
00:31:25.100 --> 00:31:29.200
 a login again in here and

598
00:31:28.200 --> 00:31:31.600
 it has the same hostname and

599
00:31:31.600 --> 00:31:34.800
 the same IP address. However, he

600
00:31:34.800 --> 00:31:37.700
 attempt to login with a different username.

601
00:31:39.800 --> 00:31:40.700
and this time

602
00:31:42.100 --> 00:31:45.500
successfully locked in so this

603
00:31:45.500 --> 00:31:48.900
 is so this in itself is abnormal

604
00:31:48.900 --> 00:31:51.900
 and high resuspicious and this

605
00:31:51.900 --> 00:31:54.500
 in itself is abnormal and

606
00:31:54.500 --> 00:31:55.800
 highly suspicious.

607
00:31:56.800 --> 00:31:58.900
So moreover it creates.

608
00:32:00.800 --> 00:32:03.700
That's the let's look at it's it's great.

609
00:32:07.100 --> 00:32:08.700
It creates a file name.

610
00:32:10.100 --> 00:32:13.900
SRV SVC on the

611
00:32:13.900 --> 00:32:14.100
 server

612
00:32:15.400 --> 00:32:16.400
after the traffic

613
00:32:17.900 --> 00:32:21.100
So then we see the right operations

614
00:32:20.100 --> 00:32:24.000
 to write operate operations. You

615
00:32:23.100 --> 00:32:26.100
 can see here the right.

616
00:32:28.000 --> 00:32:28.600
process

617
00:32:29.700 --> 00:32:30.600
and

618
00:32:32.500 --> 00:32:35.600
then we see and finally

619
00:32:35.600 --> 00:32:38.300
 we can see the burning we can

620
00:32:38.300 --> 00:32:41.800
 see the warning the warning.

621
00:32:43.700 --> 00:32:45.000
We can see the warning.

622
00:32:48.400 --> 00:32:51.600
And finally, we can see the burning that it

623
00:32:51.600 --> 00:32:53.500
 is a malicious file.

624
00:32:54.500 --> 00:32:57.100
So in the package with the phrase in the

625
00:32:57.100 --> 00:33:01.100
 package with the phrase malformed packet warning.

626
00:33:02.300 --> 00:33:02.400
so

627
00:33:03.600 --> 00:33:07.700
It says to us. This is a malformed

628
00:33:06.700 --> 00:33:10.600
 packet and its

629
00:33:09.600 --> 00:33:14.100
 name is SRV SVC.

630
00:33:15.600 --> 00:33:18.000
Which is the malformed packet?

631
00:33:18.600 --> 00:33:21.800
So as here to detect whether the

632
00:33:21.800 --> 00:33:25.000
 generated file contains malicious content,

633
00:33:24.700 --> 00:33:29.100
 and we need to directly we

634
00:33:27.100 --> 00:33:30.500
 need to directly to

635
00:33:30.500 --> 00:33:33.800
 detect whether the generated file contains malicious

636
00:33:33.800 --> 00:33:36.600
 content. We need to directly examine the

637
00:33:36.600 --> 00:33:40.100
 contents of the file created

638
00:33:39.100 --> 00:33:42.100
 on the server after such a

639
00:33:42.100 --> 00:33:43.700
 login attempting.

640
00:33:45.800 --> 00:33:47.600
As a result we have seen.

641
00:33:48.400 --> 00:33:52.100
That there may be a harmful activity and

642
00:33:51.100 --> 00:33:54.300
 malicious activity at the end

643
00:33:54.300 --> 00:33:57.300
 of the login attempts made in

644
00:33:57.300 --> 00:33:58.000
 this way.

645
00:33:59.500 --> 00:34:02.700
So keep in mind that and you should

646
00:34:02.700 --> 00:34:06.800
 make an analysis in this

647
00:34:06.800 --> 00:34:11.000
 way. You should follow the traffic better.

648
00:34:09.600 --> 00:34:12.700
 It is

649
00:34:12.700 --> 00:34:16.900
 a suspicious suspicious contents

650
00:34:15.900 --> 00:34:18.400
 or the

651
00:34:18.400 --> 00:34:21.500
 attempting or the another change

652
00:34:21.500 --> 00:34:24.400
 on the traffic. You should

653
00:34:24.400 --> 00:34:25.100
 notice that

654
00:34:26.100 --> 00:34:29.300
so that's all for now and we have

655
00:34:30.300 --> 00:34:33.400
a quick and the sample analysis on the

656
00:34:33.400 --> 00:34:34.900
 SMB protocol.

657
00:34:37.300 --> 00:34:40.700
So we will talk about the filtering techniques on

658
00:34:40.700 --> 00:34:43.300
 the next lesson. See you on the next video.
