WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.800 --> 00:00:10.200
Hello everyone in this lesson. We will learn

1
00:00:10.200 --> 00:00:13.400
 how to find the DNS and icmp tunneling

2
00:00:13.400 --> 00:00:17.900
 patterns and how to analyze the suspicious

3
00:00:16.900 --> 00:00:20.100
 packets in Wireshark.

4
00:00:21.100 --> 00:00:21.900
So let's begin.

5
00:00:32.700 --> 00:00:35.400
First of all, let's talk briefly about how

6
00:00:35.400 --> 00:00:39.000
 the DNS protocol Works DNS means

7
00:00:38.300 --> 00:00:41.400
 domain name system as you

8
00:00:41.400 --> 00:00:44.300
 know, and it is a protocol that is used to

9
00:00:44.300 --> 00:00:48.000
 map domains names to IP addresses. The

10
00:00:47.600 --> 00:00:50.700
 primary purpose of DNS is to translate

11
00:00:50.700 --> 00:00:53.700
 Humanity domain names such

12
00:00:53.700 --> 00:00:56.800
 as a wire shark dot org into

13
00:00:56.800 --> 00:01:00.300
 IP addresses that computers can understand such

14
00:00:59.300 --> 00:01:04.000
 as 10.0.2.1 and

15
00:01:03.100 --> 00:01:06.100
 firstly in this

16
00:01:06.100 --> 00:01:10.200
 conversation DNS conversation. The

17
00:01:09.200 --> 00:01:12.400
 first step is a client

18
00:01:12.400 --> 00:01:15.100
 such as a reproduction think of

19
00:01:15.100 --> 00:01:19.800
 a web processor or email client sends DNS

20
00:01:18.800 --> 00:01:21.300
 query to a DNS

21
00:01:21.300 --> 00:01:24.000
 server in order to resolve a domain name

22
00:01:24.200 --> 00:01:25.200
 to an IP address.

23
00:01:26.100 --> 00:01:29.400
The credit includes the domain name and the type

24
00:01:29.400 --> 00:01:32.400
 of record Being crooked requested such as

25
00:01:32.400 --> 00:01:36.400
 a letter upward case for IP

26
00:01:35.400 --> 00:01:38.500
 version for address and

27
00:01:38.500 --> 00:01:41.700
 for a letters for

28
00:01:41.700 --> 00:01:45.100
 IP version 6 address we

29
00:01:44.100 --> 00:01:47.900
 can see in the record type and

30
00:01:47.900 --> 00:01:51.100
 MX for mail servers.

31
00:01:50.100 --> 00:01:54.300
 You can see these record types

32
00:01:53.300 --> 00:01:56.800
 empty Second Step

33
00:01:56.800 --> 00:01:59.600
 the DNS server receives the query

34
00:01:59.600 --> 00:02:03.300
 and processes it by looking up the request

35
00:02:02.300 --> 00:02:06.400
 domain name in its local database or

36
00:02:05.400 --> 00:02:08.100
 forwarding the query to

37
00:02:08.100 --> 00:02:11.400
 another DNS server. The DNS server uses

38
00:02:11.400 --> 00:02:15.400
 a hierarchical system of nameservers

39
00:02:14.400 --> 00:02:17.400
 to resolve the domain name.

40
00:02:18.100 --> 00:02:21.700
And in The Next Step the root name servers

41
00:02:21.700 --> 00:02:25.200
 are the first point of contact and now

42
00:02:24.200 --> 00:02:27.400
 the address of the top level domain

43
00:02:27.400 --> 00:02:32.700
 TLD name servers such as.com dot

44
00:02:31.700 --> 00:02:35.100
 org or that edu and

45
00:02:34.100 --> 00:02:37.600
 those TLD name servers

46
00:02:37.600 --> 00:02:40.800
 will know the others of the next level for

47
00:02:40.800 --> 00:02:43.300
 example domains nameserver and so on

48
00:02:43.300 --> 00:02:46.600
 and then once the DNS server

49
00:02:46.600 --> 00:02:49.400
 has resulted domain name to an IP address.

50
00:02:49.400 --> 00:02:52.000
 It sends a DNS response to

51
00:02:52.100 --> 00:02:55.100
 the client with the result IP others.

52
00:02:55.500 --> 00:02:58.700
And declined receives the response

