WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.400 --> 00:00:11.000
Hello everyone in this lesson. I will show you how you can decrypted

1
00:00:10.700 --> 00:00:13.300
 RDP protocol and what kind of

2
00:00:13.300 --> 00:00:17.200
 information we can have decryptility RDP

3
00:00:16.200 --> 00:00:17.500
 traffic.

4
00:00:19.100 --> 00:00:20.100
Now let's begin.

5
00:00:23.100 --> 00:00:27.000
Percy let's talk about Rd people called briefly the

6
00:00:26.300 --> 00:00:29.400
 remote desktop protocol RDP is

7
00:00:29.400 --> 00:00:32.400
 a protocol developed by Microsoft that provides

8
00:00:32.400 --> 00:00:35.300
 a user with a graphical interface to

9
00:00:35.300 --> 00:00:38.100
 connect to another computer over a network

10
00:00:38.100 --> 00:00:41.600
 connection and the user employs RDP client

11
00:00:41.600 --> 00:00:45.100
 software for this purpose. As you know, while the

12
00:00:44.100 --> 00:00:47.200
 other computer must run

13
00:00:47.200 --> 00:00:50.400
 RDP server software RDP uses a

14
00:00:50.400 --> 00:00:53.200
 client server architecture where the remote

15
00:00:53.200 --> 00:00:56.800
 computer This Server listens for incoming connections

16
00:00:56.800 --> 00:00:59.700
 from RDP clients and decline

17
00:00:59.700 --> 00:01:02.800
 established connection to the server or

18
00:01:02.800 --> 00:01:06.300
 the case the user and then this

19
00:01:05.300 --> 00:01:08.100
 place this servers desktop in

20
00:01:08.100 --> 00:01:11.700
 a window on the clients computer. Let's look

21
00:01:11.700 --> 00:01:15.100
 at the RDP traffic encrypted with

22
00:01:14.100 --> 00:01:18.000
 TLS protocol now and our

23
00:01:17.600 --> 00:01:20.400
 focus is on RDP protocol.

24
00:01:20.400 --> 00:01:22.600
 So let's take a second to

25
00:01:23.400 --> 00:01:26.700
On RDP and see what it returns when we

26
00:01:26.700 --> 00:01:29.500
 typed an RDP filter expression.

27
00:01:33.800 --> 00:01:36.700
Look at this we can see no packets associated

28
00:01:36.700 --> 00:01:39.300
 with the RDP protocol. Now, this is

29
00:01:39.300 --> 00:01:42.600
 because RDP is using TLS to encrypt the

30
00:01:42.600 --> 00:01:46.100
 data in our PK file in our

31
00:01:45.100 --> 00:01:48.200
 traffic. And so we will

32
00:01:48.200 --> 00:01:51.500
 not be able to see anything that happens with

33
00:01:51.500 --> 00:01:54.500
 RDP traffic at this moment. So now

34
00:01:54.500 --> 00:01:57.200
 let's decrypt the RDP traffic

35
00:01:57.200 --> 00:01:59.800
 using the TLs key values.

36
00:02:02.200 --> 00:02:05.400
And as you can see at this moment, we cannot

37
00:02:05.400 --> 00:02:09.200
 see any packet associated with the RDP

38
00:02:08.200 --> 00:02:11.800
 protocol all the data that

39
00:02:11.800 --> 00:02:12.500
 we can see.

40
00:02:14.600 --> 00:02:17.300
Is a TLS packet and

41
00:02:17.300 --> 00:02:20.400
 we can see only the application

42
00:02:20.400 --> 00:02:24.000
 data in here and these application

43
00:02:23.700 --> 00:02:26.200
 status are encrypted with

44
00:02:26.200 --> 00:02:29.100
 the ALS protocol. So when we

45
00:02:29.100 --> 00:02:29.400
 look at the

46
00:02:30.300 --> 00:02:33.600
Application data part under the transport

47
00:02:33.600 --> 00:02:36.700
 layer security. You can see only the

48
00:02:36.700 --> 00:02:39.600
 encrypted application data part

49
00:02:39.600 --> 00:02:41.100
 and you cannot see

50
00:02:42.100 --> 00:02:45.700
what it contains exactly so now

51
00:02:47.300 --> 00:02:50.900
it will decrypty RDP traffic in here

