WEBVTT

1
00:00:00.080 --> 00:00:02.520
<v Speaker 1>Okay, so you sent over a ton of info on

2
00:00:02.640 --> 00:00:04.400
<v Speaker 1>this whole IoT hacking thing.

3
00:00:04.719 --> 00:00:08.839
<v Speaker 2>Yeah, it's it's pretty fascinating stuff. You know. It kind

4
00:00:08.839 --> 00:00:12.480
<v Speaker 2>of combines that traditional cybersecurity world, right with the unique

5
00:00:12.519 --> 00:00:15.679
<v Speaker 2>vulnerabilities you get with physical devices.

6
00:00:15.320 --> 00:00:20.800
<v Speaker 1>So not just software anymore exactly. Yeah, talking hardware, radio signals,

7
00:00:21.079 --> 00:00:24.600
<v Speaker 1>even like the physical environment. Yeah, these devices operated.

8
00:00:24.480 --> 00:00:27.000
<v Speaker 2>It really expands the attack surface, you know what I mean.

9
00:00:27.519 --> 00:00:29.719
<v Speaker 2>We're going to try and like give you a clear

10
00:00:29.839 --> 00:00:32.759
<v Speaker 2>picture of the security landscape of the whole Internet of things.

11
00:00:32.960 --> 00:00:36.640
<v Speaker 1>I think the first question here, Yeah, what exactly are

12
00:00:36.640 --> 00:00:38.719
<v Speaker 1>we even talking about when we say IoT.

13
00:00:39.200 --> 00:00:41.000
<v Speaker 2>Yeah, that's a great question, and you're.

14
00:00:40.920 --> 00:00:43.439
<v Speaker 1>Right, everything has a chip and WiFi these days.

15
00:00:43.200 --> 00:00:46.320
<v Speaker 2>It seems like it, right. Yeah, there's not like a

16
00:00:46.439 --> 00:00:50.159
<v Speaker 2>single universal definition, okay, but for our purposes, we're going

17
00:00:50.200 --> 00:00:52.960
<v Speaker 2>to use the one from practical IoT hacking, right, which

18
00:00:53.039 --> 00:00:57.159
<v Speaker 2>is physical devices that have computing power and can transfer

19
00:00:57.359 --> 00:01:03.039
<v Speaker 2>data over networks, yet don't typically require human to computer interaction.

20
00:01:03.719 --> 00:01:06.040
<v Speaker 1>Okay, So like my smart refrigerator that tells me when

21
00:01:06.079 --> 00:01:06.599
<v Speaker 1>I'm low.

22
00:01:06.480 --> 00:01:11.439
<v Speaker 2>On milk exactly, or like a smart thermostat, security cameras,

23
00:01:12.120 --> 00:01:15.599
<v Speaker 2>even things like connected insulin pumps Wow. And here's where

24
00:01:15.640 --> 00:01:19.840
<v Speaker 2>it gets really interesting. The book actually paints this picture

25
00:01:20.159 --> 00:01:23.280
<v Speaker 2>of a city skyline Okay, not just with buildings, but

26
00:01:23.319 --> 00:01:29.480
<v Speaker 2>with this dense network of antennas and sensors connecting all

27
00:01:29.519 --> 00:01:33.959
<v Speaker 2>these devices, millions of points of data, all talking to

28
00:01:34.040 --> 00:01:34.480
<v Speaker 2>each other.

29
00:01:34.599 --> 00:01:37.719
<v Speaker 1>So this isn't like some futuristic concept, not at all.

30
00:01:37.799 --> 00:01:38.799
<v Speaker 1>This is already happening.

31
00:01:38.879 --> 00:01:41.000
<v Speaker 2>It's woven into the fabric of our lives.

32
00:01:41.519 --> 00:01:41.879
<v Speaker 1>Wow.

33
00:01:42.040 --> 00:01:45.200
<v Speaker 2>Yeah, so you're starting to understand why security for all

34
00:01:45.200 --> 00:01:46.280
<v Speaker 2>this is so crucial.

35
00:01:46.680 --> 00:01:50.599
<v Speaker 1>Absolutely, it goes beyond just protecting data, right, this is

36
00:01:50.719 --> 00:01:55.920
<v Speaker 1>like protecting our physical safety, yes, our privacy, even critical

37
00:01:55.959 --> 00:01:57.319
<v Speaker 1>infrastructure exactly.

38
00:01:57.319 --> 00:01:59.920
<v Speaker 2>I mean if someone can hack into like a power

39
00:02:00.040 --> 00:02:04.760
<v Speaker 2>grid or a traffic management system, consequences can be really devastating.

40
00:02:04.959 --> 00:02:07.680
<v Speaker 1>Okay, that's making this feel very real. Yeah, so how

41
00:02:07.760 --> 00:02:11.280
<v Speaker 1>is this different from the traditional IT security that we're

42
00:02:11.360 --> 00:02:12.159
<v Speaker 1>used to hearing about.

43
00:02:12.360 --> 00:02:15.680
<v Speaker 2>Well, one major difference is that IoT devices often have

44
00:02:15.800 --> 00:02:19.919
<v Speaker 2>limited resources. Okay, you know, they don't necessarily have the

45
00:02:20.159 --> 00:02:23.639
<v Speaker 2>processing power or memory to handle complex security.

46
00:02:23.800 --> 00:02:26.039
<v Speaker 1>Oh so it's like, yeah, trying to install a bank

47
00:02:26.120 --> 00:02:27.599
<v Speaker 1>vault door on a garden shed.

48
00:02:27.680 --> 00:02:28.599
<v Speaker 2>That's a great analogy.

49
00:02:28.680 --> 00:02:29.560
<v Speaker 1>Yeah, it's just not.

50
00:02:30.080 --> 00:02:32.560
<v Speaker 2>It's not designed designed for that level of for that

51
00:02:32.639 --> 00:02:33.759
<v Speaker 2>level of security exactly.

52
00:02:33.840 --> 00:02:34.120
<v Speaker 1>Okay.

53
00:02:34.719 --> 00:02:38.360
<v Speaker 2>Another challenge is just the sheer diversity of technologies okay,

54
00:02:38.520 --> 00:02:45.400
<v Speaker 2>countless hardware and software, combinations, different communication protocols. It creates

55
00:02:45.439 --> 00:02:48.360
<v Speaker 2>this massive attack surface for hackers to exploit.

56
00:02:48.680 --> 00:02:52.159
<v Speaker 1>And unlike a server and a data center, right, so

57
00:02:52.319 --> 00:02:56.159
<v Speaker 1>many of these devices are just physically accessible, yeah, exactly,

58
00:02:56.199 --> 00:02:57.479
<v Speaker 1>anyone could tamper with them.

59
00:02:57.599 --> 00:03:01.599
<v Speaker 2>Anyone could. Yeah. And we can't forget the lack of

60
00:03:01.680 --> 00:03:05.520
<v Speaker 2>security awareness among some manufacturers. A lot of times the

61
00:03:05.520 --> 00:03:07.240
<v Speaker 2>focus is just on, you know.

62
00:03:07.439 --> 00:03:10.159
<v Speaker 1>Getting it to market, getting cort quickly and cheaply.

63
00:03:09.960 --> 00:03:14.039
<v Speaker 2>Quickly and cheaply, rather than building in those robust security features.

64
00:03:14.199 --> 00:03:16.479
<v Speaker 1>Okay, let's get out of theory, okay and talk about

65
00:03:16.479 --> 00:03:20.639
<v Speaker 1>some real world examples. Sure, the book talks about Jay Radcliffe, right,

66
00:03:20.800 --> 00:03:25.080
<v Speaker 1>the security researcher who found vulnerabilities in his own insulin pump.

67
00:03:25.280 --> 00:03:28.439
<v Speaker 2>Yeah, so he realizes that a hacker could potentially like

68
00:03:29.319 --> 00:03:32.680
<v Speaker 2>manipulate the dosage, putting his life at risk.

69
00:03:32.840 --> 00:03:33.400
<v Speaker 1>Wow.

70
00:03:33.680 --> 00:03:36.759
<v Speaker 2>It really highlights the potential life or death consequences of

71
00:03:36.879 --> 00:03:39.960
<v Speaker 2>insecure IoT medical devices.