53
00:02:58.700 --> 00:03:01.300
 and uses the IP address to establish

54
00:03:01.300 --> 00:03:05.100
 a connection to the destination. And additionally

55
00:03:04.100 --> 00:03:07.900
 DNS protocol is built

56
00:03:07.900 --> 00:03:11.300
 on top of the user datagram protocol on

57
00:03:10.300 --> 00:03:13.400
 top of the UDP

58
00:03:13.400 --> 00:03:16.500
 protocol on Part 53.

59
00:03:17.200 --> 00:03:21.200
It is a connection list and stateless protocol.

60
00:03:20.200 --> 00:03:23.600
 Meaning that each query is

61
00:03:23.600 --> 00:03:27.000
 independent and that there is no persistence

62
00:03:26.400 --> 00:03:30.600
 between the requests and responses. Now,

63
00:03:29.600 --> 00:03:32.800
 let's examine that example the

64
00:03:32.800 --> 00:03:35.500
 NS traffic in Wireshark. I have opened

65
00:03:35.500 --> 00:03:36.900
 the PK file.

66
00:03:38.300 --> 00:03:42.300
And we will investigate over this PK

67
00:03:41.300 --> 00:03:45.000
 file or network traffic. So now

68
00:03:44.600 --> 00:03:47.400
 we are scrolling down and

69
00:03:49.500 --> 00:03:54.100
Let's take a look at this pact. We

70
00:03:52.100 --> 00:03:55.400
 see a DNS

71
00:03:55.400 --> 00:03:58.400
 query in here. You can see maybe

72
00:03:58.400 --> 00:04:01.800
 we see it. DNS query is sent

73
00:04:01.800 --> 00:04:04.900
 for the wireshark.org.

74
00:04:05.700 --> 00:04:08.200
On this IP address, there is a

75
00:04:08.200 --> 00:04:08.600
 DNS.

76
00:04:09.600 --> 00:04:12.800
And the destination Port is

77
00:04:12.800 --> 00:04:15.900
 53 as you can see and

78
00:04:15.900 --> 00:04:18.800
 let's take a look at packet details.

79
00:04:19.700 --> 00:04:20.900
on this packet

80
00:04:23.000 --> 00:04:23.300
so

81
00:04:24.500 --> 00:04:27.000
I'm scrolling here up a little bit.

82
00:04:28.300 --> 00:04:31.500
And you need to know that the DNS

83
00:04:31.500 --> 00:04:35.000
 protocol works on UDP Port 503.

84
00:04:36.200 --> 00:04:37.100
as in here

85
00:04:38.600 --> 00:04:41.500
on this packet the destination Port

86
00:04:41.500 --> 00:04:44.300
 53 because DNS protocol is

87
00:04:44.300 --> 00:04:47.300
 running on this port and

88
00:04:48.600 --> 00:04:51.600
so here we see that the Target Port

89
00:04:51.600 --> 00:04:54.600
 and because the query we send

90
00:04:54.600 --> 00:04:57.200
 is a DNS query and therefore it

91
00:04:57.200 --> 00:05:00.900
 goes to Port 53. Let's expand the

92
00:05:00.900 --> 00:05:03.700
 DNS field the domain

93
00:05:03.700 --> 00:05:05.200
 name system we have now.

94
00:05:05.800 --> 00:05:06.100
and

95
00:05:07.100 --> 00:05:11.500
the first thing we see is the transaction

96
00:05:10.500 --> 00:05:11.900
 ID.

97
00:05:12.500 --> 00:05:16.200
We can reach the conversation by filtering the

98
00:05:15.200 --> 00:05:17.500
 transaction ID.

99
00:05:18.200 --> 00:05:21.700
In any network traffic so

100
00:05:21.700 --> 00:05:24.800
 since the response packet

101
00:05:24.800 --> 00:05:27.600
 comes right after the query in

102
00:05:27.600 --> 00:05:28.800
 this traffic.

103
00:05:29.400 --> 00:05:32.500
We can easily examine it but let's reach

104
00:05:32.500 --> 00:05:35.600
 the conversation directly by filtering

105
00:05:35.600 --> 00:05:38.100
 with transaction ID to do

106
00:05:38.100 --> 00:05:41.700
 this. Let's click on the transaction ID

107
00:05:41.700 --> 00:05:43.100
 information and