52
00:02:50.900 --> 00:02:52.300
 and then

53
00:02:53.500 --> 00:02:57.200
we will be able to see the all RDP

54
00:02:56.200 --> 00:02:59.600
 traffic in our PK file, but

55
00:02:59.600 --> 00:03:02.200
 at this moment we cannot see any.

56
00:03:03.200 --> 00:03:06.400
Data any packet associated with the RDP

57
00:03:06.400 --> 00:03:09.700
 or any other protocols all the

58
00:03:09.700 --> 00:03:10.200
 data.

59
00:03:11.300 --> 00:03:14.700
Is with the TLs protocol at

60
00:03:14.700 --> 00:03:15.300
 this moment?

61
00:03:18.300 --> 00:03:21.600
So now let me show you how you can decrypt the RDP traffic

62
00:03:21.600 --> 00:03:23.000
 in the easiest way.

63
00:03:24.300 --> 00:03:28.500
To do this you can go to the edit menu and references

64
00:03:27.500 --> 00:03:30.800
 menu. Then you

65
00:03:30.800 --> 00:03:34.200
 will choose the protocol as TLS.

66
00:03:36.300 --> 00:03:36.600
and

67
00:03:37.700 --> 00:03:40.700
in the transport layer security TLS window,

68
00:03:40.700 --> 00:03:43.200
 we will use the RSA Keys list

69
00:03:43.200 --> 00:03:46.400
 menu, and we will click on the edit.

70
00:03:47.600 --> 00:03:50.400
In here, it will add the our server

71
00:03:50.400 --> 00:03:53.800
 information and the key file. We will

72
00:03:53.800 --> 00:03:56.900
 show our key file to Wireshark and

73
00:03:56.900 --> 00:03:59.500
 we will locate the key file

74
00:03:59.500 --> 00:04:02.500
 in here. So to add our

75
00:04:02.500 --> 00:04:04.600
 information click on the

76
00:04:05.500 --> 00:04:08.400
Last button and in here, we will

77
00:04:08.400 --> 00:04:11.700
 type our server IP address in our

78
00:04:11.700 --> 00:04:12.600
 traffic as you can see.

79
00:04:14.300 --> 00:04:17.700
Our client is who signs the

80
00:04:17.700 --> 00:04:20.600
 client Hello message. So in this

81
00:04:20.600 --> 00:04:23.500
 situation arcline is this machine

82
00:04:23.500 --> 00:04:26.900
 with this IP address and our server?

83
00:04:27.600 --> 00:04:31.100
Is who sense the TLs server

84
00:04:30.100 --> 00:04:33.700
 Hello message and so in

85
00:04:33.700 --> 00:04:36.700
 illustration are server is

86
00:04:36.700 --> 00:04:39.600
 this machine and it has the IP

87
00:04:39.600 --> 00:04:42.600
 address 10.0.2 dot

88
00:04:42.600 --> 00:04:45.500
 15 so our IP address

89
00:04:45.500 --> 00:04:48.400
 our server IP address is that and I

90
00:04:48.400 --> 00:04:51.500
 will type it into the IP address field.

91
00:05:01.600 --> 00:05:04.500
Then I will add the port information

92
00:05:04.500 --> 00:05:08.400
 of the server and the server

93
00:05:07.400 --> 00:05:11.000
 sport is 33 and

94
00:05:10.300 --> 00:05:13.400
 89 and I

95
00:05:13.400 --> 00:05:15.500
 will add the server port number here.

96
00:05:18.200 --> 00:05:21.900
So then I will choose my SSL or

97
00:05:21.900 --> 00:05:24.300
 TLS key file in here.

98
00:05:25.400 --> 00:05:28.200
Click on browse and then I will

99
00:05:28.200 --> 00:05:29.800
 choose my key file.

100
00:05:30.300 --> 00:05:32.700
as in here and open

101
00:05:33.700 --> 00:05:36.300
then I will click on OK button.

102
00:05:38.400 --> 00:05:41.500
And when I click on the OK button

103
00:05:41.500 --> 00:05:44.400
 in this window or traffic will be changed.

104
00:05:45.800 --> 00:05:48.800
And we will see the traffic as

105
00:05:48.800 --> 00:05:49.900
 decrypted mode.

106
00:05:50.900 --> 00:05:54.100
As in the decrypted form and you

