WEBVTT

1
00:00:00.120 --> 00:00:03.439
<v Speaker 1>Welcome to the Deep Dive. When you hear the word hacking,

2
00:00:03.759 --> 00:00:07.960
<v Speaker 1>what immediately comes to mind? For for many of us,

3
00:00:07.960 --> 00:00:12.519
<v Speaker 1>it's probably those shadowy figures, right sending encrypted programs, gaining

4
00:00:12.599 --> 00:00:15.480
<v Speaker 1>unauthorized access, causing chaos.

5
00:00:15.640 --> 00:00:18.960
<v Speaker 2>That's definitely the popular image. Yeah, but you know what's

6
00:00:19.000 --> 00:00:21.719
<v Speaker 2>really interesting is that the term hacking originally meant something

7
00:00:22.199 --> 00:00:23.879
<v Speaker 2>well quite different.

8
00:00:23.640 --> 00:00:25.879
<v Speaker 1>Oh really like what Historically it was.

9
00:00:25.839 --> 00:00:30.079
<v Speaker 2>More about tinkering, you know, playing with a computer's hardware, software,

10
00:00:30.160 --> 00:00:32.520
<v Speaker 2>pushing it beyond what it was supposed to do. It

11
00:00:32.560 --> 00:00:36.200
<v Speaker 2>came from curiosity, wanting to improve things or just understand

12
00:00:36.240 --> 00:00:39.200
<v Speaker 2>them better, more innovation than malice. Really, huh.

13
00:00:39.240 --> 00:00:41.719
<v Speaker 1>So that spirit is still around, that curiosity, but the

14
00:00:41.759 --> 00:00:46.280
<v Speaker 1>perception of hacking has well, it's shifted dramatically massively. So

15
00:00:46.560 --> 00:00:49.079
<v Speaker 1>for this deep dive, our mission is kind of cut

16
00:00:49.119 --> 00:00:51.799
<v Speaker 1>through those common ideas. We want to clarify how information

17
00:00:51.920 --> 00:00:56.200
<v Speaker 1>security can be compromised, sure, but maybe more importantly, how

18
00:00:56.200 --> 00:01:00.240
<v Speaker 1>you can spot and prevent attacks. It's about understanding the

19
00:01:00.240 --> 00:01:01.719
<v Speaker 1>hackers mindset.

20
00:01:01.320 --> 00:01:03.840
<v Speaker 2>Right, and this isn't just theory. It's about empowering you

21
00:01:03.920 --> 00:01:05.079
<v Speaker 2>to stay a step ahead.

22
00:01:05.400 --> 00:01:08.799
<v Speaker 1>And our insights today they're drawn from a pretty comprehensive

23
00:01:08.799 --> 00:01:15.359
<v Speaker 1>guide covering computer hacking, basic security, penetration, testing, the works.

24
00:01:15.560 --> 00:01:17.799
<v Speaker 2>Yeah, think of it as your shortcut to getting informed

25
00:01:17.799 --> 00:01:21.760
<v Speaker 2>about digital self protection, giving you a practical knowledge you

26
00:01:21.760 --> 00:01:22.519
<v Speaker 2>can actually use.

27
00:01:22.599 --> 00:01:26.120
<v Speaker 1>Okay, let's dive in then hacking one or one. First off,

28
00:01:26.159 --> 00:01:28.359
<v Speaker 1>when we talk hackers, they're not all the same, are they.

29
00:01:28.400 --> 00:01:29.799
<v Speaker 1>People talk about different hats.

30
00:01:30.159 --> 00:01:33.319
<v Speaker 2>That's a really crucial distinction. Yeah. We often hear about

31
00:01:33.359 --> 00:01:37.280
<v Speaker 2>the black hat hackers. They're the criminals driven by selfish gain,

32
00:01:37.680 --> 00:01:40.840
<v Speaker 2>maybe money, maybe just disruption, right.

33
00:01:40.719 --> 00:01:46.519
<v Speaker 1>The ones maliciously accessing systems, stealing data, deleting files, that kind.

34
00:01:46.319 --> 00:01:49.920
<v Speaker 2>Of thing precisely for personal profit or causing damage. They're

35
00:01:49.959 --> 00:01:51.480
<v Speaker 2>the digital bad guys essentially.

36
00:01:51.640 --> 00:01:54.319
<v Speaker 1>So if they're the villains, who are the guardians?

37
00:01:54.359 --> 00:01:56.959
<v Speaker 2>Ah, those would be the white hat hackers or ethical hackers.

38
00:01:57.200 --> 00:02:01.480
<v Speaker 2>Their whole motivation is defensive, defensive, so they hunt for

39
00:02:01.640 --> 00:02:06.040
<v Speaker 2>system vulnerabilities, specifically to figure out how to protect against attacks.

40
00:02:06.599 --> 00:02:10.479
<v Speaker 2>They find the flaws, share that knowledge, often within communities,

41
00:02:10.719 --> 00:02:14.599
<v Speaker 2>all to improve security for everyone. They're like the cybersecurity frontline.

42
00:02:14.240 --> 00:02:17.960
<v Speaker 1>Making things stronger before the black hats find the weaknesses exactly.

43
00:02:18.080 --> 00:02:20.000
<v Speaker 1>And then there's a third category, right, the one that

44
00:02:20.039 --> 00:02:22.240
<v Speaker 1>sort of blurs the lines. Gray hats.

45
00:02:22.520 --> 00:02:24.840
<v Speaker 2>Yeah, the gray hat hackers, they operate in a more

46
00:02:25.439 --> 00:02:28.759
<v Speaker 2>ambiguous space. They might use a mix of legal and

47
00:02:28.840 --> 00:02:30.919
<v Speaker 2>illegal techniques to find a vulnerability.

48
00:02:31.080 --> 00:02:34.199
<v Speaker 1>Okay, so what makes them different from black hats then?

49
00:02:34.599 --> 00:02:37.319
<v Speaker 2>Well, the key thing is if they do exploit the system,

50
00:02:37.400 --> 00:02:39.719
<v Speaker 2>they usually tell the owner about the flaw. They might

51
00:02:39.759 --> 00:02:42.199
<v Speaker 2>even offer suggestions on how to fix it. They're kind

52
00:02:42.199 --> 00:02:47.599
<v Speaker 2>of like digital vigilantes, maybe exposing flaws, but not necessarily

53
00:02:47.639 --> 00:02:49.240
<v Speaker 2>with purely malicious intent.

54
00:02:49.919 --> 00:02:53.439
<v Speaker 1>Interesting, So understanding these different motivations black, white, gray, that

55
00:02:53.479 --> 00:02:56.120
<v Speaker 1>seems super useful. It helps you anticipate what kind of

56
00:02:56.120 --> 00:02:58.199
<v Speaker 1>attacks you might face, how to build defenses.

57
00:02:58.520 --> 00:03:01.759
<v Speaker 2>Absolutely, knowing the w W I helped predict the how.

58
00:03:02.199 --> 00:03:05.360
<v Speaker 1>But it does raise a big question is learning about

59
00:03:05.360 --> 00:03:08.919
<v Speaker 1>this stuff about hacking really for everyone? I mean, how

60
00:03:08.919 --> 00:03:10.319
<v Speaker 1>hard is it? Sounds like you need to be some

61
00:03:10.400 --> 00:03:11.719
<v Speaker 1>kind of coding genius.

62
00:03:12.319 --> 00:03:17.120
<v Speaker 2>Not necessarily. No, that's a common misconception. While yeah, advanced

63
00:03:17.120 --> 00:03:20.639
<v Speaker 2>hacking definitely involves deep coding skills, the truth is anyone

64
00:03:20.719 --> 00:03:23.159
<v Speaker 2>with a computer or even just a smartphone can learn

65
00:03:23.199 --> 00:03:26.039
<v Speaker 2>the basics, especially if your goal is just securing your

66
00:03:26.080 --> 00:03:26.719
<v Speaker 2>own systems.

67
00:03:27.000 --> 00:03:30.360
<v Speaker 1>So you don't need a supercomputer and years of training

68
00:03:30.479 --> 00:03:32.479
<v Speaker 1>just to wrap your head around the fundamentals.

69
00:03:32.719 --> 00:03:35.199
<v Speaker 2>Not for the fundamentals, no, or even for doing some

70
00:03:35.280 --> 00:03:37.680
<v Speaker 2>basic checks on your own setup. If you can use

71
00:03:37.680 --> 00:03:41.080
<v Speaker 2>a computer follow instructions, you can get started now. If

72
00:03:41.120 --> 00:03:44.680
<v Speaker 2>you want to excel, if you want to build custom

73
00:03:44.759 --> 00:03:49.439
<v Speaker 2>security tools or design really sophisticated tests, then yes, coding

74
00:03:49.479 --> 00:03:50.479
<v Speaker 2>becomes pretty essential.

75
00:03:50.599 --> 00:03:52.879
<v Speaker 1>Okay, that makes sense. So let's say you do want

76
00:03:52.879 --> 00:03:55.800
<v Speaker 1>to become a capable ethical hacker. Go beyond just basic

77
00:03:55.800 --> 00:03:58.960
<v Speaker 1>computer use what's in that toolkit? What skills are absolutely key.

78
00:03:59.080 --> 00:04:01.319
<v Speaker 2>It's quite a diverse set. Actually, it builds up layer

79
00:04:01.360 --> 00:04:05.639
<v Speaker 2>by layer. First, you need solid intermediate computer skills, more

80
00:04:05.680 --> 00:04:09.360
<v Speaker 2>than just writing documents, like navigating Windows command lines, setting

81
00:04:09.400 --> 00:04:12.159
<v Speaker 2>up networks, maybe editing the registry.

82
00:04:12.080 --> 00:04:14.039
<v Speaker 1>That level, getting under the hood a bit exactly.

83
00:04:14.319 --> 00:04:19.079
<v Speaker 2>Then strong networking skills are absolutely critical. Most attacks happen online, right,

84
00:04:19.439 --> 00:04:23.040
<v Speaker 2>so you need to really understand protocols like TCPIP, how

85
00:04:23.079 --> 00:04:27.560
<v Speaker 2>IP addresses a network, the OSI model, layers, all that stuff.

86
00:04:27.879 --> 00:04:30.600
<v Speaker 2>Without that, you're kind of flying blind.

87
00:04:30.720 --> 00:04:33.639
<v Speaker 1>It's like needing to understand the language the Internet speaks.

88
00:04:33.959 --> 00:04:38.480
<v Speaker 2>Perfect analogy and for operating systems. Most ethical hackers lean

89
00:04:38.519 --> 00:04:39.439
<v Speaker 2>heavily on Linux.

90
00:04:39.519 --> 00:04:41.199
<v Speaker 1>Why Linux specifically, It.

91
00:04:41.240 --> 00:04:44.439
<v Speaker 2>Just offers unique programs, tons of customization things you can't

92
00:04:44.439 --> 00:04:47.439
<v Speaker 2>easily do on Windows or Mac. Plus, honestly, most of

93
00:04:47.439 --> 00:04:49.199
<v Speaker 2>the best hacking tools are built for Linux.