108
00:05:44.400 --> 00:05:48.000
hold it and leave it to the display filter

109
00:05:47.000 --> 00:05:48.500
 field.

110
00:05:49.300 --> 00:05:50.300
Like in this way.

111
00:05:51.600 --> 00:05:54.900
And I am dropping in the display filter

112
00:05:54.900 --> 00:05:55.300
 field.

113
00:05:57.900 --> 00:05:59.300
So as you can see.

114
00:06:00.300 --> 00:06:04.200
The filtering is applied directly.

115
00:06:05.200 --> 00:06:09.100
And now we are seeing the conversation only.

116
00:06:09.800 --> 00:06:10.000
so

117
00:06:11.100 --> 00:06:11.400
since

118
00:06:12.300 --> 00:06:15.800
It is a query package on

119
00:06:15.800 --> 00:06:18.900
 this packet. Let's move on to investigate the

120
00:06:18.900 --> 00:06:22.200
 query packet in here. We

121
00:06:21.200 --> 00:06:24.800
 see the queries field because

122
00:06:24.800 --> 00:06:27.900
 this packet a DNS query packet and

123
00:06:27.900 --> 00:06:30.900
 let's expand this field.

124
00:06:31.800 --> 00:06:34.000
and expand this to

125
00:06:36.500 --> 00:06:40.200
equally was made for in here.

126
00:06:39.200 --> 00:06:42.900
 Why shark.org as

127
00:06:42.900 --> 00:06:43.200
 you can see?

128
00:06:43.900 --> 00:06:47.700
And type A indicates that

129
00:06:46.700 --> 00:06:49.600
 this query is an

130
00:06:49.600 --> 00:06:51.300
 IP version query.

131
00:06:52.100 --> 00:06:56.100
So IP version 4 information was

132
00:06:55.100 --> 00:06:59.000
 requested for wireshark.org.

133
00:07:01.100 --> 00:07:04.700
There were four a letters in the

134
00:07:04.700 --> 00:07:07.700
 type value then it would mean requesting

135
00:07:07.700 --> 00:07:10.900
 IP version 6 information, but here

136
00:07:10.900 --> 00:07:14.700
 we can see the type value is as

137
00:07:13.700 --> 00:07:17.400
 a the one a

138
00:07:16.400 --> 00:07:19.500
 letter. So it means

139
00:07:19.500 --> 00:07:22.800
 that the query is for IP version

140
00:07:22.800 --> 00:07:25.700
 for information. So keep

141
00:07:25.700 --> 00:07:28.700
 in mind that and now let's click

142
00:07:28.700 --> 00:07:31.300
 on the response package.

143
00:07:33.500 --> 00:07:36.500
The unlike the query packet we see

144
00:07:36.500 --> 00:07:38.300
 the answers field in here.

145
00:07:39.300 --> 00:07:41.900
so in the answers field

146
00:07:42.600 --> 00:07:45.500
Let's expand and there it

147
00:07:45.500 --> 00:07:49.800
 is. You can see wireshark.org information

148
00:07:48.800 --> 00:07:51.600
 and as you

149
00:07:51.600 --> 00:07:54.600
 can see the resolution from the domain address.

150
00:07:55.400 --> 00:07:57.000
to the IP information

151
00:07:58.200 --> 00:08:02.100
Now we can see the IP address of the domain name

152
00:08:01.100 --> 00:08:04.200
 wireshark.org.

153
00:08:05.100 --> 00:08:08.400
So now the client can access the relevant

154
00:08:08.400 --> 00:08:11.100
 domain using this IP address.

155
00:08:12.300 --> 00:08:14.600
And let's remove the filter.

156
00:08:16.500 --> 00:08:19.700
and when we look at next packet

157
00:08:20.300 --> 00:08:22.600
after the response packet

158
00:08:23.700 --> 00:08:26.600
and let's click on the next packet.

159
00:08:28.300 --> 00:08:31.200
When we look at the dispute packet, we see

160
00:08:31.200 --> 00:08:35.600
 that it sends a pink messages a

161
00:08:34.600 --> 00:08:38.400
 pink message to the IP that

162
00:08:37.400 --> 00:08:40.200
 we have obtained by

163
00:08:40.200 --> 00:08:43.800
 the DNS query previously. So

164
00:08:43.800 --> 00:08:46.300
 keep in mind that when we type