107
00:05:53.100 --> 00:05:56.800
 will see the change when I

108
00:05:56.800 --> 00:05:58.600
 click on the OK button.

109
00:05:59.600 --> 00:06:02.600
So you can see now decrypted traffic

110
00:06:02.600 --> 00:06:05.900
 in our PK file and now

111
00:06:05.900 --> 00:06:09.100
 there is no more application data

112
00:06:08.100 --> 00:06:10.000
 expression.

113
00:06:10.900 --> 00:06:12.200
in the info field

114
00:06:14.400 --> 00:06:17.300
we can see clearly the RDP traffic

115
00:06:17.300 --> 00:06:21.600
 and the create SSP protocol information

116
00:06:20.600 --> 00:06:24.300
 here. So let me

117
00:06:25.300 --> 00:06:28.500
talk about the process after the

118
00:06:28.500 --> 00:06:29.700
 TLs handshake.

119
00:06:30.300 --> 00:06:33.300
What we are seeing in this traffic.

120
00:06:34.300 --> 00:06:38.100
Starts with the create SSP packets. Let

121
00:06:37.100 --> 00:06:40.800
 me explain this for a

122
00:06:40.800 --> 00:06:44.500
 while and create SSP, maybe

123
00:06:43.500 --> 00:06:46.900
 some of you know about

124
00:06:46.900 --> 00:06:49.600
 the credit SSP protocol after

125
00:06:49.600 --> 00:06:52.900
 the tennis handshake process in here.

126
00:06:52.900 --> 00:06:56.300
 We see the authentication packets

127
00:06:55.300 --> 00:06:58.200
 begin with the

128
00:06:58.200 --> 00:07:03.100
 negotiate packet begins with the ntlm SSP.

129
00:07:02.100 --> 00:07:05.600
 Negotiate packet. And in here

130
00:07:05.600 --> 00:07:08.900
 are protocol is great SSP, and we

131
00:07:08.900 --> 00:07:12.800
 couldn't see the credit SSP protocol information

132
00:07:11.800 --> 00:07:15.400
 before the description

133
00:07:14.400 --> 00:07:16.300
 of the traffic.

134
00:07:16.900 --> 00:07:20.400
And credit SSP means credential

135
00:07:19.400 --> 00:07:22.700
 security support provider. So

136
00:07:22.700 --> 00:07:26.000
 it is a credit SSP is a

137
00:07:25.500 --> 00:07:28.300
 security protocol that is used in Windows

138
00:07:28.300 --> 00:07:31.600
 operating systems to allow remote servers to

139
00:07:31.600 --> 00:07:34.900
 delegate the user's credentials from the client computer

140
00:07:34.900 --> 00:07:37.300
 to the Target server. And this is

141
00:07:37.300 --> 00:07:40.700
 typically used in remote desktop protocol

142
00:07:40.700 --> 00:07:43.800
 in RDP protocol connections. When

143
00:07:43.800 --> 00:07:46.900
 a user attempts to connect to a remote server using

144
00:07:46.900 --> 00:07:49.800
 RDP declined computers

145
00:07:49.800 --> 00:07:53.600
 spread SSP component is used to secure

146
00:07:52.600 --> 00:07:56.000
 delegate. The user's credentials

147
00:07:55.200 --> 00:07:58.800
 to the remote server the remote server

148
00:07:58.800 --> 00:08:01.900
 can then use the delegated credentials

149
00:08:01.900 --> 00:08:04.200
 to access resources on the

150
00:08:04.200 --> 00:08:07.900
 computer or on other servers that

151
00:08:07.900 --> 00:08:11.100
 the user has access to so create

152
00:08:10.100 --> 00:08:13.200
 SSP uses encryption to

153
00:08:13.200 --> 00:08:16.400
 ensure that users credentials are

154
00:08:16.900 --> 00:08:19.100
Will transmitted over the network

155
00:08:19.100 --> 00:08:23.300
 and are only available to the intended recipient.

156
00:08:23.800 --> 00:08:27.000
This helps to prevent unorderized access

157
00:08:26.300 --> 00:08:29.600
 to the user's credentials and to

158
00:08:29.600 --> 00:08:32.900
 protect against various types of network based

159
00:08:32.900 --> 00:08:36.400
 attacks. So in here create SSP

160
00:08:35.400 --> 00:08:38.500
 allows to delegate the

