WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.500 --> 00:00:10.200
Hello everyone in this video as the beginning

1
00:00:10.200 --> 00:00:13.900
 we will talk about how we perform NTA we will

2
00:00:13.900 --> 00:00:16.800
 learn the phases of NTA in detailed so

3
00:00:16.800 --> 00:00:20.000
 that we will take a closer. Look at the NTA. Let's

4
00:00:19.100 --> 00:00:20.400
 get started.

5
00:00:21.900 --> 00:00:24.600
How can we perform Network traffic analysis?

6
00:00:25.300 --> 00:00:28.200
There are several tools and techniques that can be used

7
00:00:28.200 --> 00:00:30.400
 to perform Network traffic analysis.

8
00:00:31.600 --> 00:00:33.100
See some common approaches now.

9
00:00:33.800 --> 00:00:36.900
First one pickets anything pack is

10
00:00:36.900 --> 00:00:39.800
 anything involves capturing and analyzing individual

11
00:00:39.800 --> 00:00:42.500
 packets of data as they travel

12
00:00:42.500 --> 00:00:45.200
 across Network take it something can be

13
00:00:45.200 --> 00:00:48.600
 done using specialized software or hardware tools

14
00:00:48.600 --> 00:00:51.500
 such as packet analyzers or sniffers.

15
00:00:52.300 --> 00:00:55.900
And the second one flow analysis low analysis

16
00:00:55.900 --> 00:00:58.400
 involves combining packets into logical

17
00:00:58.400 --> 00:01:01.400
 flows and analyzing patterns in

18
00:01:01.400 --> 00:01:04.600
 the data. This can be useful for understanding. How

19
00:01:04.600 --> 00:01:08.600
 data is moving across the network and identifying

20
00:01:07.600 --> 00:01:11.200
 Trends or anomalies and

21
00:01:10.200 --> 00:01:13.300
 third one protocol analysis.

22
00:01:13.900 --> 00:01:17.000
Protocol analysis involves investigating the

23
00:01:16.400 --> 00:01:19.700
 structure and content of packets

24
00:01:19.700 --> 00:01:22.400
 to understand how different Protocols are being

25
00:01:22.400 --> 00:01:25.900
 used on the network protocol analyzers are

26
00:01:25.900 --> 00:01:28.700
 specialized tools that can decode

27
00:01:28.700 --> 00:01:31.500
 and display the contents or packets in a human

28
00:01:31.500 --> 00:01:32.500
 readable format.

29
00:01:33.900 --> 00:01:36.300
And the fourth one network tabs and

30
00:01:36.300 --> 00:01:39.400
 probes Network tabs and probes are

31
00:01:39.400 --> 00:01:42.400
 Hardware devices that can be placed on a network

32
00:01:42.400 --> 00:01:44.600
 to capture and analyze traffic.

33
00:01:45.500 --> 00:01:48.400
And network tabs allow traffic to pass through

34
00:01:48.400 --> 00:01:52.000
 them and can be used to monitor life. Terrific while

35
00:01:51.700 --> 00:01:54.500
 probes can be inserted into a network to capture

36
00:01:54.500 --> 00:01:56.900
 traffic for offline analysis.

37
00:01:57.700 --> 00:02:01.400
And the fifth one network analyzers Network

38
00:02:00.400 --> 00:02:03.400
 analyzers are software tools

39
00:02:03.400 --> 00:02:06.600
 that can use it to capture and analyze Network

40
00:02:06.600 --> 00:02:09.800
 traffic these tools often have a graphical user

41
00:02:09.800 --> 00:02:12.700
 interface and can display traffic data

42
00:02:12.700 --> 00:02:15.500
 in a variety of formats such as

43
00:02:15.500 --> 00:02:17.800
 charts tables and graphs.

44
00:02:18.800 --> 00:02:21.500
Network traffic analysis is an important aspect

45
00:02:21.500 --> 00:02:24.300
 of network management and can be used to

46
00:02:24.300 --> 00:02:28.300
 ensure that a network is running efficiently and securely

47
00:02:29.500 --> 00:02:32.100
They have thought about the NTA phases on the last