165
00:08:46.300 --> 00:08:49.700
 also fireshark.org and enter

166
00:08:49.700 --> 00:08:51.800
 on the our web browser.

167
00:08:52.300 --> 00:08:55.600
the same process takes place in the background

168
00:08:56.900 --> 00:08:58.400
like in this

169
00:08:59.200 --> 00:08:59.800
traffic

170
00:09:00.600 --> 00:09:03.600
So now that we have seen a basic and

171
00:09:03.600 --> 00:09:06.400
 normal example of DNS communication.

172
00:09:06.400 --> 00:09:10.500
 Let's see examples of suspicious and

173
00:09:10.500 --> 00:09:12.000
 potential cyber attacks.

174
00:09:12.900 --> 00:09:13.900
and we are

175
00:09:14.900 --> 00:09:17.600
we are gonna to write to understand the

176
00:09:17.600 --> 00:09:20.300
 difference between them in a normal

177
00:09:20.300 --> 00:09:24.600
 DNS terrific and attack terrific suspicious

178
00:09:23.600 --> 00:09:25.500
 terrific.

179
00:09:26.400 --> 00:09:29.700
So for this we open a we will open a PK

180
00:09:29.700 --> 00:09:32.800
 file containing Network packets captured at

181
00:09:32.800 --> 00:09:35.900
 the time of DNS tunnelink attack. So

182
00:09:35.900 --> 00:09:37.400
 let me open this 5

183
00:09:38.600 --> 00:09:40.000
attack traffic file

184
00:09:43.100 --> 00:09:43.300
and

185
00:09:45.300 --> 00:09:48.300
we will investigate the speaker file.

186
00:09:48.300 --> 00:09:51.300
 First of all, if you are working on a very

187
00:09:51.300 --> 00:09:54.500
 large pickup NG file, you should

188
00:09:54.500 --> 00:09:58.400
 do DNS filtering to see on DNS

189
00:09:57.400 --> 00:09:58.600
 traffic.

190
00:09:59.300 --> 00:10:02.700
Don't forget it. You can do this in two ways

191
00:10:02.700 --> 00:10:06.100
 you either type DNS?

192
00:10:07.400 --> 00:10:08.600
as filters

193
00:10:09.700 --> 00:10:12.400
or you can write you can

194
00:10:12.400 --> 00:10:12.700
 type.

195
00:10:14.400 --> 00:10:16.700
This filter you repeat that.

196
00:10:17.500 --> 00:10:17.900
port

197
00:10:19.200 --> 00:10:24.000
Is equal to DNS Port 503?

198
00:10:24.800 --> 00:10:27.300
And your channel, so use this filter.

199
00:10:28.400 --> 00:10:30.700
instead of only DNS

200
00:10:31.300 --> 00:10:34.500
this is the first thing you should do, but I don't

201
00:10:34.500 --> 00:10:38.000
 need to do this because my all

202
00:10:37.600 --> 00:10:41.500
 packets are already DNS

203
00:10:40.500 --> 00:10:42.700
 packets and there is

204
00:10:43.800 --> 00:10:44.700
no other

205
00:10:46.100 --> 00:10:47.200
type packet

206
00:10:48.100 --> 00:10:48.600
So much.

207
00:10:51.200 --> 00:10:53.100
so now secondly

208
00:10:54.500 --> 00:10:57.700
they will use you should look for any packet that

209
00:10:57.700 --> 00:11:00.700
 have unusual characteristics such as

210
00:11:00.700 --> 00:11:03.300
 specially long domain names.

211
00:11:04.700 --> 00:11:06.200
As you can see in here.

212
00:11:08.300 --> 00:11:11.700
What a such a long domain names

213
00:11:11.700 --> 00:11:12.300
 you can see.

214
00:11:14.700 --> 00:11:15.000
and

215
00:11:16.500 --> 00:11:19.000
in addition to unusual characteristics

216
00:11:19.900 --> 00:11:23.400
like in this field in these records,

217
00:11:22.400 --> 00:11:25.800
 you can see some

218
00:11:25.800 --> 00:11:28.700
 especially long domain names and

219
00:11:28.700 --> 00:11:32.100
 high numbers of sub

220
00:11:31.100 --> 00:11:32.900
 domains.

221
00:11:33.400 --> 00:11:34.900
Maybe you can see in here.

