WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.700 --> 00:00:10.100
In this video we'll cover. What is

1
00:00:10.100 --> 00:00:13.700
 the importance of network penetration testing and

2
00:00:13.700 --> 00:00:16.300
 the need for it plus you'll also

3
00:00:16.300 --> 00:00:19.500
 understand how it helps organizations to

4
00:00:19.500 --> 00:00:22.800
 improve their security posture while preventing

5
00:00:22.800 --> 00:00:25.500
 future cyber attacks answer some

6
00:00:25.500 --> 00:00:28.500
 compromising the assets. So let's dive on

7
00:00:28.500 --> 00:00:28.600
 in

8
00:00:29.900 --> 00:00:32.700
So what exactly is Network penetration

9
00:00:32.700 --> 00:00:35.500
 testing to put simply you have

10
00:00:35.500 --> 00:00:38.700
 various cyber Security Professionals within the industry such

11
00:00:38.700 --> 00:00:41.500
 as pantry contesters and ethical hackers

12
00:00:41.500 --> 00:00:44.700
 who uses similar techniques as straight

13
00:00:44.700 --> 00:00:47.300
 actors thread actors being the hackers or

14
00:00:47.300 --> 00:00:51.100
 the bad guys to simulate real sciotox

15
00:00:50.100 --> 00:00:53.400
 within an organization's Network

16
00:00:53.400 --> 00:00:56.900
 infrastructure with intention of discovering any

17
00:00:56.900 --> 00:01:00.500
 sort of hidden security vulnerabilities.

18
00:00:59.500 --> 00:01:03.700
 Remember security vulnerabilities

19
00:01:02.700 --> 00:01:06.000
 are simply security weaknesses

20
00:01:05.600 --> 00:01:08.900
 or flaws, which are found on

21
00:01:08.900 --> 00:01:11.500
 a system that can be exploited or

22
00:01:11.500 --> 00:01:14.400
 tea can advantage of by each doctor.

23
00:01:14.400 --> 00:01:17.900
 The objective of network pain testing

24
00:01:17.900 --> 00:01:21.200
 is to Simply find unresolve any

25
00:01:20.200 --> 00:01:24.300
 sort of security vulnerabilities before

26
00:01:23.300 --> 00:01:26.100
 a real hard case able to

27
00:01:26.100 --> 00:01:29.800
 compromise the sets of an organization, so,

28
00:01:29.900 --> 00:01:33.300
What exactly are these assets assets

29
00:01:32.300 --> 00:01:35.900
 are simply anything that has value

30
00:01:35.900 --> 00:01:38.500
 to an organization assets could

31
00:01:38.500 --> 00:01:41.800
 be tangible assets intangible assets

32
00:01:41.800 --> 00:01:44.200
 and also the employees which is people.

33
00:01:45.300 --> 00:01:48.700
Network penetration testing is simply common

34
00:01:48.700 --> 00:01:52.000
 security practice as it allows organizations

35
00:01:51.400 --> 00:01:54.600
 of any sizes whether it's

36
00:01:54.600 --> 00:01:57.200
 a large organization medium size or

37
00:01:57.200 --> 00:02:01.200
 even a large Enterprise. So these different

38
00:02:00.200 --> 00:02:03.400
 sizes of organizations are able

39
00:02:03.400 --> 00:02:06.800
 to do too many security posture as in

40
00:02:06.800 --> 00:02:09.800
 a current security posture of the network infrastructure

41
00:02:09.800 --> 00:02:12.600
 and also determine the

42
00:02:12.600 --> 00:02:15.900
 security risk of any sort of vulnerable tease

43
00:02:15.900 --> 00:02:19.400
 that will found within the organization. Imagine.

44
00:02:18.400 --> 00:02:21.500
 There are many companies are

45
00:02:21.500 --> 00:02:24.400
 many organizations that will create new

46
00:02:24.400 --> 00:02:27.400
 business process create new products create new

47
00:02:27.400 --> 00:02:30.400
 services or even try to reach new customers

48
00:02:30.400 --> 00:02:33.900
 Beyond borders by doing. So these organizations

49
00:02:33.900 --> 00:02:37.000
 will Implement new technologies such as

50
00:02:36.400 --> 00:02:39.700
 new computers new servers new

51
00:02:39.700 --> 00:02:43.400
 networking devices new security devices even

52
00:02:42.400 --> 00:02:44.900
 store data in different.

53
00:02:45.300 --> 00:02:48.600
cases, what are your storing on Prem on a

54
00:02:48.600 --> 00:02:51.200
 local server or storing data on

55
00:02:51.200 --> 00:02:54.700
 the cloud however by implementing new and additional

56
00:02:54.700 --> 00:02:55.400
 infrastructure

57
00:02:56.400 --> 00:02:59.200
Not much organizations May pay attention to

58
00:02:59.200 --> 00:03:02.600
 the security risks that comes with implementing these