94
00:04:49.319 --> 00:04:52.279
<v Speaker 1>Gotcha, and you probably need a safe place to practice, right,

95
00:04:52.399 --> 00:04:54.160
<v Speaker 1>don't want to accidentally wreck your own computer?

96
00:04:54.399 --> 00:04:58.040
<v Speaker 2>Oh definitely. That's where virtualization software comes in. Things like

97
00:04:58.160 --> 00:05:03.199
<v Speaker 2>VMware Workstation lets you create isolated virtual machines safe sandboxes

98
00:05:03.279 --> 00:05:06.519
<v Speaker 2>to test things out without risking your main system.

99
00:05:06.600 --> 00:05:11.160
<v Speaker 1>Absolutely indispensable, smart learn without the self inflicted rooms. What

100
00:05:11.279 --> 00:05:14.480
<v Speaker 1>about tools for actually seeing what's happening on a network?

101
00:05:14.600 --> 00:05:18.000
<v Speaker 2>Yeah, you need packet analyzers. Tools like Wireshark are famous

102
00:05:18.040 --> 00:05:21.120
<v Speaker 2>are often called sniffers. Sniffers, yeah, because they let you

103
00:05:21.160 --> 00:05:23.800
<v Speaker 2>capture and look at the raw data packets flowing across

104
00:05:23.839 --> 00:05:27.439
<v Speaker 2>the network, see exactly what's being sent and received. Beyond that,

105
00:05:27.600 --> 00:05:32.800
<v Speaker 2>you need a good knowledge of security technologies. You know SSL, encryption, firewalls,

106
00:05:32.839 --> 00:05:38.040
<v Speaker 2>intrusion detection systems IDs, PKI, how wireless works fundamentally.

107
00:05:38.079 --> 00:05:40.879
<v Speaker 1>And you mentioned coding earlier, so scripting skills must be

108
00:05:40.879 --> 00:05:42.439
<v Speaker 1>pretty high on the list. If you want to get.

109
00:05:42.319 --> 00:05:45.800
<v Speaker 2>Creative, absolutely, getting handy with languages like Ruby on Rails

110
00:05:45.920 --> 00:05:48.519
<v Speaker 2>or Python that lets you build your own tools, your

111
00:05:48.519 --> 00:05:51.319
<v Speaker 2>own defenses. You're not just relying on off the shelf stuff.

112
00:05:51.319 --> 00:05:53.519
<v Speaker 1>We're adapting to new threats exactly.

113
00:05:53.920 --> 00:05:57.560
<v Speaker 2>You also need database skills. Understanding Oracle or mice equel

114
00:05:57.560 --> 00:06:01.360
<v Speaker 2>helps you see how data repositories get compromise, and reverse

115
00:06:01.360 --> 00:06:02.639
<v Speaker 2>engineering is powerful too.

116
00:06:02.800 --> 00:06:04.720
<v Speaker 1>Reverse engineering malware.

117
00:06:04.399 --> 00:06:07.519
<v Speaker 2>Yeah, taking apart malware or existing exploits to understand how

118
00:06:07.560 --> 00:06:10.279
<v Speaker 2>they work. You can learn a lot, even turn adversary

119
00:06:10.319 --> 00:06:11.600
<v Speaker 2>tools into defensive ones.

120
00:06:11.720 --> 00:06:15.079
<v Speaker 1>Wow. Okay, so understanding the bad guys tools helps build

121
00:06:15.120 --> 00:06:16.519
<v Speaker 1>better shields incisely.

122
00:06:16.959 --> 00:06:22.120
<v Speaker 2>And finally, cryptography. Understanding encryption and decryption is key. You

123
00:06:22.160 --> 00:06:24.680
<v Speaker 2>see how hackers hide their tracks, and you learn the

124
00:06:24.680 --> 00:06:28.279
<v Speaker 2>strengths but also the weaknesses of algorithms used for things

125
00:06:28.279 --> 00:06:29.040
<v Speaker 2>like passwords.

126
00:06:29.120 --> 00:06:31.279
<v Speaker 1>It all comes together. I mean, think about the devices

127
00:06:31.319 --> 00:06:34.839
<v Speaker 1>you use every day, your phone, laptop, smart speakers, right.

128
00:06:34.759 --> 00:06:37.160
<v Speaker 2>These are the skills ethical hackers used to make those

129
00:06:37.160 --> 00:06:40.079
<v Speaker 2>things safer for you. Finding the weak spots before the

130
00:06:40.079 --> 00:06:40.639
<v Speaker 2>criminals do.

131
00:06:40.959 --> 00:06:43.759
<v Speaker 1>That really flips the perspective, doesn't it from just being

132
00:06:43.839 --> 00:06:47.839
<v Speaker 1>scared to being proactive, understanding the adversary. That's the goal,

133
00:06:47.920 --> 00:06:51.560
<v Speaker 1>which leads us perfectly into our next bit. Actually thinking

134
00:06:51.639 --> 00:06:55.560
<v Speaker 1>like a hacker, a criminal hacker specifically, what's their strategy?

135
00:06:55.600 --> 00:06:56.759
<v Speaker 1>What are they really after?

136
00:06:57.120 --> 00:07:00.759
<v Speaker 2>Well, criminal hackers, the serious ones, they're strategic. They don't

137
00:07:00.800 --> 00:07:06.920
<v Speaker 2>just randomly smash windows. Digitally speaking, they research their targets meticulously.

138
00:07:07.199 --> 00:07:09.480
<v Speaker 2>They want the most valuable data for the least amount

139
00:07:09.519 --> 00:07:10.319
<v Speaker 2>of effort.

140
00:07:10.160 --> 00:07:13.079
<v Speaker 1>And their motivations shape their targets totally.

141
00:07:13.480 --> 00:07:17.199
<v Speaker 2>Some go after banking systems for obvious financial gain, Others

142
00:07:17.240 --> 00:07:21.399
<v Speaker 2>want personal info for identity theft. Some just want to

143
00:07:21.439 --> 00:07:24.759
<v Speaker 2>deface a website for notoriety, or maybe get free access

144
00:07:24.759 --> 00:07:25.600
<v Speaker 2>to a paid service.

145
00:07:25.839 --> 00:07:30.040
<v Speaker 1>So for us listening, what's the core defense principle here?

146
00:07:30.319 --> 00:07:32.600
<v Speaker 1>How does knowing their strategy help us?

147
00:07:32.800 --> 00:07:36.160
<v Speaker 2>It's about making yourself a less attractive target. If they

148
00:07:36.160 --> 00:07:38.959
<v Speaker 2>look at you or your system and don't see much value,

149
00:07:39.240 --> 00:07:40.879
<v Speaker 2>or if it looks like it'll take way too much

150
00:07:40.879 --> 00:07:42.959
<v Speaker 2>work to get in, yeah, to likely just move on,

151
00:07:43.199 --> 00:07:44.079
<v Speaker 2>find easier.

152
00:07:43.800 --> 00:07:46.839
<v Speaker 1>Prey, right, harden the target so they look elsewhere, exactly know.

153
00:07:46.759 --> 00:07:48.560
<v Speaker 2>What they value so you can protect it better.

154
00:07:48.600 --> 00:07:50.439
<v Speaker 1>Okay, So putting on that black hat for a moment

155
00:07:50.959 --> 00:07:54.040
<v Speaker 1>what specific kinds of information are they actively looking for

156
00:07:54.279 --> 00:07:55.439
<v Speaker 1>During that research phase.

157
00:07:55.720 --> 00:07:59.199
<v Speaker 2>They often start with stuff that's surprisingly public. For businesses,

158
00:07:59.240 --> 00:08:03.199
<v Speaker 2>they look at organization design, public filings. Simple web searches

159
00:08:03.240 --> 00:08:07.160
<v Speaker 2>can reveal what software or hardware a company uses, SEC registrations,

160
00:08:07.399 --> 00:08:10.040
<v Speaker 2>public bids, even names of it staff.

161
00:08:10.199 --> 00:08:12.439
<v Speaker 1>Wow, just from public records.

162
00:08:12.600 --> 00:08:16.439
<v Speaker 2>Yeah. For individuals, it might be subscriptions, online payment systems.

163
00:08:16.879 --> 00:08:19.560
<v Speaker 2>Any smart device holding financial info is a gold mine

164
00:08:19.600 --> 00:08:22.480
<v Speaker 2>for identity theft. It bundles so much together.

165
00:08:22.279 --> 00:08:24.639
<v Speaker 1>And social media. I mean, it feels so public, but

166
00:08:24.839 --> 00:08:26.160
<v Speaker 1>I bet it's a treasure trove for that.

167
00:08:26.240 --> 00:08:29.600
<v Speaker 2>Oh absolutely. Social media accounts are often a gateway. Get

168
00:08:29.639 --> 00:08:31.920
<v Speaker 2>access there, and suddenly you might find links to other

169
00:08:32.000 --> 00:08:35.840
<v Speaker 2>personal details. Passwords they've reused, email addresses, phone.

170
00:08:35.720 --> 00:08:37.559
<v Speaker 1>Numbers, which leads right to emails.

171
00:08:37.679 --> 00:08:40.559
<v Speaker 2>Emails are often the central hub, aren't they linked to everything?

172
00:08:41.039 --> 00:08:45.360
<v Speaker 2>Passwords resets, online accounts, payment confirmations. If a hacker gets

173
00:08:45.360 --> 00:08:48.919
<v Speaker 2>into your email, they could potentially unlock your entire digital life.

174
00:08:49.120 --> 00:08:52.840
<v Speaker 1>Yikes, And the source material explicitly calls out passwords as

175
00:08:52.840 --> 00:08:57.120
<v Speaker 1>being among the easiest targets because users are well negligent.

176
00:08:57.360 --> 00:09:02.000
<v Speaker 2>Well, it's harsh, but often true. Reuse passwords constantly, they

177
00:09:02.120 --> 00:09:05.080
<v Speaker 2>choose weak ones. It makes the hacker's job much much easier.

178
00:09:05.120 --> 00:09:08.320
<v Speaker 1>Okay, and then there's the physical side. Surprisingly, the source

179
00:09:08.320 --> 00:09:11.440
<v Speaker 1>says physical hardware access is maybe the easiest way to

180
00:09:11.480 --> 00:09:12.200
<v Speaker 1>steal info.

181
00:09:12.679 --> 00:09:15.440
<v Speaker 2>It really can be. If a hacker can physically get

182
00:09:15.480 --> 00:09:17.919
<v Speaker 2>their hands on your phone or computer, even for a

183
00:09:17.919 --> 00:09:21.840
<v Speaker 2>few minutes, they can pull browser history, check registry keys

184
00:09:21.879 --> 00:09:25.840
<v Speaker 2>for save credentials, maybe even install keyloggers or listening devices.

185
00:09:26.279 --> 00:09:29.600
<v Speaker 2>Direct access bypasses a lot of digital locks.

186
00:09:29.360 --> 00:09:32.320
<v Speaker 1>So our physical location can even become a target itself.

187
00:09:32.399 --> 00:09:35.039
<v Speaker 2>Yes, if other routes fail, they might try to find

