WEBVTT

1
00:00:00.120 --> 00:00:03.240
<v Speaker 1>Welcome to the deep dive. Today. We're going behind the

2
00:00:03.279 --> 00:00:07.320
<v Speaker 1>scenes of a tool that's practically legendary in cybersecurity circles.

3
00:00:07.400 --> 00:00:08.839
<v Speaker 2>Legendary is a good word for it.

4
00:00:09.000 --> 00:00:12.480
<v Speaker 1>End Map. Think of this deep dive as a crash

5
00:00:12.560 --> 00:00:17.120
<v Speaker 1>course in network reconnaissance. Ooh, I like that. Think Sherlock

6
00:00:17.160 --> 00:00:19.160
<v Speaker 1>Holmes meets the digital age.

7
00:00:19.480 --> 00:00:22.879
<v Speaker 2>It's a great comparison for this deep dive. We're using

8
00:00:22.920 --> 00:00:24.800
<v Speaker 2>the book en Map Network Standing.

9
00:00:24.960 --> 00:00:25.280
<v Speaker 1>Okay.

10
00:00:25.480 --> 00:00:28.640
<v Speaker 2>It's packed with details on how end map works, what

11
00:00:28.800 --> 00:00:33.000
<v Speaker 2>makes it so powerful and why everyone from security pros

12
00:00:33.039 --> 00:00:36.600
<v Speaker 2>to well, let's just say less than ethical hackers find

13
00:00:36.600 --> 00:00:37.399
<v Speaker 2>it so useful.

14
00:00:37.560 --> 00:00:40.840
<v Speaker 1>Okay, let's unpact this. Okay, when we say network reconnaissance, yeah,

15
00:00:40.840 --> 00:00:42.439
<v Speaker 1>what are we actually talking about here? Can take me

16
00:00:42.479 --> 00:00:42.880
<v Speaker 1>a picture?

17
00:00:42.960 --> 00:00:46.200
<v Speaker 2>Okay. So imagine you're a detective stepping onto a crime scene.

18
00:00:46.240 --> 00:00:46.399
<v Speaker 1>Right.

19
00:00:46.759 --> 00:00:49.079
<v Speaker 2>The first thing you do is take stock of the surroundings.

20
00:00:49.119 --> 00:00:52.079
<v Speaker 2>Who's there, what's out of place. That's essentially what network

21
00:00:52.119 --> 00:00:54.799
<v Speaker 2>reconnaissance is in the digital world, okay, and it's where

22
00:00:54.920 --> 00:00:57.399
<v Speaker 2>end map comes in. Good. End map lets you discover

23
00:00:57.479 --> 00:01:00.560
<v Speaker 2>devices on a network, see which doors are open we

24
00:01:00.640 --> 00:01:03.640
<v Speaker 2>call these ports, and even get clues about the operating

25
00:01:03.679 --> 00:01:05.959
<v Speaker 2>system and services running on those devices.

26
00:01:06.040 --> 00:01:08.239
<v Speaker 1>So it's like en map is giving us X ray

27
00:01:08.319 --> 00:01:10.599
<v Speaker 1>vision into a network. It is, can you give us

28
00:01:10.640 --> 00:01:12.879
<v Speaker 1>a concrete example of how this plays out in the

29
00:01:12.879 --> 00:01:13.439
<v Speaker 1>real world.

30
00:01:13.599 --> 00:01:17.519
<v Speaker 2>Absolutely. Let's say you're a security consultant brought into test

31
00:01:17.599 --> 00:01:20.680
<v Speaker 2>a company's defenses. Okay, you could use end map to

32
00:01:20.680 --> 00:01:23.519
<v Speaker 2>perform a pink scan. Okay, It's like sending out a

33
00:01:23.519 --> 00:01:26.599
<v Speaker 2>digital bat signal to see which devices answer back.

34
00:01:26.719 --> 00:01:29.000
<v Speaker 1>Right, So we're mapping out the network, finding out what's

35
00:01:29.000 --> 00:01:31.400
<v Speaker 1>out there. What else can we do with end map

36
00:01:31.439 --> 00:01:32.239
<v Speaker 1>to dig deeper?

37
00:01:32.840 --> 00:01:36.079
<v Speaker 2>So enmap can identify potential weak points?

38
00:01:36.200 --> 00:01:36.519
<v Speaker 1>Okay?

39
00:01:36.719 --> 00:01:39.120
<v Speaker 2>For instance, it can tell you if a server is

40
00:01:39.200 --> 00:01:41.719
<v Speaker 2>running an outdated version of a service, which is like

41
00:01:41.879 --> 00:01:45.239
<v Speaker 2>leaving the back door unlocked for hackers. Right. This information

42
00:01:45.359 --> 00:01:48.760
<v Speaker 2>is pure gold for security professionals because it lets them

43
00:01:48.840 --> 00:01:52.519
<v Speaker 2>fix vulnerabilities before someone with bad intentions finds them.

44
00:01:52.840 --> 00:01:54.879
<v Speaker 1>It's like end map is handing us a treasure map,

45
00:01:55.200 --> 00:01:58.280
<v Speaker 1>but instead of marking X for buried treasure, it's pointing

46
00:01:58.319 --> 00:02:01.040
<v Speaker 1>out all the security gaps exactly.

47
00:02:01.200 --> 00:02:03.280
<v Speaker 2>And that's what makes end map so valuable for both

48
00:02:03.319 --> 00:02:06.480
<v Speaker 2>the good guys and the bad guys. Security teams use

49
00:02:06.519 --> 00:02:09.599
<v Speaker 2>it to keep things safe, while attackers use it to

50
00:02:10.159 --> 00:02:11.199
<v Speaker 2>well do the opposite.

51
00:02:11.319 --> 00:02:13.960
<v Speaker 1>Let's talk about the different ways end map can be used. Okay,

52
00:02:14.080 --> 00:02:17.520
<v Speaker 1>the book mentioned something called syn scan. Yes, what's that

53
00:02:17.599 --> 00:02:18.039
<v Speaker 1>all about.

54
00:02:18.639 --> 00:02:22.000
<v Speaker 2>S yn scan is like trying to discreetly check if

55
00:02:22.039 --> 00:02:24.240
<v Speaker 2>a high security server has any open doors.

56
00:02:24.520 --> 00:02:24.800
<v Speaker 1>Okay.

57
00:02:25.039 --> 00:02:27.560
<v Speaker 2>Instead of going through the whole process of making a connection,

58
00:02:27.639 --> 00:02:30.479
<v Speaker 2>which could raise alarms, you just send a quick signal

59
00:02:30.479 --> 00:02:33.639
<v Speaker 2>to see if anyone's listening. If they respond, you know

60
00:02:33.680 --> 00:02:36.319
<v Speaker 2>the doors open, but you slip away before anyone can

61
00:02:36.360 --> 00:02:37.319
<v Speaker 2>fully identify you.

62
00:02:38.000 --> 00:02:41.159
<v Speaker 1>So it's all about being stealthy and avoiding detection.

63
00:02:41.400 --> 00:02:42.759
<v Speaker 2>Stealthy is the name of the game.

64
00:02:42.919 --> 00:02:46.439
<v Speaker 1>The book also talks about TCP ack packets for this

65
00:02:46.560 --> 00:02:48.599
<v Speaker 1>kind of stealth mission. What's the deal with those?

66
00:02:49.159 --> 00:02:52.520
<v Speaker 2>Imagine sending a confirmation message for a conversation that hasn't

67
00:02:52.520 --> 00:02:56.800
<v Speaker 2>even started. Okay, that's a TCP ack packet. It's like

68
00:02:56.840 --> 00:02:58.840
<v Speaker 2>slipping a note under the door to see if someone

69
00:02:58.879 --> 00:03:03.080
<v Speaker 2>picks it up. Some firewalls might let this unusual message

70
00:03:03.120 --> 00:03:06.560
<v Speaker 2>through because it looks harmless, but we can analyze the

71
00:03:06.599 --> 00:03:10.439
<v Speaker 2>response to see if someone's home and potentially even if

72
00:03:10.479 --> 00:03:13.000
<v Speaker 2>they are trying to hide behind a security system.

73
00:03:13.199 --> 00:03:16.800
<v Speaker 1>Wow, so we're uncovering hidden devices and even peeking behind

74
00:03:16.840 --> 00:03:19.800
<v Speaker 1>digital curtains. A good thing that good guys use end

75
00:03:19.840 --> 00:03:20.919
<v Speaker 1>map precisely.

76
00:03:21.360 --> 00:03:25.960
<v Speaker 2>But with great power comes great responsibility. That's why the

77
00:03:26.000 --> 00:03:30.800
<v Speaker 2>book emphasizes ethical hacking. Scanning networks without permission can land

78
00:03:30.840 --> 00:03:35.159
<v Speaker 2>you in hot water. Legally and ethically, ethical hacking is key,

79
00:03:35.319 --> 00:03:38.639
<v Speaker 2>very key with the digital detectives, not the burglars exactly.

80
00:03:38.879 --> 00:03:42.319
<v Speaker 1>Speaking of wish, let's dive deeper into port scanning, the

81
00:03:42.439 --> 00:03:45.240
<v Speaker 1>art of checking those digital doors. Okay, what are some