48
00:02:32.100 --> 00:02:35.500
 video and we will talk about now NTA process.

49
00:02:36.900 --> 00:02:39.600
The process of network traffic analysis can

50
00:02:39.600 --> 00:02:42.700
 be described in detail as here. First one

51
00:02:42.700 --> 00:02:45.000
 determine the scope of the analysis.

52
00:02:45.800 --> 00:02:48.900
Identify the specific calls and objectives of

53
00:02:48.900 --> 00:02:51.800
 the analysis such as identifying security

54
00:02:51.800 --> 00:02:55.100
 threats optimizing Network performance or

55
00:02:54.100 --> 00:02:58.200
 troubleshooting issues and the

56
00:02:57.200 --> 00:02:59.700
 next step is collecting data.

57
00:03:00.700 --> 00:03:03.700
We will select the suitable data collection method

58
00:03:03.700 --> 00:03:06.500
 based on your goals and the resources available

59
00:03:06.500 --> 00:03:07.000
 to you.

60
00:03:07.800 --> 00:03:10.400
Options include packets anything log

61
00:03:10.400 --> 00:03:13.200
 analysis and network flow analysis.

62
00:03:14.100 --> 00:03:18.600
And the third step is analyze the data identifying patterns

63
00:03:17.600 --> 00:03:21.300
 Trends and enemies and

64
00:03:20.300 --> 00:03:24.200
 the next step is preparing data data

65
00:03:23.200 --> 00:03:26.700
 collection needs to be cleaned filtered and

66
00:03:26.700 --> 00:03:28.700
 formatted for analysis.

67
00:03:29.300 --> 00:03:32.600
In the last step, we will report and take an

68
00:03:32.600 --> 00:03:32.700
 action.

69
00:03:33.500 --> 00:03:36.400
They will present the results of the analysis and

70
00:03:36.400 --> 00:03:39.600
 take action based on the findings. Now, we

71
00:03:39.600 --> 00:03:41.400
 will learn the each step in depth.

72
00:03:42.800 --> 00:03:45.200
In the first step. We will determine the

73
00:03:45.200 --> 00:03:48.600
 scope of the analysis clearly Define the specific

74
00:03:48.600 --> 00:03:51.600
 calls and objectives of the analysis. This

75
00:03:51.600 --> 00:03:54.400
 may include identifying security threats and

76
00:03:54.400 --> 00:03:57.600
 optimizing Network performance and

77
00:03:57.600 --> 00:04:00.500
 then troubleshooting issues or

78
00:04:00.500 --> 00:04:03.900
 analyzing traffic patterns for business intelligence purposes

79
00:04:03.900 --> 00:04:06.700
 identify the specific Network segment

80
00:04:06.700 --> 00:04:09.600
 or device that will be analyzed. This

81
00:04:09.600 --> 00:04:12.800
 may be a specific router switch or server

82
00:04:12.800 --> 00:04:15.900
 or it may be a group of devices. You

83
00:04:15.900 --> 00:04:18.400
 may also want to consider analyzing traffic on

84
00:04:18.400 --> 00:04:21.900
 multiple devices or segments in order to get a

85
00:04:21.900 --> 00:04:23.900
 more comprehensive view of the network.

86
00:04:24.800 --> 00:04:27.200
Specify the time period that will be

87
00:04:27.200 --> 00:04:30.100
 covered by the analyzers. This may be a

88
00:04:30.100 --> 00:04:33.300
 specific day week or Mount or it may be

89
00:04:33.300 --> 00:04:37.000
 a longer period of time in order to identify Trends

90
00:04:36.200 --> 00:04:38.000
 and patterns.

91
00:04:38.700 --> 00:04:41.800
Considering constraints or limitations that

92
00:04:41.800 --> 00:04:45.300
 may impact the scope of the analysis. This

93
00:04:44.300 --> 00:04:46.900
 may include technical limitations.

94
00:04:47.700 --> 00:04:50.500
Such as the availability of data collections

95
00:04:50.500 --> 00:04:53.200
 tools and/or the capacity of