59
00:03:02.600 --> 00:03:05.600
 new technologies. However, it doesn't

60
00:03:05.600 --> 00:03:08.200
 mean to see that implementing new technologies is

61
00:03:08.200 --> 00:03:11.500
 only method for creating new risk

62
00:03:11.500 --> 00:03:14.700
 with an analyzation. What about organizations that

63
00:03:14.700 --> 00:03:17.500
 has a lot of Legacy systems which are

64
00:03:17.500 --> 00:03:20.500
 still operating for instance. Imagine if

65
00:03:20.500 --> 00:03:23.700
 an organization has an outdated operating

66
00:03:23.700 --> 00:03:26.200
 system on a civil. Let's say the operating

67
00:03:26.200 --> 00:03:29.300
 system. It's let's say it's Windows silver

68
00:03:29.300 --> 00:03:32.800
 2003 and that operating system specifically

69
00:03:32.800 --> 00:03:35.800
 kept indoorization to whose

70
00:03:35.800 --> 00:03:39.200
 a custom built application. However, because

71
00:03:38.200 --> 00:03:41.600
 this operating system is legacy

72
00:03:41.600 --> 00:03:44.200
 and let's say it is end of

73
00:03:44.200 --> 00:03:47.800
 life. This means to see the vendor me not even support or

74
00:03:47.800 --> 00:03:50.400
 provide any sort of security update such

75
00:03:50.400 --> 00:03:53.600
 as security patches to this operating system that

76
00:03:53.600 --> 00:03:55.800
 means this operating system.

77
00:03:56.400 --> 00:03:59.800
It is a huge risk with an organization. So

78
00:03:59.800 --> 00:04:02.700
 with network penetration testing, it

79
00:04:02.700 --> 00:04:05.900
 allows a penetration tester on ethical

80
00:04:05.900 --> 00:04:08.900
 hacker to determine the security

81
00:04:08.900 --> 00:04:12.500
 posture of the organization and

82
00:04:11.500 --> 00:04:14.300
 identify the various types of

83
00:04:14.300 --> 00:04:17.700
 restart exists together with any sort of security

84
00:04:17.700 --> 00:04:20.200
 vulnerabilities and the impact

85
00:04:20.200 --> 00:04:23.300
 overall Network penetration, testing

86
00:04:23.300 --> 00:04:27.200
 helps companies to determint likelihood of

87
00:04:26.200 --> 00:04:30.100
 being compromised by a real threat

88
00:04:29.100 --> 00:04:31.300
 doctor such as a hacker.

89
00:04:31.900 --> 00:04:34.400
Together with improving the security

90
00:04:34.400 --> 00:04:37.000
 of all the assets within the company.

91
00:04:39.100 --> 00:04:43.100
So why exactly do we need Network penetration testing?

92
00:04:42.100 --> 00:04:46.100
 Why should we perform Network penetration

93
00:04:45.100 --> 00:04:48.700
 testing frequently some organizations

94
00:04:48.700 --> 00:04:52.300
 are required to meet various Regulatory Compliance

95
00:04:51.300 --> 00:04:54.800
 remix and standards within

96
00:04:54.800 --> 00:04:57.800
 the industry simply to ensure their systems

97
00:04:57.800 --> 00:05:00.400
 are their networks are secure enough

98
00:05:00.400 --> 00:05:03.500
 to transmit anyone store data

99
00:05:03.500 --> 00:05:06.700
 data being the most valuable asset

100
00:05:06.700 --> 00:05:09.700
 or the most valuable thing to anyone on

101
00:05:09.700 --> 00:05:12.800
 any organization in today's world as simple

102
00:05:12.800 --> 00:05:15.500
 example is Healthcare Providers are

103
00:05:15.500 --> 00:05:18.800
 required to be HIPAA compliant hippo being

104
00:05:18.800 --> 00:05:21.900
 the health insurance portability on accountability

105
00:05:21.900 --> 00:05:25.000
 act to put simply hippo focuses

106
00:05:24.300 --> 00:05:27.700
 on ensuring patience information

107
00:05:27.700 --> 00:05:30.700
 commonly known as protected health information

108
00:05:30.700 --> 00:05:33.700
 and this is the medical

109
00:05:33.700 --> 00:05:36.900
 records or medical data that could be used to

110
00:05:36.900 --> 00:05:38.900
 identify person. So hip

111
00:05:39.100 --> 00:05:42.500
Is designed to ensure that Healthcare Providers

112
00:05:42.500 --> 00:05:45.600
 systems Aryan networks are secure

113
00:05:45.600 --> 00:05:49.000
 the protect the Phi of their

114
00:05:48.900 --> 00:05:52.000
 customers such as a patients this

115
00:05:51.600 --> 00:05:54.700
 data if it is leaked anywhere, it

116
00:05:54.700 --> 00:05:57.200
 can actually compromise the patients.