72
00:03:40.120 --> 00:03:43.120
<v Speaker 1>That's terrifying. It is that really hits home how high

73
00:03:43.159 --> 00:03:44.039
<v Speaker 1>the stakes are here.

74
00:03:44.159 --> 00:03:47.439
<v Speaker 2>Another example that might surprise you is the vulnerability of

75
00:03:47.560 --> 00:03:49.039
<v Speaker 2>VoIP phones.

76
00:03:48.800 --> 00:03:51.280
<v Speaker 1>Voy p Those are just internet phones, yeah, pretty much.

77
00:03:51.319 --> 00:03:52.639
<v Speaker 1>How could those be a security risk?

78
00:03:52.680 --> 00:03:55.639
<v Speaker 2>Well, they're often overlooked from a security standpoint, but they

79
00:03:55.639 --> 00:03:58.759
<v Speaker 2>can actually be used as entry points, oh wow, to

80
00:03:58.879 --> 00:04:03.759
<v Speaker 2>gain access to corporate networks, including those with sensitive IoT devices.

81
00:04:04.080 --> 00:04:07.840
<v Speaker 1>So even a seemingly harmless device, yeah, can be a

82
00:04:07.879 --> 00:04:09.000
<v Speaker 1>weak link in the chain.

83
00:04:09.240 --> 00:04:10.960
<v Speaker 2>It can absolutely.

84
00:04:10.599 --> 00:04:12.479
<v Speaker 1>Okay, I'm starting to see how all this connects it.

85
00:04:12.479 --> 00:04:13.280
<v Speaker 2>It's all connected.

86
00:04:13.479 --> 00:04:16.879
<v Speaker 1>So how does a hacker actually target these devices?

87
00:04:17.079 --> 00:04:19.399
<v Speaker 2>Well, they usually follow like a systematic.

88
00:04:18.839 --> 00:04:22.319
<v Speaker 1>Approach okay, So they don't just randomly start not usually

89
00:04:22.399 --> 00:04:23.360
<v Speaker 1>no poken around.

90
00:04:23.480 --> 00:04:27.199
<v Speaker 2>It often starts with reconnaissance okay, gathering information about the

91
00:04:27.240 --> 00:04:34.279
<v Speaker 2>target device, it's network configuration, any available documentation or firmware updates.

92
00:04:34.480 --> 00:04:37.639
<v Speaker 1>So like doing their homework before making a move.

93
00:04:37.639 --> 00:04:41.079
<v Speaker 2>Exactly like casing the joint in a heist movie.

94
00:04:41.199 --> 00:04:41.560
<v Speaker 1>Okay.

95
00:04:41.759 --> 00:04:44.680
<v Speaker 2>Once they have a good understanding of the device, huh,

96
00:04:44.800 --> 00:04:48.360
<v Speaker 2>they move on to vulnerability analysis okay. This is where

97
00:04:48.399 --> 00:04:53.439
<v Speaker 2>they identify potential weaknesses in the software, hardware, or communication.

98
00:04:53.000 --> 00:04:56.600
<v Speaker 1>Protocols, looking for those chinks in the armor exactly. Yeah,

99
00:04:56.639 --> 00:05:00.319
<v Speaker 1>and I'm guessing the final step is the actual attack.

100
00:05:00.199 --> 00:05:03.480
<v Speaker 2>Yes, the exploitation phase. This is where they use the

101
00:05:03.680 --> 00:05:08.759
<v Speaker 2>identified vulnerabilities to gain control of the device, access sensitive data,

102
00:05:09.279 --> 00:05:10.800
<v Speaker 2>or disrupt its operation.

103
00:05:11.600 --> 00:05:14.680
<v Speaker 1>So let's get into some of the specific hacking techniques. Okay,

104
00:05:14.959 --> 00:05:20.000
<v Speaker 1>what are some of the more shall we say, ingenious ones.

105
00:05:20.160 --> 00:05:25.199
<v Speaker 2>Well, one example is VLAN hopping, which involves exploiting misconfigured

106
00:05:25.199 --> 00:05:28.120
<v Speaker 2>network switches to gain access to restricted vlands.

107
00:05:28.240 --> 00:05:30.439
<v Speaker 1>Wait, can you back up a second, sure, what exactly

108
00:05:30.480 --> 00:05:31.000
<v Speaker 1>is a vlan?

109
00:05:31.120 --> 00:05:35.439
<v Speaker 2>Think of it as like creating separate virtual networks within

110
00:05:35.480 --> 00:05:39.000
<v Speaker 2>a larger physical network, having different lanes on a highway

111
00:05:39.439 --> 00:05:42.680
<v Speaker 2>to separate different types of traffic. So in a company,

112
00:05:43.000 --> 00:05:45.839
<v Speaker 2>they might use VLANs to separate sensitive data from the

113
00:05:45.879 --> 00:05:48.920
<v Speaker 2>rest of the network. Vland hopping allows a hacker to

114
00:05:49.040 --> 00:05:52.639
<v Speaker 2>jump between those lanes and access information they shouldn't be

115
00:05:52.680 --> 00:05:53.360
<v Speaker 2>able to see.

116
00:05:53.600 --> 00:05:57.199
<v Speaker 1>So like finding a secret passageway to bypass security checkpoint.

117
00:05:57.279 --> 00:06:01.079
<v Speaker 2>That's a very act analogy. Another fastenating technique is the

118
00:06:01.199 --> 00:06:06.319
<v Speaker 2>MQTT attack. IMQTT it stands for Message Queuing Telemetry Transport.

119
00:06:07.079 --> 00:06:11.360
<v Speaker 2>It's a lightweight messaging protocol often used in IoT ecosystems

120
00:06:11.959 --> 00:06:15.839
<v Speaker 2>for communication between devices. Okay, the book details a way

121
00:06:15.879 --> 00:06:18.879
<v Speaker 2>to create a custom and crack module that's a password

122
00:06:18.920 --> 00:06:23.439
<v Speaker 2>cracking tool to crack the authentication of an MQTT broker.

123
00:06:23.560 --> 00:06:24.120
<v Speaker 1>A broker.

124
00:06:24.279 --> 00:06:27.839
<v Speaker 2>Think of it as like a central hub that manages

125
00:06:27.879 --> 00:06:31.800
<v Speaker 2>the communication between all the devices. So by cracking the broker,

126
00:06:31.879 --> 00:06:35.680
<v Speaker 2>the attacker gains control over an entire network of devices.

127
00:06:36.040 --> 00:06:39.199
<v Speaker 1>Wow, so it's like finding the master key that unlocks

128
00:06:39.240 --> 00:06:40.160
<v Speaker 1>every door in the building.

129
00:06:40.199 --> 00:06:43.920
<v Speaker 2>You're catching on quickly. Then there's UPnP exploitation.

130
00:06:44.519 --> 00:06:45.000
<v Speaker 1>UPNB.

131
00:06:45.240 --> 00:06:48.040
<v Speaker 2>It stands for Universal plug and Play. Okay, it's designed

132
00:06:48.040 --> 00:06:50.560
<v Speaker 2>to make it super easy to like set up devices

133
00:06:50.600 --> 00:06:53.959
<v Speaker 2>on a network, but it can also be a security.

134
00:06:53.560 --> 00:06:55.360
<v Speaker 1>Nightmare, so convenience often comes at.

135
00:06:55.319 --> 00:07:00.079
<v Speaker 2>A cost unfortunately. Yes, hackers can exploit flaws in UPNKE

136
00:07:00.319 --> 00:07:03.639
<v Speaker 2>to open up ports in a router's firewall, exposing internal

137
00:07:03.680 --> 00:07:04.759
<v Speaker 2>devices to the Internet.

138
00:07:04.959 --> 00:07:07.360
<v Speaker 1>So it's like leaving the front door wide open with

139
00:07:07.399 --> 00:07:10.560
<v Speaker 1>the big scien and says come on in exactly. Yikes.

140
00:07:10.720 --> 00:07:13.000
<v Speaker 2>Yeah, it's a good reminder to be careful about what

141
00:07:13.079 --> 00:07:14.879
<v Speaker 2>features you enable on your router.