96
00:04:53.200 --> 00:04:57.200
 the network to handle additional traffic or organizing

97
00:04:56.200 --> 00:04:59.300
 or compliance considerations.

98
00:05:00.900 --> 00:05:03.600
In the collecting data setup, you will

99
00:05:03.600 --> 00:05:06.000
 select the suitable data collection method based on

100
00:05:06.100 --> 00:05:10.200
 your goals and resources available to you options include

101
00:05:09.200 --> 00:05:12.400
 packets anything log analysis and

102
00:05:12.400 --> 00:05:14.100
 network flow analysis.

103
00:05:14.600 --> 00:05:17.700
Each method has its own strengths and

104
00:05:17.700 --> 00:05:20.400
 limitations and the best approach

105
00:05:20.400 --> 00:05:23.500
 will depend on your specific needs and we

106
00:05:23.500 --> 00:05:27.100
 will set up the data collection process including putting together

107
00:05:26.100 --> 00:05:31.100
 the necessary tools and establishing protocols

108
00:05:30.100 --> 00:05:33.300
 for capturing and storing the

109
00:05:33.300 --> 00:05:36.800
 data and we will make sure to consider any

110
00:05:36.800 --> 00:05:39.900
 privacy or compliance concerns when

111
00:05:39.900 --> 00:05:42.100
 collecting data we will collect

112
00:05:42.100 --> 00:05:45.400
 the data over the specified time period we should

113
00:05:45.400 --> 00:05:48.400
 be sure to collect enough data to provide

114
00:05:48.400 --> 00:05:52.000
 representative sample of network traffic and

115
00:05:51.400 --> 00:05:54.400
 this may involve collecting data at

116
00:05:54.400 --> 00:05:58.100
 different times of the day or week or during

117
00:05:57.100 --> 00:06:00.500
 different seasons to account

118
00:06:00.500 --> 00:06:03.000
 for variations in terrific Peters.

119
00:06:04.400 --> 00:06:07.300
And step three we will prepare the data.

120
00:06:07.300 --> 00:06:11.200
 We will clean the data by removing any irrelevant

121
00:06:10.200 --> 00:06:12.800
 or duplicate records.

122
00:06:13.500 --> 00:06:16.800
This may involve filtering out traffic from specific

123
00:06:16.800 --> 00:06:20.000
 sources or destinations or removing

124
00:06:19.400 --> 00:06:22.200
 data that is not relevant to your

125
00:06:22.200 --> 00:06:25.900
 analysis. We'll through the data to include only

126
00:06:25.900 --> 00:06:28.900
 the specific types of traffic that

127
00:06:28.900 --> 00:06:32.200
 are relevant to your analysis. This may

128
00:06:31.200 --> 00:06:35.100
 involve selecting specific protocols and

129
00:06:34.100 --> 00:06:37.200
 or IP addresses

130
00:06:38.200 --> 00:06:41.600
and we will normalize the data if necessary for

131
00:06:41.600 --> 00:06:44.600
 example by converting data from different

132
00:06:44.600 --> 00:06:47.100
 sources into a consistent format.

133
00:06:48.100 --> 00:06:51.800
And this may have converting timestamps to

134
00:06:51.800 --> 00:06:54.600
 a common time zone or converting data

135
00:06:54.600 --> 00:06:57.300
 from different units into a standard

136
00:06:57.300 --> 00:06:58.000
 format.

137
00:06:58.600 --> 00:07:01.800
And we will format the data into a usable form

138
00:07:01.800 --> 00:07:05.300
 such as a spreadsheet or database.

139
00:07:06.700 --> 00:07:10.000
And the most important step is analyzing

140
00:07:09.500 --> 00:07:13.100
 the data use statistical analysis

141
00:07:12.100 --> 00:07:16.700
 machine learning or visualization tools

142
00:07:15.700 --> 00:07:18.800
 or to identify patterns

143
00:07:18.800 --> 00:07:20.300
 and Trends in the data.

144
00:07:21.200 --> 00:07:24.300
This may contain calculating metrics such as