117
00:05:58.700 --> 00:06:01.400
Additionally there are

118
00:06:01.400 --> 00:06:04.600
 many organizations that provide payment card services

119
00:06:04.600 --> 00:06:07.500
 and solutions and these

120
00:06:07.500 --> 00:06:11.300
 organizations are required to be PCI DSS

121
00:06:10.300 --> 00:06:13.700
 compliant. This means it's a

122
00:06:13.700 --> 00:06:16.900
 payment card industry Theta security standard. For

123
00:06:16.900 --> 00:06:19.100
 example, if you work with an

124
00:06:19.100 --> 00:06:22.700
 organization, let's say you look at a bank that is UCP man

125
00:06:22.700 --> 00:06:26.500
 card such as a credit card Visa master

126
00:06:26.500 --> 00:06:29.200
 or any sort of payment card. All of this

127
00:06:29.200 --> 00:06:32.300
 systems are performing a transaction between the

128
00:06:32.300 --> 00:06:35.900
 user such as own of the payment card on

129
00:06:35.900 --> 00:06:39.400
 a processing system needs to be pcis compliant

130
00:06:38.400 --> 00:06:41.800
 to ensure this data is

131
00:06:41.800 --> 00:06:45.600
 protected during the entire transaction. However, being

132
00:06:44.600 --> 00:06:47.800
 compliant whether it's PC

133
00:06:47.800 --> 00:06:51.200
 idss compliant or even hippo being compliant

134
00:06:50.200 --> 00:06:54.200
 does not provide a 100%

135
00:06:53.200 --> 00:06:56.800
 guarantee on any systems

136
00:06:56.800 --> 00:06:57.800
 or Networks.

137
00:06:58.600 --> 00:07:02.400
See that they are fully secured compliance simply ensures

138
00:07:01.400 --> 00:07:04.600
 a system or systems are

139
00:07:04.600 --> 00:07:07.600
 networks has met a baseline of

140
00:07:07.600 --> 00:07:10.800
 security features and controls to

141
00:07:10.800 --> 00:07:11.500
 protect data.

142
00:07:11.900 --> 00:07:14.700
However, it is best practice to

143
00:07:14.700 --> 00:07:17.700
 also Implement additional security features to

144
00:07:17.700 --> 00:07:20.700
 ensure data is always kept safe

145
00:07:20.700 --> 00:07:23.600
 and protected from the bad people such as

146
00:07:23.600 --> 00:07:25.500
 a thread actors the hackers.

147
00:07:29.600 --> 00:07:32.800
Network penetration testing helps many organizations

148
00:07:32.800 --> 00:07:35.800
 to find those hidden security weaknesses,

149
00:07:35.800 --> 00:07:38.900
 which are not always found during a

150
00:07:38.900 --> 00:07:41.800
 compliant audit or during a vulnerability

151
00:07:41.800 --> 00:07:42.500
 scanning tool.

152
00:07:43.800 --> 00:07:46.800
However, Network penetration testing also

153
00:07:46.800 --> 00:07:49.600
 helps organizations to efficiently discover

154
00:07:49.600 --> 00:07:52.200
 unresolved any sort of

155
00:07:52.200 --> 00:07:55.700
 security flaws while understanding the

156
00:07:55.700 --> 00:07:58.200
 mitigation uncounter measures that

157
00:07:58.200 --> 00:08:01.200
 are needed to prevent future cyber attacks.

158
00:08:01.200 --> 00:08:04.900
 So I performing frequent Network penetration,

159
00:08:04.900 --> 00:08:08.200
 testing organizations can determine their

160
00:08:07.200 --> 00:08:10.800
 current security posture then after

161
00:08:10.800 --> 00:08:14.400
 they Implement, let's see mitigation countermeasures

162
00:08:13.400 --> 00:08:16.900
 technique. They can even perform another

163
00:08:16.900 --> 00:08:20.300
 penetration testing after to determine

164
00:08:19.300 --> 00:08:22.400
 whether their systems actually become

165
00:08:22.400 --> 00:08:25.300
 more secure and whether they are

166
00:08:25.300 --> 00:08:28.600
 able to fill that gap of lack of security to

167
00:08:28.600 --> 00:08:29.200
 put simply

168
00:08:31.500 --> 00:08:34.600
Before we perform any sort of painstreusion testing

169
00:08:34.600 --> 00:08:37.700
 such as Network penetration testing. There are

170
00:08:37.700 --> 00:08:41.200
 various phases the first phase being pre-engagement.

171
00:08:40.200 --> 00:08:43.800
 Then there is information gathering

172
00:08:43.800 --> 00:08:47.100
 trapped modeling vulnerability analysis.

173
00:08:46.100 --> 00:08:50.200
 The exploitation fees pulse

174
00:08:49.200 --> 00:08:52.200
 exploitation fees. And of course