161
00:08:38.500 --> 00:08:40.600
 user's credentials from the client.

162
00:08:41.600 --> 00:08:45.000
Is in here these packets this negotiate

163
00:08:44.600 --> 00:08:47.300
 packets are coming from the

164
00:08:47.300 --> 00:08:50.700
 client and credit SSP allows

165
00:08:50.700 --> 00:08:53.200
 to delegate the user's credentials from the

166
00:08:53.200 --> 00:08:56.900
 client side to the Target server for

167
00:08:56.900 --> 00:08:58.900
 remote or the indication.

168
00:08:59.800 --> 00:09:02.000
So keep in mind that this is

169
00:09:02.300 --> 00:09:05.700
 the key point of the organication the remote

170
00:09:05.700 --> 00:09:08.600
 identification and now let me show

171
00:09:08.600 --> 00:09:12.600
 you the ntlm SSP negotiate

172
00:09:11.600 --> 00:09:13.800
 packets details.

173
00:09:14.900 --> 00:09:17.600
So when we look at the details under the

174
00:09:17.600 --> 00:09:20.400
 transport layer security now, we can

175
00:09:20.400 --> 00:09:23.900
 see clearly the credential security support provider

176
00:09:23.900 --> 00:09:26.700
 details, but before the decryption of

177
00:09:26.700 --> 00:09:29.600
 the traffic, we couldn't see the create

178
00:09:29.600 --> 00:09:32.700
 SSP details because the credit

179
00:09:32.700 --> 00:09:36.200
 SSP data are encrypted by

180
00:09:35.200 --> 00:09:38.400
 the TLs protocol, but now

181
00:09:38.400 --> 00:09:41.700
 I have decrypted to traffic and I

182
00:09:41.700 --> 00:09:44.900
 Can See Clearly these information

183
00:09:44.900 --> 00:09:48.100
 under the transport layer

184
00:09:47.100 --> 00:09:50.900
 security. So when I expand the

185
00:09:50.900 --> 00:09:53.600
 all the fields we can

186
00:09:53.600 --> 00:09:56.900
 see some information under this

187
00:09:56.900 --> 00:09:57.100
 field.

188
00:09:57.900 --> 00:10:00.600
And let me explain one by

189
00:10:00.600 --> 00:10:00.700
 one.

190
00:10:01.300 --> 00:10:04.200
First the negotiate packet is

191
00:10:04.200 --> 00:10:07.700
 a packet user in the RDP to initiate the

192
00:10:07.700 --> 00:10:10.700
 process of authenticating a user it is

193
00:10:10.700 --> 00:10:13.800
 part of the ntlm and the

194
00:10:13.800 --> 00:10:16.700
 land managers and the local

195
00:10:16.700 --> 00:10:19.400
 local area network manager security

196
00:10:19.400 --> 00:10:22.900
 protocol and which is and which

197
00:10:22.900 --> 00:10:25.500
 is used for authentication in RDP. When

198
00:10:25.500 --> 00:10:28.200
 an RDP client established a connection to

199
00:10:28.200 --> 00:10:32.000
 an RDP server by this TLS and

200
00:10:31.700 --> 00:10:35.100
 Shake process the first packet

201
00:10:34.100 --> 00:10:38.300
 it stands is the anti-alamassa speed

202
00:10:38.300 --> 00:10:41.300
 negotiate packet. And in this situation, of

203
00:10:41.300 --> 00:10:45.400
 course the ntlm is the authentication method

204
00:10:45.400 --> 00:10:49.000
 which is which is used by the client and

205
00:10:48.400 --> 00:10:51.200
 it is the first packet sent from

206
00:10:51.200 --> 00:10:54.300
 the client to the server during the

207
00:10:54.300 --> 00:10:58.400
 ntlm authentication process and contains

208
00:10:57.400 --> 00:11:00.500
 the clients supported and

209
00:11:01.300 --> 00:11:04.500
authentication options with the

210
00:11:04.500 --> 00:11:07.900
 flex value we will investigate them soon

211
00:11:07.900 --> 00:11:08.500
 and

212
00:11:09.800 --> 00:11:12.500
The packet contains some several

213
00:11:12.500 --> 00:11:15.600
 fields in here. So let's start

214
00:11:15.600 --> 00:11:18.600
 with the negot token to explain.