222
00:11:36.700 --> 00:11:38.400
in this example

223
00:11:42.300 --> 00:11:46.000
and lastly repeated queries for

224
00:11:45.300 --> 00:11:48.400
 the same domain you may see

225
00:11:48.400 --> 00:11:51.800
 in the suspicious packets. So

226
00:11:51.800 --> 00:11:55.300
 these can be signs of DNS tunneling

227
00:11:54.300 --> 00:11:58.000
 and for example, almost all

228
00:11:57.400 --> 00:12:00.600
 of the packets here are made up

229
00:12:00.600 --> 00:12:03.200
 of long domain names and

230
00:12:04.200 --> 00:12:07.100
Unusual character sets you can see

231
00:12:07.100 --> 00:12:10.600
 in here. There are two many unreal character

232
00:12:10.600 --> 00:12:14.500
 sets and multiple sub

233
00:12:13.500 --> 00:12:15.500
 domains. You can see

234
00:12:16.700 --> 00:12:18.300
like this like

235
00:12:19.400 --> 00:12:21.000
the other ones

236
00:12:21.800 --> 00:12:22.100
and

237
00:12:23.200 --> 00:12:26.800
this is a typical example of DNS tunnel

238
00:12:26.800 --> 00:12:27.700
 link attack.

239
00:12:28.400 --> 00:12:31.400
So and you should look at the timing of

240
00:12:31.400 --> 00:12:34.200
 the DNS requests and responses.

241
00:12:35.400 --> 00:12:39.200
You should investigate those also the

242
00:12:38.200 --> 00:12:43.100
 timing and if

243
00:12:42.100 --> 00:12:46.000
 there is a frequent data

244
00:12:45.300 --> 00:12:48.400
 transfer in a specific time frame,

245
00:12:48.400 --> 00:12:51.100
 especially it could be a sign of

246
00:12:51.100 --> 00:12:54.700
 a tunnel and you can also apply these filters

247
00:12:54.700 --> 00:12:59.000
 in order to find dnskat patterns.

248
00:13:01.100 --> 00:13:04.600
you can also some filters in

249
00:13:04.600 --> 00:13:07.300
 order to find DNS get patterns and

250
00:13:07.300 --> 00:13:10.900
 suspicious DNS queries like this you can

251
00:13:10.900 --> 00:13:12.100
 use

252
00:13:13.700 --> 00:13:15.100
DNS contains

253
00:13:18.000 --> 00:13:18.500
DNS

254
00:13:19.400 --> 00:13:19.700
cat

255
00:13:23.200 --> 00:13:27.100
So this is the first one of the filter Expressions

256
00:13:26.100 --> 00:13:29.200
 you can use this one

257
00:13:29.200 --> 00:13:32.400
 in order to find dnskat patterns.

258
00:13:32.400 --> 00:13:35.700
 And the other one is DNS.

259
00:13:39.400 --> 00:13:40.800
You are why?

260
00:13:41.700 --> 00:13:43.300
means query

261
00:13:44.100 --> 00:13:45.100
dot name

262
00:13:46.300 --> 00:13:46.700
Dot

263
00:13:49.200 --> 00:13:49.900
length

264
00:13:51.900 --> 00:13:54.500
Greater than for example

265
00:13:54.500 --> 00:13:55.700
 15.

266
00:13:57.600 --> 00:14:01.100
And you can use also this filter to

267
00:14:00.100 --> 00:14:04.700
 find the DNS channeling

268
00:14:04.700 --> 00:14:05.300
 patterns.

269
00:14:06.100 --> 00:14:10.400
So these are the filters that you can use to find

270
00:14:09.400 --> 00:14:12.900
 some suspicious patterns

271
00:14:12.900 --> 00:14:16.700
 like in this PK file.

272
00:14:19.400 --> 00:14:23.400
and you can also investigate the

273
00:14:22.400 --> 00:14:26.300
 queries in the

274
00:14:26.300 --> 00:14:29.600
 packet details pain and

275
00:14:31.300 --> 00:14:35.500
for example in this query there is a sum there's

276
00:14:34.500 --> 00:14:39.000
 some characters said

277
00:14:38.200 --> 00:14:41.400
 suspicious character set

278
00:14:41.400 --> 00:14:45.500
 and to look closer