188
00:09:35.039 --> 00:09:38.480
<v Speaker 2>the system's physical location. Every device has a max address

189
00:09:38.639 --> 00:09:42.399
<v Speaker 2>an IP address. When online, they can be tracked. Ackers,

190
00:09:42.440 --> 00:09:44.679
<v Speaker 2>of course, are usually very good at hiding their own location.

191
00:09:44.840 --> 00:09:48.000
<v Speaker 1>Okay, So to really protect yourself just building digital walls

192
00:09:48.120 --> 00:09:50.840
<v Speaker 1>isn't enough. You genuinely need to think like a thief.

193
00:09:51.639 --> 00:09:54.600
<v Speaker 1>What are those common weak spots? The vulnerabilities hackers love

194
00:09:54.639 --> 00:09:55.200
<v Speaker 1>to exploit.

195
00:09:55.360 --> 00:09:58.399
<v Speaker 2>They go for the path of police resistance, So unattended

196
00:09:58.440 --> 00:10:02.399
<v Speaker 2>devices laptops have to open in a cafe, weak or

197
00:10:02.440 --> 00:10:07.000
<v Speaker 2>reuse passwords, especially across sync devices. Users who just aren't

198
00:10:07.000 --> 00:10:10.159
<v Speaker 2>aware of how their systems work, or basic security hygiene,

199
00:10:10.759 --> 00:10:15.039
<v Speaker 2>unmonitored connection points like guest Wi Fi, and situations where

200
00:10:15.080 --> 00:10:18.639
<v Speaker 2>system administrators just aren't alerted when something weird happens. They

201
00:10:18.679 --> 00:10:21.480
<v Speaker 2>bank on systems not being as buttoned up as people assume,

202
00:10:21.559 --> 00:10:22.320
<v Speaker 2>and they're patient.

203
00:10:22.559 --> 00:10:24.759
<v Speaker 1>Right, It's not always a quick smash and grab.

204
00:10:24.879 --> 00:10:29.039
<v Speaker 2>Often not serious attackers might plant their tools slowly, move

205
00:10:29.080 --> 00:10:32.759
<v Speaker 2>carefully laterally across a network, trying to avoid setting off alarms.

206
00:10:33.120 --> 00:10:35.600
<v Speaker 2>They wait for the right moment, the most vulnerable state

207
00:10:35.799 --> 00:10:37.559
<v Speaker 2>before launching the main attack.

208
00:10:37.240 --> 00:10:39.600
<v Speaker 1>Which makes it absolutely critical for you to find your

209
00:10:39.639 --> 00:10:42.799
<v Speaker 1>own weaknesses first at waiting until your underattack is well

210
00:10:43.120 --> 00:10:43.519
<v Speaker 1>too late.

211
00:10:43.639 --> 00:10:45.799
<v Speaker 2>Precisely proactive defense is key.

212
00:10:45.879 --> 00:10:48.000
<v Speaker 1>Okay, so let's talk about setting up your own ethical

213
00:10:48.000 --> 00:10:50.879
<v Speaker 1>hacking plan. How do you establish clear goals for that?

214
00:10:50.960 --> 00:10:51.759
<v Speaker 1>How do you prepare?

215
00:10:52.120 --> 00:10:54.720
<v Speaker 2>Your main goal should be finding your own systems vulnerability

216
00:10:54.799 --> 00:10:57.399
<v Speaker 2>so you can fix them build robust security, and a

217
00:10:57.480 --> 00:11:00.559
<v Speaker 2>huge part of this, absolutely critical is documentation.

218
00:11:01.000 --> 00:11:03.240
<v Speaker 1>Documenting what exactly.

219
00:11:02.879 --> 00:11:06.399
<v Speaker 2>For your personal systems, keep track of your credentials, all

220
00:11:06.440 --> 00:11:09.759
<v Speaker 2>the software you use, the security tests you run. This

221
00:11:09.840 --> 00:11:12.519
<v Speaker 2>lets you retrace your steps if something goes wrong, and

222
00:11:12.559 --> 00:11:14.720
<v Speaker 2>it's vital proof if you ever need to show what

223
00:11:14.759 --> 00:11:17.120
<v Speaker 2>you did, especially in an organizational context.

224
00:11:17.240 --> 00:11:21.600
<v Speaker 1>Okay, solid advice. So you're ready to start testing, how

225
00:11:21.639 --> 00:11:24.360
<v Speaker 1>do you prioritize? It seems like there's so much you

226
00:11:24.360 --> 00:11:24.960
<v Speaker 1>could test.

227
00:11:25.399 --> 00:11:28.559
<v Speaker 2>It can feel overwhelming. Yeah, but you can focus it.

228
00:11:28.759 --> 00:11:32.320
<v Speaker 2>Ask yourself which systems would cause the absolute most trouble

229
00:11:32.399 --> 00:11:35.080
<v Speaker 2>if they got hit. Where would the biggest losses.

230
00:11:34.679 --> 00:11:37.039
<v Speaker 1>Be, right, the critical assets exactly?

231
00:11:37.519 --> 00:11:40.679
<v Speaker 2>Then which parts just look vulnerable maybe old software or

232
00:11:40.720 --> 00:11:44.279
<v Speaker 2>something you haven't updated in ages. And finally, what parts

233
00:11:44.279 --> 00:11:47.759
<v Speaker 2>are least documented, the things you rarely check or maybe

234
00:11:47.799 --> 00:11:50.519
<v Speaker 2>don't fully understand. Those are often good places to start

235
00:11:50.519 --> 00:11:51.200
<v Speaker 2>poking around.

236
00:11:51.559 --> 00:11:54.399
<v Speaker 1>And what specific types of systems should be on that

237
00:11:54.480 --> 00:11:55.159
<v Speaker 1>testing list?

238
00:11:55.480 --> 00:12:00.799
<v Speaker 2>Definitely your critical service, email, print file service, your fire obviously,

239
00:12:01.080 --> 00:12:05.320
<v Speaker 2>database servers, webservers, application servers, the operating systems themselves, both

240
00:12:05.399 --> 00:12:10.200
<v Speaker 2>client and server. And don't forget personal devices, tablets, laptops, workstations,

241
00:12:10.639 --> 00:12:13.759
<v Speaker 2>even the network gear itself like switches and routers.

242
00:12:13.320 --> 00:12:16.159
<v Speaker 1>And timing matters too. Right, not just what to test,

243
00:12:16.200 --> 00:12:18.240
<v Speaker 1>but when you don't want to crash your own system

244
00:12:18.320 --> 00:12:19.639
<v Speaker 1>during peak hours.

245
00:12:19.519 --> 00:12:23.440
<v Speaker 2>Oh crucially important, you absolutely want to run tests during

246
00:12:23.559 --> 00:12:27.480
<v Speaker 2>off peak times when disruption will be minimal. Imagine running

247
00:12:27.480 --> 00:12:30.519
<v Speaker 2>a denial of service test during a major online sale disaster,

248
00:12:30.960 --> 00:12:34.000
<v Speaker 2>and always always make sure everyone who might be affected

249
00:12:34.080 --> 00:12:36.320
<v Speaker 2>knows what you're doing and when get buy.

250
00:12:36.159 --> 00:12:39.799
<v Speaker 1>In right clear communication. Okay, So, once you've mapped out

251
00:12:39.840 --> 00:12:42.639
<v Speaker 1>your own potential week spots, the next step is understanding

252
00:12:42.679 --> 00:12:45.919
<v Speaker 1>how hackers gather info about you your network.

253
00:12:45.639 --> 00:12:47.480
<v Speaker 2>Those digital footprints we all leave.

254
00:12:47.440 --> 00:12:51.399
<v Speaker 1>Exactly your computer. Your online activities are constantly shetting data

255
00:12:51.480 --> 00:12:53.720
<v Speaker 1>to see what a potential attacker might see. You need

256
00:12:53.759 --> 00:12:56.919
<v Speaker 1>to understand OSENT open source intelligence techniques OSEND.

257
00:12:57.000 --> 00:12:59.960
<v Speaker 2>Okay, what does that involve? It starts simply just doing

258
00:13:00.080 --> 00:13:04.080
<v Speaker 2>online searches for yourself or your organization. Be amazed. What's

259
00:13:04.120 --> 00:13:10.399
<v Speaker 2>public patents, trademarks, sec filings, news releases about acquisitions, employee

260
00:13:10.399 --> 00:13:14.000
<v Speaker 2>contact details sometimes found on people search sites like US

261
00:13:14.039 --> 00:13:17.440
<v Speaker 2>search or zabasearch, or official sources like sec dot gov

262
00:13:17.440 --> 00:13:18.240
<v Speaker 2>for company info.

263
00:13:18.559 --> 00:13:21.720
<v Speaker 1>So even stuff we think of as just out there

264
00:13:21.879 --> 00:13:26.320
<v Speaker 1>can be weaponized. What about specific tools like Who's who is.

265
00:13:26.279 --> 00:13:29.960
<v Speaker 2>A classic example. Its main job is checking domain name availability,

266
00:13:30.279 --> 00:13:34.279
<v Speaker 2>but for registered domains, it reveals a lot registration details,

267
00:13:34.360 --> 00:13:37.919
<v Speaker 2>contact emails, phone numbers, even the specific DNS servers being

268
00:13:38.000 --> 00:13:42.360
<v Speaker 2>used more clues definitely, and public forums, Google groups they

269
00:13:42.360 --> 00:13:45.360
<v Speaker 2>can be gold mines too. People sometimes post network info,

270
00:13:45.480 --> 00:13:49.759
<v Speaker 2>IP addresses, user names, fqtns without realizing the risk. If

271
00:13:49.799 --> 00:13:52.000
<v Speaker 2>you ever find your confidential info post it somewhere like that,

272
00:13:52.039 --> 00:13:53.440
<v Speaker 2>you should definitely try to get it removed.

273
00:13:53.559 --> 00:13:57.080
<v Speaker 1>And privacy policies, that's ironic. They're meant to protect us,

274
00:13:57.080 --> 00:13:58.440
<v Speaker 1>but they can give hackers info.

275
00:13:58.639 --> 00:14:01.840
<v Speaker 2>It's a weird one, right. A good privacy policy tells

276
00:14:01.960 --> 00:14:05.600
<v Speaker 2>users how their data is protected, but it shouldn't spill

277
00:14:05.600 --> 00:14:09.360
<v Speaker 2>the beans on the specific network security setup, revealing details

278
00:14:09.360 --> 00:14:14.519
<v Speaker 2>about firewall types or specific protocols. That gives hackers a roadmap.

279
00:14:14.360 --> 00:14:17.240
<v Speaker 1>A roadmap to breach the system. Okay, So the hacker

280
00:14:17.320 --> 00:14:21.360
<v Speaker 1>gathers all this ocent then they start scanning for vulnerabilities, right,

281
00:14:21.399 --> 00:14:22.200
<v Speaker 1>what are they looking for?

282
00:14:22.240 --> 00:14:24.720
<v Speaker 2>Then they use the info they gather to connect the