82
00:03:45.360 --> 00:03:48.080
<v Speaker 1>techniques en map uses to map out what's running on

83
00:03:48.120 --> 00:03:48.759
<v Speaker 1>a network.

84
00:03:49.080 --> 00:03:51.599
<v Speaker 2>One of the most popular techniques is the s yn scan,

85
00:03:51.680 --> 00:03:54.639
<v Speaker 2>which we talked about earlier. It's stealthy because it doesn't

86
00:03:54.639 --> 00:03:57.400
<v Speaker 2>fully complete a connection. Think of it like knocking on

87
00:03:57.439 --> 00:03:59.560
<v Speaker 2>a door and running away before anyone can answer or

88
00:03:59.560 --> 00:04:01.360
<v Speaker 2>sever a classic.

89
00:04:01.080 --> 00:04:04.120
<v Speaker 1>But what if the system is like a fortress configured

90
00:04:04.120 --> 00:04:07.120
<v Speaker 1>to block those initial knocks. Yeah, or we need more

91
00:04:07.159 --> 00:04:08.599
<v Speaker 1>than a quick peak behind the door.

92
00:04:08.919 --> 00:04:11.400
<v Speaker 2>End map has options for that too. Okay, there's the

93
00:04:11.759 --> 00:04:14.840
<v Speaker 2>TCP connect scam, which is like walking right up to

94
00:04:14.879 --> 00:04:17.480
<v Speaker 2>the door and ringing the bell. Okay, it completes the connection,

95
00:04:17.639 --> 00:04:21.040
<v Speaker 2>so it's more reliable but also more noticeable. And then

96
00:04:21.079 --> 00:04:24.079
<v Speaker 2>there's the UDP scan, which is like sending a letter.

97
00:04:24.319 --> 00:04:27.360
<v Speaker 2>It's used for specific types of services and can be

98
00:04:27.480 --> 00:04:29.879
<v Speaker 2>useful for getting a different view of what's going on.

99
00:04:30.360 --> 00:04:34.439
<v Speaker 1>This is amazing. It's incredible how much we can learn.

100
00:04:34.959 --> 00:04:39.000
<v Speaker 1>With just a few well placed digital knocks.

101
00:04:38.720 --> 00:04:40.199
<v Speaker 2>Or letters, you can learn a lot.

102
00:04:40.360 --> 00:04:42.959
<v Speaker 1>It really shows how complex network security can be.

103
00:04:43.240 --> 00:04:43.839
<v Speaker 2>It really does.

104
00:04:43.959 --> 00:04:44.399
<v Speaker 1>Yeah.

105
00:04:44.600 --> 00:04:46.879
<v Speaker 2>Yeah, what seems like a simple scan can tell you

106
00:04:46.959 --> 00:04:49.480
<v Speaker 2>a lot about how a system is configured and if

107
00:04:49.480 --> 00:04:52.879
<v Speaker 2>there are any potential weaknesses. This is where end map's

108
00:04:52.879 --> 00:04:56.639
<v Speaker 2>ability to detect specific software versions comes in handy.

109
00:04:56.879 --> 00:04:59.800
<v Speaker 1>It's like being able to tell the make, model, and

110
00:05:00.079 --> 00:05:02.600
<v Speaker 1>even the year of a car just by looking at.

111
00:05:02.439 --> 00:05:06.759
<v Speaker 2>Its headlights exactly. Outdated software versions are often riddled with

112
00:05:06.800 --> 00:05:09.720
<v Speaker 2>security flaws, and hackers love to exploit them.

113
00:05:10.000 --> 00:05:10.800
<v Speaker 1>Of course, en.

114
00:05:10.759 --> 00:05:12.879
<v Speaker 2>Map helps us spot these issues so they can be

115
00:05:12.920 --> 00:05:14.720
<v Speaker 2>fixed before any damage is done.

116
00:05:14.839 --> 00:05:17.600
<v Speaker 1>It's like having a digital security audit right at your fingertips.

117
00:05:17.680 --> 00:05:20.360
<v Speaker 1>It really is, yep, and I bet this level of

118
00:05:20.439 --> 00:05:24.600
<v Speaker 1>detail means NMAP can help us pinpoint specific devices to right.

119
00:05:24.920 --> 00:05:28.800
<v Speaker 2>Absolutely. One interesting example from the book is how enmap

120
00:05:28.839 --> 00:05:32.160
<v Speaker 2>can be used to find those rogue Wi Fi networks

121
00:05:32.199 --> 00:05:34.480
<v Speaker 2>that employees sometimes set up.

122
00:05:34.759 --> 00:05:34.959
<v Speaker 1>Right.

123
00:05:35.040 --> 00:05:37.439
<v Speaker 2>You see, they might not realize the security risks.

124
00:05:37.720 --> 00:05:37.920
<v Speaker 1>Right.

125
00:05:38.000 --> 00:05:40.720
<v Speaker 2>It's like leaving a side door unlocked to your entire

126
00:05:40.759 --> 00:05:41.560
<v Speaker 2>office building.

127
00:05:41.759 --> 00:05:45.120
<v Speaker 1>So NMAP is like our security guard sniffing out potential

128
00:05:45.160 --> 00:05:46.959
<v Speaker 1>problems before they become major breaches.

129
00:05:47.120 --> 00:05:50.560
<v Speaker 2>Exactly. And it gets even more impressive. Endmap can even

130
00:05:50.639 --> 00:05:55.399
<v Speaker 2>fingerprint operating system, which is like leaving digital fingerprints at

131
00:05:55.399 --> 00:05:56.079
<v Speaker 2>a crime scene.

132
00:05:56.120 --> 00:05:58.720
<v Speaker 1>Right, Like leaving digital fingerprints at a crime scene, Yeah,

133
00:05:58.759 --> 00:05:59.360
<v Speaker 1>tell me more.

134
00:05:59.480 --> 00:06:03.199
<v Speaker 2>So MAP analyzes the subtle ways a system responds to

135
00:06:03.240 --> 00:06:07.199
<v Speaker 2>certain requests. It's all about the timing, the specific options.

136
00:06:07.319 --> 00:06:10.439
<v Speaker 2>Use things like that, right. These variations are like digital

137
00:06:10.519 --> 00:06:14.079
<v Speaker 2>fingerprints that can reveal the operating system running on the device.

138
00:06:14.360 --> 00:06:17.839
<v Speaker 1>So it's like analyzing someone's handwriting to determine their personality,

139
00:06:18.439 --> 00:06:21.600
<v Speaker 1>except in this case, we're figuring out the personality the operating.

140
00:06:21.240 --> 00:06:25.000
<v Speaker 2>System precisely, and just like handwriting analysis, this helps us

141
00:06:25.000 --> 00:06:28.839
<v Speaker 2>identify systems that might be trying to hide their true identity. Wow,

142
00:06:29.079 --> 00:06:30.800
<v Speaker 2>end map can see through those disguises.

143
00:06:31.120 --> 00:06:34.360
<v Speaker 1>That's both impressive and a little unnerving. It is pretty cool,

144
00:06:34.360 --> 00:06:37.199
<v Speaker 1>and map seems to have an answer for everything? What's next?

145
00:06:37.560 --> 00:06:40.160
<v Speaker 2>Well, have you ever wished you could customize your digital

146
00:06:40.160 --> 00:06:42.040
<v Speaker 2>toolkit with specialized gadgets?

147
00:06:42.199 --> 00:06:42.399
<v Speaker 1>Oh?

148
00:06:42.480 --> 00:06:46.120
<v Speaker 2>Yeah, that's where end Map's secret weapon comes into play. Okay,

149
00:06:46.480 --> 00:06:49.199
<v Speaker 2>the en Map Scripting Engine or NSE for sure.

150
00:06:49.399 --> 00:06:53.480
<v Speaker 1>NSE it rings a bell, but I need a refresher. Yeah,

151
00:06:53.519 --> 00:06:56.800
<v Speaker 1>what exactly is so special about this scripting engine?

152
00:06:57.000 --> 00:06:59.759
<v Speaker 2>The NSC lets you write and share custom scripts that

153
00:06:59.800 --> 00:07:03.160
<v Speaker 2>all sorts of new tricks to n maps repertoire. Okay,

154
00:07:03.439 --> 00:07:07.160
<v Speaker 2>want to automate a complex network scan? NSC can do that.

155
00:07:07.480 --> 00:07:11.160
<v Speaker 2>Want to test for specific vulnerabilities? NC can do that too?

156
00:07:11.360 --> 00:07:11.920
<v Speaker 1>Incredible.

157
00:07:12.040 --> 00:07:15.199
<v Speaker 2>It's like having a team of expert coders at your disposal,

158
00:07:15.480 --> 00:07:18.360
<v Speaker 2>ready to build custom tools for any hacking scenario.

159
00:07:18.639 --> 00:07:22.240
<v Speaker 1>Now that's what I call next level hacking. Yeah, but

160
00:07:22.319 --> 00:07:24.920
<v Speaker 1>writing codes sounds a bit intimidating.

161
00:07:24.399 --> 00:07:24.879
<v Speaker 2>It can be.

162
00:07:25.000 --> 00:07:27.519
<v Speaker 1>Yeah, is NSE only for seasoned hackers?