279
00:14:44.500 --> 00:14:47.900
 this query

280
00:14:47.900 --> 00:14:48.900
 you can use

281
00:14:50.900 --> 00:14:52.400
show packet bytes.

282
00:14:54.500 --> 00:14:56.900
pain and in here

283
00:14:57.500 --> 00:15:01.200
you can see some hex or base

284
00:15:00.200 --> 00:15:05.000
 64 structure

285
00:15:03.500 --> 00:15:06.000
 and you can

286
00:15:06.300 --> 00:15:10.500
 take this character groups and

287
00:15:09.500 --> 00:15:11.000
 you can

288
00:15:12.200 --> 00:15:15.400
you can encode sorry. You can

289
00:15:15.400 --> 00:15:18.900
 decode these characters using some

290
00:15:18.900 --> 00:15:20.900
 hex converter tools.

291
00:15:21.500 --> 00:15:23.400
So, okay. That's all now.

292
00:15:26.500 --> 00:15:29.600
We can close the pain and we

293
00:15:29.600 --> 00:15:31.900
 can close the pick file.

294
00:15:34.200 --> 00:15:37.600
Now we will talk about icmp tunneling

295
00:15:37.600 --> 00:15:38.700
 attacks.

296
00:15:45.100 --> 00:15:48.600
Icmp tunneling attacks are often anomalies that

297
00:15:48.600 --> 00:15:52.500
 arise after malware activity. So

298
00:15:51.500 --> 00:15:54.900
 the militia sectors exploit

299
00:15:54.900 --> 00:15:58.900
 these part to exfiltrate data

300
00:15:57.900 --> 00:16:00.600
 and create a c to

301
00:16:00.600 --> 00:16:04.100
 connection since icmp packets

302
00:16:03.100 --> 00:16:07.100
 can include an additional data payload. It

303
00:16:06.100 --> 00:16:09.300
 might be a data is playing text or

304
00:16:09.300 --> 00:16:12.200
 a file contain some scripts or

305
00:16:12.200 --> 00:16:17.300
 even an image with hidden patterns while icmp

306
00:16:15.300 --> 00:16:18.200
 protocols give

307
00:16:18.200 --> 00:16:21.500
 a great chance to transmit additional data.

308
00:16:21.500 --> 00:16:24.400
 They also have this some this

309
00:16:24.400 --> 00:16:27.900
 this advantages most business

310
00:16:27.900 --> 00:16:31.000
 networks either prohibit custom

311
00:16:30.500 --> 00:16:34.800
 packets or need administrator access

312
00:16:34.800 --> 00:16:38.400
 to send custom icmp packets

313
00:16:37.400 --> 00:16:40.300
 a huge amount

314
00:16:40.300 --> 00:16:44.700
 of icmp traffic or unusual packet

315
00:16:44.700 --> 00:16:45.000
 sizes.

316
00:16:45.100 --> 00:16:48.500
Are signs of icmp tunneling so

317
00:16:48.500 --> 00:16:52.200
 however, because attackers can

318
00:16:51.200 --> 00:16:54.600
 built unique packets that match

319
00:16:54.600 --> 00:16:57.700
 the standard icmp packet

320
00:16:57.700 --> 00:17:01.200
 size, which is 64 bytes

321
00:17:00.200 --> 00:17:04.100
 discovering these tunneling operations

322
00:17:03.100 --> 00:17:07.100
 becomes difficult. So here

323
00:17:06.100 --> 00:17:10.300
 we will review and icmp

324
00:17:09.300 --> 00:17:13.300
 tunneling I have done before in

325
00:17:12.300 --> 00:17:16.200
 a lab environment I made

326
00:17:15.200 --> 00:17:18.500
 and icmp tunnel

327
00:17:18.500 --> 00:17:21.700
 link instrumentation in

328
00:17:21.700 --> 00:17:24.800
 the my local network. And

329
00:17:24.800 --> 00:17:27.100
 while this tunneling was

330
00:17:27.100 --> 00:17:30.800
 happening. I captured Network traffic with

331
00:17:30.800 --> 00:17:34.100
 Wireshark using Wireshark. Let's

332
00:17:33.100 --> 00:17:36.000
 investigate the pickup file that I

333
00:17:36.300 --> 00:17:40.500
 have opened and continuing

334
00:17:39.500 --> 00:17:43.100
 the icmp