283
00:14:24.759 --> 00:14:28.639
<v Speaker 2>dots whose data helps map host names to IP addresses.

284
00:14:29.279 --> 00:14:32.399
<v Speaker 2>Then they start scanning. They'll scan internally, maybe looking for

285
00:14:32.480 --> 00:14:35.559
<v Speaker 2>rogue devices, and they'll scan from the outside in looking

286
00:14:35.559 --> 00:14:38.399
<v Speaker 2>for open ports using tools like endmap or super scan.

287
00:14:38.879 --> 00:14:40.960
<v Speaker 1>And they use the sniffers again like wire shark.

288
00:14:41.120 --> 00:14:43.600
<v Speaker 2>Yeah, to analyze the traffic, see what's visible from an

289
00:14:43.639 --> 00:14:46.919
<v Speaker 2>external perspective, what data is just flying around in the clear.

290
00:14:46.799 --> 00:14:49.240
<v Speaker 1>And what kind of sensitive stuff do these open port

291
00:14:49.320 --> 00:14:53.559
<v Speaker 1>scans actually reveal? What can a hacker learn a surprising amount.

292
00:14:53.919 --> 00:14:56.080
<v Speaker 2>They can see what VPN services you might be running,

293
00:14:56.120 --> 00:15:01.399
<v Speaker 2>like IPsec or sslvpns. They identify active services email servers, databases,

294
00:15:01.440 --> 00:15:05.240
<v Speaker 2>web servers. They can figure out authentication requirements for network shares,

295
00:15:05.759 --> 00:15:08.279
<v Speaker 2>and they see what remote access services are available like

296
00:15:08.360 --> 00:15:12.360
<v Speaker 2>remote desktop, ssh, V and C. Each open port is

297
00:15:12.360 --> 00:15:13.879
<v Speaker 2>like a potential unlocked door.

298
00:15:14.519 --> 00:15:17.200
<v Speaker 1>So once a hacker finds these vulnerabilities, what are their

299
00:15:17.279 --> 00:15:19.759
<v Speaker 1>end goals? What are the malicious actions they're aiming for?

300
00:15:19.960 --> 00:15:23.000
<v Speaker 2>Oh, the list is long. They might try to capture

301
00:15:23.039 --> 00:15:25.759
<v Speaker 2>your screen while you're working on sensitive files, get direct

302
00:15:25.799 --> 00:15:28.639
<v Speaker 2>access to that data, send emails or files, pretending to

303
00:15:28.639 --> 00:15:32.720
<v Speaker 2>be an administrator, remotely stop or start critical applications, get

304
00:15:32.720 --> 00:15:36.279
<v Speaker 2>a remote command prompt for full control, disable security software,

305
00:15:36.480 --> 00:15:39.679
<v Speaker 2>launch denial of service attacks, performs sqal injection to mess

306
00:15:39.720 --> 00:15:42.600
<v Speaker 2>with databases or even upload their attack files, turning your

307
00:15:42.639 --> 00:15:44.720
<v Speaker 2>system into a launch pad for more attacks.

308
00:15:44.799 --> 00:15:47.720
<v Speaker 1>Wow, okay, And these attacks generally fall into different types, right,

309
00:15:47.759 --> 00:15:49.799
<v Speaker 1>passive versus active. What's the difference.

310
00:15:50.080 --> 00:15:53.600
<v Speaker 2>Think of a passive attack as reconnaissance. The hacker is

311
00:15:53.679 --> 00:15:57.360
<v Speaker 2>just observing, watching your network structure, the software, you use,

312
00:15:57.480 --> 00:16:01.120
<v Speaker 2>your security measures, but they're not actually chained anything, just

313
00:16:01.200 --> 00:16:03.759
<v Speaker 2>gathering intel, waiting for an opening.

314
00:16:03.519 --> 00:16:05.200
<v Speaker 1>Like a digital stakeout exactly.

315
00:16:05.679 --> 00:16:09.200
<v Speaker 2>Now, passive attacks can involve active reconnaissance, which sounds contradictory,

316
00:16:09.679 --> 00:16:12.480
<v Speaker 2>but it means the intruder does engage the target, maybe

317
00:16:12.559 --> 00:16:16.279
<v Speaker 2>with port scanning to find those weak points. Usually defend

318
00:16:16.320 --> 00:16:19.720
<v Speaker 2>against this with things like intrusion prevention systems IPS and

319
00:16:19.759 --> 00:16:20.559
<v Speaker 2>good firewalls.

320
00:16:20.600 --> 00:16:23.039
<v Speaker 1>Okay, And the other type of passive that's.

321
00:16:22.960 --> 00:16:26.159
<v Speaker 2>Passive reconnaissance where they studied the system without direct interaction.

322
00:16:26.960 --> 00:16:31.039
<v Speaker 2>Classic examples are war driving, driving around looking for unsecured WiFi.

323
00:16:31.120 --> 00:16:33.000
<v Speaker 1>People still do that, oh yeah.

324
00:16:33.080 --> 00:16:36.720
<v Speaker 2>And dumpster diving literally going through trash for discarded documents

325
00:16:36.759 --> 00:16:39.799
<v Speaker 2>or hard drives, or even just masquerading maybe pretending to

326
00:16:39.799 --> 00:16:42.559
<v Speaker 2>be someone else online to gather info indirectly.

327
00:16:42.679 --> 00:16:45.120
<v Speaker 1>Of course, that's passive observation. Then you have the direct

328
00:16:45.159 --> 00:16:47.919
<v Speaker 1>assaults active attacks, right.

329
00:16:48.240 --> 00:16:50.279
<v Speaker 2>These are the ones where the hacker actively tries to

330
00:16:50.360 --> 00:16:53.200
<v Speaker 2>change data or create new data, usually to set up

331
00:16:53.240 --> 00:16:57.519
<v Speaker 2>further exploits. A common one is a masquerade attack. Masquerade, Yeah,

332
00:16:57.559 --> 00:17:00.200
<v Speaker 2>the hacker pretends to be a legitimate user, The use

333
00:17:00.240 --> 00:17:04.759
<v Speaker 2>stolen credentials IDs passwords to get deeper access. Once inside,

334
00:17:04.799 --> 00:17:07.920
<v Speaker 2>they might modify files, delete data, or even kick the

335
00:17:07.960 --> 00:17:09.640
<v Speaker 2>real authorized user off the system.

336
00:17:10.039 --> 00:17:13.079
<v Speaker 1>That really shows why stolen passwords are so dangerous. What

337
00:17:13.200 --> 00:17:15.200
<v Speaker 1>about something called a session replay?

338
00:17:15.319 --> 00:17:18.640
<v Speaker 2>A session replay attack uses a stolen session ID. You

339
00:17:18.680 --> 00:17:20.839
<v Speaker 2>know how websites sometimes keep you log in? Uh huh?

340
00:17:21.039 --> 00:17:24.160
<v Speaker 2>That uses a session ID. If a hacker steals that ID,

341
00:17:24.599 --> 00:17:27.599
<v Speaker 2>they can sometimes reuse it to automatically authenticate as you

342
00:17:28.119 --> 00:17:31.720
<v Speaker 2>on that website without needing your password. It exploits how

343
00:17:31.759 --> 00:17:35.200
<v Speaker 2>sites handle sessions, cookies, forms. Often you only find out

344
00:17:35.240 --> 00:17:37.880
<v Speaker 2>after your identity has been compromised because the initial attack

345
00:17:38.000 --> 00:17:40.119
<v Speaker 2>is an obvious in real time sneaky.

346
00:17:40.200 --> 00:17:43.720
<v Speaker 1>And then the big ones denial of service at US

347
00:17:43.960 --> 00:17:46.519
<v Speaker 1>and distributed denial of services.

348
00:17:46.920 --> 00:17:50.400
<v Speaker 2>Yeah, these are about disruption, not usually data theft. Directly,

349
00:17:50.839 --> 00:17:53.839
<v Speaker 2>they flood a service or server with so much traffic

350
00:17:53.920 --> 00:17:56.440
<v Speaker 2>or so many requests that it gets overwhelmed and crashes

351
00:17:56.519 --> 00:17:59.319
<v Speaker 2>or slows to a crawl. Legitimate users can't get.

352
00:17:59.200 --> 00:18:04.000
<v Speaker 1>Access costing chaos, potentially huge financial loss. If it's a business.

353
00:18:03.920 --> 00:18:07.319
<v Speaker 2>Exactly or just rendering a system useless signs you might

354
00:18:07.359 --> 00:18:11.759
<v Speaker 2>be hit really slow network performance, suddenly can't access certain websites,

355
00:18:11.960 --> 00:18:14.960
<v Speaker 2>or maybe a huge unexplained flood of spam or weird

356
00:18:15.000 --> 00:18:15.799
<v Speaker 2>network traffic.

357
00:18:15.920 --> 00:18:19.119
<v Speaker 1>Okay, so we know how they find targets, the kinds

358
00:18:19.160 --> 00:18:22.359
<v Speaker 1>of attacks. Let's talk about the hackers arsenal. What tools

359
00:18:22.400 --> 00:18:23.359
<v Speaker 1>are they actually using.

360
00:18:23.680 --> 00:18:26.000
<v Speaker 2>There's a massive number of tools out there available to

361
00:18:26.039 --> 00:18:30.240
<v Speaker 2>both ethical hackers and criminals. Understanding the categories of tools

362
00:18:30.240 --> 00:18:32.279
<v Speaker 2>is helpful. You've got things like network scanners, as we

363
00:18:32.359 --> 00:18:35.960
<v Speaker 2>mentioned from mapping networks and finding open ports. Tools like

364
00:18:36.000 --> 00:18:37.440
<v Speaker 2>Angry IP scanner fall.

365
00:18:37.359 --> 00:18:39.599
<v Speaker 1>Into this, and password crackers.

366
00:18:39.279 --> 00:18:43.759
<v Speaker 2>Definitely, password cracking tools tried to guess or brute force passwords.

367
00:18:43.960 --> 00:18:46.440
<v Speaker 2>Canaan Able is a well known one, especially for Windows.

368
00:18:46.720 --> 00:18:48.880
<v Speaker 2>John the Ripper is another classic brute forcer.

369
00:18:48.920 --> 00:18:50.680
<v Speaker 1>I've heard calli Linux mentioned a lot.

370
00:18:50.880 --> 00:18:53.160
<v Speaker 2>Is that a tool or Collie Linux is more like

371
00:18:53.160 --> 00:18:58.400
<v Speaker 2>a whole toolkit. It's a specialized Linux distribution, absolutely packed

372
00:18:58.519 --> 00:19:01.519
<v Speaker 2>with security and penetration tests tools. You can often run

373
00:19:01.559 --> 00:19:03.359
<v Speaker 2>it right off a USB stick. You can do tons

374
00:19:03.400 --> 00:19:07.920
<v Speaker 2>of stuff, create fake networks, spoof messages, crack Wi Fi passwords.

375
00:19:08.359 --> 00:19:09.400
<v Speaker 2>It's very powerful.

376
00:19:09.480 --> 00:19:11.000
<v Speaker 1>Okay, what else is key?