163
00:07:27.680 --> 00:07:30.680
<v Speaker 2>Not at all? Okay, While writing your own scripts requires

164
00:07:30.759 --> 00:07:34.240
<v Speaker 2>some coding knowledge, right, there's a huge community of users

165
00:07:34.319 --> 00:07:36.800
<v Speaker 2>who share their pre written scripts for free.

166
00:07:37.000 --> 00:07:37.519
<v Speaker 1>Oh wow.

167
00:07:37.639 --> 00:07:40.000
<v Speaker 2>You can find scripts for just about anything on sites

168
00:07:40.040 --> 00:07:42.920
<v Speaker 2>like the n MAP Scripting Engine database and get hub.

169
00:07:43.040 --> 00:07:46.199
<v Speaker 1>That's a relief. So even if we're not coding gurus,

170
00:07:46.199 --> 00:07:49.279
<v Speaker 1>we can still tap into the power of NSESE Exactly.

171
00:07:49.360 --> 00:07:52.040
<v Speaker 2>It's like having access to a vast library of pre

172
00:07:52.079 --> 00:07:55.279
<v Speaker 2>written code snippets ready to be plugged in and used

173
00:07:55.319 --> 00:07:57.279
<v Speaker 2>to supercharge your n MAP scans.

174
00:07:57.279 --> 00:07:57.800
<v Speaker 1>Wow.

175
00:07:58.079 --> 00:08:00.680
<v Speaker 2>The book even provides clear examples of how to use

176
00:08:00.720 --> 00:08:03.199
<v Speaker 2>these scripts, making it easy for anyone to get started.

177
00:08:03.279 --> 00:08:05.839
<v Speaker 1>That's reassuring. So we don't need to be coding ninjas

178
00:08:05.879 --> 00:08:07.000
<v Speaker 1>to harness the power of NSE.

179
00:08:07.240 --> 00:08:07.800
<v Speaker 2>Yeah, you don't.

180
00:08:07.920 --> 00:08:11.920
<v Speaker 1>This is all incredibly interesting. We've gone from the basics

181
00:08:11.959 --> 00:08:15.000
<v Speaker 1>of host discovery all the way to advanced techniques like

182
00:08:15.240 --> 00:08:17.800
<v Speaker 1>OS fingerprinting and NSE scripting.

183
00:08:18.000 --> 00:08:18.920
<v Speaker 2>We've covered a lot.

184
00:08:19.040 --> 00:08:21.439
<v Speaker 1>It really highlights en Map's versatility.

185
00:08:21.560 --> 00:08:22.000
<v Speaker 2>It does.

186
00:08:22.199 --> 00:08:25.040
<v Speaker 1>It's an incredibly powerful tool with a wide range of

187
00:08:25.040 --> 00:08:27.759
<v Speaker 1>applications in the world of cybersecurity.

188
00:08:27.879 --> 00:08:29.160
<v Speaker 2>Absolutely, it makes you.

189
00:08:29.160 --> 00:08:32.720
<v Speaker 1>Wonder what does the future hold for tools like en

190
00:08:32.840 --> 00:08:37.600
<v Speaker 1>map and the ongoing battle between hackers and security professionals.

191
00:08:37.759 --> 00:08:40.519
<v Speaker 2>It's a constant game of cat and mouse, with both

192
00:08:40.559 --> 00:08:44.600
<v Speaker 2>sides continually upping their game. What's certain is that n

193
00:08:44.679 --> 00:08:47.320
<v Speaker 2>MAP and tools like it will continue to play a

194
00:08:47.399 --> 00:08:50.759
<v Speaker 2>vital role in shaping the future of cybersecurity. Sure, but

195
00:08:50.840 --> 00:08:53.759
<v Speaker 2>before we get too far ahead of ourselves, right, we

196
00:08:53.799 --> 00:08:56.360
<v Speaker 2>need to talk about the ethical considerations that come with

197
00:08:56.399 --> 00:08:58.679
<v Speaker 2>this kind of power. Absolutely, After all, it's a thin

198
00:08:58.759 --> 00:09:01.879
<v Speaker 2>line between using n map for good and well, not

199
00:09:01.960 --> 00:09:02.320
<v Speaker 2>so good.

200
00:09:02.360 --> 00:09:05.440
<v Speaker 1>Right, you're absolutely right. Yeah, let's switch gears and delve

201
00:09:05.480 --> 00:09:08.639
<v Speaker 1>into the ethical considerations of wielding a tool as powerful

202
00:09:08.679 --> 00:09:11.600
<v Speaker 1>as nd map. Okay, ready to explore that side of things.

203
00:09:11.879 --> 00:09:16.279
<v Speaker 2>Absolutely, Understanding the ethical implications is just as important as

204
00:09:16.360 --> 00:09:20.000
<v Speaker 2>understanding the technical ones. Right, let's dive in. You know,

205
00:09:20.039 --> 00:09:23.080
<v Speaker 2>it's like the difference between a skilled locksmith who can

206
00:09:23.120 --> 00:09:26.080
<v Speaker 2>pick any lock and someone using those skills to break

207
00:09:26.120 --> 00:09:30.159
<v Speaker 2>into houses. And Map's power comes with a responsibility to

208
00:09:30.240 --> 00:09:32.039
<v Speaker 2>use it ethically and legally.

209
00:09:32.240 --> 00:09:34.919
<v Speaker 1>Exactly. So, let's say you're a security pro using en

210
00:09:35.039 --> 00:09:38.919
<v Speaker 1>map for a legitimate purpose, like a security audit. What

211
00:09:39.000 --> 00:09:41.039
<v Speaker 1>are some of the ethical guidelines you'd follow?

212
00:09:41.120 --> 00:09:45.879
<v Speaker 2>First and foremost, you need explicit permission from the network

213
00:09:45.919 --> 00:09:49.519
<v Speaker 2>owner before you even think about running a scan. Oh no,

214
00:09:49.639 --> 00:09:52.080
<v Speaker 2>ifs ands or butts about it. It's like having a

215
00:09:52.159 --> 00:09:56.519
<v Speaker 2>warrant before searching someone's property. You need that legal and

216
00:09:56.559 --> 00:09:57.440
<v Speaker 2>ethical clearance.

217
00:09:58.320 --> 00:10:02.159
<v Speaker 1>Makes sense? Yeah, so no drive scanning just because you're curious. No,

218
00:10:02.320 --> 00:10:03.600
<v Speaker 1>what else do we need to keep in mind?

219
00:10:03.759 --> 00:10:06.440
<v Speaker 2>You need to be mindful of the scope of your permission.

220
00:10:06.919 --> 00:10:10.480
<v Speaker 2>If you're authorized to scan for vulnerabilities in a web application,

221
00:10:10.879 --> 00:10:13.480
<v Speaker 2>that doesn't give you free rein to start snooping around

222
00:10:13.480 --> 00:10:16.759
<v Speaker 2>their financial database. Stay within the boundaries.

223
00:10:16.840 --> 00:10:20.200
<v Speaker 1>It's like being given a backstage pass to a concert, exact,

224
00:10:20.320 --> 00:10:22.480
<v Speaker 1>you can just wander into the band's stressing.

225
00:10:22.200 --> 00:10:25.919
<v Speaker 2>Room exactly, And just as importantly, you need to be

226
00:10:26.039 --> 00:10:30.000
<v Speaker 2>aware of the potential impact of your scans. Okay, Bombarding

227
00:10:30.000 --> 00:10:32.759
<v Speaker 2>a network with too many requests at once can slow

228
00:10:32.840 --> 00:10:35.879
<v Speaker 2>things down for everyone, like clogging up a highway during

229
00:10:35.919 --> 00:10:36.440
<v Speaker 2>rush hour.

230
00:10:36.960 --> 00:10:38.519
<v Speaker 1>So no digital traffic jams.

231
00:10:38.519 --> 00:10:39.879
<v Speaker 2>No digital traffic jams.

232
00:10:40.559 --> 00:10:41.720
<v Speaker 1>What can we do to prevent that?

233
00:10:41.879 --> 00:10:44.639
<v Speaker 2>And map has options for that. You can adjust the

234
00:10:44.679 --> 00:10:48.240
<v Speaker 2>speed and frequency of its probes to avoid overloading systems.

235
00:10:48.480 --> 00:10:48.799
<v Speaker 1>Okay.

236
00:10:48.960 --> 00:10:52.960
<v Speaker 2>It's all about being a considerate digital citizen. And of course,

237
00:10:53.000 --> 00:10:56.960
<v Speaker 2>when you find vulnerabilities, you report them responsibly through the

238
00:10:56.960 --> 00:11:00.600
<v Speaker 2>proper channels, giving the organization time to fix them before

239
00:11:00.639 --> 00:11:01.960
<v Speaker 2>publicly disclosing them.

240
00:11:02.360 --> 00:11:05.840
<v Speaker 1>So it's not just about finding the flaws, it's about

241
00:11:06.000 --> 00:11:09.279
<v Speaker 1>giving organizations a chance to fix them quietly and safely.

242
00:11:09.639 --> 00:11:13.679
<v Speaker 2>Exactly. Ethical hacking is about making the digital world safer,

243
00:11:14.159 --> 00:11:17.759
<v Speaker 2>not about public shaming or causing unnecessary harm.