175
00:08:52.200 --> 00:08:54.100
 the report writing fees,

176
00:08:56.600 --> 00:08:58.600
during the pre-engagement is

177
00:08:59.800 --> 00:09:02.600
the following needs to be performed by

178
00:09:02.600 --> 00:09:05.500
 the provider the provider being the person

179
00:09:05.500 --> 00:09:08.100
 or the organization who is going

180
00:09:08.100 --> 00:09:11.100
 to perform the network penetration testing for the client.

181
00:09:11.900 --> 00:09:14.300
First and foremost during the

182
00:09:14.300 --> 00:09:17.200
 pre-engagement fees is really important that the legal

183
00:09:17.200 --> 00:09:20.800
 permission is obtained from the right authorities

184
00:09:20.800 --> 00:09:23.400
 before performing any sort

185
00:09:23.400 --> 00:09:26.600
 of patient testing activities to put

186
00:09:26.600 --> 00:09:30.100
 simply penetration testing uses almost or

187
00:09:29.100 --> 00:09:32.700
 the same techniques used

188
00:09:32.700 --> 00:09:36.100
 by hackers to actually compromise systems.

189
00:09:35.100 --> 00:09:38.400
 So to be on the safe side, it's

190
00:09:38.400 --> 00:09:42.000
 really important that a service provider and all

191
00:09:41.200 --> 00:09:44.700
 the penetration test of teen legal written

192
00:09:44.700 --> 00:09:47.600
 permission from the right authorities before

193
00:09:47.600 --> 00:09:51.500
 even performing any sort of penetration testing

194
00:09:51.500 --> 00:09:54.200
 ethical Hawking or even any sort of

195
00:09:54.200 --> 00:09:56.200
 scanning on the customers Network.

196
00:09:56.900 --> 00:09:59.700
Furthermore it's important to Define The

197
00:09:59.700 --> 00:10:03.000
 Rules of Engagement. This is a scoop the

198
00:10:02.400 --> 00:10:05.900
 scope will determine or the scoopal outline

199
00:10:05.900 --> 00:10:08.500
 the timeline for performing the

200
00:10:08.500 --> 00:10:11.200
 security testing when the test can actually

201
00:10:11.200 --> 00:10:15.000
 happen. What devices what systems what

202
00:10:14.900 --> 00:10:18.100
 IPS or even what networks can

203
00:10:17.100 --> 00:10:20.900
 be tested what type of data can

204
00:10:20.900 --> 00:10:23.400
 be collected are there any sort of

205
00:10:23.400 --> 00:10:26.800
 security concerns? Are there any third party concerns

206
00:10:26.800 --> 00:10:29.900
 and most importantly if anything

207
00:10:29.900 --> 00:10:32.500
 should go wrong who should a painter

208
00:10:32.500 --> 00:10:35.500
 you should test a contact such as let's say the IT

209
00:10:35.500 --> 00:10:38.800
 professional or perhaps the it coordinator within

210
00:10:38.800 --> 00:10:39.900
 a client's organization.

211
00:10:40.700 --> 00:10:43.200
So the Rules of Engagement or the scoop

212
00:10:43.200 --> 00:10:46.500
 is extremely important another important

213
00:10:46.500 --> 00:10:49.500
 documentation The Source provided needs to

214
00:10:49.500 --> 00:10:52.700
 have is a non-disclosure agreement

215
00:10:52.700 --> 00:10:55.700
 for the client this non-disclosure agreement

216
00:10:55.700 --> 00:10:58.800
 or the ND is simply an

217
00:10:58.800 --> 00:11:02.000
 official contractual agreement between the

218
00:11:01.300 --> 00:11:04.400
 customer honestly is provide on

219
00:11:04.400 --> 00:11:07.600
 penetration test. So that says any soda sensitive

220
00:11:07.600 --> 00:11:10.500
 confidential data that was found during the painteration

221
00:11:10.500 --> 00:11:13.500
 tests on the customers in that week. The paint

222
00:11:13.500 --> 00:11:16.200
 Trish interest provider will not disclose it

223
00:11:16.200 --> 00:11:19.800
 to any parties. So in other words, the customer

224
00:11:19.800 --> 00:11:23.000
 might be we can on some important technology that

225
00:11:22.100 --> 00:11:25.300
 is being new on the market

226
00:11:25.300 --> 00:11:29.400
 and this is intellectual property or perhaps there

227
00:11:28.400 --> 00:11:31.400
 is some Financial records that were

228
00:11:31.400 --> 00:11:31.600
 discovered.

229
00:11:32.600 --> 00:11:35.600
It's really important that you build a trust with the

230
00:11:35.600 --> 00:11:38.800
 customer and to do so in non-disclosure agreement

231
00:11:38.800 --> 00:11:40.500
 can help you with this.

232
00:11:42.900 --> 00:11:45.700
The information gathering fees. It's really