215
00:11:19.400 --> 00:11:22.300
The negot token value is a binary

216
00:11:22.300 --> 00:11:25.600
 value in negotiate packet that represents

217
00:11:25.600 --> 00:11:28.600
 the clients and the alarm negotiation information

218
00:11:28.600 --> 00:11:32.500
 and it is an encoded as

219
00:11:32.500 --> 00:11:35.600
 you can see. It is an encoded representation

220
00:11:35.600 --> 00:11:38.800
 of the ntlm negotiation plagues and

221
00:11:38.800 --> 00:11:41.600
 other information such as the client's domain

222
00:11:41.600 --> 00:11:44.500
 name workstation name and version information.

223
00:11:45.500 --> 00:11:48.600
So the Negro token value is used by

224
00:11:48.600 --> 00:11:51.300
 the server to the determine the

225
00:11:51.300 --> 00:11:54.900
 clients and PLM authentication options.

226
00:11:54.900 --> 00:11:57.200
 And when we look

227
00:11:57.200 --> 00:12:00.600
 at the options value with the flex

228
00:12:00.600 --> 00:12:01.800
 value.

229
00:12:06.800 --> 00:12:07.000
so

230
00:12:07.900 --> 00:12:11.400
in here, we see some some Flex

231
00:12:10.400 --> 00:12:12.700
 value and

232
00:12:14.400 --> 00:12:15.300
scrolling down

233
00:12:17.600 --> 00:12:21.200
so you can see in here negotiate version is

234
00:12:20.200 --> 00:12:21.800
 set.

235
00:12:23.300 --> 00:12:26.400
Anti-session or we can

236
00:12:26.400 --> 00:12:29.700
 see the extended security is set. This

237
00:12:29.700 --> 00:12:32.500
 means that the client that the

238
00:12:32.500 --> 00:12:33.300
 client requires.

239
00:12:34.300 --> 00:12:38.100
And support the extended security option and

240
00:12:37.100 --> 00:12:41.200
 we can see another negotiate

241
00:12:40.200 --> 00:12:43.300
 always sign in here

242
00:12:43.300 --> 00:12:47.300
 and the negotiate always sign flag

243
00:12:46.300 --> 00:12:50.200
 indicates that the client

244
00:12:49.200 --> 00:12:52.600
 requires all messages to be signed.

245
00:12:53.900 --> 00:12:57.300
So then we can see some other

246
00:12:56.300 --> 00:12:59.900
 values in here the

247
00:12:59.900 --> 00:13:00.900
 negotiate sign.

248
00:13:01.600 --> 00:13:02.000
and

249
00:13:04.300 --> 00:13:07.300
the target type server we

250
00:13:07.300 --> 00:13:10.100
 can see in here the target type server.

251
00:13:14.100 --> 00:13:17.700
So the other one is negotiate ntlmt and

252
00:13:17.700 --> 00:13:19.700
 it is set as you can see.

253
00:13:21.300 --> 00:13:24.300
And this is indicating that the client requires the

254
00:13:24.300 --> 00:13:29.000
 use of land manager lmkts. So

255
00:13:28.800 --> 00:13:32.000
 this is indicating that the

256
00:13:31.400 --> 00:13:34.900
 client requires the use of land manager

257
00:13:34.900 --> 00:13:37.500
 keys and then we can

258
00:13:37.500 --> 00:13:39.800
 see some other information.

259
00:13:55.900 --> 00:13:58.500
So now let me explain the negotiate Flags

260
00:13:58.500 --> 00:14:02.000
 in here. And first one is negotiate flag

261
00:14:01.400 --> 00:14:04.700
 and is set because the client

262
00:14:04.700 --> 00:14:07.700
 wants to negotiate with the server and

263
00:14:07.700 --> 00:14:10.100
 key exchange also is set.

264
00:14:11.300 --> 00:14:14.400
Then we see the extended security is

265
00:14:14.400 --> 00:14:15.000
 set.

266
00:14:16.200 --> 00:14:19.800
And the negotiate always sign is set.

267
00:14:19.800 --> 00:14:22.800
 This flag is indicating that

268
00:14:22.800 --> 00:14:25.500
 the client requires all messages to

269
00:14:25.500 --> 00:14:26.300
 be signed.

270
00:14:27.100 --> 00:14:29.700
So then scrolling down.