145
00:07:24.300 --> 00:07:27.400
 average traffic volume. Terrific volume

146
00:07:27.400 --> 00:07:31.100
 over time old number of unique IP

147
00:07:30.100 --> 00:07:33.700
 addresses look for anomalies or

148
00:07:33.700 --> 00:07:37.100
 durations from normal traffic patterns, which

149
00:07:36.100 --> 00:07:39.700
 may indicate issues or security

150
00:07:39.700 --> 00:07:40.300
 threats.

151
00:07:41.300 --> 00:07:44.300
Now if you want to picture the analyzing step in

152
00:07:44.300 --> 00:07:48.300
 more detailed we can talk about these phases consider

153
00:07:47.300 --> 00:07:50.700
 the specific context of the network and

154
00:07:50.700 --> 00:07:53.800
 the goals of the analysis when identifying

155
00:07:53.800 --> 00:07:56.100
 anomalies, for example, if you are

156
00:07:56.100 --> 00:07:59.100
 analyzing traffic on a server, you may look

157
00:07:59.100 --> 00:08:02.600
 for patterns that indicate High resource usage or

158
00:08:02.600 --> 00:08:03.900
 unusual activity.

159
00:08:04.700 --> 00:08:07.600
If you are analyzing traffic on a router, you

160
00:08:07.600 --> 00:08:10.900
 may look for patterns that indicate congestion or

161
00:08:10.900 --> 00:08:12.100
 drop packets.

162
00:08:12.700 --> 00:08:15.900
For example, if you are trying to optimize Network

163
00:08:15.900 --> 00:08:19.100
 performance, you may make recommendations for

164
00:08:18.100 --> 00:08:21.500
 improving Network efficiency based

165
00:08:21.500 --> 00:08:24.600
 on the patterns and Trends you

166
00:08:24.600 --> 00:08:25.800
 identified in the data.

167
00:08:26.600 --> 00:08:29.700
If you are trying to identify security threats, you

168
00:08:29.700 --> 00:08:33.100
 may look for patterns that indicate malicious activity

169
00:08:32.100 --> 00:08:36.000
 and take suitable action

170
00:08:35.300 --> 00:08:37.900
 to respond to these threats.

171
00:08:38.600 --> 00:08:41.500
And consider the specific context of the network

172
00:08:41.500 --> 00:08:45.400
 and the goals of the analysis when interpreting

173
00:08:44.400 --> 00:08:47.600
 the data and in the

174
00:08:47.600 --> 00:08:50.700
 step 5, we will validate the results. We will

175
00:08:50.700 --> 00:08:53.800
 verify the accuracy and reliability of

176
00:08:53.800 --> 00:08:56.400
 the results by comparing them to other sources

177
00:08:56.400 --> 00:08:59.600
 of data or using other analysis techniques

178
00:08:59.600 --> 00:09:02.500
 and we will consider the limitations of

179
00:09:02.500 --> 00:09:05.900
 the analysis and the data that was collected and how

180
00:09:05.900 --> 00:09:08.800
 these limitations may have impacted the

181
00:09:08.800 --> 00:09:09.100
 results.

182
00:09:10.600 --> 00:09:13.700
And step 6 we will review the findings.

183
00:09:14.200 --> 00:09:18.100
We will reveal the results of the analysis and consider

184
00:09:17.100 --> 00:09:19.000
 their implications.

185
00:09:19.900 --> 00:09:22.200
They will determine what actions should be taken

186
00:09:22.200 --> 00:09:26.100
 based on the findings such as making recommendations for

187
00:09:25.100 --> 00:09:29.500
 improving Network performance identifying

188
00:09:28.500 --> 00:09:31.800
 and responding to secret threats

189
00:09:31.800 --> 00:09:34.600
 or terrible shooting issues in the

190
00:09:34.600 --> 00:09:37.400
 last step. We will prepare a report and take

191
00:09:37.400 --> 00:09:40.300
 action. We will document the findings of

192
00:09:40.300 --> 00:09:44.200
 the analysis in a clear and concise manner including

193
00:09:43.200 --> 00:09:47.000
 any recommendations for Action. We