244
00:11:18.080 --> 00:11:21.279
<v Speaker 1>Makes sense, Yeah, but let's face it, not everyone out

245
00:11:21.279 --> 00:11:23.919
<v Speaker 1>there using end map is playing by the rules.

246
00:11:23.759 --> 00:11:24.440
<v Speaker 2>Unfortunately not.

247
00:11:24.600 --> 00:11:27.039
<v Speaker 1>What are some of the ways that hackers with less

248
00:11:27.080 --> 00:11:30.840
<v Speaker 1>than noble intentions might misuse this tool?

249
00:11:31.799 --> 00:11:34.200
<v Speaker 2>Sadly, endmap can be used for a whole range of

250
00:11:34.240 --> 00:11:37.720
<v Speaker 2>malicious activities. Right, Hackers might use it to scan for

251
00:11:38.200 --> 00:11:42.200
<v Speaker 2>vulnerable systems to exploit, launch denial of service attacks that

252
00:11:42.240 --> 00:11:45.399
<v Speaker 2>cripple websites, or even steal sensitive data.

253
00:11:45.559 --> 00:11:48.240
<v Speaker 1>Okay, that's the dark side of endmap. Yeah, it sounds

254
00:11:48.240 --> 00:11:50.159
<v Speaker 1>like this tool can be a real double edged sword.

255
00:11:50.399 --> 00:11:53.639
<v Speaker 2>It definitely can be. Yeah, but remember knowledge is power.

256
00:11:54.080 --> 00:11:57.320
<v Speaker 2>The more we understand about how hackers can misuse these tools,

257
00:11:57.840 --> 00:11:59.799
<v Speaker 2>the better we can defend against those attacks.

258
00:12:00.600 --> 00:12:02.279
<v Speaker 1>So how can we make sure that we're staying on

259
00:12:02.279 --> 00:12:03.559
<v Speaker 1>the right side of that line?

260
00:12:03.679 --> 00:12:03.960
<v Speaker 2>Well?

261
00:12:04.039 --> 00:12:06.879
<v Speaker 1>Are there any resources or communities where people can learn

262
00:12:06.919 --> 00:12:10.840
<v Speaker 1>more about ethical hacking and responsible in map usage?

263
00:12:10.919 --> 00:12:14.840
<v Speaker 2>Absolutely, there are tons of great resources available online and

264
00:12:14.919 --> 00:12:19.759
<v Speaker 2>in person. Websites like SANDS Institute, Offensive Security and NIST

265
00:12:20.279 --> 00:12:25.200
<v Speaker 2>have excellent resources on ethical hacking and penetration testing methodologies.

266
00:12:25.279 --> 00:12:28.600
<v Speaker 1>What about communities. Are there groups where ethical hackers can

267
00:12:28.639 --> 00:12:31.360
<v Speaker 1>connect with each other and stay updated on best practices?

268
00:12:31.480 --> 00:12:36.159
<v Speaker 2>Definitely okay. Organizations like o WASP, Open Web Application Security

269
00:12:36.159 --> 00:12:43.440
<v Speaker 2>Project and ISA Information System Security Association host conferences, workshops,

270
00:12:43.480 --> 00:12:47.279
<v Speaker 2>and online forums where security professionals can exchange knowledge and

271
00:12:47.320 --> 00:12:51.679
<v Speaker 2>best practices. There's even Defcon, one of the longest running

272
00:12:51.720 --> 00:12:55.360
<v Speaker 2>and largest hacker conventions globally. It's a great place to

273
00:12:55.399 --> 00:12:58.679
<v Speaker 2>learn about the latest security trends and meet like minded individuals.

274
00:12:58.759 --> 00:13:02.279
<v Speaker 1>It sounds like the cybersecurity community is pretty active and collaborative.

275
00:13:02.440 --> 00:13:05.440
<v Speaker 2>It really is. We're all in this together, trying to

276
00:13:05.480 --> 00:13:07.759
<v Speaker 2>make the digital world a safer place.

277
00:13:08.559 --> 00:13:11.200
<v Speaker 1>Well said, Now, I don't want to dwell on the

278
00:13:11.279 --> 00:13:14.559
<v Speaker 1>dark side too much, but before we move on, I

279
00:13:14.600 --> 00:13:17.399
<v Speaker 1>have to ask if someone suspects they're on the receiving

280
00:13:17.480 --> 00:13:20.559
<v Speaker 1>end of a malicious end map scan, what should they do.

281
00:13:20.879 --> 00:13:23.720
<v Speaker 2>That's a great question. Yeah, it's important to remember that

282
00:13:23.879 --> 00:13:26.879
<v Speaker 2>simply detecting an end map scan doesn't automatically mean you're

283
00:13:26.919 --> 00:13:27.480
<v Speaker 2>under attack.

284
00:13:27.759 --> 00:13:28.080
<v Speaker 1>Okay.

285
00:13:28.120 --> 00:13:31.559
<v Speaker 2>Security researchers and even automated systems use en map for

286
00:13:31.639 --> 00:13:33.279
<v Speaker 2>legitimate purposes all the time.

287
00:13:33.679 --> 00:13:35.919
<v Speaker 1>So how do you tell the difference between a harmless

288
00:13:35.919 --> 00:13:39.159
<v Speaker 1>scan and something more nefarious? That's a good question.

289
00:13:39.399 --> 00:13:43.279
<v Speaker 2>Yeah, look for red flags like repeated scans from the

290
00:13:43.320 --> 00:13:48.440
<v Speaker 2>same source, scans targeting unusual ports, right, or attempts to

291
00:13:48.480 --> 00:13:52.440
<v Speaker 2>exploit known vulnerabilities. Okay, if you see any of these,

292
00:13:52.600 --> 00:13:55.000
<v Speaker 2>that's when you need to dig deeper and potentially involve

293
00:13:55.080 --> 00:13:57.399
<v Speaker 2>your security team or incident response plan.

294
00:13:57.759 --> 00:13:59.879
<v Speaker 1>It's a bit like hearing a knock on your door, right,

295
00:14:00.039 --> 00:14:02.720
<v Speaker 1>You don't automatically assume it's a burglar. You might check

296
00:14:02.759 --> 00:14:05.720
<v Speaker 1>the peepole or ask who is it before you panic exactly.

297
00:14:06.080 --> 00:14:10.799
<v Speaker 2>Don't overreact, but do stay vigilant and follow your security protocols.

298
00:14:11.240 --> 00:14:14.600
<v Speaker 1>Solid advice. Now, let's shift gears a bit and talk

299
00:14:14.639 --> 00:14:18.039
<v Speaker 1>more about end maps technical capabilities. We touched on timing

300
00:14:18.080 --> 00:14:21.279
<v Speaker 1>templates earlier, those presets that control the speed of scams.

301
00:14:21.759 --> 00:14:24.519
<v Speaker 1>But I'm curious about how else end map can adapt

302
00:14:25.240 --> 00:14:28.559
<v Speaker 1>to different network conditions and security measures. Yeah. It's not

303
00:14:28.559 --> 00:14:29.919
<v Speaker 1>a one size fits all tool.

304
00:14:29.759 --> 00:14:34.000
<v Speaker 2>Right, absolutely not. End map is surprisingly versatile. One area

305
00:14:34.039 --> 00:14:36.879
<v Speaker 2>where it shines is in its ability to slip past

306
00:14:37.000 --> 00:14:41.080
<v Speaker 2>firewalls and intrusion detection. Systems. Okay, think of it like this.

307
00:14:41.840 --> 00:14:45.240
<v Speaker 2>Firewalls are like the walls of a castle, right, and

308
00:14:45.279 --> 00:14:48.639
<v Speaker 2>intrusion detection systems are the guards patrolling.

309
00:14:48.200 --> 00:14:50.720
<v Speaker 1>Those walls, and end map is like a master spy

310
00:14:50.919 --> 00:14:52.320
<v Speaker 1>sneaking past those defenses.

311
00:14:52.480 --> 00:14:57.000
<v Speaker 2>Exactly. Hackers and ethical hackers like us are constantly finding

312
00:14:57.039 --> 00:15:01.000
<v Speaker 2>new ways to bypass security measures. Provides the tools to

313
00:15:01.120 --> 00:15:03.000
<v Speaker 2>test and improve those defenses.

314
00:15:03.240 --> 00:15:06.720
<v Speaker 1>Okay, I'm hooked. Tell me more about these spy tactics

315
00:15:06.759 --> 00:15:09.480
<v Speaker 1>that enmac uses to slip past security systems.

316
00:15:09.600 --> 00:15:13.080
<v Speaker 2>Okay, So, one technique is called fragmentation, which involves breaking

317
00:15:13.159 --> 00:15:17.759
<v Speaker 2>up those digital packets of information into smaller pieces. Imagine

318
00:15:17.919 --> 00:15:21.000
<v Speaker 2>trying to sneak a large message past a guard by

319
00:15:21.000 --> 00:15:23.759
<v Speaker 2>dividing it into tiny pieces of paper and sending them

320
00:15:23.759 --> 00:15:24.879
<v Speaker 2>through different channels.

321
00:15:25.120 --> 00:15:28.440
<v Speaker 1>That's sneaky, so you're making it harder for the guards,

322
00:15:29.159 --> 00:15:32.639
<v Speaker 1>the firewalls, and intrusion detection systems to detect.