335
00:17:42.100 --> 00:17:44.600
 channel link terrific.

336
00:17:45.100 --> 00:17:48.600
Filter we will use to detect icmp tunnel

337
00:17:48.600 --> 00:17:50.800
 link should be like this.

338
00:17:52.400 --> 00:17:56.200
icmp and data Dot

339
00:18:02.800 --> 00:18:06.100
Which was a 64 bytes

340
00:18:05.100 --> 00:18:08.400
 as the packet pipes

341
00:18:08.400 --> 00:18:11.200
 is the packet size because this is

342
00:18:11.200 --> 00:18:14.800
 the maximum maximum expected size

343
00:18:14.800 --> 00:18:17.300
 of a standard pythmp packet.

344
00:18:17.300 --> 00:18:20.400
 For example, let's first take a look

345
00:18:20.400 --> 00:18:23.400
 at the data length sizes in

346
00:18:23.400 --> 00:18:27.600
 the pink packets. You can see these are

347
00:18:27.600 --> 00:18:30.200
 the pink packets and there are

348
00:18:30.200 --> 00:18:32.900
 so many pink packets we have

349
00:18:33.700 --> 00:18:38.100
and let's take a look icmp field

350
00:18:37.100 --> 00:18:40.700
 in the packet details field

351
00:18:40.700 --> 00:18:42.800
 and as you can see

352
00:18:44.800 --> 00:18:47.900
the data link size in

353
00:18:47.900 --> 00:18:49.500
 normal pink packets

354
00:18:50.400 --> 00:18:53.900
is 48 bytes. So when

355
00:18:53.900 --> 00:18:57.600
 the icmp header size is added

356
00:18:56.600 --> 00:18:59.600
 to to the

357
00:18:59.600 --> 00:19:02.800
 data bytes to the data size the

358
00:19:02.800 --> 00:19:05.300
 maximum packet length value

359
00:19:05.300 --> 00:19:09.900
 must be 56 or 60 for

360
00:19:09.900 --> 00:19:10.500
 bytes.

361
00:19:11.300 --> 00:19:12.400
these are the

362
00:19:13.500 --> 00:19:15.800
possible maximum values

363
00:19:17.500 --> 00:19:19.300
a pink packet can be

364
00:19:20.600 --> 00:19:24.100
56 bytes or 64 bytes.

365
00:19:23.100 --> 00:19:26.800
 So now let's apply our filter

366
00:19:26.800 --> 00:19:29.600
 and see these packs.

367
00:19:32.900 --> 00:19:35.900
Take a look at how the packet length

368
00:19:35.900 --> 00:19:38.700
 size greater than the normal

369
00:19:38.700 --> 00:19:41.200
 packet size and let's go to

370
00:19:41.200 --> 00:19:45.200
 pack a details and take a closer look for these

371
00:19:44.200 --> 00:19:47.300
 huge packets.

372
00:19:48.300 --> 00:19:52.600
So I click on the first

373
00:19:51.600 --> 00:19:55.100
 packet that has

374
00:19:54.100 --> 00:19:55.900
 the length.

375
00:19:57.600 --> 00:20:01.000
Greater than 1,000 bytes. And

376
00:20:00.500 --> 00:20:04.300
 when we look at the packet details,

377
00:20:04.300 --> 00:20:08.100
 you can see icmp field in

378
00:20:07.100 --> 00:20:10.900
 here and we are expanding the

379
00:20:10.900 --> 00:20:14.200
 icmp field and scrolling down

380
00:20:13.200 --> 00:20:16.900
 and the data as

381
00:20:16.900 --> 00:20:20.800
 you can see as a very

382
00:20:19.800 --> 00:20:24.400
 huge size data

383
00:20:22.400 --> 00:20:29.100
 size is 1,300 bytes.

384
00:20:28.100 --> 00:20:32.300
 And this is really so

385
00:20:31.300 --> 00:20:34.500
 unusual size for

386
00:20:34.500 --> 00:20:37.400
 a ice for icmp picked.

387
00:20:37.900 --> 00:20:41.400
And this is not normal, so we

388
00:20:40.400 --> 00:20:45.600
 should investigate in a

389
00:20:44.600 --> 00:20:46.300
 more detailed.

390
00:20:47.600 --> 00:20:51.900
and when we look at the show packed bytes