142
00:07:15.560 --> 00:07:18.839
<v Speaker 1>Speaking of sneaky techniques, yeah, what about these man in

143
00:07:18.879 --> 00:07:22.519
<v Speaker 1>the middle attacks? Using mDNS and WS discovery.

144
00:07:22.839 --> 00:07:27.720
<v Speaker 2>So mDNS and WS discovery are meant for simple device

145
00:07:27.800 --> 00:07:31.160
<v Speaker 2>discovery on local networks. Like say you want to print

146
00:07:31.199 --> 00:07:35.560
<v Speaker 2>something and your computer needs to find the printer on

147
00:07:35.600 --> 00:07:39.439
<v Speaker 2>your home network. Right, these protocols help with that, okay,

148
00:07:39.480 --> 00:07:44.199
<v Speaker 2>But hackers can abuse them to intercept and manipulate communications,

149
00:07:44.519 --> 00:07:46.680
<v Speaker 2>even impersonating legitimate devices.

150
00:07:46.920 --> 00:07:49.560
<v Speaker 1>So it's like intercepting a phone call and pretending to

151
00:07:49.600 --> 00:07:51.079
<v Speaker 1>be the person on the other end exactly.

152
00:07:51.240 --> 00:07:53.839
<v Speaker 2>Oh wow, And these attacks can be used to steal data,

153
00:07:54.079 --> 00:07:57.199
<v Speaker 2>disrupt operations, or even gain control of devices.

154
00:07:57.360 --> 00:07:59.879
<v Speaker 1>And I'm guessing it's pretty hard to detect it can be.

155
00:08:00.279 --> 00:08:01.879
<v Speaker 1>Ye is getting seriously intense.

156
00:08:02.040 --> 00:08:04.199
<v Speaker 2>Let's bring it back to something a little more tangible

157
00:08:04.240 --> 00:08:07.240
<v Speaker 2>and maybe a little scary. The book talks about RFID

158
00:08:07.399 --> 00:08:12.079
<v Speaker 2>tag cloning, using readily available tools to potentially gain access

159
00:08:12.160 --> 00:08:14.160
<v Speaker 2>to buildings or systems.

160
00:08:14.319 --> 00:08:18.199
<v Speaker 1>So it's not just about securing the digital world. Yeah,

161
00:08:18.240 --> 00:08:18.800
<v Speaker 1>it's also the.

162
00:08:18.720 --> 00:08:20.120
<v Speaker 2>Physical physical implication.

163
00:08:20.199 --> 00:08:20.399
<v Speaker 1>Yeah.

164
00:08:20.399 --> 00:08:23.519
<v Speaker 2>Absolutely, And that brings us to another crucial point, the

165
00:08:23.600 --> 00:08:28.399
<v Speaker 2>vulnerability of mobile apps that are often used to control

166
00:08:28.439 --> 00:08:30.279
<v Speaker 2>and configure IoT devices.

167
00:08:30.360 --> 00:08:32.600
<v Speaker 1>Right those appsolutely, you adjust your thermostat from.

168
00:08:32.480 --> 00:08:35.759
<v Speaker 2>Your phone, exactly, or check your security cameras while you're away.

169
00:08:36.240 --> 00:08:39.159
<v Speaker 2>The problem is these apps can be easier targets than

170
00:08:39.200 --> 00:08:42.840
<v Speaker 2>the devices themselves. Oh wow, they might store data insecurely

171
00:08:43.720 --> 00:08:47.399
<v Speaker 2>or be susceptible to injection attacks where malicious code is inserted.

172
00:08:47.600 --> 00:08:50.720
<v Speaker 1>So hacking the app could give the attack or backdoor.

173
00:08:50.279 --> 00:08:53.279
<v Speaker 2>Access to the device and the entire network. Wow, it's

174
00:08:53.279 --> 00:08:54.600
<v Speaker 2>connected to It's.

175
00:08:54.440 --> 00:08:57.840
<v Speaker 1>A sobering thought. His It seems like with all this connectivity,

176
00:08:58.080 --> 00:09:00.919
<v Speaker 1>there's always some new vulnerability to worry about.

177
00:09:01.039 --> 00:09:04.159
<v Speaker 2>It's a constantly evolving landscape. That's why it's so important

178
00:09:04.159 --> 00:09:08.559
<v Speaker 2>to understand like the hacking mindset. By learning how attackers think,

179
00:09:08.679 --> 00:09:11.799
<v Speaker 2>we can better anticipate their moves and protect ourselves.

180
00:09:12.320 --> 00:09:14.279
<v Speaker 1>Knowledge is power, exactly.

181
00:09:14.559 --> 00:09:18.159
<v Speaker 2>But before we go full on cyber detective, right, let's

182
00:09:18.200 --> 00:09:21.080
<v Speaker 2>remember that not all hacking is malicious, right.

183
00:09:21.120 --> 00:09:23.080
<v Speaker 1>There are ethical hackers exactly right.

184
00:09:23.279 --> 00:09:27.440
<v Speaker 2>Ethical hackers use their skills to find and report vulnerabilities,

185
00:09:27.639 --> 00:09:29.360
<v Speaker 2>helping to make systems more secure.

186
00:09:29.600 --> 00:09:32.399
<v Speaker 1>So they're like the white hats in an old Western right,

187
00:09:32.519 --> 00:09:34.399
<v Speaker 1>using their knowledge for good exactly.

188
00:09:35.039 --> 00:09:40.240
<v Speaker 2>Practical IoT hacking actually emphasizes the importance of ethical hacking, okay,

189
00:09:40.279 --> 00:09:43.960
<v Speaker 2>and working within those legal frameworks. It even mentions specific

190
00:09:44.080 --> 00:09:48.519
<v Speaker 2>laws like the Digital Millennium Copyright Act and the Computer

191
00:09:48.600 --> 00:09:51.159
<v Speaker 2>Fraud and Abuse Act that govern these activities.

192
00:09:51.240 --> 00:09:53.840
<v Speaker 1>So we've got legal and ethical guidelines we do to

193
00:09:53.879 --> 00:09:56.000
<v Speaker 1>consider as well. Yeah, that's a whole other layer.

194
00:09:55.879 --> 00:09:59.600
<v Speaker 2>Of complexity, it is, but it's an important one. Cybersecurity

195
00:09:59.679 --> 00:10:03.879
<v Speaker 2>isn't just about technical skills. It's also about understanding the

196
00:10:03.919 --> 00:10:07.120
<v Speaker 2>implications of what we do and making sure we're using

197
00:10:07.120 --> 00:10:08.399
<v Speaker 2>our knowledge responsibly.

198
00:10:08.840 --> 00:10:10.840
<v Speaker 1>Okay, we've covered a lot of ground here. We have

199
00:10:11.159 --> 00:10:16.519
<v Speaker 1>define the IoT, explored its unique security challenges, h delved

200
00:10:16.519 --> 00:10:20.559
<v Speaker 1>into real world examples, and even peaked into the hacker's toolbox.

201
00:10:20.759 --> 00:10:23.480
<v Speaker 2>We've only just scratched the surface, though, Right, there's so

202
00:10:23.639 --> 00:10:26.919
<v Speaker 2>much more to learn about this, this rapidly evolving field.

203
00:10:26.919 --> 00:10:29.240
<v Speaker 2>But hopefully this has given you a solid foundation to

204
00:10:29.240 --> 00:10:29.799
<v Speaker 2>build upon.

205
00:10:30.000 --> 00:10:32.559
<v Speaker 1>It definitely has. Yeah, it seems like we're just at

206
00:10:32.600 --> 00:10:35.240
<v Speaker 1>the beginning, I think so of a much larger conversation

207
00:10:35.879 --> 00:10:40.159
<v Speaker 1>about how we secure this right increasingly interconnected world.

208
00:10:40.360 --> 00:10:43.000
<v Speaker 2>You're absolutely right, the security of the IoT is not

209
00:10:43.120 --> 00:10:46.039
<v Speaker 2>just a technical issue. It's a societal issue.

210
00:10:46.240 --> 00:10:46.519
<v Speaker 1>Wow.

211
00:10:46.639 --> 00:10:51.159
<v Speaker 2>As our world becomes increasingly interconnected, the line between the