194
00:09:46.300 --> 00:09:50.000
 will provide the documentation to relevant stakeholders

195
00:09:49.400 --> 00:09:52.300
 such as Network administrators or

196
00:09:52.300 --> 00:09:52.800
 management.

197
00:09:54.400 --> 00:09:57.900
Imagine that a company has recently experienced

198
00:09:57.900 --> 00:10:00.800
 a series of security breeds and the

199
00:10:00.800 --> 00:10:04.300
 IT department wants to use Network

200
00:10:03.300 --> 00:10:06.600
 traffic analysis for identify

201
00:10:06.600 --> 00:10:09.700
 the cause of the bridge and prevent feature attacks

202
00:10:09.700 --> 00:10:12.200
 to do this. They set up a

203
00:10:12.200 --> 00:10:15.600
 packet signer on their Network to capture and

204
00:10:15.600 --> 00:10:18.200
 analyze all traffic passing through

205
00:10:18.200 --> 00:10:22.000
 their Network the IT department Begins by

206
00:10:22.200 --> 00:10:26.200
 examining the packets to understand how different Protocols

207
00:10:25.200 --> 00:10:28.700
 are being used on the network. They

208
00:10:28.700 --> 00:10:31.100
 annotize that a large number of packets are

209
00:10:31.100 --> 00:10:34.600
 being sent using the FTP which means file

210
00:10:34.600 --> 00:10:37.400
 transfer protocol, which is used for

211
00:10:37.400 --> 00:10:41.600
 transferring files between devices further analysis

212
00:10:40.600 --> 00:10:43.300
 reveals that many of

213
00:10:43.300 --> 00:10:46.400
 these FTP packets are coming from

214
00:10:46.400 --> 00:10:49.600
 a single device on the network and the

215
00:10:49.600 --> 00:10:52.400
 fire is being transferred are large in size

216
00:10:52.400 --> 00:10:54.100
 and contain sensitive data.

217
00:10:54.400 --> 00:10:58.000
The IT department also uses flow

218
00:10:57.300 --> 00:11:00.000
 analysis to identify patterns in the

219
00:11:00.400 --> 00:11:03.800
 data denetize that there are several forms of

220
00:11:03.800 --> 00:11:06.700
 data between the suspicious device and

221
00:11:06.700 --> 00:11:09.900
 external servers which suggest that

222
00:11:09.900 --> 00:11:12.400
 the device may be sending data out of

223
00:11:12.400 --> 00:11:13.200
 the network.

224
00:11:14.100 --> 00:11:17.900
Based on this analysis. The IT department concludes that

225
00:11:17.900 --> 00:11:20.600
 the security Bridge are likely the

226
00:11:20.600 --> 00:11:22.400
 result of an Insider thread.

227
00:11:23.200 --> 00:11:27.000
And that the suspicious device is being used to exfiltrate

228
00:11:26.600 --> 00:11:28.500
 sensitive data from the network.

229
00:11:29.200 --> 00:11:32.800
They take steps to secure the device and Implement

230
00:11:32.800 --> 00:11:35.400
 additional security measures to prevent future

231
00:11:35.400 --> 00:11:36.200
 breaches.

232
00:11:36.900 --> 00:11:39.700
This is just one example of how Network traffic

233
00:11:39.700 --> 00:11:42.900
 analysis can be used to identify security threats

234
00:11:42.900 --> 00:11:45.600
 and prevent future attacks. In

235
00:11:45.600 --> 00:11:49.400
 this case. The IT department used a

236
00:11:48.400 --> 00:11:52.600
 combination of packets anything protocol analysis

237
00:11:51.600 --> 00:11:54.700
 and flow analysis to

238
00:11:54.700 --> 00:11:57.800
 identify patterns and Trends in

239
00:11:57.800 --> 00:12:00.500
 the data understand the behavior

240
00:12:00.500 --> 00:12:01.900
 of devices on the network.

241
00:12:03.700 --> 00:12:07.400
another scenario based on HTTP traffic

242
00:12:08.100 --> 00:12:11.700
imagine you are a network security Analyst at a