377
00:19:11.519 --> 00:19:15.319
<v Speaker 2>You have vulnerability exploitation frameworks. The big one is metasploid.

378
00:19:15.480 --> 00:19:19.000
<v Speaker 2>It helps find security flaws, verify fixes, and can even

379
00:19:19.039 --> 00:19:22.000
<v Speaker 2>be used for things like masking your identity during tests.

380
00:19:23.000 --> 00:19:26.720
<v Speaker 2>Then there are web application proxies like burp suite, essential

381
00:19:26.799 --> 00:19:30.599
<v Speaker 2>for finding website vulnerabilities, messing with cookies, probing web apps

382
00:19:30.799 --> 00:19:32.519
<v Speaker 2>crucial for man in the middle stuff.

383
00:19:32.559 --> 00:19:34.160
<v Speaker 1>And those sniffers again, yep.

384
00:19:34.319 --> 00:19:37.279
<v Speaker 2>Packet sniffers like wire shark are fundamental for seeing the traffic,

385
00:19:37.680 --> 00:19:41.079
<v Speaker 2>sometimes used alongside tools like air cracking for Wi Fi hacking.

386
00:19:41.640 --> 00:19:44.480
<v Speaker 2>Wire shark captures the packets, aircrack tries to crack the

387
00:19:44.519 --> 00:19:45.680
<v Speaker 2>password from that data.

388
00:19:45.720 --> 00:19:48.279
<v Speaker 1>So these aren't just abstract ideas. These are the actual

389
00:19:48.319 --> 00:19:49.519
<v Speaker 1>tools being used out there.

390
00:19:49.559 --> 00:19:52.880
<v Speaker 2>Absolutely knowing the tools helps you understand the capabilities you're

391
00:19:52.960 --> 00:19:55.079
<v Speaker 2>up against and how you might defend yourself.

392
00:19:55.240 --> 00:19:58.240
<v Speaker 1>And a big part of their capability is deception. Right

393
00:19:58.839 --> 00:20:01.960
<v Speaker 1>this idea of spoof what exactly does that mean?

394
00:20:02.000 --> 00:20:05.599
<v Speaker 2>Spoofing is all about disguise. A hacker pretends to be

395
00:20:05.680 --> 00:20:10.359
<v Speaker 2>someone or something else, another person, a trusted organization, a

396
00:20:10.440 --> 00:20:14.480
<v Speaker 2>legitimate piece of software, even a website. The goal is

397
00:20:14.519 --> 00:20:17.960
<v Speaker 2>to trick security systems or users into giving them access

398
00:20:18.039 --> 00:20:19.079
<v Speaker 2>or information so.

399
00:20:19.000 --> 00:20:21.720
<v Speaker 1>They can fake more than just an email sender.

400
00:20:21.839 --> 00:20:24.920
<v Speaker 2>Oh yeah, there's IP spoofing, where they hide their real

401
00:20:24.960 --> 00:20:27.799
<v Speaker 2>IP address and make malicious network packets look like they

402
00:20:27.799 --> 00:20:30.680
<v Speaker 2>came from a trusted source, makes tracing them really hard.

403
00:20:31.160 --> 00:20:32.319
<v Speaker 2>Then there's DNS spoofing.

404
00:20:32.319 --> 00:20:33.079
<v Speaker 1>How does that work?

405
00:20:33.200 --> 00:20:35.720
<v Speaker 2>That redirects you to a fake, malicious website when you

406
00:20:35.720 --> 00:20:38.200
<v Speaker 2>think you're going to a legitimate one like your bank.

407
00:20:38.559 --> 00:20:41.240
<v Speaker 2>They do this to harvest your log in details. Usually

408
00:20:41.359 --> 00:20:43.359
<v Speaker 2>requires a hacker to be on the same local.

409
00:20:43.119 --> 00:20:46.160
<v Speaker 1>Network though, and email spoofing we've probably all seen right.

410
00:20:46.319 --> 00:20:49.359
<v Speaker 2>Email spoofing making malicious emails look like they came from

411
00:20:49.400 --> 00:20:54.200
<v Speaker 2>a legitimate source bypassing spam filters often carrying malware attachments,

412
00:20:54.559 --> 00:20:58.119
<v Speaker 2>and even phone number spoofing using fake caller IDs. The

413
00:20:58.160 --> 00:21:00.720
<v Speaker 2>real danger with all spoofing is how hard it can

414
00:21:00.720 --> 00:21:04.200
<v Speaker 2>be to spot. It. Lets attackers blend in, interact, and

415
00:21:04.279 --> 00:21:07.559
<v Speaker 2>manipulate things without raising immediate alarms, which.

416
00:21:07.359 --> 00:21:09.759
<v Speaker 1>Seems like a perfect setup for the next step. The

417
00:21:09.799 --> 00:21:12.480
<v Speaker 1>man in the middle attack or MAYTM.

418
00:21:12.079 --> 00:21:15.319
<v Speaker 2>Exactly my PM is often the follow up to successful spoofing.

419
00:21:15.799 --> 00:21:19.680
<v Speaker 2>It typically involves something called ARP spoofing RP speefing yeah

420
00:21:19.759 --> 00:21:23.880
<v Speaker 2>Address resolution protocol on a local network. Devices use ARP

421
00:21:24.359 --> 00:21:27.400
<v Speaker 2>to find each other's physical AMC addresses based on their

422
00:21:27.440 --> 00:21:32.480
<v Speaker 2>IP addresses. In ARP spoofing, the hacker sends fake ARP messages,

423
00:21:32.599 --> 00:21:35.559
<v Speaker 2>essentially telling your computer, hey, I'm the router, and telling

424
00:21:35.599 --> 00:21:36.960
<v Speaker 2>the router, hey I'm that computer.

425
00:21:37.720 --> 00:21:40.440
<v Speaker 1>So they insert themselves right into the conversation precisely.

426
00:21:40.480 --> 00:21:43.200
<v Speaker 2>They position their machine logically between you and the router

427
00:21:43.440 --> 00:21:46.160
<v Speaker 2>or between two communicating devices. All the data flows through.

428
00:21:46.000 --> 00:21:48.240
<v Speaker 1>Them first, and once they're in the middle, what can

429
00:21:48.279 --> 00:21:50.440
<v Speaker 1>they actually do with that traffic hold on?

430
00:21:50.839 --> 00:21:54.200
<v Speaker 2>They can perform session hijacking, stealing those session ideas we

431
00:21:54.240 --> 00:21:56.960
<v Speaker 2>talked about to access your accounts. Later, they could launch

432
00:21:56.960 --> 00:21:59.920
<v Speaker 2>a targeted denial of service by flooding one specific device

433
00:22:00.279 --> 00:22:03.359
<v Speaker 2>with all the traffic they intercept, or the classic MITM,

434
00:22:03.759 --> 00:22:06.400
<v Speaker 2>they can just read, modify, or inject data into the

435
00:22:06.400 --> 00:22:09.279
<v Speaker 2>communication stream between the two victims who think they're talking

436
00:22:09.319 --> 00:22:10.279
<v Speaker 2>directly and securely.

437
00:22:10.599 --> 00:22:13.279
<v Speaker 1>That sounds incredibly powerful. Can you give us just a

438
00:22:13.319 --> 00:22:17.839
<v Speaker 1>conceptual idea of how ARP spoofing might work in practice

439
00:22:18.160 --> 00:22:19.519
<v Speaker 1>without the actual commands.

440
00:22:19.759 --> 00:22:23.039
<v Speaker 2>Sure, Conceptually, imagine the hackers on the same wy Fine

441
00:22:23.079 --> 00:22:25.880
<v Speaker 2>network as you. They run a tool. This tool starts

442
00:22:25.920 --> 00:22:29.400
<v Speaker 2>sending out those fake ARP messages. One message goes to

443
00:22:29.400 --> 00:22:32.000
<v Speaker 2>your laptop saying the hackers MSS address belongs to the

444
00:22:32.079 --> 00:22:34.920
<v Speaker 2>router's IP address. Another message goes to the router saying

445
00:22:34.920 --> 00:22:37.839
<v Speaker 2>the hackers m AS address belongs to your laptop's IP address.

446
00:22:38.319 --> 00:22:40.960
<v Speaker 2>Now both your laptop and the router send traffic intended

447
00:22:41.000 --> 00:22:44.079
<v Speaker 2>for each other to the hacker's machine instead. The hacker's

448
00:22:44.119 --> 00:22:47.000
<v Speaker 2>machine then forwards it along. So everything still seems to work,

449
00:22:47.319 --> 00:22:48.000
<v Speaker 2>but they see it.

450
00:22:47.960 --> 00:22:52.559
<v Speaker 1>All and they capture everything going through, including passwords if.

451
00:22:52.519 --> 00:22:56.319
<v Speaker 2>They're sent unencrypted. Yes, And the really scary part for you,

452
00:22:56.400 --> 00:23:00.839
<v Speaker 2>the listener, is how often people reuse passwords. Hacker intercepts

453
00:23:00.839 --> 00:23:04.039
<v Speaker 2>one password this way, they'll immediately try it on your email,

454
00:23:04.119 --> 00:23:07.319
<v Speaker 2>your bank, everything else. One breach can cascade.

455
00:23:07.759 --> 00:23:11.400
<v Speaker 1>That's a really sobering thought. Passwords they really are often

456
00:23:11.440 --> 00:23:13.480
<v Speaker 1>the weakest link, aren't they. Why are they just so

457
00:23:13.519 --> 00:23:14.559
<v Speaker 1>inherently vulnerable?

458
00:23:15.039 --> 00:23:18.319
<v Speaker 2>Well, fundamentally they rely on secrecy, and once that secret

459
00:23:18.359 --> 00:23:21.640
<v Speaker 2>is out, accountability just vanishes. Anyone could be using it,

460
00:23:22.200 --> 00:23:25.759
<v Speaker 2>But the biggest issue users We share them, we write

461
00:23:25.759 --> 00:23:29.680
<v Speaker 2>them down, and crucially, we reuse them constantly. That reuse

462
00:23:29.759 --> 00:23:33.880
<v Speaker 2>makes one single compromised password a potential skeleton key to

463
00:23:34.000 --> 00:23:34.640
<v Speaker 2>many doors.

464
00:23:34.920 --> 00:23:37.759
<v Speaker 1>Okay, so, besides tricking people or finding them written down,

465
00:23:38.160 --> 00:23:41.559
<v Speaker 1>how do hackers actually crack passwords technically? What methods do

466
00:23:41.599 --> 00:23:42.200
<v Speaker 1>they use.

467
00:23:42.240 --> 00:23:45.799
<v Speaker 2>These specialized tools and techniques. Passwords usually aren't stored in

468
00:23:45.839 --> 00:23:48.799
<v Speaker 2>plain text. Thankfully, they're hashed, turned into a unique string

469
00:23:48.839 --> 00:23:51.559
<v Speaker 2>of characters using a one way algorithm you can't easily

470
00:23:51.559 --> 00:23:55.359
<v Speaker 2>reverse it. Linux systems often add salt two random data