212
00:10:51.240 --> 00:10:55.960
<v Speaker 2>digital and physical realms is blurring. What happens in cyberspace

213
00:10:56.039 --> 00:10:58.759
<v Speaker 2>can have very real consequences.

214
00:10:58.039 --> 00:10:59.919
<v Speaker 1>And that's a thought we should all be grappling with.

215
00:11:00.240 --> 00:11:02.320
<v Speaker 2>We'll dive deeper into that in the next part of

216
00:11:02.360 --> 00:11:05.919
<v Speaker 2>our deep dive. We'll explore some advanced hacking techniques and

217
00:11:06.000 --> 00:11:11.039
<v Speaker 2>discuss the broader implications of the IoT security landscape. Sounds

218
00:11:11.039 --> 00:11:16.039
<v Speaker 2>like a plan until then, stay curious and stay vigilant.

219
00:11:15.519 --> 00:11:19.799
<v Speaker 1>Seed in part two. Okay, so last time we were

220
00:11:19.799 --> 00:11:24.279
<v Speaker 1>talking about the importance of understanding the hacker's mindset and

221
00:11:24.320 --> 00:11:25.960
<v Speaker 1>how they approach these IoT.

222
00:11:25.720 --> 00:11:28.679
<v Speaker 2>Systems, and now we're going to explore some of those

223
00:11:28.720 --> 00:11:32.480
<v Speaker 2>advanced hacking techniques that kind of take that understanding a

224
00:11:32.480 --> 00:11:35.320
<v Speaker 2>step for it air, It's like peeling back the layers

225
00:11:35.360 --> 00:11:39.200
<v Speaker 2>of an onion, uncovering like new levels of complexity.

226
00:11:39.399 --> 00:11:41.879
<v Speaker 1>Okay, you've intrigued me, but I'm also a little nervous.

227
00:11:42.240 --> 00:11:46.799
<v Speaker 2>Let's start with network sniffing and protocol analysis. Okay, this

228
00:11:46.840 --> 00:11:49.679
<v Speaker 2>is where things get a bit more technical. Oka, but

229
00:11:49.759 --> 00:11:54.360
<v Speaker 2>it's really crucial for understanding how attackers can intercept and

230
00:11:54.480 --> 00:11:58.519
<v Speaker 2>manipulate data that's flowing between these IoT devices.

231
00:11:58.519 --> 00:12:01.039
<v Speaker 1>Okay, I'll try and keep up. So network sniffing.

232
00:12:01.320 --> 00:12:03.639
<v Speaker 2>Yeah, it sounds kind of ominous, it doesn't it. What

233
00:12:03.679 --> 00:12:04.440
<v Speaker 2>exactly is it?

234
00:12:04.799 --> 00:12:09.000
<v Speaker 1>Think of it like eavesdropping on a conversation. When devices

235
00:12:09.039 --> 00:12:13.080
<v Speaker 1>communicate over a network, they send these packets of data

236
00:12:13.159 --> 00:12:17.279
<v Speaker 1>back and forth. A network sniffer is a tool that

237
00:12:17.480 --> 00:12:21.320
<v Speaker 1>captures those packets, allowing a hacker to see what information

238
00:12:21.399 --> 00:12:22.360
<v Speaker 1>is being transmitted.

239
00:12:22.440 --> 00:12:26.120
<v Speaker 2>So they're basically spying on the conversation between the devices.

240
00:12:26.159 --> 00:12:28.320
<v Speaker 1>But it's not enough just to see the data. You

241
00:12:28.360 --> 00:12:32.000
<v Speaker 1>need to understand what it means. And that's where protocol

242
00:12:32.000 --> 00:12:37.600
<v Speaker 1>analysis comes in. Different types of data use different communication protocols,

243
00:12:38.159 --> 00:12:41.080
<v Speaker 1>which are kind of like sets of rules for how

244
00:12:41.080 --> 00:12:44.480
<v Speaker 1>the information is structured and transmitted.

245
00:12:43.960 --> 00:12:47.799
<v Speaker 2>So like different languages for different types of data exactly.

246
00:12:47.960 --> 00:12:52.679
<v Speaker 1>And by analyzing those protocols, hackers can decipher the meaning

247
00:12:53.240 --> 00:12:57.039
<v Speaker 1>of the data they're intercepting. Once they understand the language,

248
00:12:57.320 --> 00:13:00.840
<v Speaker 1>they can start manipulating the data, injecting their own commands

249
00:13:00.919 --> 00:13:04.879
<v Speaker 1>oh okay, or even like disrupting the communication entirely.

250
00:13:04.559 --> 00:13:09.480
<v Speaker 2>So it's not just passively listening. They can actually interfere.

251
00:13:09.159 --> 00:13:10.000
<v Speaker 1>With the conversation.

252
00:13:10.679 --> 00:13:13.000
<v Speaker 2>Yeah, it can be a problem. This is getting scary,

253
00:13:13.159 --> 00:13:16.320
<v Speaker 2>especially if the protocols being used aren't very secure.

254
00:13:16.840 --> 00:13:17.200
<v Speaker 1>Okay.

255
00:13:17.240 --> 00:13:18.919
<v Speaker 2>The book actually gives the example of.

256
00:13:18.919 --> 00:13:21.200
<v Speaker 1>Di com DICOM. That sounds familiar.

257
00:13:21.279 --> 00:13:25.600
<v Speaker 2>It stands for Digital Imaging and Communications in Medicine, right, Okay.

258
00:13:25.639 --> 00:13:29.080
<v Speaker 2>It's how medical images like X rays and CT scams

259
00:13:29.320 --> 00:13:33.360
<v Speaker 2>are stored and transmitted. If someone were able to intercept

260
00:13:33.360 --> 00:13:37.200
<v Speaker 2>and manipulate those images, the consequences could be serious.

261
00:13:37.360 --> 00:13:40.759
<v Speaker 1>Okay, that's definitely unsettling. Yeah, but surely it's not that

262
00:13:40.879 --> 00:13:43.039
<v Speaker 1>easy to just sniff network traffic.

263
00:13:43.679 --> 00:13:46.600
<v Speaker 2>Well, there are security measures in place, but they're not

264
00:13:46.639 --> 00:13:49.200
<v Speaker 2>always fool proof okay, and sometimes hackers have to get

265
00:13:49.240 --> 00:13:52.639
<v Speaker 2>a little creative and develop their own tools to analyze

266
00:13:52.639 --> 00:13:53.960
<v Speaker 2>and manipulate these protocols.

267
00:13:54.039 --> 00:13:54.279
<v Speaker 1>Okay.

268
00:13:54.639 --> 00:13:56.919
<v Speaker 2>The book talks about extending wire shark.

269
00:13:57.039 --> 00:13:59.879
<v Speaker 1>Wire Shark is that something anyone can use well? Or

270
00:14:00.080 --> 00:14:02.240
<v Speaker 1>is that like specialized hacker software.

271
00:14:02.720 --> 00:14:06.679
<v Speaker 2>Wireshark itself is actually a legitimate tool used by network

272
00:14:06.720 --> 00:14:12.039
<v Speaker 2>administrators and security professionals okay, for troubleshooting and analysis. It's

273
00:14:12.080 --> 00:14:16.639
<v Speaker 2>open source, meaning anyone can download and use it. But

274
00:14:16.720 --> 00:14:19.080
<v Speaker 2>in the wrong hands, it can also be used for

275
00:14:19.120 --> 00:14:20.360
<v Speaker 2>those malicious purposes.

276
00:14:20.480 --> 00:14:24.039
<v Speaker 1>So it's like any powerful tool. It could be used

277
00:14:24.080 --> 00:14:26.600
<v Speaker 1>for good or evil it can depending on the intentions

278
00:14:26.600 --> 00:14:29.200
<v Speaker 1>of the user exactly. The book also explains how to

279
00:14:29.200 --> 00:14:33.120
<v Speaker 1>write custom modules for enmap, which is another powerful network

280
00:14:33.159 --> 00:14:37.200
<v Speaker 1>scanning tool. It is to identify and target new network protocols.

281
00:14:37.360 --> 00:14:40.720
<v Speaker 2>It's like giving hackers a set of lock picks for