271
00:14:30.800 --> 00:14:34.500
And we see in here negotiate ntlm

272
00:14:33.500 --> 00:14:36.800
 key is set and

273
00:14:36.800 --> 00:14:39.300
 this flag indicates that

274
00:14:39.300 --> 00:14:42.700
 the client supports ntlm or the

275
00:14:42.700 --> 00:14:43.000
 indication.

276
00:14:43.600 --> 00:14:47.000
So then we can see the negotiate

277
00:14:46.300 --> 00:14:49.400
 land manager key and this

278
00:14:49.400 --> 00:14:52.700
 flag is indicating that the client

279
00:14:52.700 --> 00:14:55.700
 requires the use of land manager Keys the

280
00:14:55.700 --> 00:14:58.800
 client requires the use of LM keys.

281
00:14:58.800 --> 00:15:01.000
 So then we are

282
00:15:01.400 --> 00:15:05.000
 scrolling down again and we have a in

283
00:15:04.100 --> 00:15:06.500
 here negotiate seal.

284
00:15:06.900 --> 00:15:09.400
So negotiate seal black is

285
00:15:09.400 --> 00:15:13.400
 also set in here and the this

286
00:15:12.400 --> 00:15:15.800
 flag indicates that the client requires

287
00:15:15.800 --> 00:15:17.500
 message encryption.

288
00:15:18.500 --> 00:15:19.400
So then

289
00:15:20.200 --> 00:15:24.000
and in here the request Target value is

290
00:15:23.200 --> 00:15:26.600
 set and this black indicates that

291
00:15:26.600 --> 00:15:29.300
 the client requires to server to

292
00:15:29.300 --> 00:15:33.100
 return the target name in the authentication process. So these

293
00:15:32.100 --> 00:15:35.500
 flags play an important role in the

294
00:15:35.500 --> 00:15:38.300
 determining the ntlm or the education

295
00:15:38.300 --> 00:15:42.300
 process such as the type of encryption and

296
00:15:41.300 --> 00:15:44.600
 signing to use the

297
00:15:44.600 --> 00:15:48.100
 target name and the type of the target. So

298
00:15:47.100 --> 00:15:50.900
 on and we see

299
00:15:50.900 --> 00:15:53.800
 another information as the

300
00:15:53.800 --> 00:15:55.900
 version field in here and

301
00:15:56.900 --> 00:15:59.900
the this field contains version

302
00:15:59.900 --> 00:16:02.600
 information about client that the

303
00:16:02.600 --> 00:16:05.500
 client supports which version of

304
00:16:05.500 --> 00:16:06.500
 the ntlm.

305
00:16:07.500 --> 00:16:10.700
So to sum up ntlm SSP negotiate

306
00:16:10.700 --> 00:16:13.500
 packet is the first packet user to identicate

307
00:16:13.500 --> 00:16:16.500
 the user and the server will reply

308
00:16:16.500 --> 00:16:19.800
 with an challenge packet which contains a

309
00:16:19.800 --> 00:16:23.200
 challenge that the client must respond to than the

310
00:16:22.200 --> 00:16:27.100
 client will send and authentication packet

311
00:16:26.100 --> 00:16:30.000
 which contains the response to the challenge

312
00:16:29.600 --> 00:16:32.800
 packet and the user's

313
00:16:32.800 --> 00:16:36.000
 credentials if the server accepts the

314
00:16:35.200 --> 00:16:38.500
 credentials the authentication process is

315
00:16:38.500 --> 00:16:41.500
 complete and the user will

316
00:16:41.500 --> 00:16:44.300
 be granted access to the server.

317
00:16:45.200 --> 00:16:48.700
So now let's look at the ntlm SSP

318
00:16:48.700 --> 00:16:51.700
 challenge packet as the second packet

319
00:16:51.700 --> 00:16:52.500
 in detail.

320
00:16:53.600 --> 00:16:56.400
Let me show you the details

321
00:16:56.400 --> 00:16:56.900
 in here.

322
00:16:58.300 --> 00:17:01.600
So in this field you can see some details

323
00:17:01.600 --> 00:17:04.600
 about the servers in

324
00:17:04.600 --> 00:17:05.900
 the challenge effect.

325
00:17:06.500 --> 00:17:10.000
So the target name is the first field

326
00:17:09.700 --> 00:17:12.600
 as you can see and the target