323
00:15:32.320 --> 00:15:35.440
<v Speaker 2>What's going on precisely. Firewalls are designed to look for

324
00:15:35.480 --> 00:15:39.559
<v Speaker 2>specific patterns or signatures, but when you fragment packets, they

325
00:15:39.600 --> 00:15:41.480
<v Speaker 2>might not be able to put all the pieces together.

326
00:15:41.600 --> 00:15:44.200
<v Speaker 2>It's like sending a puzzle that's missing a few pieces

327
00:15:44.679 --> 00:15:45.919
<v Speaker 2>much harder to figure out.

328
00:15:46.320 --> 00:15:49.799
<v Speaker 1>So end map is outsmarting those defenses by being.

329
00:15:49.519 --> 00:15:51.279
<v Speaker 2>Sneakier, that's one way to put it.

330
00:15:51.559 --> 00:15:55.399
<v Speaker 1>But what if even fragmentation isn't enough. Are there ways

331
00:15:55.399 --> 00:15:57.639
<v Speaker 1>to further disguise those digital messages?

332
00:15:57.840 --> 00:15:58.440
<v Speaker 2>Absolutely?

333
00:15:58.559 --> 00:15:58.799
<v Speaker 1>Okay?

334
00:15:59.320 --> 00:16:03.279
<v Speaker 2>Map can also manipulate the timing of those fragmented packets, okay,

335
00:16:03.399 --> 00:16:06.480
<v Speaker 2>sending them at a regular intervals to further obfuscate their

336
00:16:06.519 --> 00:16:07.120
<v Speaker 2>true nature.

337
00:16:07.440 --> 00:16:07.840
<v Speaker 1>Okay.

338
00:16:08.120 --> 00:16:10.960
<v Speaker 2>Imagine those tiny pieces of paper arriving at the guard's

339
00:16:11.000 --> 00:16:14.240
<v Speaker 2>post at random times throughout the day. It much harder

340
00:16:14.279 --> 00:16:15.360
<v Speaker 2>to connect the dots.

341
00:16:15.159 --> 00:16:17.399
<v Speaker 1>Right, That makes sense. It's like creating a trail that's

342
00:16:17.480 --> 00:16:19.960
<v Speaker 1>nearly impossible to follow because it's so broken up in

343
00:16:20.000 --> 00:16:24.840
<v Speaker 1>irregular Right. But wouldn't a sophisticated firewall eventually notice these

344
00:16:24.919 --> 00:16:25.960
<v Speaker 1>unusual patterns?

345
00:16:26.080 --> 00:16:28.320
<v Speaker 2>They might, which is why end map has even more

346
00:16:28.360 --> 00:16:29.320
<v Speaker 2>tricks up its sleeve.

347
00:16:29.519 --> 00:16:29.879
<v Speaker 1>Okay.

348
00:16:30.200 --> 00:16:34.399
<v Speaker 2>Remember those TCP flags we talked about earlier, Yes, syn

349
00:16:34.480 --> 00:16:39.120
<v Speaker 2>ack RST. They're like little signals embedded in each packet,

350
00:16:39.600 --> 00:16:42.519
<v Speaker 2>indicating the purpose and state of a connection vaguely.

351
00:16:42.799 --> 00:16:44.200
<v Speaker 1>Yeah, refresh my memory.

352
00:16:44.279 --> 00:16:48.000
<v Speaker 2>Okay, Well, imagine each flag as a different colored flag

353
00:16:48.039 --> 00:16:50.960
<v Speaker 2>on a ship. Okay, Normally, ships use these flags to

354
00:16:51.000 --> 00:16:54.080
<v Speaker 2>communicate their intentions, like I'm coming in for a landing

355
00:16:54.279 --> 00:16:57.759
<v Speaker 2>or I'm experiencing difficulties. But what if a ship started

356
00:16:57.799 --> 00:17:01.519
<v Speaker 2>flying unusual combinations of flags, ones that didn't make sense

357
00:17:01.519 --> 00:17:03.320
<v Speaker 2>according to standard maritime signals.

358
00:17:03.360 --> 00:17:05.480
<v Speaker 1>It would raise some eyebrows. The other ships wouldn't know

359
00:17:05.480 --> 00:17:06.119
<v Speaker 1>what to make of it.

360
00:17:06.240 --> 00:17:09.839
<v Speaker 2>Exactly. That's what endmap can do with TCP flags. Okay,

361
00:17:09.880 --> 00:17:14.039
<v Speaker 2>it can send out packets with weird, unexpected flag combinations

362
00:17:14.039 --> 00:17:18.119
<v Speaker 2>that confuse firewalls and intrusion detection systems. Right.

363
00:17:18.400 --> 00:17:21.559
<v Speaker 1>They see these unusual flags and think that's not right,

364
00:17:21.640 --> 00:17:22.480
<v Speaker 1>what's going on here?

365
00:17:22.799 --> 00:17:25.359
<v Speaker 2>So it's like end map is speaking a secret language

366
00:17:25.400 --> 00:17:28.799
<v Speaker 2>that only it understands. You could say that, and while

367
00:17:28.839 --> 00:17:31.640
<v Speaker 2>the firewalls are busy scratching their heads, end map is

368
00:17:31.680 --> 00:17:34.279
<v Speaker 2>slipping past with valuable information.

369
00:17:34.000 --> 00:17:35.519
<v Speaker 1>Sneaking right by them. Hmm.

370
00:17:36.119 --> 00:17:37.039
<v Speaker 2>This is incredible.

371
00:17:37.200 --> 00:17:39.920
<v Speaker 1>Yeah, it's pretty clever, it is. It's all about exploiting

372
00:17:39.920 --> 00:17:43.640
<v Speaker 1>those little inconsistencies and loopholes in how systems are designed

373
00:17:43.640 --> 00:17:44.279
<v Speaker 1>and configured.

374
00:17:44.480 --> 00:17:48.319
<v Speaker 2>Speaking of inconsistencies, yeah, earlier we talked about the importance

375
00:17:48.359 --> 00:17:52.680
<v Speaker 2>of ethical hacking and responsible disclosure, right, but let's be real. Yeah,

376
00:17:52.759 --> 00:17:54.640
<v Speaker 2>not everyone out there plays by the rules.

377
00:17:55.119 --> 00:17:58.640
<v Speaker 1>Unfortunately, you're right right. While end map is an invaluable

378
00:17:58.680 --> 00:18:01.599
<v Speaker 1>tool for security profession and all, it can also be

379
00:18:01.680 --> 00:18:05.319
<v Speaker 1>misused by those with malicious intent. Of course, it's a

380
00:18:05.359 --> 00:18:09.039
<v Speaker 1>constant cat and mouse game between ethical hackers trying to

381
00:18:09.079 --> 00:18:13.559
<v Speaker 1>secure systems and those seeking to exploit them.

382
00:18:13.400 --> 00:18:16.519
<v Speaker 2>And like in any good spy thriller, the stakes are high.

383
00:18:16.799 --> 00:18:20.559
<v Speaker 1>Data breaches, system outages, and financial losses are all too

384
00:18:20.640 --> 00:18:23.160
<v Speaker 1>real possibilities. If endmap falls into.

385
00:18:23.000 --> 00:18:24.519
<v Speaker 2>The wrong hands, all ceial.

386
00:18:24.799 --> 00:18:26.920
<v Speaker 1>What can we do to stay ahead of the curve

387
00:18:27.079 --> 00:18:28.960
<v Speaker 1>and protect ourselves from these threats?

388
00:18:29.160 --> 00:18:32.839
<v Speaker 2>Well, knowledge is our best defense. The more we understand

389
00:18:32.839 --> 00:18:36.400
<v Speaker 2>about the tactics and techniques used by malicious actors, right,

390
00:18:36.440 --> 00:18:39.000
<v Speaker 2>the better equipped will be to thwart their efforts.

391
00:18:39.480 --> 00:18:42.400
<v Speaker 1>So it's not enough to just understand how endmap works.

392
00:18:42.960 --> 00:18:45.240
<v Speaker 1>We need to think like the bad guys to anticipate

393
00:18:45.279 --> 00:18:48.039
<v Speaker 1>their moves. What are some of the ways that attackers

394
00:18:48.119 --> 00:18:51.880
<v Speaker 1>might use end map for malicious purposes?

395
00:18:51.960 --> 00:18:56.079
<v Speaker 2>Well, one common tactic is to use endmap for reconnaissance. Okay,

396
00:18:56.119 --> 00:18:59.240
<v Speaker 2>but instead of looking for vulnerabilities to fix, they're looking

397
00:18:59.279 --> 00:19:02.680
<v Speaker 2>for weaknesses to exploit. They might use end map to

398
00:19:02.720 --> 00:19:07.680
<v Speaker 2>identify systems running outdated software, open ports with weak passwords right,

399
00:19:08.039 --> 00:19:11.000
<v Speaker 2>or even map out the entire network infrastructure to plan

400
00:19:11.079 --> 00:19:11.599
<v Speaker 2>their attack.

401
00:19:11.839 --> 00:19:14.720
<v Speaker 1>So it's like casing the joint before a heist exactly.

402
00:19:14.799 --> 00:19:17.079
<v Speaker 1>Now you're using end map to gather intel and plan