282
00:14:40.840 --> 00:14:43.240
<v Speaker 2>any type of digital door they encounter.

283
00:14:43.080 --> 00:14:46.200
<v Speaker 1>So they're constantly developing new ways they are to exploit

284
00:14:46.240 --> 00:14:47.399
<v Speaker 1>weaknesses in these systems.

285
00:14:47.519 --> 00:14:50.279
<v Speaker 2>Yeah, it feels like an arms race almost between the

286
00:14:50.279 --> 00:14:52.840
<v Speaker 2>hackers and the security professionals.

287
00:14:53.120 --> 00:14:57.759
<v Speaker 1>Speaking of exploiting weaknesses, you mentioned manipulating data earlier. Can

288
00:14:57.799 --> 00:15:00.440
<v Speaker 1>you give me like a specific example of what that

289
00:15:00.519 --> 00:15:01.120
<v Speaker 1>might look like.

290
00:15:01.279 --> 00:15:04.039
<v Speaker 2>One common technique is called a bit flipping attack.

291
00:15:04.200 --> 00:15:04.440
<v Speaker 1>Okay.

292
00:15:04.720 --> 00:15:08.039
<v Speaker 2>It involves changing specific bits in a data packet.

293
00:15:08.279 --> 00:15:12.039
<v Speaker 1>Hold on, bakup bits. Yeah, like ones and zeros.

294
00:15:11.759 --> 00:15:15.440
<v Speaker 2>Exactly, those tiny ones and zeros that make up all

295
00:15:15.559 --> 00:15:16.519
<v Speaker 2>digital information.

296
00:15:16.960 --> 00:15:17.320
<v Speaker 1>Okay.

297
00:15:17.480 --> 00:15:21.159
<v Speaker 2>By flipping just a few bits, an attacker can potentially

298
00:15:21.240 --> 00:15:25.159
<v Speaker 2>change the meaning of a message wow, corrupt data, or

299
00:15:25.200 --> 00:15:28.080
<v Speaker 2>even trigger unexpected behavior in a device.

300
00:15:28.399 --> 00:15:28.759
<v Speaker 1>Okay.

301
00:15:28.960 --> 00:15:32.080
<v Speaker 2>Imagine like changing a single letter in a recipe.

302
00:15:32.320 --> 00:15:32.519
<v Speaker 1>Right.

303
00:15:33.480 --> 00:15:37.440
<v Speaker 2>It might seem small, but it could drastically alter the outcome.

304
00:15:38.039 --> 00:15:40.720
<v Speaker 2>That's what bitflipping does to digital data.

305
00:15:40.799 --> 00:15:43.519
<v Speaker 1>So they're basically introducing like typos.

306
00:15:43.639 --> 00:15:45.759
<v Speaker 2>That's a good analogy under the code to mess things

307
00:15:45.840 --> 00:15:49.240
<v Speaker 2>up exactly. And the scary thing is these attacks can

308
00:15:49.279 --> 00:15:52.840
<v Speaker 2>be difficult to detect, oh wow, because they often don't

309
00:15:52.960 --> 00:15:54.679
<v Speaker 2>leave any obvious traces.

310
00:15:54.960 --> 00:15:57.399
<v Speaker 1>So it's like a ghost in the machine it is.

311
00:15:57.480 --> 00:16:01.279
<v Speaker 1>So we've covered network sniffing right and data manipulation. What

312
00:16:01.320 --> 00:16:03.919
<v Speaker 1>are the tricks do the cybern inges have up their sleeves.

313
00:16:03.960 --> 00:16:07.279
<v Speaker 2>Well, let's shift gears a bit and talk about hardware hacking.

314
00:16:07.679 --> 00:16:10.720
<v Speaker 2>This is where we delve into the physical world of circuits,

315
00:16:10.759 --> 00:16:14.559
<v Speaker 2>micro controllers, and all sorts of electronic components.

316
00:16:14.799 --> 00:16:18.960
<v Speaker 1>Hardware hacking. Yeah, so like soldering irons and server boards.

317
00:16:19.360 --> 00:16:20.519
<v Speaker 1>That sounds pretty hardcore.

318
00:16:20.679 --> 00:16:23.759
<v Speaker 2>It can be. Yeah. The goal of hardware hacking is

319
00:16:23.840 --> 00:16:27.879
<v Speaker 2>usually to gain access to a device's firmware, which is

320
00:16:27.960 --> 00:16:31.960
<v Speaker 2>the low level software that controls its operation. Think of

321
00:16:31.960 --> 00:16:35.840
<v Speaker 2>it like the operating system for a specific piece of hardware.

322
00:16:35.879 --> 00:16:36.200
<v Speaker 1>Got it.

323
00:16:36.440 --> 00:16:41.720
<v Speaker 2>By modifying the firmware, an attacker can potentially bypass security mechanisms,

324
00:16:42.080 --> 00:16:46.360
<v Speaker 2>installed back doors, or even completely reprogram the device to

325
00:16:46.399 --> 00:16:47.960
<v Speaker 2>do something it wasn't intended to do.

326
00:16:48.360 --> 00:16:51.639
<v Speaker 1>So like taking apart a car engine and rewiring it. Yeah,

327
00:16:51.679 --> 00:16:52.519
<v Speaker 1>to make it go faster.

328
00:16:52.639 --> 00:16:55.360
<v Speaker 2>That's a pretty good analogy, okay. And the motivations for

329
00:16:55.399 --> 00:16:58.120
<v Speaker 2>hardware hacking can vary, right. Some people do it for

330
00:16:58.200 --> 00:17:02.679
<v Speaker 2>research purposes to understand how devices work and find vulnerabilities.

331
00:17:03.039 --> 00:17:06.759
<v Speaker 2>Others might do it to unlock hidden features okay, or

332
00:17:06.839 --> 00:17:09.039
<v Speaker 2>customize the device's functionality.

333
00:17:09.279 --> 00:17:11.119
<v Speaker 1>But I'm guessing there are also those who do it

334
00:17:11.160 --> 00:17:12.400
<v Speaker 1>for less noble reasons.

335
00:17:12.680 --> 00:17:17.519
<v Speaker 2>Unfortunately. Yes, yeh, a hacker could use hardware hacking techniques

336
00:17:17.559 --> 00:17:22.839
<v Speaker 2>to steal data, disrupt operations, or even cause physical damage.

337
00:17:22.920 --> 00:17:26.440
<v Speaker 1>This is getting into like some serious spy thriller territory here.

338
00:17:26.359 --> 00:17:29.279
<v Speaker 2>It is. Yeah. The book talks about using techniques like

339
00:17:29.440 --> 00:17:32.440
<v Speaker 2>side channel analysis and fault injection.

340
00:17:32.920 --> 00:17:35.799
<v Speaker 1>Okay. Side channel analysis, yeah, fault injection.

341
00:17:35.880 --> 00:17:37.880
<v Speaker 2>I'm gonna need a little more explanation on those, I

342
00:17:37.880 --> 00:17:41.400
<v Speaker 2>think so so. Side channel analysis involves monitoring the physical

343
00:17:41.480 --> 00:17:47.519
<v Speaker 2>properties of a device, like its power consumption or electromagnetic emissions, okay,

344
00:17:47.759 --> 00:17:52.000
<v Speaker 2>to glean information about its internal workings. It's like listening

345
00:17:52.079 --> 00:17:54.599
<v Speaker 2>to the subtle clicks and wars of a safe right

346
00:17:54.720 --> 00:17:58.359
<v Speaker 2>to figure out the combination. Fault injection, on the other hand,

347
00:17:58.440 --> 00:18:03.039
<v Speaker 2>involves deliberately introduced seeing errors or glitches okay into a

348
00:18:03.119 --> 00:18:07.559
<v Speaker 2>device's operation, right, to force it to reveal secrets or

349
00:18:07.599 --> 00:18:09.079
<v Speaker 2>behave in unexpected ways.

350
00:18:09.119 --> 00:18:11.359
<v Speaker 1>So you're basically trying to Yeah, it's.

351
00:18:11.240 --> 00:18:13.519
<v Speaker 2>Like jostling a vending machine to try and get a

352
00:18:13.559 --> 00:18:14.160
<v Speaker 2>free snack.