471
00:23:55.359 --> 00:23:58.519
<v Speaker 2>mixed in before hashing to make identical passwords look different.

472
00:23:58.680 --> 00:24:00.759
<v Speaker 1>But hackers try to crack the hashes anyway.

473
00:24:00.839 --> 00:24:03.599
<v Speaker 2>Oh yeah, they use several methods. The most common is

474
00:24:03.640 --> 00:24:07.519
<v Speaker 2>a dictionary attack. The tool tries words from massive lists,

475
00:24:07.799 --> 00:24:13.200
<v Speaker 2>actual dictionary words, common names, common substitutions like a for at,

476
00:24:13.519 --> 00:24:18.079
<v Speaker 2>even known breached passwords, including common misspellings.

477
00:24:17.440 --> 00:24:20.920
<v Speaker 1>Like patword, trying all the common guesses first exactly.

478
00:24:21.359 --> 00:24:24.000
<v Speaker 2>If that fails, they might try a brute force attack.

479
00:24:24.359 --> 00:24:28.599
<v Speaker 2>This just tries every single possible combination of letters, numbers, symbols.

480
00:24:28.960 --> 00:24:31.920
<v Speaker 2>It will eventually find any password, but for strong long

481
00:24:32.079 --> 00:24:37.160
<v Speaker 2>complex ones. It can take an infeasibly long time years centuries, even.

482
00:24:37.000 --> 00:24:39.799
<v Speaker 1>So complexity really helps there. What about rainbow attacks.

483
00:24:40.000 --> 00:24:43.440
<v Speaker 2>Rainbow attacks use precomputed tables of hashes for common passwords.

484
00:24:43.680 --> 00:24:46.440
<v Speaker 2>It's much faster than brute forcing hashes directly, but the

485
00:24:46.480 --> 00:24:49.839
<v Speaker 2>tables are huge, and they're generally less effective against longer passwords,

486
00:24:49.880 --> 00:24:52.400
<v Speaker 2>say over fourteen characters or assaulted hashes.

487
00:24:52.480 --> 00:24:54.799
<v Speaker 1>Okay, so cracking is one way. What are some other,

488
00:24:55.039 --> 00:24:58.119
<v Speaker 1>maybe less direct ways hackers uncover passwords?

489
00:24:58.519 --> 00:25:00.920
<v Speaker 2>There are quite a few. Keystroke law is a big one.

490
00:25:00.960 --> 00:25:05.440
<v Speaker 2>That's malware or sometimes even physical hardware that secretly records

491
00:25:05.480 --> 00:25:08.440
<v Speaker 2>everything you type, including passwords as you enterre them.

492
00:25:08.480 --> 00:25:10.119
<v Speaker 1>Ooh nasty.

493
00:25:10.440 --> 00:25:15.160
<v Speaker 2>Very Hackers also look for weak passwords storage. Some applications

494
00:25:15.279 --> 00:25:18.839
<v Speaker 2>carelessly might store passwords locally on your machine in poorly

495
00:25:18.880 --> 00:25:24.160
<v Speaker 2>secured files, sometimes even plain text. Also weak bios passwords.

496
00:25:24.640 --> 00:25:28.000
<v Speaker 2>The password protecting your computer's basic startup can sometimes be

497
00:25:28.119 --> 00:25:31.920
<v Speaker 2>reset with physical access, like removing the little CMOS battery

498
00:25:31.920 --> 00:25:35.519
<v Speaker 2>on the motherboard or just looking up default manufacturer passwords online.

499
00:25:35.559 --> 00:25:37.680
<v Speaker 1>And they can even grab password hashes remotely.

500
00:25:37.839 --> 00:25:41.200
<v Speaker 2>Yes, if they can exploit another vulnerability to get system access.

501
00:25:41.519 --> 00:25:44.200
<v Speaker 2>So using minisploit. Once they have that access, they can

502
00:25:44.200 --> 00:25:47.279
<v Speaker 2>often run commands like hash dump on Windows to extract

503
00:25:47.279 --> 00:25:49.680
<v Speaker 2>the stored password hashes from the system. They can then

504
00:25:49.720 --> 00:25:51.880
<v Speaker 2>take those hashes offline and try to crack them at

505
00:25:51.880 --> 00:25:54.920
<v Speaker 2>their leisure using those dictionary or brute force methods.

506
00:25:55.279 --> 00:25:57.599
<v Speaker 1>Wow, the idea of passwords just being pulled off your

507
00:25:57.640 --> 00:26:02.759
<v Speaker 1>machine remotely is unsettling. Okay, let's shift to networks. Hacking

508
00:26:02.799 --> 00:26:05.480
<v Speaker 1>network connections seems like a really attractive target.

509
00:26:05.519 --> 00:26:08.960
<v Speaker 2>Why is that several reasons. It allows the hacker to

510
00:26:09.039 --> 00:26:11.119
<v Speaker 2>hide their own identity better. They might be able to

511
00:26:11.119 --> 00:26:14.559
<v Speaker 2>piggyback on your connection for free bandwidth, But the biggest

512
00:26:14.559 --> 00:26:18.079
<v Speaker 2>prize is often decrypting the traffic flowing over that network.

513
00:26:18.400 --> 00:26:20.559
<v Speaker 2>See what everyone else is doing, what data they're sending.

514
00:26:20.839 --> 00:26:23.400
<v Speaker 2>Access to that data stream is incredibly valuable.

515
00:26:23.480 --> 00:26:28.079
<v Speaker 1>And when we talk wireless security, we hear terms like WEP, WPA,

516
00:26:28.279 --> 00:26:31.079
<v Speaker 1>WPA two. Can you break down those levels of protection?

517
00:26:31.240 --> 00:26:34.559
<v Speaker 2>Sure, they represent an evolution, each trying to fix the

518
00:26:34.559 --> 00:26:38.920
<v Speaker 2>flaws of the previous one. WEP wired equivalent privacy is

519
00:26:38.920 --> 00:26:41.680
<v Speaker 2>the oldest and weakest. It's considered totally broken now very

520
00:26:41.720 --> 00:26:44.200
<v Speaker 2>easy to crack because of flaws in its encryption design,

521
00:26:44.680 --> 00:26:49.000
<v Speaker 2>specifically a small predictable initialization vector. Don't use it.

522
00:26:48.880 --> 00:26:51.480
<v Speaker 1>Ever, Okay, WEP is out. What came next?

523
00:26:51.559 --> 00:26:54.880
<v Speaker 2>WPA the first version of Wi Fi Protected Access. It

524
00:26:54.880 --> 00:26:58.440
<v Speaker 2>improved on WP, using something called TKP for encryption, but

525
00:26:58.480 --> 00:27:01.559
<v Speaker 2>it still had some underlying WAE elements, so it wasn't perfect.

526
00:27:01.880 --> 00:27:05.400
<v Speaker 2>Better but still vulnerable. Then WPA two right, WP two

527
00:27:05.559 --> 00:27:08.960
<v Speaker 2>is the standard. Now you mostly see WPA two PSK

528
00:27:09.200 --> 00:27:12.400
<v Speaker 2>pre shared key in homes and small businesses. It uses

529
00:27:12.440 --> 00:27:15.039
<v Speaker 2>a password the pre shared key, and it's much more

530
00:27:15.039 --> 00:27:18.039
<v Speaker 2>secure than WEP or WPA one if you use a

531
00:27:18.039 --> 00:27:21.400
<v Speaker 2>strong password. Weak passwords can still be brute forced, and

532
00:27:21.440 --> 00:27:25.519
<v Speaker 2>the strongest version that's typically WPA two AES, often called

533
00:27:25.680 --> 00:27:30.240
<v Speaker 2>WPA two Enterprise. It uses the strong AES encryption standard

534
00:27:30.440 --> 00:27:33.839
<v Speaker 2>and usually requires users to authenticate against a central server

535
00:27:34.079 --> 00:27:37.319
<v Speaker 2>like Radius. This is common in larger organizations and is

536
00:27:37.400 --> 00:27:38.519
<v Speaker 2>very difficult to bypass.

537
00:27:38.880 --> 00:27:41.240
<v Speaker 1>Just to really hit home how weak the old stuff

538
00:27:41.319 --> 00:27:44.640
<v Speaker 1>is conceptually? How easy is it to hack a WEP connection?

539
00:27:44.880 --> 00:27:47.119
<v Speaker 1>Not a step by step, but what's the core weakness?

540
00:27:47.240 --> 00:27:49.720
<v Speaker 2>The core weakness in WEP is that its encryption key

541
00:27:49.799 --> 00:27:53.440
<v Speaker 2>usage is predictable and repeats. A hacker puts their wireless

542
00:27:53.440 --> 00:27:56.839
<v Speaker 2>card into promiscuous mode to capture all nearby Wi Fi traffic.

543
00:27:57.240 --> 00:27:59.319
<v Speaker 2>They then inject certain types of traffic to force the

544
00:27:59.319 --> 00:28:02.680
<v Speaker 2>network to generate lots of response packets. By analyzing enough

545
00:28:02.720 --> 00:28:04.960
<v Speaker 2>of these packets, often just a few minutes worth, they

546
00:28:05.000 --> 00:28:08.720
<v Speaker 2>can mathematically deduce the WEP key. It's a fundamental design.

547
00:28:08.400 --> 00:28:11.759
<v Speaker 1>Flaw, alarmingly simple when you put it that way. Okay,

548
00:28:11.799 --> 00:28:15.920
<v Speaker 1>what about this evil twin access point attack? That sounds dramatic.

549
00:28:16.200 --> 00:28:18.920
<v Speaker 2>It's a pretty sneaky social engineering type of network attack.

550
00:28:19.559 --> 00:28:22.519
<v Speaker 2>The hacker sets up their own wireless access point, but

551
00:28:22.640 --> 00:28:25.359
<v Speaker 2>configures it to look exactly like a legitimate one you

552
00:28:25.440 --> 00:28:28.559
<v Speaker 2>might trust, like the coffee shops Wi Fi or your

553
00:28:28.599 --> 00:28:33.000
<v Speaker 2>office network. Same name, maybe even similar signal strength.

554
00:28:32.960 --> 00:28:35.720
<v Speaker 1>So it mimics a trusted network. How do they get

555
00:28:35.759 --> 00:28:36.440
<v Speaker 1>you to connect?

556
00:28:36.799 --> 00:28:38.839
<v Speaker 2>Often, though, first try to kick you off the real

557
00:28:38.880 --> 00:28:43.000
<v Speaker 2>network using de authentication packets. Your device gets disconnected, then

558
00:28:43.079 --> 00:28:46.960
<v Speaker 2>automatically scans for networks to rejoin. The hacker might boost

559
00:28:47.039 --> 00:28:49.400
<v Speaker 2>the signal of their evil twins so it appears stronger

560
00:28:49.480 --> 00:28:51.759
<v Speaker 2>or closer than the real one. Your device might just

561
00:28:51.839 --> 00:28:54.000
<v Speaker 2>automatically connect to the stronger signal.

562
00:28:53.799 --> 00:28:57.720
<v Speaker 1>And once you're connected to their network, game over pretty much.