243
00:12:11.700 --> 00:12:14.200
 company and you are responsible for

244
00:12:14.200 --> 00:12:17.200
 monitoring the network traffic to ensure the

245
00:12:17.200 --> 00:12:20.500
 security of the company's systems one day

246
00:12:20.500 --> 00:12:24.000
 you're notice and unusual amount of HTTP

247
00:12:23.600 --> 00:12:27.100
 traffic coming from a particular IP

248
00:12:26.100 --> 00:12:29.800
 address that isn't known to belong

249
00:12:29.800 --> 00:12:32.300
 to any of the companies employees.

250
00:12:33.900 --> 00:12:36.500
Upon further investigation you discover that

251
00:12:36.500 --> 00:12:39.200
 the traffic is coming from a device that has

252
00:12:39.200 --> 00:12:42.300
 been infected with malware and is

253
00:12:42.300 --> 00:12:45.800
 now being used to perform a d-dose attack

254
00:12:45.800 --> 00:12:49.200
 on the company's website to diminish

255
00:12:48.200 --> 00:12:51.800
 their attack. You can use a variety of

256
00:12:51.800 --> 00:12:54.200
 tools and techniques to analyze the

257
00:12:54.200 --> 00:12:57.700
 HTTP traffic and identify the

258
00:12:57.700 --> 00:13:00.700
 source of the attack this might involve

259
00:13:00.700 --> 00:13:03.200
 investigating the heaters and the content of

260
00:13:03.200 --> 00:13:04.800
 the HTTP requests.

261
00:13:05.500 --> 00:13:08.700
Analyzing the patterns of the terrific and using

262
00:13:08.700 --> 00:13:11.500
 other network forensic techniques to

263
00:13:11.500 --> 00:13:13.700
 trace the traffic back to its source.

264
00:13:14.400 --> 00:13:17.500
After identifying the source of the attack and

265
00:13:17.500 --> 00:13:20.300
 securing the infected device you can take

266
00:13:20.300 --> 00:13:23.500
 additional steps to prevent similar attacks in

267
00:13:23.500 --> 00:13:27.300
 the feature. This might include implementing measures

268
00:13:26.300 --> 00:13:30.200
 such as rate limiting filtering

269
00:13:29.200 --> 00:13:32.300
 traffic based on IP address

270
00:13:32.300 --> 00:13:35.500
 or other characteristics or deploying

271
00:13:35.500 --> 00:13:38.600
 firewalls or other security measures

272
00:13:38.600 --> 00:13:41.700
 to block malicious traffic. You can

273
00:13:41.700 --> 00:13:44.300
 also use the information you gather during your

274
00:13:44.300 --> 00:13:47.900
 analysis to report the attack to relevant authorities

275
00:13:47.900 --> 00:13:50.600
 such as low enforcement or

276
00:13:50.600 --> 00:13:53.800
 cyber security organizations this can

277
00:13:53.800 --> 00:13:56.500
 help to identify and prosecure the

278
00:13:56.500 --> 00:14:00.200
 individuals or groups responsible for that attack and

279
00:13:59.200 --> 00:14:02.300
 can also serve as a warning to

280
00:14:02.300 --> 00:14:05.300
 others who might be considering similar types of

281
00:14:05.300 --> 00:14:06.000
 attacks.

282
00:14:06.800 --> 00:14:09.400
Finally you can use the lessons learned

283
00:14:09.400 --> 00:14:12.800
 from this incident to improve the company's overall

284
00:14:12.800 --> 00:14:15.900
 security position by proactively addressing

285
00:14:15.900 --> 00:14:18.700
 security threats and continually improving the

286
00:14:18.700 --> 00:14:21.400
 company's defenses. You can help to protect

287
00:14:21.400 --> 00:14:24.700
 the company systems and data from feature attacks.

288
00:14:26.700 --> 00:14:29.800
That's all for now. We will discuss about the OSI and

289
00:14:29.800 --> 00:14:32.800
 tcp/ip models in the next lesson. So

290
00:14:32.800 --> 00:14:34.300
 see you on the next video.