233
00:11:45.700 --> 00:11:48.900
 common amongst thread actors ethical

234
00:11:48.900 --> 00:11:51.600
 attackers penetration testers are even

235
00:11:51.600 --> 00:11:54.900
 security researchers to put simply this phase

236
00:11:54.900 --> 00:11:58.100
 is used to passively collect information about

237
00:11:57.100 --> 00:12:01.100
 the targets organization and their

238
00:12:00.100 --> 00:12:01.900
 Network infrastructure.

239
00:12:02.700 --> 00:12:05.700
So what passive information gathering this

240
00:12:05.700 --> 00:12:08.600
 is where the penetration tester will actually switch

241
00:12:08.600 --> 00:12:11.600
 through any sort of public records that

242
00:12:11.600 --> 00:12:14.600
 are available on the internet about the

243
00:12:14.600 --> 00:12:17.400
 target. For instance. If you if you

244
00:12:17.400 --> 00:12:20.200
 are a network penetration tester and you're given

245
00:12:20.200 --> 00:12:23.400
 a particular organization, then you will need to collect a

246
00:12:23.400 --> 00:12:26.700
 lot of data about organization to create a some

247
00:12:26.700 --> 00:12:29.200
 type of portfolio. Where would you search

248
00:12:29.200 --> 00:12:32.300
 for this information? Typically penetration classes

249
00:12:32.300 --> 00:12:35.600
 will switch through social media platforms such as

250
00:12:35.600 --> 00:12:38.700
 LinkedIn for any employees who may have

251
00:12:38.700 --> 00:12:41.100
 a week and that organization and let's

252
00:12:41.100 --> 00:12:44.700
 say you find an employee who works within your target organization. You

253
00:12:44.700 --> 00:12:47.800
 can check through the employees LinkedIn profile and

254
00:12:47.800 --> 00:12:50.300
 see what projects this person has worked

255
00:12:50.300 --> 00:12:53.300
 on while this person was employed within the

256
00:12:53.300 --> 00:12:54.200
 targets organization.

257
00:12:55.100 --> 00:12:58.700
Sometime employees may post a LinkedIn

258
00:12:58.700 --> 00:13:01.900
 articles or include projects and

259
00:13:01.900 --> 00:13:04.700
 specify internal technologies

260
00:13:04.700 --> 00:13:08.100
 that could actually give you an idea on what

261
00:13:07.100 --> 00:13:10.300
 type of devices and systems are

262
00:13:10.300 --> 00:13:13.200
 running within their well within the

263
00:13:13.200 --> 00:13:16.500
 targets internal Network. You can also check job boosting

264
00:13:16.500 --> 00:13:19.700
 websites. Typically when the human resource department

265
00:13:19.700 --> 00:13:22.500
 or a recruiter is posting an IT

266
00:13:22.500 --> 00:13:25.400
 job related vacancy. Sometimes they may

267
00:13:25.400 --> 00:13:28.700
 post their internal Technologies specifying. Hey

268
00:13:28.700 --> 00:13:31.300
 a potential candidates should

269
00:13:31.300 --> 00:13:33.700
 understand. Let's say particular operating system.

270
00:13:34.600 --> 00:13:37.500
What about web applications? So all

271
00:13:37.500 --> 00:13:40.400
 of this details could actually help you as a network

272
00:13:40.400 --> 00:13:43.600
 penetration tester to determine what type

273
00:13:43.600 --> 00:13:47.700
 of Technology systems devices and let's

274
00:13:46.700 --> 00:13:49.400
 say the skill sets

275
00:13:49.400 --> 00:13:52.700
 that are needed for their internal ID employees.

276
00:13:52.700 --> 00:13:55.500
 This information helps to build a

277
00:13:55.500 --> 00:13:55.800
 portfolio.

278
00:13:56.700 --> 00:13:57.600
without even

279
00:13:58.500 --> 00:14:02.000
compromising the organization you could simply search

280
00:14:01.400 --> 00:14:04.800
 online again on social

281
00:14:04.800 --> 00:14:07.800
 media platforms job posting websites even

282
00:14:07.800 --> 00:14:10.700
 online forums uneven the

283
00:14:10.700 --> 00:14:14.100
 Target's website for any sort of information that

284
00:14:13.100 --> 00:14:16.700
 reveals sensitive details

285
00:14:16.700 --> 00:14:19.600
 about internal and the external

286
00:14:19.600 --> 00:14:20.700
 network infrastructure.

287
00:14:21.700 --> 00:14:24.900
Another simple example is this imagine that

288
00:14:24.900 --> 00:14:28.200
 you're going through a job boosting website and you

289
00:14:27.200 --> 00:14:30.500
 saw that the company Pool City

290
00:14:30.500 --> 00:14:33.200
 vacancy for an IT professional and some