353
00:18:14.359 --> 00:18:14.960
<v Speaker 1>Right right.

354
00:18:15.440 --> 00:18:18.759
<v Speaker 2>Those are some pretty clever, albeit devious techniques.

355
00:18:18.920 --> 00:18:21.680
<v Speaker 1>It seems like these hackers are always thinking outside the box.

356
00:18:21.960 --> 00:18:24.359
<v Speaker 2>They are. That's why it's so important to stay ahead

357
00:18:24.359 --> 00:18:24.839
<v Speaker 2>of the curve.

358
00:18:25.119 --> 00:18:27.920
<v Speaker 1>Speaking of staying ahead of the curve, what are some

359
00:18:28.039 --> 00:18:32.440
<v Speaker 1>common tools and techniques used for this kind of hardware hacking?

360
00:18:33.200 --> 00:18:37.079
<v Speaker 2>Well, one popular tool is the JTAG interface JTAG. Yeah,

361
00:18:37.079 --> 00:18:40.200
<v Speaker 2>it stands for Joint Test Action Group. It's a standard

362
00:18:40.279 --> 00:18:44.039
<v Speaker 2>for testing and debugging electronic Circuitskay. Think of it like

363
00:18:44.079 --> 00:18:47.880
<v Speaker 2>a backdoor into the device's brain, allowing a hacker to

364
00:18:47.920 --> 00:18:50.759
<v Speaker 2>connect to a device and read or write data to

365
00:18:50.799 --> 00:18:53.640
<v Speaker 2>its memory, including the firmware.

366
00:18:53.920 --> 00:18:56.559
<v Speaker 1>JTAG Is that something that anyone can get their hands on.

367
00:18:56.799 --> 00:19:00.599
<v Speaker 2>JTAG interfaces themselves are fairly common. Yeah, you can find

368
00:19:00.599 --> 00:19:04.119
<v Speaker 2>them online or at electronics stores. They're often used by

369
00:19:04.200 --> 00:19:08.039
<v Speaker 2>engineers and hobbyists for legitimate purposes, but again, in the

370
00:19:08.079 --> 00:19:10.759
<v Speaker 2>wrong hands. They can also be used for malicious hacking.

371
00:19:11.119 --> 00:19:14.319
<v Speaker 1>So, like most of these tools, it's not the tool itself, No,

372
00:19:14.720 --> 00:19:16.480
<v Speaker 1>that's good or bad. It's the intention.

373
00:19:16.680 --> 00:19:17.839
<v Speaker 2>It's the intention behind it.

374
00:19:17.960 --> 00:19:20.359
<v Speaker 1>Another technique is called you ARET sniffing.

375
00:19:20.759 --> 00:19:24.359
<v Speaker 2>You ARE stands for universal asynchronous receiver transmitter Okay, and

376
00:19:24.400 --> 00:19:28.160
<v Speaker 2>it's a common interface for serial communication between different components

377
00:19:28.200 --> 00:19:28.839
<v Speaker 2>of a device.

378
00:19:29.079 --> 00:19:31.160
<v Speaker 1>Okay, you're losing me a bit with the technical jargon.

379
00:19:31.200 --> 00:19:34.039
<v Speaker 2>Imagine you have a walkie talkie conversation with a friend, right,

380
00:19:34.400 --> 00:19:36.319
<v Speaker 2>you are is kind of like the channel you're using

381
00:19:36.359 --> 00:19:39.720
<v Speaker 2>to communicate. By listening in on that channel, a hacker

382
00:19:40.000 --> 00:19:41.519
<v Speaker 2>could intercept your conversation.

383
00:19:41.839 --> 00:19:46.799
<v Speaker 1>So by sniffing the art traffic, they're essentially eavesdropping on

384
00:19:46.839 --> 00:19:47.519
<v Speaker 1>the conversation.

385
00:19:47.640 --> 00:19:48.440
<v Speaker 2>That's a good way to put it.

386
00:19:48.480 --> 00:19:50.079
<v Speaker 1>Yeah, between different parts of a device.

387
00:19:50.319 --> 00:19:52.839
<v Speaker 2>The book gives an example of using you ARET sniffing

388
00:19:52.960 --> 00:19:55.599
<v Speaker 2>to extract the firmware from a smart loock.

389
00:19:55.759 --> 00:19:56.079
<v Speaker 1>Okay.

390
00:19:56.240 --> 00:19:59.480
<v Speaker 2>Once they have the firmware, they can analyze it for vulnerabilities,

391
00:20:00.000 --> 00:20:03.759
<v Speaker 2>tracked encryption keys, or even modify it to change the

392
00:20:03.799 --> 00:20:04.880
<v Speaker 2>device's behavior.

393
00:20:05.400 --> 00:20:08.160
<v Speaker 1>So they're basically rewriting the rules of the game in

394
00:20:08.200 --> 00:20:08.599
<v Speaker 1>a way.

395
00:20:08.839 --> 00:20:12.000
<v Speaker 2>Yes, and that's why hardware hacking, yeah, could be.

396
00:20:11.920 --> 00:20:15.559
<v Speaker 1>Such a serious threat, especially in the context of the IoT.

397
00:20:15.839 --> 00:20:18.720
<v Speaker 2>Can you elaborate on that a bit sure. Why is

398
00:20:18.759 --> 00:20:23.160
<v Speaker 2>hardware hacking particularly dangerous for IoT devices?

399
00:20:23.559 --> 00:20:29.279
<v Speaker 1>Well, as we discussed earlier, many IoT devices are physically accessible, right.

400
00:20:29.319 --> 00:20:33.720
<v Speaker 1>They're in our homes, our offices, even our cars. This

401
00:20:33.799 --> 00:20:37.480
<v Speaker 1>makes them very vulnerable to hardware tampering. It's one thing

402
00:20:37.519 --> 00:20:40.759
<v Speaker 1>to worry about someone hacking your computer remotely, it's another

403
00:20:40.799 --> 00:20:44.240
<v Speaker 1>thing to worry about them physically messing with your devices.

404
00:20:44.480 --> 00:20:46.559
<v Speaker 2>Yeah. I see your point. Yeah, it feels a lot

405
00:20:46.599 --> 00:20:49.079
<v Speaker 2>more invasive it's been someone's physically tampering.

406
00:20:49.119 --> 00:20:52.319
<v Speaker 1>It does, and the consequences of hardware hacking could be significant.

407
00:20:52.799 --> 00:20:56.680
<v Speaker 1>Imagine someone tampering with the firmware of a medical device

408
00:20:57.119 --> 00:20:59.680
<v Speaker 1>or a self driving car. It could have life or death.

409
00:21:00.359 --> 00:21:02.000
<v Speaker 2>Okay, now you're just giving me nightmares.

410
00:21:02.200 --> 00:21:06.480
<v Speaker 1>But seriously, it makes you realize that we need to

411
00:21:06.519 --> 00:21:10.720
<v Speaker 1>think about security from both a software and a hardware perspective.

412
00:21:10.839 --> 00:21:12.920
<v Speaker 2>It's not enough to just protect your data.

413
00:21:13.000 --> 00:21:15.559
<v Speaker 1>You also need to protect the physical devices themselves.

414
00:21:15.880 --> 00:21:19.039
<v Speaker 2>That's one of the key takeaways from our deep dive

415
00:21:19.200 --> 00:21:20.960
<v Speaker 2>into IoT hacking.

416
00:21:21.279 --> 00:21:24.200
<v Speaker 1>It's not just about protecting your data. No, it's about

417
00:21:24.200 --> 00:21:28.079
<v Speaker 1>protecting your devices, your physical safety, and the integrity of

418
00:21:28.119 --> 00:21:30.759
<v Speaker 1>the systems we rely on every day. It's a lot

419
00:21:30.759 --> 00:21:33.160
<v Speaker 1>to wrap your head around, it is, But hopefully this

420
00:21:33.240 --> 00:21:36.480
<v Speaker 1>conversation has shed some light, yeah, on the hidden dangers

421
00:21:36.480 --> 00:21:39.319
<v Speaker 1>of the IoT and empowered you to take steps to

422
00:21:39.319 --> 00:21:40.079
<v Speaker 1>protect yourself.