391
00:20:50.900 --> 00:20:52.900
 as you can see

392
00:20:55.500 --> 00:20:56.300
Oh, look at this.

393
00:20:57.400 --> 00:21:00.800
We can see the payload data in

394
00:21:00.800 --> 00:21:03.700
 our icmp packet and

395
00:21:03.700 --> 00:21:06.300
 here there is a plain Text

396
00:21:06.300 --> 00:21:08.000
 data.

397
00:21:08.800 --> 00:21:11.900
And it says this is a payload for

398
00:21:11.900 --> 00:21:13.900
 icmp tunnel.

399
00:21:14.600 --> 00:21:17.700
So in here there is a payload

400
00:21:17.700 --> 00:21:20.700
 within the icmp packet

401
00:21:20.700 --> 00:21:23.500
 pink packet. When we look at

402
00:21:23.500 --> 00:21:26.800
 first, we we can think this

403
00:21:26.800 --> 00:21:29.200
 is a normal icmp pink

404
00:21:29.200 --> 00:21:32.200
 packet, but when we look at the look at

405
00:21:32.200 --> 00:21:37.900
 in details in the data field and white

406
00:21:35.900 --> 00:21:39.200
 Spain by

407
00:21:40.300 --> 00:21:45.100
In the bright Spain we can see the data payload

408
00:21:43.100 --> 00:21:46.800
 data in here and

409
00:21:46.800 --> 00:21:49.600
 there is a some plain Text data.

410
00:21:51.400 --> 00:21:53.400
so, okay, we can close this and

411
00:21:55.500 --> 00:21:58.600
look at this. There is a another and greater

412
00:21:58.600 --> 00:22:01.600
 packet icmp pink packet

413
00:22:01.600 --> 00:22:04.000
 as well. And then we look at

414
00:22:04.900 --> 00:22:06.600
 to the data field also.

415
00:22:08.300 --> 00:22:11.400
Let's look at the show packet bytes again.

416
00:22:12.400 --> 00:22:15.400
And as you can see in this

417
00:22:15.400 --> 00:22:18.500
 time, we can see an image

418
00:22:18.500 --> 00:22:18.900
 file.

419
00:22:19.600 --> 00:22:21.600
So that is unexpected.

420
00:22:22.400 --> 00:22:25.700
And this is a payload payload data

421
00:22:25.700 --> 00:22:29.900
 a suspicious and unexpected payload

422
00:22:28.900 --> 00:22:30.100
 data.

423
00:22:31.400 --> 00:22:34.300
When we look at the packet bytes pane

424
00:22:34.300 --> 00:22:35.200
 you can see.

425
00:22:36.700 --> 00:22:39.700
if you look at the packet price

426
00:22:39.700 --> 00:22:42.700
 pane first, you can see only

427
00:22:43.500 --> 00:22:48.500
a sign like this gajif so

428
00:22:47.500 --> 00:22:50.300
 we can have an information

429
00:22:50.300 --> 00:22:53.800
 there is a there is an image file, but

430
00:22:53.800 --> 00:22:56.600
 if we can see the image itself in

431
00:22:56.600 --> 00:22:57.100
 here.

432
00:22:57.900 --> 00:23:01.800
Just we can see the bytes information. But

433
00:23:00.800 --> 00:23:03.300
 if you look at look

434
00:23:03.300 --> 00:23:06.900
 at the show packed by Spain, you

435
00:23:06.900 --> 00:23:08.700
 can see the original image.

436
00:23:09.300 --> 00:23:12.500
And there's a radio image that we

437
00:23:12.500 --> 00:23:16.300
 that is hidden in the acmp pink

438
00:23:16.300 --> 00:23:16.800
 packet.

439
00:23:17.800 --> 00:23:19.100
So that's all and

440
00:23:21.400 --> 00:23:25.200
can see the icmp tunnel link patterns in

441
00:23:24.200 --> 00:23:25.600
 this way.

442
00:23:26.400 --> 00:23:31.600
And you can use these filtering expressions.

443
00:23:32.500 --> 00:23:36.100
In order to find some icmp tunnel

444
00:23:35.100 --> 00:23:37.200
 link patterns.

445
00:23:39.500 --> 00:23:42.100
So that's all for now. See you on the

446
00:23:42.100 --> 00:23:42.300
 next video.