403
00:19:17.160 --> 00:19:17.599
<v Speaker 1>their moves.

404
00:19:17.680 --> 00:19:18.559
<v Speaker 2>Yep, that's exactly it.

405
00:19:18.920 --> 00:19:22.000
<v Speaker 1>What can we do to make ourselves less appealing targets

406
00:19:22.039 --> 00:19:24.480
<v Speaker 1>for this kind of digital reconnaissance?

407
00:19:24.880 --> 00:19:28.559
<v Speaker 2>There are several things. Keeping software up to date is crucial.

408
00:19:29.079 --> 00:19:33.960
<v Speaker 2>Those updates often include security patches for known vulnerabilities. Strong

409
00:19:34.000 --> 00:19:38.400
<v Speaker 2>passwords are also essential. A complex password can make the

410
00:19:38.440 --> 00:19:41.920
<v Speaker 2>difference between someone waltzing into your system and hitting a

411
00:19:41.960 --> 00:19:47.000
<v Speaker 2>brick wall. And don't underestimate the importance of network segmentation, okay.

412
00:19:47.200 --> 00:19:50.720
<v Speaker 2>Dividing your network into smaller, isolated segments can limit the

413
00:19:50.799 --> 00:19:53.839
<v Speaker 2>damage an attacker can cause if they manage to breach

414
00:19:53.920 --> 00:19:55.000
<v Speaker 2>one part of the system.

415
00:19:55.160 --> 00:19:57.920
<v Speaker 1>It's like having multiple layers of security, exact. Even if

416
00:19:57.920 --> 00:20:00.519
<v Speaker 1>one layer fails, the others are their to pick.

417
00:20:00.359 --> 00:20:03.039
<v Speaker 2>Up the slack exactly. And on that note, let's dive

418
00:20:03.079 --> 00:20:05.640
<v Speaker 2>into some of the more advanced techniques that both ethical

419
00:20:05.640 --> 00:20:08.720
<v Speaker 2>hackers and malicious actors use to make end map even

420
00:20:08.759 --> 00:20:12.640
<v Speaker 2>more effective. Okay, have you heard of source port manipulation?

421
00:20:13.119 --> 00:20:15.599
<v Speaker 1>It rings a bell, but I can use a refresher. Okay,

422
00:20:15.640 --> 00:20:16.640
<v Speaker 1>remind me how that works.

423
00:20:16.720 --> 00:20:19.759
<v Speaker 2>I think back to our earlier analogy about TCP flags

424
00:20:19.759 --> 00:20:23.039
<v Speaker 2>being like colored flags on ships. Okay, source port manipulation

425
00:20:23.319 --> 00:20:26.960
<v Speaker 2>is like disguising your ship by flying flags that normally

426
00:20:27.039 --> 00:20:28.480
<v Speaker 2>belong to a different type of vessel.

427
00:20:28.759 --> 00:20:30.799
<v Speaker 1>So you're making it look like you're someone You're not

428
00:20:31.079 --> 00:20:34.039
<v Speaker 1>exactly clever, But how does that actually work?

429
00:20:34.079 --> 00:20:36.759
<v Speaker 2>In the digital world, every packet of data sent over

430
00:20:36.799 --> 00:20:39.480
<v Speaker 2>a network has a source port. Okay, it's like a

431
00:20:39.480 --> 00:20:43.160
<v Speaker 2>return address telling the receiving computer where the data came from.

432
00:20:43.599 --> 00:20:46.680
<v Speaker 2>N MAP allows you to spoof the source port, okay,

433
00:20:46.680 --> 00:20:48.759
<v Speaker 2>making it seem like your packets are coming from a

434
00:20:48.759 --> 00:20:49.559
<v Speaker 2>trusted source.

435
00:20:49.680 --> 00:20:52.519
<v Speaker 1>So it's like sending a letter with a fake return address.

436
00:20:52.799 --> 00:20:54.079
<v Speaker 1>What's the advantage of doing that.

437
00:20:54.480 --> 00:20:59.279
<v Speaker 2>Imagine you're a hacker trying to sneak past a firewall. Okay,

438
00:20:59.400 --> 00:21:02.559
<v Speaker 2>you know that the firewall is configured to block traffic

439
00:21:02.640 --> 00:21:06.279
<v Speaker 2>from certain IP addresses or port numbers, right, So you

440
00:21:06.359 --> 00:21:08.519
<v Speaker 2>spoof your source port to make it look like your

441
00:21:08.559 --> 00:21:11.519
<v Speaker 2>traffic is coming from a trusted internal system.

442
00:21:11.559 --> 00:21:15.160
<v Speaker 1>So the firewall sees this seemingly legitimate traffic and waves

443
00:21:15.160 --> 00:21:15.680
<v Speaker 1>it right through.

444
00:21:15.960 --> 00:21:16.519
<v Speaker 2>Exactly.

445
00:21:16.720 --> 00:21:19.720
<v Speaker 1>That's incredibly sneaky, it is. Are there other ways that

446
00:21:19.920 --> 00:21:23.200
<v Speaker 1>endmap can be used to make those digital disguises even

447
00:21:23.240 --> 00:21:23.920
<v Speaker 1>more convincing?

448
00:21:24.240 --> 00:21:28.200
<v Speaker 2>Absolutely? Remember how we talked about endmap's ability to fingerprint

449
00:21:28.240 --> 00:21:32.079
<v Speaker 2>operating systems based on those subtle variations in network traffic.

450
00:21:31.839 --> 00:21:34.640
<v Speaker 1>I do, Yeah, it was like analyzing digital fingerprints.

451
00:21:34.720 --> 00:21:37.759
<v Speaker 2>Well, endmap can also be used to forge those fingerprints.

452
00:21:38.079 --> 00:21:40.839
<v Speaker 2>Would making a system appear to be running a different

453
00:21:40.880 --> 00:21:43.279
<v Speaker 2>operating system than it actually is, So.

454
00:21:43.200 --> 00:21:45.960
<v Speaker 1>You could make a Windows server look like a Linux server,

455
00:21:46.160 --> 00:21:46.839
<v Speaker 1>or vice versa.

456
00:21:47.039 --> 00:21:47.559
<v Speaker 2>You could.

457
00:21:47.880 --> 00:21:48.920
<v Speaker 1>Why would you want to do that?

458
00:21:49.160 --> 00:21:51.920
<v Speaker 2>Let's say you're an attacker, okay, and you know that

459
00:21:52.079 --> 00:21:57.160
<v Speaker 2>a particular system is only vulnerable to attacks targeting a

460
00:21:57.240 --> 00:22:00.920
<v Speaker 2>specific operating system. Okay, By forging your finger prints, you

461
00:22:00.960 --> 00:22:03.759
<v Speaker 2>can trick that system into thinking you're running the right

462
00:22:03.880 --> 00:22:06.920
<v Speaker 2>operating system, potentially opening it up to your attack.

463
00:22:07.200 --> 00:22:09.640
<v Speaker 1>It's like wearing a disguise to blend in with a

464
00:22:09.680 --> 00:22:14.039
<v Speaker 1>crowd exact, except in this case, you're disguising your digital identityact.

465
00:22:14.079 --> 00:22:17.200
<v Speaker 1>This is getting pretty deep. Into the world of cyber espionage.

466
00:22:17.759 --> 00:22:20.839
<v Speaker 2>It is, and it highlights the fact that cybersecurity isn't

467
00:22:20.880 --> 00:22:24.519
<v Speaker 2>just about having the strongest firewalls or the most sophisticated

468
00:22:24.599 --> 00:22:29.680
<v Speaker 2>intrusion detection systems. It's also about understanding the psychology of attackers,

469
00:22:30.160 --> 00:22:34.480
<v Speaker 2>anticipating their moves, and staying one step ahead in this

470
00:22:34.640 --> 00:22:36.519
<v Speaker 2>digital game of chess.

471
00:22:36.559 --> 00:22:38.799
<v Speaker 1>Well said, and speaking is staying ahead of the game.

472
00:22:39.359 --> 00:22:42.000
<v Speaker 1>You mentioned earlier that NMAP can be used for both

473
00:22:42.039 --> 00:22:45.200
<v Speaker 1>offensive and defensive security. We've talked a lot about the

474
00:22:45.200 --> 00:22:49.720
<v Speaker 1>offensive side, the spycraft techniques, but what about the defensive applications.

475
00:22:50.359 --> 00:22:54.519
<v Speaker 1>How can security professionals use enmap to stringen their defenses

476
00:22:54.799 --> 00:22:56.079
<v Speaker 1>and protect their systems.

477
00:22:56.920 --> 00:22:59.799
<v Speaker 2>En MAP is an invaluable tool for ethical hackers and

478
00:23:00.000 --> 00:23:03.240
<v Speaker 2>security professionals looking to shore up their defenses. One of

479
00:23:03.240 --> 00:23:07.079
<v Speaker 2>the most common uses is vulnerability scanning, where you proactively

480
00:23:07.240 --> 00:23:12.119
<v Speaker 2>scan your systems and networks.

481
00:23:15.079 --> 00:23:17.519
<v Speaker 1>Exactly, looking for any signs of trouble before they turn

482
00:23:17.559 --> 00:23:18.799
<v Speaker 1>into full blown problems.