423
00:21:40.200 --> 00:21:41.440
<v Speaker 2>Exactly what else do.

424
00:21:41.400 --> 00:21:42.720
<v Speaker 1>We need to cover in our deep dive?

425
00:21:42.960 --> 00:21:45.720
<v Speaker 2>Well, and the final part, we'll take everything we've learned,

426
00:21:45.960 --> 00:21:49.160
<v Speaker 2>okay and apply it to some real world attack scenarios.

427
00:21:49.240 --> 00:21:52.640
<v Speaker 2>Oh okay, it'll be like those uh true crime shows, right,

428
00:21:53.000 --> 00:21:55.440
<v Speaker 2>but for the world of cybersecurity.

429
00:21:54.799 --> 00:21:59.359
<v Speaker 1>Consider me hooked until next time, folks. All right, so

430
00:21:59.400 --> 00:22:01.839
<v Speaker 1>we've spent the life couple episodes kind of unpacking this

431
00:22:01.920 --> 00:22:03.519
<v Speaker 1>world of IoT hacking.

432
00:22:03.640 --> 00:22:04.000
<v Speaker 2>We have.

433
00:22:04.240 --> 00:22:08.920
<v Speaker 1>We've defined the IoT, We've explored those unique security challenges,

434
00:22:09.440 --> 00:22:12.759
<v Speaker 1>learned about all sorts of sneaky techniques hackers are using

435
00:22:12.799 --> 00:22:14.279
<v Speaker 1>to exploit those weaknesses.

436
00:22:14.480 --> 00:22:16.519
<v Speaker 2>It's been quite a journey, it has. But we're not

437
00:22:16.559 --> 00:22:19.000
<v Speaker 2>done yet. Okay, now it's time to actually see how

438
00:22:19.000 --> 00:22:21.640
<v Speaker 2>this all plays out in real world scenarios.

439
00:22:21.720 --> 00:22:23.519
<v Speaker 1>Okay, I'm ready for the main event. Hit me with

440
00:22:23.559 --> 00:22:24.279
<v Speaker 1>your best shot.

441
00:22:24.200 --> 00:22:26.359
<v Speaker 2>Right, So we're going to walk you through three different scenarios,

442
00:22:26.799 --> 00:22:31.839
<v Speaker 2>each one highlighting the potential consequences of insecure IoT devices.

443
00:22:32.160 --> 00:22:33.759
<v Speaker 1>Take me to the scene of the cybercrime.

444
00:22:34.519 --> 00:22:38.279
<v Speaker 2>Okay. So our first scenario, okay, takes place in a

445
00:22:38.359 --> 00:22:43.160
<v Speaker 2>seemingly ordinary apartment building. A hacker has their sites set

446
00:22:43.240 --> 00:22:45.519
<v Speaker 2>on bypassing the security system.

447
00:22:46.000 --> 00:22:49.400
<v Speaker 1>Okay, so we're talking physical security breaches. Now, this is getting.

448
00:22:49.160 --> 00:22:54.359
<v Speaker 2>Real, it is, yeah, Okay. This scenario focuses on RFID technology,

449
00:22:54.440 --> 00:22:58.759
<v Speaker 2>which is commonly used in keyless entry systems and security tags. Right.

450
00:22:59.119 --> 00:23:01.839
<v Speaker 2>The hackers weapon of choice here is a device called

451
00:23:01.880 --> 00:23:03.000
<v Speaker 2>the prox Mark three.

452
00:23:03.240 --> 00:23:05.839
<v Speaker 1>Prox Mark three. Yeah, that sounds like something out of

453
00:23:05.880 --> 00:23:06.480
<v Speaker 1>James Bond.

454
00:23:06.720 --> 00:23:09.240
<v Speaker 2>It might sound fancy, but it's actually a real tool

455
00:23:09.440 --> 00:23:12.559
<v Speaker 2>used by security researchers and unfortunately hackers as well.

456
00:23:12.759 --> 00:23:13.039
<v Speaker 1>Okay.

457
00:23:13.200 --> 00:23:17.119
<v Speaker 2>It can read, write, and emulate RFID tags. They can

458
00:23:17.200 --> 00:23:19.559
<v Speaker 2>even use something called a dark.

459
00:23:19.319 --> 00:23:21.720
<v Speaker 1>Side attack, a dark side attack.

460
00:23:21.519 --> 00:23:26.440
<v Speaker 2>To exploit vulnerabilities in an RFID cards random number generator,

461
00:23:26.680 --> 00:23:27.079
<v Speaker 2>so they.

462
00:23:26.960 --> 00:23:30.039
<v Speaker 1>Can create like a perfect copy of the RFID tag.

463
00:23:30.160 --> 00:23:32.720
<v Speaker 2>Yeah, pretty much. It just walts right in exactly and

464
00:23:32.759 --> 00:23:33.680
<v Speaker 2>it doesn't stop there.

465
00:23:33.799 --> 00:23:34.079
<v Speaker 1>Okay.

466
00:23:34.359 --> 00:23:38.440
<v Speaker 2>They might also target the building's alarm system using a

467
00:23:38.480 --> 00:23:40.440
<v Speaker 2>technique called jamming.

468
00:23:40.440 --> 00:23:43.759
<v Speaker 1>Jenning to disable it. Is that like creating interference? Yeah,

469
00:23:43.799 --> 00:23:44.319
<v Speaker 1>to block the.

470
00:23:44.319 --> 00:23:48.759
<v Speaker 2>Signal precisely, so, by transmitting a strong signal on the

471
00:23:48.799 --> 00:23:52.640
<v Speaker 2>same frequency as the alarm system, Okay, they can effectively

472
00:23:52.720 --> 00:23:57.359
<v Speaker 2>drown out the communication between the sensors and the control panel.

473
00:23:57.519 --> 00:24:00.799
<v Speaker 1>So they bypassed the RFID loss jam the alarm.

474
00:24:00.880 --> 00:24:03.240
<v Speaker 2>What's next, Let's say they want to spy on the

475
00:24:03.240 --> 00:24:05.000
<v Speaker 2>building security cameras.

476
00:24:05.200 --> 00:24:05.440
<v Speaker 1>Okay.

477
00:24:05.680 --> 00:24:09.640
<v Speaker 2>Many modern security cameras use IP based networks, meaning they

478
00:24:09.680 --> 00:24:12.480
<v Speaker 2>can be accessed remotely over the Internet. Oh and a

479
00:24:12.519 --> 00:24:16.000
<v Speaker 2>lot of these cameras have weak security configurations, making them

480
00:24:16.000 --> 00:24:18.200
<v Speaker 2>easy targets for hackers, So.

481
00:24:18.319 --> 00:24:21.400
<v Speaker 1>Even if they don't physically break into the building, they

482
00:24:21.440 --> 00:24:23.880
<v Speaker 1>can still see what's going on inside unfortunately.

483
00:24:23.960 --> 00:24:27.079
<v Speaker 2>Yes, and the book describes how hackers use a tool

484
00:24:27.160 --> 00:24:28.519
<v Speaker 2>called FFmpeg.

485
00:24:29.039 --> 00:24:29.960
<v Speaker 1>FFmpeg.

486
00:24:30.119 --> 00:24:31.039
<v Speaker 2>Yeah, what's that.

487
00:24:31.160 --> 00:24:34.039
<v Speaker 1>It stands for a fast forward m PEG. It's a

488
00:24:34.119 --> 00:24:38.400
<v Speaker 1>powerful multi media framework that can handle a wide range

489
00:24:38.440 --> 00:24:42.279
<v Speaker 1>of audio and video formats. So in this scenario, the

490
00:24:42.359 --> 00:24:46.599
<v Speaker 1>hacker would use FFmpeg to connect to the camera's RTP stream.

491
00:24:46.839 --> 00:24:48.160
<v Speaker 2>RTP stream that's.

492
00:24:48.079 --> 00:24:52.559
<v Speaker 1>The real time Transport protocol which is how videos often

493
00:24:52.599 --> 00:24:56.240
<v Speaker 1>sent over a network and then record the footage.

494
00:24:55.839 --> 00:24:58.839
<v Speaker 2>So they could watch the live footage, record it, or