291
00:14:33.200 --> 00:14:36.700
 of the requirements are let's see Windows Server a particular

292
00:14:36.700 --> 00:14:40.300
 year or particular release water ball.

293
00:14:39.300 --> 00:14:42.000
 Let's say Deepu said

294
00:14:42.100 --> 00:14:45.900
 you need to know Lenox servers. What about some Cloud Technologies? Let's

295
00:14:45.900 --> 00:14:48.500
 say Azure AWS or even

296
00:14:48.500 --> 00:14:51.700
 another cloud provider. This gives you much more

297
00:14:51.700 --> 00:14:54.900
 details about hey, this organization is

298
00:14:54.900 --> 00:14:57.100
 storing data or storing the

299
00:14:57.100 --> 00:15:00.900
 editor in a particular clothes provider environment.

300
00:15:00.900 --> 00:15:04.500
 Plus they're using specific Technologies within

301
00:15:03.500 --> 00:15:06.900
 the internal Network. So overall

302
00:15:06.900 --> 00:15:10.100
 from our paintration Tessa perspective.

303
00:15:09.100 --> 00:15:12.800
 You already have some

304
00:15:12.800 --> 00:15:15.400
 knowledge about it, you know

305
00:15:15.400 --> 00:15:18.400
 next week components their devices and of

306
00:15:18.400 --> 00:15:20.400
 course overall the it infrastructure.

307
00:15:21.100 --> 00:15:24.300
Furthermore Patrician testers uses all

308
00:15:24.300 --> 00:15:27.200
 of this collected into Mission as mentioned to

309
00:15:27.200 --> 00:15:30.800
 create a profile about the Target that also help

310
00:15:30.800 --> 00:15:33.600
 you as a penetration testing later

311
00:15:33.600 --> 00:15:36.500
 phases of penetration testing. For example,

312
00:15:36.500 --> 00:15:40.100
 if you have a solid portfolio or

313
00:15:39.100 --> 00:15:42.800
 you able to create a solid portfolio about

314
00:15:42.800 --> 00:15:45.100
 the target organization, then you can

315
00:15:45.100 --> 00:15:48.800
 further develop exploits to take advantage

316
00:15:48.800 --> 00:15:52.200
 of known security weaknesses within devices

317
00:15:51.200 --> 00:15:54.800
 that are hosted or devices that

318
00:15:54.800 --> 00:15:56.700
 are running on the internal Network.

319
00:15:58.600 --> 00:16:01.500
Another fees is Shrek modeling with shred

320
00:16:01.500 --> 00:16:04.100
 modeling. It helps Security Professionals such as

321
00:16:04.100 --> 00:16:07.700
 penetration testers aren't even security researchers

322
00:16:07.700 --> 00:16:10.300
 to determine how tread actors are

323
00:16:10.300 --> 00:16:14.000
 able to compromise various security vulnerabilities on

324
00:16:13.700 --> 00:16:16.900
 systems and networks within many

325
00:16:16.900 --> 00:16:19.800
 large companies track modeling provides

326
00:16:19.800 --> 00:16:22.800
 insights on how organizations commonly

327
00:16:22.800 --> 00:16:25.300
 defend or become a

328
00:16:25.300 --> 00:16:27.200
 Defender against common threats.

329
00:16:27.700 --> 00:16:31.100
Hence, it is better to understand the account

330
00:16:30.100 --> 00:16:33.600
 measures as a penetration tester.

331
00:16:33.600 --> 00:16:36.300
 For example, if you're going to break

332
00:16:36.300 --> 00:16:40.200
 into a system, ethically or legally and

333
00:16:39.200 --> 00:16:42.600
 let's say you try a particular exploit but

334
00:16:42.600 --> 00:16:45.400
 exploit doesn't work. Well, perhaps the company

335
00:16:45.400 --> 00:16:48.700
 or the target has some type of car countermeasures

336
00:16:48.700 --> 00:16:51.800
 or even a mitigation implemented. It

337
00:16:51.800 --> 00:16:55.200
 might be a security control or perhaps

338
00:16:54.200 --> 00:16:58.100
 it might be a threat prevention

339
00:16:57.100 --> 00:16:58.600
 solution.

340
00:16:59.400 --> 00:17:03.100
However, if you use sharp modeling accurately, you

341
00:17:02.100 --> 00:17:05.800
 could determine how companies are secure

342
00:17:05.800 --> 00:17:08.900
 in their networks plus you can determine what

343
00:17:08.900 --> 00:17:12.000
 are some of the most common and popular techniques used

344
00:17:11.100 --> 00:17:14.500
 by real hackers out in

345
00:17:14.500 --> 00:17:14.900
 industry.

346
00:17:15.400 --> 00:17:18.400
Lastly penetration testers use a

347
00:17:18.400 --> 00:17:22.100
 strat modeling to understand types of security controls and

348
00:17:21.100 --> 00:17:24.700
 how these security controls can