327
00:17:12.600 --> 00:17:15.200
 name contains the name of the

328
00:17:15.200 --> 00:17:18.200
 domain or server that the client is trying to

329
00:17:18.200 --> 00:17:18.900
 connect to.

330
00:17:21.100 --> 00:17:24.700
And then you can see the target info field in here.

331
00:17:24.700 --> 00:17:28.400
 You can see some detailed information

332
00:17:27.400 --> 00:17:31.000
 such as net buyers domain

333
00:17:30.100 --> 00:17:34.200
 name netbios computer name and DNS

334
00:17:33.200 --> 00:17:36.600
 domain name as well. DNS computer

335
00:17:36.600 --> 00:17:39.700
 name time step formations in here.

336
00:17:40.800 --> 00:17:44.000
And you can see some attribute

337
00:17:43.600 --> 00:17:46.700
 in here. So and the

338
00:17:46.700 --> 00:17:48.300
 version information also you can see

339
00:17:49.300 --> 00:17:52.400
so the target info contains additional

340
00:17:52.400 --> 00:17:55.800
 information about Target in

341
00:17:55.800 --> 00:17:58.200
 here such as the targets

342
00:17:58.200 --> 00:18:01.300
 DNS or net bios name and then

343
00:18:03.300 --> 00:18:06.900
you can see ntlm Server challenge

344
00:18:06.900 --> 00:18:09.200
 value in here. So this

345
00:18:09.200 --> 00:18:12.500
 field contains a random value a random

346
00:18:12.500 --> 00:18:15.100
 8 byte challenge value that

347
00:18:15.100 --> 00:18:18.700
 the client must use to prove its identity.

348
00:18:19.300 --> 00:18:22.100
and when I click on the

349
00:18:23.600 --> 00:18:26.000
show bytes as bits.

350
00:18:27.600 --> 00:18:28.800
and click on the

351
00:18:30.200 --> 00:18:34.100
And tlm server challenge, you can see the values

352
00:18:33.100 --> 00:18:36.800
 response to a bytes.

353
00:18:37.700 --> 00:18:38.200
on the

354
00:18:39.300 --> 00:18:39.900
packet

355
00:18:40.800 --> 00:18:42.300
bytes pain in here

356
00:18:43.200 --> 00:18:47.100
so here is as you can see we have

357
00:18:47.700 --> 00:18:51.600
8 bytes value corresponds to

358
00:18:50.600 --> 00:18:53.700
 the ntlm server challenge

359
00:18:53.700 --> 00:18:54.500
 value

360
00:18:55.100 --> 00:18:55.200
and

361
00:18:56.800 --> 00:18:58.000
we can close this.

362
00:18:59.000 --> 00:18:59.100
so

363
00:19:01.100 --> 00:19:04.800
we have seen some important information about the

364
00:19:04.800 --> 00:19:07.600
 target about the server such as

365
00:19:07.600 --> 00:19:08.500
 Target name.

366
00:19:09.300 --> 00:19:12.300
The DNS name in The Challenge

367
00:19:12.300 --> 00:19:15.800
 packet, which is sent by the server

368
00:19:15.800 --> 00:19:19.400
 and you can access the important information

369
00:19:18.400 --> 00:19:21.800
 about the server within this

370
00:19:21.800 --> 00:19:23.000
 challenge packet.

371
00:19:24.400 --> 00:19:27.500
Okay. Now let's look at the next packet.

372
00:19:29.200 --> 00:19:32.900
Which is sent by the client as antialam SSP

373
00:19:32.900 --> 00:19:35.600
 authentication pack and when we

374
00:19:35.600 --> 00:19:38.300
 click on the ntlm SSP authentication packet.

375
00:19:38.900 --> 00:19:41.500
We see some information about the

376
00:19:41.500 --> 00:19:42.100
 client.

377
00:19:43.100 --> 00:19:44.100
that when you click

378
00:19:46.200 --> 00:19:49.700
the details of the credential security support provider

379
00:19:49.700 --> 00:19:52.400
 when we expand it is

380
00:19:52.400 --> 00:19:56.100
 this is some detailed information about

381
00:19:55.100 --> 00:19:57.000
 the client.

382
00:19:58.600 --> 00:20:02.000
as response to the challenge packet