563
00:28:58.440 --> 00:29:01.319
<v Speaker 2>Once you're connected to the evil twin, the hacker is

564
00:29:01.400 --> 00:29:03.599
<v Speaker 2>now the man in the middle. They can use tools

565
00:29:03.640 --> 00:29:07.720
<v Speaker 2>like entercap to intercept all your traffic, analyze it, steal credentials,

566
00:29:07.799 --> 00:29:11.359
<v Speaker 2>inject malware, redirect you to fake websites. They have full

567
00:29:11.359 --> 00:29:14.680
<v Speaker 2>control over your connection. It's worth noting, though, that messing

568
00:29:14.680 --> 00:29:17.680
<v Speaker 2>with signal strengths and channels can have legal consequences in

569
00:29:17.720 --> 00:29:18.640
<v Speaker 2>places like the US.

570
00:29:18.839 --> 00:29:22.480
<v Speaker 1>Good caveat okay. Shifting from networks to the devices in

571
00:29:22.519 --> 00:29:25.960
<v Speaker 1>our pockets. Mobile devices they hold so much personal info?

572
00:29:26.000 --> 00:29:27.079
<v Speaker 1>Are they major targets?

573
00:29:27.200 --> 00:29:33.160
<v Speaker 2>Huge targets? Absolutely? Think about it. Location, data, emails, calls, texts, browsing, history, photos,

574
00:29:33.240 --> 00:29:37.279
<v Speaker 2>banking apps. It's all there, and sometimes security practices on

575
00:29:37.359 --> 00:29:40.799
<v Speaker 2>mobile aren't as rigorous as on PCs, making them potentially

576
00:29:40.839 --> 00:29:41.680
<v Speaker 2>easier targets.

577
00:29:41.720 --> 00:29:44.599
<v Speaker 1>What can hackers actually do if they compromise a mobile.

578
00:29:44.359 --> 00:29:47.799
<v Speaker 2>Device a lot track your location in real time, access

579
00:29:47.839 --> 00:29:51.440
<v Speaker 2>your emails, calls, messages, see what websites you visit, view

580
00:29:51.480 --> 00:29:54.440
<v Speaker 2>your photos and files. They could potentially send remote commands

581
00:29:54.480 --> 00:29:57.680
<v Speaker 2>to the device, install more malware, or even spoof messages

582
00:29:57.680 --> 00:29:59.519
<v Speaker 2>and calls from your device, making it.

583
00:29:59.440 --> 00:30:01.880
<v Speaker 1>Look like they can from you, and the source calls.

584
00:30:01.960 --> 00:30:06.559
<v Speaker 1>Mobile app hacking low hanging fruit. Why are apps so vulnerable?

585
00:30:06.759 --> 00:30:11.119
<v Speaker 2>Primarily because the executable code. For many apps, the binary

586
00:30:11.160 --> 00:30:14.920
<v Speaker 2>code is relatively accessible. Hackers can often download an app,

587
00:30:15.039 --> 00:30:17.759
<v Speaker 2>decopile it, and look at the code. This makes it

588
00:30:17.799 --> 00:30:18.759
<v Speaker 2>easier to modify it.

589
00:30:18.920 --> 00:30:19.480
<v Speaker 1>Modify it.

590
00:30:19.519 --> 00:30:22.359
<v Speaker 2>How they could remove security checks or ads. They could

591
00:30:22.359 --> 00:30:25.400
<v Speaker 2>inject malicious code and repackage the app, maybe distributing it

592
00:30:25.440 --> 00:30:28.839
<v Speaker 2>as a fake update. They could create entirely robe apps

593
00:30:28.880 --> 00:30:31.720
<v Speaker 2>designed purely for drive by attacks to steal credentials when

594
00:30:31.759 --> 00:30:35.039
<v Speaker 2>you install them. Or they could reverse engineer a popular

595
00:30:35.039 --> 00:30:38.039
<v Speaker 2>app to find vulnerabilities they can exploit, or even just

596
00:30:38.079 --> 00:30:40.160
<v Speaker 2>create counterfeit versions to spread malware.

597
00:30:40.279 --> 00:30:43.519
<v Speaker 1>So even a trusted app, if modified, could become malicious.

598
00:30:43.880 --> 00:30:45.839
<v Speaker 1>Can you give us a conceptual example of how a

599
00:30:45.920 --> 00:30:48.359
<v Speaker 1>remote mobile hack might work? Maybe using one of those

600
00:30:48.359 --> 00:30:49.160
<v Speaker 1>malicious apps.

601
00:30:49.440 --> 00:30:52.960
<v Speaker 2>Sure. Imagine a hacker creates an Android application package an

602
00:30:52.960 --> 00:30:56.400
<v Speaker 2>ePK file. Maybe it looks like a simple game or utility.

603
00:30:56.720 --> 00:30:59.720
<v Speaker 2>They embed malicious code inside it, code that's designed to

604
00:30:59.720 --> 00:31:03.119
<v Speaker 2>canne back to a server. The hacker controls their listening post.

605
00:31:03.640 --> 00:31:06.880
<v Speaker 2>They then trick a target into downloading and installing this APK,

606
00:31:07.440 --> 00:31:10.319
<v Speaker 2>maybe through a phishing email, a dodgy website, or a

607
00:31:10.359 --> 00:31:13.559
<v Speaker 2>fake app store. Once the target runs the app, it

608
00:31:13.680 --> 00:31:16.720
<v Speaker 2>secretly connects back to the hacker server. Now the hacker

609
00:31:16.759 --> 00:31:19.240
<v Speaker 2>has a remote connection and can start sending commands to

610
00:31:19.279 --> 00:31:23.319
<v Speaker 2>the phone, accessing data, whatever the malware was designed to do.

611
00:31:23.599 --> 00:31:27.319
<v Speaker 1>That's deeply concerning. Okay, this has all been very tech focus,

612
00:31:27.400 --> 00:31:30.799
<v Speaker 1>but hackers don't always need complex code, do they. Sometimes

613
00:31:30.799 --> 00:31:33.920
<v Speaker 1>the easiest path is through us, through people. Let's talk

614
00:31:33.920 --> 00:31:36.160
<v Speaker 1>about social engineering, the art of people hacking.

615
00:31:36.240 --> 00:31:39.680
<v Speaker 2>That's absolutely right. Social engineering targets the human element, which

616
00:31:39.720 --> 00:31:43.119
<v Speaker 2>is often, frankly the weakest link in any security chain.

617
00:31:43.240 --> 00:31:47.400
<v Speaker 2>It's all about manipulation, tricking people into revealing confidential information

618
00:31:47.640 --> 00:31:48.960
<v Speaker 2>or performing actions.

619
00:31:48.599 --> 00:31:50.519
<v Speaker 1>They should so it bypasses the tech.

620
00:31:50.599 --> 00:31:54.640
<v Speaker 2>Often, yes, why spend weeks trying to crack a complex

621
00:31:54.640 --> 00:31:57.240
<v Speaker 2>system if you can just trick someone into giving you

622
00:31:57.279 --> 00:32:01.680
<v Speaker 2>the password. It's about building trust, exploiting that trust, and

623
00:32:01.759 --> 00:32:04.480
<v Speaker 2>gaining access with the least technical resistance.

624
00:32:05.240 --> 00:32:06.640
<v Speaker 1>What's the typical process?

625
00:32:07.240 --> 00:32:11.039
<v Speaker 2>Usually involves research on the target, then carefully building rapport

626
00:32:11.119 --> 00:32:14.240
<v Speaker 2>and trust, then exploiting that relationship to get the information

627
00:32:14.319 --> 00:32:17.519
<v Speaker 2>or access they need, and finally using whatever they obtained

628
00:32:17.559 --> 00:32:18.680
<v Speaker 2>for malicious purposes.

629
00:32:18.720 --> 00:32:20.160
<v Speaker 1>And who's most vulnerable to this?

630
00:32:20.839 --> 00:32:24.400
<v Speaker 2>Anyone can be, really, but common targets include people in

631
00:32:24.440 --> 00:32:28.200
<v Speaker 2>public facing roles like receptionists or call center agents. Maybe

632
00:32:28.279 --> 00:32:31.480
<v Speaker 2>users who aren't very tech savvy, people who overshare personal

633
00:32:31.519 --> 00:32:35.000
<v Speaker 2>details online definitely, people who reuse passwords, or those who

634
00:32:35.000 --> 00:32:37.839
<v Speaker 2>are just careless about physically securing devices or documents.

635
00:32:37.960 --> 00:32:40.480
<v Speaker 1>What are some of the classic social engineering attacks we

636
00:32:40.480 --> 00:32:41.839
<v Speaker 1>should really be watching out for?

637
00:32:42.160 --> 00:32:45.839
<v Speaker 2>Phishing is probably the most well known. Sending emails, texts,

638
00:32:45.880 --> 00:32:48.720
<v Speaker 2>or messages designed to look legitimate, trying to trick you

639
00:32:48.720 --> 00:32:51.359
<v Speaker 2>into clicking a bad link or giving up credentials often

640
00:32:51.400 --> 00:32:54.680
<v Speaker 2>creates a sense of urgency. Your account is locked, suspicious

641
00:32:54.720 --> 00:32:58.960
<v Speaker 2>activity detected to make you react without thinking. Remember the

642
00:32:59.160 --> 00:33:03.279
<v Speaker 2>infamous love lugworm. That was pure social engineering, tricking people

643
00:33:03.319 --> 00:33:04.960
<v Speaker 2>with a love letter attachment.

644
00:33:04.759 --> 00:33:07.759
<v Speaker 1>Right, playing on emotions. What about that dumpster diving thing again?

645
00:33:07.799 --> 00:33:09.240
<v Speaker 1>Is that really social engineering?

646
00:33:09.319 --> 00:33:12.839
<v Speaker 2>It fits? Yeah, dumpster diving isn't direct interaction, but it's

647
00:33:12.880 --> 00:33:17.480
<v Speaker 2>exploiting human carelessness, finding discarded reports, printouts, old hard drives,

648
00:33:17.480 --> 00:33:22.200
<v Speaker 2>network diagrams. Even shredded documents can sometimes be painstakingly reassembled.

649
00:33:22.559 --> 00:33:26.400
<v Speaker 2>It's gathering intel by exploiting poor disposal habits and voicemail.

650
00:33:26.599 --> 00:33:28.000
<v Speaker 1>How can that be exploited?

651
00:33:28.359 --> 00:33:32.039
<v Speaker 2>Voicemail digging is surprisingly effective. Hackers might use dial by

652
00:33:32.119 --> 00:33:35.920
<v Speaker 2>name directories to find employee extensions, then check voicemails. Out

653
00:33:35.960 --> 00:33:39.519
<v Speaker 2>of office messages can give away schedules, maybe even colleagues, names,

654
00:33:39.599 --> 00:33:43.279
<v Speaker 2>or alternative contacts, all useful for planning attacks or impersonation.

655
00:33:44.079 --> 00:33:46.960
<v Speaker 2>They often use voap to hide their caller ID while

656
00:33:47.000 --> 00:33:48.039
<v Speaker 2>doing this clever.