349
00:17:24.700 --> 00:17:27.600
 simply be bypassed use and

350
00:17:27.600 --> 00:17:30.700
 threat emulation techniques, of course from a

351
00:17:30.700 --> 00:17:33.600
 network penetration tester perspectives. You must

352
00:17:33.600 --> 00:17:36.900
 do this, ethically on legally, hence.

353
00:17:36.900 --> 00:17:40.600
 It's really really important that you obtain legal

354
00:17:39.600 --> 00:17:42.500
 permission before even doing

355
00:17:42.500 --> 00:17:45.900
 any sort of security testing or assessment

356
00:17:45.900 --> 00:17:48.000
 on a client's Network.

357
00:17:49.100 --> 00:17:52.900
Next is the vulnerability assessment fees

358
00:17:52.900 --> 00:17:55.900
 or the vulnerability analysis fees

359
00:17:55.900 --> 00:17:58.400
 with vulnerable the analysis

360
00:17:58.400 --> 00:18:02.300
 it simply focuses on discovering security flaws

361
00:18:01.300 --> 00:18:05.100
 or weaknesses on systems which are

362
00:18:04.100 --> 00:18:07.300
 within the school of the network

363
00:18:07.300 --> 00:18:10.300
 penetration test. So therefore it's really important

364
00:18:10.300 --> 00:18:13.600
 that you stay within scoop. Do not go

365
00:18:13.600 --> 00:18:16.600
 outside of your scoop or else you may be

366
00:18:16.600 --> 00:18:18.300
 facing some legal trouble.

367
00:18:19.400 --> 00:18:22.700
For each vulnerability phone the network

368
00:18:22.700 --> 00:18:25.300
 penetration tester has to determine the

369
00:18:25.300 --> 00:18:28.300
 vulnerability severity reading and how this

370
00:18:28.300 --> 00:18:32.000
 security flow can be compromised plus how

371
00:18:31.500 --> 00:18:33.400
 it can be mitigated.

372
00:18:34.400 --> 00:18:37.600
This phase helps Network penetration tester to

373
00:18:37.600 --> 00:18:40.600
 determine the security vulnerabilities which

374
00:18:40.600 --> 00:18:43.400
 are easy to exploit and even gain

375
00:18:43.400 --> 00:18:46.600
 access to systems because when you're performing in

376
00:18:46.600 --> 00:18:49.300
 a penetration test to put simply

377
00:18:49.300 --> 00:18:53.500
 it's always easier to go for the low hanging

378
00:18:52.500 --> 00:18:55.400
 fruits. The low-hanging fruits

379
00:18:55.400 --> 00:18:58.900
 are the security flaws which are easy to compromise. I'll

380
00:18:58.900 --> 00:18:59.900
 gain access to a system.

381
00:19:00.700 --> 00:19:04.300
Furthermore vulnerability analysis and evils

382
00:19:03.300 --> 00:19:06.500
 the network penetration tester to provide

383
00:19:06.500 --> 00:19:09.700
 a detailed report to the client or

384
00:19:09.700 --> 00:19:12.900
 the customer outlining the security weaknesses that

385
00:19:12.900 --> 00:19:15.500
 were found on the solutions

386
00:19:15.500 --> 00:19:18.200
 on how these security flaws could

387
00:19:18.200 --> 00:19:18.800
 be resolved.

388
00:19:20.800 --> 00:19:24.600
Then this exploitation fees after performing

389
00:19:23.600 --> 00:19:26.400
 a vulnerable the analysis on

390
00:19:26.400 --> 00:19:29.200
 the network. The network penetration tester will

391
00:19:29.200 --> 00:19:32.700
 need to create or acquire exploits

392
00:19:32.700 --> 00:19:36.000
 that can take advantage of the security vulnerable

393
00:19:35.500 --> 00:19:38.900
 ties out of found on systems are networks

394
00:19:38.900 --> 00:19:41.700
 within the school of the pantry shuntest.

395
00:19:42.600 --> 00:19:45.300
The penetration tester can use various tools

396
00:19:45.300 --> 00:19:48.400
 such as Metasploit, which is simply an

397
00:19:48.400 --> 00:19:51.800
 exploit development framework to boot create

398
00:19:51.800 --> 00:19:54.900
 and launch exploits to Target systems within

399
00:19:54.900 --> 00:19:55.500
 the scope.

400
00:19:56.200 --> 00:19:59.300
The penetration tester can also acquire exploits from

401
00:19:59.300 --> 00:20:02.600
 various online sources. However, if you

402
00:20:02.600 --> 00:20:05.700
 are acquiring exploits from online sources,

403
00:20:05.700 --> 00:20:09.100
 you may need to further modify

404
00:20:08.100 --> 00:20:11.700
 these exploits and test them

405
00:20:11.700 --> 00:20:14.400
 properly before you launch it against the target system.