483
00:23:19.160 --> 00:23:23.400
<v Speaker 2>Exactly and MAT can help you identify things like open

484
00:23:23.480 --> 00:23:27.480
<v Speaker 2>ports that shouldn't be accessible from the outside world, outdated

485
00:23:27.519 --> 00:23:32.000
<v Speaker 2>software versions that are riddled with known vulnerabilities, and even

486
00:23:32.039 --> 00:23:35.680
<v Speaker 2>misconfigured security settings that could leave your systems exposed.

487
00:23:35.920 --> 00:23:38.680
<v Speaker 1>It sounds like endmap is giving you a detailed roadmap

488
00:23:38.680 --> 00:23:42.240
<v Speaker 1>of your network security posture, highlighting all the areas that need.

489
00:23:42.119 --> 00:23:46.079
<v Speaker 2>Attention precisely, and once you know where the weaknesses lie,

490
00:23:46.400 --> 00:23:50.920
<v Speaker 2>you can start taking steps to remediate them, patching vulnerable software,

491
00:23:51.279 --> 00:23:56.279
<v Speaker 2>closing unnecessary ports, and tightening up those security settings. It's

492
00:23:56.319 --> 00:23:58.960
<v Speaker 2>all about being proactive and staying ahead of the threat.

493
00:23:59.319 --> 00:24:02.640
<v Speaker 1>So it's not just about reacting to attacks after they happen.

494
00:24:03.039 --> 00:24:06.559
<v Speaker 1>It's about anticipating them and making yourself a less appealing

495
00:24:06.599 --> 00:24:07.640
<v Speaker 1>target in the first place.

496
00:24:07.799 --> 00:24:11.279
<v Speaker 2>Exactly. It's about making your systems and networks as secure

497
00:24:11.319 --> 00:24:15.119
<v Speaker 2>as possible so that even if an attacker does come knocking, yeah,

498
00:24:15.119 --> 00:24:16.960
<v Speaker 2>they'll find it much harder to break in.

499
00:24:17.559 --> 00:24:21.160
<v Speaker 1>This has been incredibly insightful. It's fascinating to see how

500
00:24:21.279 --> 00:24:23.640
<v Speaker 1>end map can be used for both good and bad,

501
00:24:23.799 --> 00:24:26.559
<v Speaker 1>depending on the intentions of the user it is. It

502
00:24:26.599 --> 00:24:30.079
<v Speaker 1>really highlights the importance of ethical hacking and responsible disclosure.

503
00:24:30.240 --> 00:24:33.200
<v Speaker 1>It does using these powerful tools for the right reasons

504
00:24:33.559 --> 00:24:35.839
<v Speaker 1>to make the digital world a safer place for everyone.

505
00:24:35.920 --> 00:24:38.599
<v Speaker 1>Couldn't agree more well said. Now we've covered a lot

506
00:24:38.599 --> 00:24:40.960
<v Speaker 1>of ground here. In Part two, we have from the

507
00:24:40.960 --> 00:24:44.240
<v Speaker 1>ethical considerations of using end map to the more technical

508
00:24:44.240 --> 00:24:46.799
<v Speaker 1>aspects of how it can be used for both offensive

509
00:24:46.839 --> 00:24:50.039
<v Speaker 1>and defensive security. But there's still so much more to explore.

510
00:24:50.119 --> 00:24:53.160
<v Speaker 2>We've only scratched the surface right. End map is a

511
00:24:53.200 --> 00:24:57.559
<v Speaker 2>tool with incredible depth and versatility. In our final part, yes,

512
00:24:57.759 --> 00:25:00.960
<v Speaker 2>we'll delve into some even more advanced TECHNIQE and explore

513
00:25:01.039 --> 00:25:04.880
<v Speaker 2>how enmap is evolving alongside the ever changing landscape of

514
00:25:04.920 --> 00:25:06.240
<v Speaker 2>cybersecurity threats.

515
00:25:06.799 --> 00:25:09.759
<v Speaker 1>I can't wait to dive back in see you there

516
00:25:10.319 --> 00:25:15.400
<v Speaker 1>for part three of our ENDMP deep dive. Welcome back

517
00:25:15.400 --> 00:25:18.680
<v Speaker 1>to the deep dive. We're wrapping up our exploration of ENMAP,

518
00:25:19.079 --> 00:25:21.680
<v Speaker 1>that Swiss Army knife of network scanning tools.

519
00:25:21.880 --> 00:25:24.640
<v Speaker 2>It's been quite a journey, hasn't it It has. We've

520
00:25:24.640 --> 00:25:27.920
<v Speaker 2>gone from the basics of ping scans to some pretty

521
00:25:27.920 --> 00:25:32.519
<v Speaker 2>advanced techniques for bypassing security measures and even manipulating network traffic.

522
00:25:32.799 --> 00:25:34.799
<v Speaker 1>It's amazing how much ground there is to cover with

523
00:25:34.839 --> 00:25:35.519
<v Speaker 1>a single tool.

524
00:25:35.640 --> 00:25:36.359
<v Speaker 2>It really is.

525
00:25:36.559 --> 00:25:38.839
<v Speaker 1>Speaking of covering your tracks, and the last part you

526
00:25:38.920 --> 00:25:42.720
<v Speaker 1>teased even more advanced ENDMP techniques. It did something about

527
00:25:42.720 --> 00:25:45.000
<v Speaker 1>idle scanninges what's that all about.

528
00:25:45.279 --> 00:25:47.759
<v Speaker 2>Idle scanning is like sending a message in a bottle

529
00:25:47.960 --> 00:25:51.920
<v Speaker 2>and using the ocean currents to deliver it for you. Okay,

530
00:25:52.519 --> 00:25:55.000
<v Speaker 2>it's a way to scan a target network without ever

531
00:25:55.119 --> 00:26:00.119
<v Speaker 2>sending a direct packet to it, making it incredibly stealthy.

532
00:26:00.119 --> 00:26:03.039
<v Speaker 1>You've officially piqued my curiosity. How does that even work?

533
00:26:03.519 --> 00:26:05.599
<v Speaker 1>Sending digital messages in bottles?

534
00:26:05.720 --> 00:26:09.839
<v Speaker 2>It involves a bit of digital Trickeryka, imagine this. You

535
00:26:09.920 --> 00:26:13.240
<v Speaker 2>find an abandoned computer connected to the internet. Okay, we

536
00:26:13.319 --> 00:26:16.039
<v Speaker 2>call this a zombie system. The zombie system is just

537
00:26:16.079 --> 00:26:19.319
<v Speaker 2>sitting there idle, not doing much, but it's still generating

538
00:26:19.359 --> 00:26:21.119
<v Speaker 2>network traffic in a predictable way.

539
00:26:21.400 --> 00:26:24.599
<v Speaker 1>Okay, so we've got our unsuspecting zombie. What's next.

540
00:26:24.880 --> 00:26:27.359
<v Speaker 2>Now, Let's say you want to scan a target system,

541
00:26:27.720 --> 00:26:30.359
<v Speaker 2>but you don't want to raise any alarms by sending

542
00:26:30.400 --> 00:26:35.200
<v Speaker 2>packets directly from your computer. So you spoof a packet. Okay,

543
00:26:35.319 --> 00:26:37.079
<v Speaker 2>that is, you make it look like it's coming from

544
00:26:37.119 --> 00:26:39.559
<v Speaker 2>the target system and you send it to the zombie.

545
00:26:39.920 --> 00:26:44.200
<v Speaker 1>So the zombie receives this spoof packet and thinks, hey,

546
00:26:44.400 --> 00:26:45.079
<v Speaker 1>this is for me.

547
00:26:46.000 --> 00:26:50.039
<v Speaker 2>What happens then, the zombie being the predictable soul it

548
00:26:50.119 --> 00:26:52.960
<v Speaker 2>is will try to respond to this packet, right, But

549
00:26:53.039 --> 00:26:56.400
<v Speaker 2>remember we spoofed the senders address, so the zombie's response

550
00:26:56.440 --> 00:26:58.359
<v Speaker 2>doesn't come back to us, it goes to the actual

551
00:26:58.359 --> 00:26:59.079
<v Speaker 2>target system.

552
00:26:59.119 --> 00:27:02.680
<v Speaker 1>Oka, trick the zombie into sending a message to our

553
00:27:02.720 --> 00:27:05.079
<v Speaker 1>target for us, right, But how does that tell us

554
00:27:05.119 --> 00:27:06.160
<v Speaker 1>anything about the target?

555
00:27:06.240 --> 00:27:07.240
<v Speaker 2>Here's where it gets clever.

556
00:27:07.440 --> 00:27:07.759
<v Speaker 1>Okay.

557
00:27:08.319 --> 00:27:12.039
<v Speaker 2>Every IP packet has a unique identifier called an IPID.

558
00:27:13.119 --> 00:27:14.440
<v Speaker 2>Think of it like a serial number.

559
00:27:14.519 --> 00:27:14.799
<v Speaker 1>Okay.

560
00:27:15.240 --> 00:27:20.000
<v Speaker 2>Many systems generate these ipids sequentially, right, which makes them predictable.

561
00:27:20.799 --> 00:27:25.359
<v Speaker 2>We know the zombie system's IPID sequence because it's well predictable.