657
00:33:48.160 --> 00:33:50.079
<v Speaker 1>And then there's just asking.

658
00:33:50.000 --> 00:33:54.119
<v Speaker 2>Active communication, just straight up building trust and asking for information,

659
00:33:54.599 --> 00:33:57.960
<v Speaker 2>or physically tailgating someone through the secure door by pretending

660
00:33:57.960 --> 00:33:59.880
<v Speaker 2>to be carrying something heavy or being on a phone call.

661
00:34:00.240 --> 00:34:03.359
<v Speaker 1>Exploiting politeness and spoofing comes back here too, in a

662
00:34:03.480 --> 00:34:05.079
<v Speaker 1>human context.

663
00:34:04.640 --> 00:34:08.920
<v Speaker 2>For sure, using fake identities, maybe a fake company email

664
00:34:09.159 --> 00:34:12.559
<v Speaker 2>posing as it support, or even creating fake social media

665
00:34:12.559 --> 00:34:16.880
<v Speaker 2>profiles to solicit sensitive data, sometimes offering something in return,

666
00:34:16.960 --> 00:34:20.039
<v Speaker 2>like free Wi Fi access if you just provide some details,

667
00:34:20.360 --> 00:34:23.639
<v Speaker 2>or a security patch that's really malware. The core defense

668
00:34:23.719 --> 00:34:25.519
<v Speaker 2>is always vigilance and skepticism.

669
00:34:25.599 --> 00:34:29.039
<v Speaker 1>Okay, so how do we defend ourselves against these manipulation tactics.

670
00:34:29.039 --> 00:34:31.000
<v Speaker 1>What are the practical steps.

671
00:34:31.079 --> 00:34:34.079
<v Speaker 2>It starts with breaking single points of failure. Don't use

672
00:34:34.199 --> 00:34:38.480
<v Speaker 2>just one email address for everything critical. Diversify, use unique,

673
00:34:38.639 --> 00:34:42.719
<v Speaker 2>strong passwords for every single account, no excuses. Enable two

674
00:34:42.719 --> 00:34:46.639
<v Speaker 2>factor authentication two FA whatever possible. It's a massive security boost.

675
00:34:46.800 --> 00:34:50.440
<v Speaker 2>Be creative with security questions. Don't use obvious answers like

676
00:34:50.480 --> 00:34:53.559
<v Speaker 2>your mother's maiden name if it's easily found online. Secure

677
00:34:53.559 --> 00:34:57.039
<v Speaker 2>your banking check for HGTPS on websites. Maybe use credit

678
00:34:57.079 --> 00:34:59.760
<v Speaker 2>cards online instead of bibit cards for better fraud protection.

679
00:35:00.400 --> 00:35:05.280
<v Speaker 2>Monitor your accounts and personal data regularly delete old unused accounts.

680
00:35:05.519 --> 00:35:08.760
<v Speaker 2>Be mindful of what personal info you share online.

681
00:35:08.280 --> 00:35:11.719
<v Speaker 1>And take responsibility for your trash digital and physical.

682
00:35:11.840 --> 00:35:16.400
<v Speaker 2>Absolutely, digital garbage needs secure deletion, and physical documents need

683
00:35:16.480 --> 00:35:21.320
<v Speaker 2>proper shredding, cross cut. Ideally, overall, just cultivate healthy skepticism.

684
00:35:21.599 --> 00:35:25.639
<v Speaker 2>Verify identities before sharing info or granting access. Remember your manager,

685
00:35:25.719 --> 00:35:28.559
<v Speaker 2>IT support your colleagues. They should never ask for your password.

686
00:35:28.639 --> 00:35:30.480
<v Speaker 2>If they do, that's a giant red flag.

687
00:35:30.559 --> 00:35:32.920
<v Speaker 1>That is such a critical point. Okay, one last area,

688
00:35:32.960 --> 00:35:35.599
<v Speaker 1>which touches on something you mentioned earlier, the often overlooked

689
00:35:35.840 --> 00:35:39.119
<v Speaker 1>physical side physical attacks. Why are these still so potent

690
00:35:39.159 --> 00:35:42.119
<v Speaker 1>when everyone's focused on firewalls and antivirus.

691
00:35:41.679 --> 00:35:45.599
<v Speaker 2>Precisely because everyone's focused on the digital side. Many security

692
00:35:45.639 --> 00:35:49.719
<v Speaker 2>teams pour resources into network defenses and endpoint protection, but

693
00:35:49.880 --> 00:35:55.039
<v Speaker 2>neglect basic physical security. A skilled attacker who gains physical access,

694
00:35:55.280 --> 00:35:58.840
<v Speaker 2>they can often bypass many digital safeguards entirely. It's almost

695
00:35:58.840 --> 00:35:59.880
<v Speaker 2>a guaranteed win for them.

696
00:36:00.000 --> 00:36:02.639
<v Speaker 1>Guaranteed that's strong. What can they do almost immediately with

697
00:36:02.679 --> 00:36:03.599
<v Speaker 1>physical access?

698
00:36:03.760 --> 00:36:07.360
<v Speaker 2>Install hardware, keyloggers or listening devices, plug in a USB

699
00:36:07.519 --> 00:36:10.880
<v Speaker 2>drive that gives them remote access, or installed malware, directly

700
00:36:10.920 --> 00:36:15.400
<v Speaker 2>access data storage, reset passwords by manipulating the hardware, boot

701
00:36:15.440 --> 00:36:18.079
<v Speaker 2>the system from their own device to bypass the installed OS.

702
00:36:18.239 --> 00:36:19.719
<v Speaker 2>It's devastatingly effective.

703
00:36:19.800 --> 00:36:22.840
<v Speaker 1>So how do you even start identifying physical vulnerabilities? Whether

704
00:36:22.880 --> 00:36:24.519
<v Speaker 1>it's at home or in a small business.

705
00:36:24.800 --> 00:36:26.760
<v Speaker 2>You need to think about all the ways someone could

706
00:36:26.760 --> 00:36:30.360
<v Speaker 2>physically get to your systems or data. At home, it's

707
00:36:30.400 --> 00:36:34.239
<v Speaker 2>locking doors securing your devices. In a business, think bigger.

708
00:36:34.480 --> 00:36:37.239
<v Speaker 2>How many buildings or sites, how many employees, how many

709
00:36:37.400 --> 00:36:40.480
<v Speaker 2>entrances and exits, where the data centers or server rooms?

710
00:36:40.800 --> 00:36:43.559
<v Speaker 2>How easy is it for someone unauthorized to just walk in.

711
00:36:44.000 --> 00:36:47.280
<v Speaker 2>What devices are connected once they access one, what else

712
00:36:47.280 --> 00:36:47.840
<v Speaker 2>can they reach?

713
00:36:48.199 --> 00:36:51.159
<v Speaker 1>What are the most common physical weak spots people should

714
00:36:51.159 --> 00:36:52.559
<v Speaker 1>look out for and try to fix.

715
00:36:52.840 --> 00:36:56.000
<v Speaker 2>Lack of monitoring on doors and entry points, no system

716
00:36:56.039 --> 00:37:00.280
<v Speaker 2>for logging visitors or requiring escorts, Employees just holding doors

717
00:37:00.320 --> 00:37:03.559
<v Speaker 2>open for strangers out of politeness. Weak locks or easily

718
00:37:03.559 --> 00:37:06.840
<v Speaker 2>copied keys using the same simple password from multiple physical

719
00:37:06.920 --> 00:37:10.639
<v Speaker 2>security systems or access cameras, et cetera. Unlocks server rooms

720
00:37:10.719 --> 00:37:14.039
<v Speaker 2>or wiring closets, leaving sensitive documents or storage media like

721
00:37:14.119 --> 00:37:18.960
<v Speaker 2>USB drives just lying around, improperly shredded documents and unsecured

722
00:37:18.960 --> 00:37:22.679
<v Speaker 2>hardware itself, laptops not locked down, old photocopiers with hard drugs,

723
00:37:22.679 --> 00:37:25.039
<v Speaker 2>full of scan documents, discarded phones or tablets.

724
00:37:25.239 --> 00:37:29.000
<v Speaker 1>So the practical advice for protection secure everything, Lock up

725
00:37:29.039 --> 00:37:32.400
<v Speaker 1>sensitive documents and devices, control access limits who can get

726
00:37:32.400 --> 00:37:34.480
<v Speaker 1>into server rooms or access critical hardware.

727
00:37:34.920 --> 00:37:39.960
<v Speaker 2>Implement strong access controls, maybe multifacture authentication even for physical

728
00:37:40.000 --> 00:37:43.559
<v Speaker 2>systems where possible. Routinely checked devices for any signs of

729
00:37:43.599 --> 00:37:48.079
<v Speaker 2>tampering physical or software, And remember physical attacks aren't always fast.

730
00:37:48.639 --> 00:37:51.599
<v Speaker 2>It could be a disgruntled employee slowly planting things over

731
00:37:51.639 --> 00:37:54.199
<v Speaker 2>weeks or months. It requires ongoing vigilance.

732
00:37:54.280 --> 00:37:57.039
<v Speaker 1>Wow, this has been incredibly eye opening. We've gone from

733
00:37:57.039 --> 00:38:00.400
<v Speaker 1>the history of hacking, through the different motivations, the skills needed,

734
00:38:00.440 --> 00:38:03.880
<v Speaker 1>how attackers plan, the tools they use, spoofing, man in

735
00:38:03.920 --> 00:38:08.400
<v Speaker 1>the middle, password cracking, network hacks, mobile threats, social engineering,

736
00:38:08.800 --> 00:38:13.000
<v Speaker 1>and finally physical attacks. Understanding how hackers operate across all

737
00:38:13.039 --> 00:38:16.119
<v Speaker 1>these fronts, technical, social, physical, It really feels like that's

738
00:38:16.159 --> 00:38:17.039
<v Speaker 1>the ultimate defense.

739
00:38:17.119 --> 00:38:19.800
<v Speaker 2>It truly is knowing their methods, their mindset, their tools.

740
00:38:20.000 --> 00:38:23.159
<v Speaker 2>That's the foundation for building effective protection for yourself. It

741
00:38:23.199 --> 00:38:26.960
<v Speaker 2>shifts your perspective from just reacting to threats to proactively

742
00:38:27.000 --> 00:38:27.880
<v Speaker 2>securing your world.

743
00:38:28.000 --> 00:38:31.599
<v Speaker 1>Absolutely, And as we wrap up this deep dive, here's

744
00:38:31.599 --> 00:38:35.360
<v Speaker 1>something to think about, given how deeply interconnected our digital

745
00:38:35.400 --> 00:38:38.599
<v Speaker 1>and physical lives really are. Now, what's the most surprising

746
00:38:38.719 --> 00:38:41.400
<v Speaker 1>hidden vulnerability in your own daily routine that maybe you've

747
00:38:41.440 --> 00:38:44.679
<v Speaker 1>spotted after this discussion, and more importantly, what's your immediate

748
00:38:44.719 --> 00:38:46.480
<v Speaker 1>next step to address it. I'm all that over