406
00:20:16.400 --> 00:20:20.800
After exploiting a system, what does traductors do

407
00:20:20.800 --> 00:20:24.000
 well, they suppose exploitation fees after

408
00:20:23.800 --> 00:20:27.000
 compromising system penetration testers.

409
00:20:26.500 --> 00:20:30.000
 Usually Implement persistence on

410
00:20:29.500 --> 00:20:32.600
 the victim's system or the compromis system

411
00:20:32.600 --> 00:20:35.400
 by implementing persistence. It simply

412
00:20:35.400 --> 00:20:38.900
 ensures the penetration tester can remotely access

413
00:20:38.900 --> 00:20:42.000
 these compromise devices whenever they

414
00:20:41.200 --> 00:20:43.900
 are online during the pantry and that's

415
00:20:44.500 --> 00:20:47.200
Think about every time you want to access

416
00:20:47.200 --> 00:20:50.500
 a system. You will need to launch and exploit over and

417
00:20:50.500 --> 00:20:53.600
 over again. What if you compromise the system and

418
00:20:53.600 --> 00:20:56.900
 you implement multiple back to access, hence, we

419
00:20:56.900 --> 00:21:00.200
 want to implement persistence. So therefore during

420
00:20:59.200 --> 00:21:02.600
 the timeline for penetration test, we

421
00:21:02.600 --> 00:21:05.200
 can simply remotely access the systems as

422
00:21:05.200 --> 00:21:07.000
 long as these systems are online.

423
00:21:08.200 --> 00:21:11.700
This technique is also commonly been used

424
00:21:11.700 --> 00:21:13.000
 by try doctors.

425
00:21:13.700 --> 00:21:16.600
Penetration testers however, uses similar techniques

426
00:21:16.600 --> 00:21:19.700
 to simulate real experiences to test

427
00:21:19.700 --> 00:21:23.100
 the client's security controls and

428
00:21:22.100 --> 00:21:26.400
 their Trad detection systems. Plus it

429
00:21:25.400 --> 00:21:28.500
 provides a good experience to determine

430
00:21:28.500 --> 00:21:31.600
 whether the client security team was able

431
00:21:31.600 --> 00:21:34.900
 to detect the penetration tester while the

432
00:21:34.900 --> 00:21:37.200
 real simulation is taking place.

433
00:21:38.300 --> 00:21:41.100
And last but not least there is a

434
00:21:41.100 --> 00:21:42.000
 report writing these.

435
00:21:42.900 --> 00:21:45.700
After any sort of technical security testing

436
00:21:45.700 --> 00:21:48.500
 the network penetration tester has to compile

437
00:21:48.500 --> 00:21:51.900
 in other words create a technical and an

438
00:21:51.900 --> 00:21:54.900
 executive report to the client the

439
00:21:54.900 --> 00:21:58.000
 technical report will contain all the technical details

440
00:21:57.400 --> 00:22:00.900
 about the security vulnerabilities that

441
00:22:00.900 --> 00:22:03.100
 were found and how they were found

442
00:22:03.100 --> 00:22:06.600
 what tools we use what techniques we use. They even

443
00:22:06.600 --> 00:22:09.800
 find these security weaknesses plus the technical

444
00:22:09.800 --> 00:22:11.300
 report will also contain

445
00:22:12.200 --> 00:22:15.200
What type of exploit and how they

446
00:22:15.200 --> 00:22:18.400
 exploiters use and the steps use to even

447
00:22:18.400 --> 00:22:22.300
 truly determine whether these are security weaknesses or

448
00:22:21.300 --> 00:22:22.600
 not?

449
00:22:23.400 --> 00:22:26.200
The executive report is a high level report of

450
00:22:26.200 --> 00:22:29.600
 the penetration tests. And that's actually designed

451
00:22:29.600 --> 00:22:32.200
 for the executive staff members who are

452
00:22:32.200 --> 00:22:36.100
 less concerned about technical details, but more focuses

453
00:22:35.100 --> 00:22:38.800
 on overall risk management of

454
00:22:38.800 --> 00:22:40.700
 the assets within the companies.

455
00:22:42.800 --> 00:22:46.100
During this video you have learned an understanding

456
00:22:45.100 --> 00:22:48.700
 importance of network penetration testing and

457
00:22:48.700 --> 00:22:51.500
 how it helps organizations to improve their security

458
00:22:51.500 --> 00:22:54.300
 posture. Furthermore. You have discovered the

459
00:22:54.300 --> 00:22:57.100
 various phases of penetration testing.

460
00:22:58.500 --> 00:23:01.200
In the next video, you will learn about a different

461
00:23:01.200 --> 00:23:04.300
 types of network penetration testing. I hope

462
00:23:04.300 --> 00:23:07.200
 this video has been informative for you and thank you

463
00:23:07.200 --> 00:23:07.600
 for viewing.