562
00:27:25.599 --> 00:27:28.799
<v Speaker 1>Right, so we can keep track of the zombies ipid

563
00:27:28.960 --> 00:27:30.119
<v Speaker 1>like it's a countdown clock.

564
00:27:30.359 --> 00:27:34.440
<v Speaker 2>Exactly. We send that initial spoofed packet to the zombie, right,

565
00:27:34.559 --> 00:27:37.319
<v Speaker 2>then we send another packet directly to the zombie from

566
00:27:37.319 --> 00:27:40.319
<v Speaker 2>our real IP address. Okay, and we closely watched the

567
00:27:40.440 --> 00:27:42.240
<v Speaker 2>zombies IPID sequence.

568
00:27:42.400 --> 00:27:42.680
<v Speaker 1>Okay.

569
00:27:42.759 --> 00:27:45.839
<v Speaker 2>If the target system responded to that first spoofed packet,

570
00:27:46.079 --> 00:27:49.240
<v Speaker 2>the zombies ipid will have skipped ahead by two right,

571
00:27:49.440 --> 00:27:52.240
<v Speaker 2>one for the received packet and one for the scent response.

572
00:27:52.400 --> 00:27:52.720
<v Speaker 1>Okay.

573
00:27:52.960 --> 00:27:56.319
<v Speaker 2>If the target didn't respond the ipid will have only

574
00:27:56.400 --> 00:27:59.359
<v Speaker 2>intermented by one.

575
00:27:58.559 --> 00:28:01.559
<v Speaker 1>So we're indirectly probe being the target through the zombie

576
00:28:01.640 --> 00:28:05.119
<v Speaker 1>without ever showing our hand directly exactly. That's brilliant and

577
00:28:05.200 --> 00:28:07.119
<v Speaker 1>sneaky and more than a little creepy.

578
00:28:07.160 --> 00:28:08.960
<v Speaker 2>It is a bit like that, isn't it. Yeah, But

579
00:28:09.000 --> 00:28:11.680
<v Speaker 2>it's an incredibly effective way to gather information about a

580
00:28:11.720 --> 00:28:15.880
<v Speaker 2>target without raising suspicion. Right, And it highlights how even

581
00:28:16.039 --> 00:28:21.079
<v Speaker 2>seemingly insignificant details like IPID generation can be exploited by

582
00:28:21.119 --> 00:28:22.079
<v Speaker 2>a skilled attacker.

583
00:28:22.240 --> 00:28:25.640
<v Speaker 1>It's like a reminder that in the world of cybersecurity,

584
00:28:25.720 --> 00:28:27.920
<v Speaker 1>the smallest details can have the biggest.

585
00:28:27.640 --> 00:28:31.680
<v Speaker 2>Impact, exactly, And that's why it's so crucial to stay vigilant,

586
00:28:31.799 --> 00:28:34.960
<v Speaker 2>keep learning, and always be one step ahead of the game.

587
00:28:35.200 --> 00:28:35.440
<v Speaker 1>Right.

588
00:28:35.759 --> 00:28:39.000
<v Speaker 2>End map and tools like it are constantly evolving alongside

589
00:28:39.079 --> 00:28:40.119
<v Speaker 2>the threat landscape.

590
00:28:40.319 --> 00:28:40.480
<v Speaker 1>Right.

591
00:28:40.559 --> 00:28:41.880
<v Speaker 2>It's a never ending race.

592
00:28:42.160 --> 00:28:45.079
<v Speaker 1>Speaking of evolution, one thing that struck me throughout our

593
00:28:45.759 --> 00:28:50.079
<v Speaker 1>end map deep dive is the ethical tightrope block involved. Yeah.

594
00:28:50.119 --> 00:28:54.920
<v Speaker 1>We've talked about responsible disclosures, staying within legal boundaries and

595
00:28:55.119 --> 00:28:57.079
<v Speaker 1>the fact that this knowledge can be used for both

596
00:28:57.119 --> 00:28:59.839
<v Speaker 1>good and bad. What are your thoughts on that balance

597
00:29:00.039 --> 00:29:02.880
<v Speaker 1>and how do we ensure that the good guys continue

598
00:29:02.880 --> 00:29:06.160
<v Speaker 1>to outweigh the bad guys in the world of cybersecurity.

599
00:29:06.359 --> 00:29:08.480
<v Speaker 2>That's the million dollar question, isn't it.

600
00:29:08.480 --> 00:29:09.480
<v Speaker 1>It really is for me.

601
00:29:09.519 --> 00:29:12.759
<v Speaker 2>It boils down to education and community. Okay, the more

602
00:29:13.400 --> 00:29:16.920
<v Speaker 2>people understand about cybersecurity, the harder it is for the

603
00:29:16.920 --> 00:29:20.720
<v Speaker 2>bad guys to operate. When we openly share knowledge about

604
00:29:20.720 --> 00:29:25.200
<v Speaker 2>tools like endmap, the capabilities, the limitations, the ethical implications,

605
00:29:25.519 --> 00:29:28.400
<v Speaker 2>we empower everyone to be better digital citizens.

606
00:29:28.720 --> 00:29:32.799
<v Speaker 1>I love that it's about democratizing knowledge, making it accessible

607
00:29:32.839 --> 00:29:35.000
<v Speaker 1>to everyone, not just to select.

608
00:29:34.680 --> 00:29:38.359
<v Speaker 2>Few exactly, and that's why initiatives like open source projects,

609
00:29:38.400 --> 00:29:41.759
<v Speaker 2>security conferences, and even podcasts like this one are so important.

610
00:29:42.079 --> 00:29:45.480
<v Speaker 2>We need to keep the conversation going, keep learning from

611
00:29:45.480 --> 00:29:49.000
<v Speaker 2>each other, and keep pushing the boundaries of what's possible

612
00:29:49.039 --> 00:29:52.880
<v Speaker 2>in cybersecurity, always with the goal of making the digital

613
00:29:52.920 --> 00:29:54.799
<v Speaker 2>world a safer place for everyone.

614
00:29:55.000 --> 00:29:58.079
<v Speaker 1>Couldn't have said it better myself. This deep dive has

615
00:29:58.119 --> 00:30:01.279
<v Speaker 1>been eye opening, to say the least. We've delved into

616
00:30:01.279 --> 00:30:05.920
<v Speaker 1>the technical nitty gritty of end map, explored its incredible versatility,

617
00:30:06.039 --> 00:30:09.480
<v Speaker 1>I did and grappled with the ethical considerations that come

618
00:30:09.559 --> 00:30:10.759
<v Speaker 1>with such a powerful tool.

619
00:30:10.920 --> 00:30:12.880
<v Speaker 2>It's a lot to think about, it really is, and

620
00:30:12.920 --> 00:30:16.559
<v Speaker 2>throughout it all, I think we've highlighted something truly crucial.

621
00:30:17.279 --> 00:30:18.160
<v Speaker 2>Knowledge is power.

622
00:30:18.400 --> 00:30:19.039
<v Speaker 1>Absolutely.

623
00:30:19.200 --> 00:30:21.480
<v Speaker 2>The more you understand about the tools and techniques at

624
00:30:21.519 --> 00:30:24.759
<v Speaker 2>play in cybersecurity, the better equipped you'll be to navigate

625
00:30:24.799 --> 00:30:26.680
<v Speaker 2>this ever evolving landscape.

626
00:30:26.839 --> 00:30:30.759
<v Speaker 1>Absolutely, whether you're a seasoned security professional or just starting

627
00:30:30.799 --> 00:30:35.279
<v Speaker 1>out on your cybersecurity journey, keep exploring, keep learning, and

628
00:30:35.400 --> 00:30:39.359
<v Speaker 1>never underestimate the importance of ethical hacking and responsible disclosure

629
00:30:39.680 --> 00:30:42.480
<v Speaker 1>very important. And hey, maybe even fire up ndmap and

630
00:30:42.480 --> 00:30:46.920
<v Speaker 1>do some exploring of your ownah within legal and ethical boundaries.

631
00:30:46.559 --> 00:30:48.039
<v Speaker 2>Of course, of course, of course.

632
00:30:47.880 --> 00:30:52.200
<v Speaker 1>Yeah, I second that. And remember the cybersecurity community is

633
00:30:52.440 --> 00:30:56.880
<v Speaker 1>vast and welcoming. There are countless resources, online, forums, and

634
00:30:56.960 --> 00:31:00.000
<v Speaker 1>local meetups where you can connect with like minded individal,

635
00:31:00.720 --> 00:31:03.319
<v Speaker 1>exchange ideas, and continue your learning journey.

636
00:31:03.400 --> 00:31:06.880
<v Speaker 2>It's all about collaboration and collective learning. That wraps up

637
00:31:06.880 --> 00:31:10.279
<v Speaker 2>our deep dive into the fascinating, complex and ever evolving

638
00:31:10.319 --> 00:31:11.240
<v Speaker 2>world of endmap.

639
00:31:11.519 --> 00:31:11.920
<v Speaker 1>It does.

640
00:31:12.119 --> 00:31:15.400
<v Speaker 2>Until next time, stay curious, stay safe, and keep those

641
00:31:15.400 --> 00:31:17.759
<v Speaker 2>firewalls strong. Goodbye everyone,