383
00:20:02.500 --> 00:20:05.700
Which is a signed by the server. So with

384
00:20:05.700 --> 00:20:08.400
 this authentication packet, the client

385
00:20:08.400 --> 00:20:11.500
 is responding to the server.

386
00:20:13.100 --> 00:20:16.000
and for the challenge, so when we look at the

387
00:20:16.600 --> 00:20:19.200
 details in authentication packet, you can

388
00:20:19.200 --> 00:20:23.000
 see some a land manager response and

389
00:20:24.100 --> 00:20:26.100
ntlm response value

390
00:20:27.800 --> 00:20:30.200
as you can see the response version.

391
00:20:31.300 --> 00:20:34.200
And net bios domain name you can see.

392
00:20:36.100 --> 00:20:40.000
Which is used by the server and

393
00:20:39.100 --> 00:20:42.200
 some Target name?

394
00:20:42.900 --> 00:20:43.900
value in here

395
00:20:45.300 --> 00:20:49.000
the term SRV with this IP

396
00:20:48.800 --> 00:20:52.000
 information with this IP address under

397
00:20:51.300 --> 00:20:54.300
 the ntlm secure service

398
00:20:54.300 --> 00:20:58.600
 providers field. You can see some important

399
00:20:57.600 --> 00:21:00.600
 information about the client

400
00:21:00.600 --> 00:21:03.500
 and the user you can find the domain

401
00:21:03.500 --> 00:21:04.600
 name of the client.

402
00:21:05.900 --> 00:21:07.800
in here Windows 7

403
00:21:09.100 --> 00:21:12.700
Is our domain name the domain name is Windows 7

404
00:21:12.700 --> 00:21:16.000
 and username is user so

405
00:21:15.400 --> 00:21:18.300
 we can find the username in

406
00:21:18.300 --> 00:21:21.200
 this field. And the host name

407
00:21:21.200 --> 00:21:24.800
 is in here as again when 7

408
00:21:24.800 --> 00:21:28.800
 so we can find some important

409
00:21:28.800 --> 00:21:31.800
 information about the client and user and

410
00:21:31.800 --> 00:21:34.600
 we can see the decision key in here.

411
00:21:35.900 --> 00:21:36.200
as

412
00:21:37.600 --> 00:21:40.900
included version encoded form

413
00:21:40.900 --> 00:21:43.300
 and negotiate Flags value

414
00:21:43.300 --> 00:21:46.400
 is in here again, and the version

415
00:21:46.400 --> 00:21:47.700
 the information.

416
00:21:48.800 --> 00:21:51.900
About the client and we can see the public

417
00:21:51.900 --> 00:21:54.800
 key for the authentication in

418
00:21:54.800 --> 00:21:55.800
 encoded for.

419
00:21:58.200 --> 00:22:02.400
So as a result after the authentication packet,

420
00:22:01.400 --> 00:22:04.900
 which is sent by the client the

421
00:22:04.900 --> 00:22:07.700
 server will validate the response and the

422
00:22:07.700 --> 00:22:10.700
 credentials and if they are valid the server

423
00:22:10.700 --> 00:22:13.600
 will send a message indicating that the order

424
00:22:13.600 --> 00:22:17.300
 indication process is successful. Otherwise, it

425
00:22:17.300 --> 00:22:21.000
 will deny the access so making analysis

426
00:22:20.200 --> 00:22:23.700
 by decrypting the RDP traffic may

427
00:22:23.700 --> 00:22:26.400
 provide lots of precious information on our

428
00:22:26.400 --> 00:22:29.600
 Network and you can learn which clients

429
00:22:29.600 --> 00:22:32.400
 are trying to connect to a specific server on

430
00:22:32.400 --> 00:22:36.400
 our Network and how many unsuccessful connection

431
00:22:35.400 --> 00:22:39.000
 attempts are there in the traffic

432
00:22:38.500 --> 00:22:41.300
 and which IP addresses are

433
00:22:41.300 --> 00:22:44.700
 trying to establish connection to the server.

434
00:22:45.700 --> 00:22:48.900
So, of course we can find answers to

435
00:22:48.900 --> 00:22:52.800
 many questions like this by decrypting

436
00:22:52.800 --> 00:22:55.300
 and analyzing RDP traffic.

437
00:22:59.200 --> 00:23:01.400
That's all for now. See you on the next video.