495
00:24:58.880 --> 00:25:02.680
<v Speaker 2>even manipulate it exactly. It highlights the importance of securing

496
00:25:02.759 --> 00:25:07.160
<v Speaker 2>your IP cameras and any other network connected devices.

497
00:25:07.359 --> 00:25:09.759
<v Speaker 1>Yeah, just because something's connected to the Internet doesn't mean

498
00:25:09.799 --> 00:25:10.319
<v Speaker 1>it's secure.

499
00:25:11.599 --> 00:25:13.839
<v Speaker 2>Okay, that's enough to make me paranoid about all the

500
00:25:13.839 --> 00:25:14.680
<v Speaker 2>cameras in my life.

501
00:25:14.720 --> 00:25:17.599
<v Speaker 1>Okay. Scenario number two, okay, takes us from the world

502
00:25:17.640 --> 00:25:20.880
<v Speaker 1>of physical security to the realm of personal fitness.

503
00:25:21.079 --> 00:25:24.400
<v Speaker 2>At this time, our target is a smart treadmill.

504
00:25:24.519 --> 00:25:27.119
<v Speaker 1>A smart treadmill, so like one of those treadmills that

505
00:25:27.160 --> 00:25:30.079
<v Speaker 1>can track your workout data and connect to the internet.

506
00:25:30.200 --> 00:25:32.000
<v Speaker 1>Exactly what could possibly go wrong with that?

507
00:25:32.079 --> 00:25:35.240
<v Speaker 2>Well, as with any connected device, right, security is key,

508
00:25:35.480 --> 00:25:38.640
<v Speaker 2>and in this case, the treadmill has a few vulnerabilities

509
00:25:38.920 --> 00:25:40.119
<v Speaker 2>that a hacker could exploit.

510
00:25:40.359 --> 00:25:41.200
<v Speaker 1>Okay, I'm all yours.

511
00:25:41.759 --> 00:25:44.559
<v Speaker 2>So the book explains how a hacker could gain access

512
00:25:44.640 --> 00:25:49.720
<v Speaker 2>to the treadmill's internal systems by exploiting flaws in the

513
00:25:49.880 --> 00:25:53.720
<v Speaker 2>user interface or the web browser that's often built into

514
00:25:53.759 --> 00:25:58.559
<v Speaker 2>these devices. Many smart devices actually use embedded web browsers,

515
00:25:59.160 --> 00:26:03.400
<v Speaker 2>and those brows might be based on older, less secure

516
00:26:03.480 --> 00:26:06.119
<v Speaker 2>versions of software like Webit WebKit.

517
00:26:06.279 --> 00:26:07.359
<v Speaker 1>Yeah, that sounds familiar.

518
00:26:07.559 --> 00:26:11.359
<v Speaker 2>It's the engine that powers the Safari web browser on

519
00:26:11.640 --> 00:26:14.799
<v Speaker 2>Apple devices as well as many other browsers, and like

520
00:26:14.880 --> 00:26:19.119
<v Speaker 2>any software, it can have vulnerabilities. Packers can exploit these

521
00:26:19.240 --> 00:26:23.039
<v Speaker 2>vulnerabilities to gain control of the device. It's like finding

522
00:26:23.039 --> 00:26:26.039
<v Speaker 2>a backdoor into the treadmill's operating system.

523
00:26:26.119 --> 00:26:28.640
<v Speaker 1>And once they have access, what can they do? Change

524
00:26:28.680 --> 00:26:29.759
<v Speaker 1>the speed exactly.

525
00:26:30.799 --> 00:26:35.079
<v Speaker 2>Imagine someone taking control of your treadmill while you're running

526
00:26:35.119 --> 00:26:37.720
<v Speaker 2>at high speed. It could cause serious injury.

527
00:26:37.839 --> 00:26:40.519
<v Speaker 1>Okay, that's not funny, that's actually terrifying. Yeah.

528
00:26:40.559 --> 00:26:45.920
<v Speaker 2>It highlights the importance of choosing smart devices from reputable

529
00:26:46.119 --> 00:26:52.119
<v Speaker 2>manufacturers who prioritize security. Do your research before you buy,

530
00:26:52.880 --> 00:26:56.119
<v Speaker 2>and make sure you keep your devices updated with the

531
00:26:56.200 --> 00:26:59.960
<v Speaker 2>latest software patches, which often includes security fit.

532
00:27:00.680 --> 00:27:04.319
<v Speaker 1>And it's not just about physical safety, right These devices

533
00:27:04.359 --> 00:27:08.960
<v Speaker 1>are collecting a lot of personal data about us. They

534
00:27:09.039 --> 00:27:11.799
<v Speaker 1>are that data could be valuable to hackers.

535
00:27:11.839 --> 00:27:15.240
<v Speaker 2>It could they might use it for identity theft, blackmail,

536
00:27:15.359 --> 00:27:20.039
<v Speaker 2>or other malicious purposes. It's not just about protecting your devices, it's.

537
00:27:19.880 --> 00:27:21.480
<v Speaker 1>About protecting your data as well.

538
00:27:21.640 --> 00:27:25.960
<v Speaker 2>Okay, we've seen how hackers can bypass physical security systems,

539
00:27:26.519 --> 00:27:30.240
<v Speaker 2>spy on us through our security cameras, and even turn

540
00:27:30.279 --> 00:27:31.799
<v Speaker 2>our exercise equipment against us.

541
00:27:33.400 --> 00:27:35.359
<v Speaker 1>This is a lot to take in, it is, but

542
00:27:35.480 --> 00:27:38.759
<v Speaker 1>the key takeaway here is this, Okay, the IoT brings

543
00:27:38.799 --> 00:27:42.200
<v Speaker 1>a lot of convenience and potential benefits, but it also

544
00:27:42.279 --> 00:27:44.759
<v Speaker 1>introduces a whole new set of security risks.

545
00:27:44.799 --> 00:27:47.680
<v Speaker 2>And those risks are real. They are They're not just

546
00:27:47.759 --> 00:27:50.039
<v Speaker 2>theoretical threats. No, they're happening right now.

547
00:27:50.119 --> 00:27:51.200
<v Speaker 1>They are happening right now.

548
00:27:51.400 --> 00:27:52.519
<v Speaker 2>So what can we do about it?

549
00:27:52.960 --> 00:27:57.599
<v Speaker 1>Knowledge is power. By understanding the threats, we're better equipped

550
00:27:57.640 --> 00:28:03.240
<v Speaker 1>to defend against them. Research, choose your devices carefully and

551
00:28:03.359 --> 00:28:06.519
<v Speaker 1>keep them updated. Be mindful of the data you're sharing.

552
00:28:07.119 --> 00:28:09.279
<v Speaker 1>Just because a company offers like a free app or

553
00:28:09.319 --> 00:28:12.599
<v Speaker 1>a cool new feature doesn't mean you should blindly trust

554
00:28:12.640 --> 00:28:14.480
<v Speaker 1>them with your personal information.

555
00:28:14.759 --> 00:28:17.759
<v Speaker 2>It's a lot to think about, but I think it's important.

556
00:28:17.880 --> 00:28:20.759
<v Speaker 1>To have these conversations. I agree. We can't just bury

557
00:28:20.799 --> 00:28:23.640
<v Speaker 1>our heads in the sand and pretend that these threats

558
00:28:23.680 --> 00:28:26.599
<v Speaker 1>don't exist. They're real, and that's what we've tried to

559
00:28:26.599 --> 00:28:28.799
<v Speaker 1>do with this deep dive. We have to shed some

560
00:28:28.880 --> 00:28:33.079
<v Speaker 1>light on the hidden dangers of the IoT and empower

561
00:28:33.200 --> 00:28:35.559
<v Speaker 1>you to take control of your own security.

562
00:28:36.079 --> 00:28:38.960
<v Speaker 2>Well said, and on that note, I think we've reached

563
00:28:39.440 --> 00:28:44.240
<v Speaker 2>the end of our journey into the world of IoT hacking.

564
00:28:44.519 --> 00:28:49.440
<v Speaker 1>Stay curious, stay vigilant, and stay safe out there. Absolutely

565
00:28:49.519 --> 00:28:50.480
<v Speaker 1>until next time, folks,