WEBVTT

1
00:00:00.320 --> 00:00:03.200
<v Speaker 1>Hey, Carl here, we're on a mission to find new

2
00:00:03.240 --> 00:00:05.919
<v Speaker 1>fans of the show. I mean, where else can you

3
00:00:05.960 --> 00:00:10.240
<v Speaker 1>get real life comedy and horror in one podcast. You

4
00:00:10.279 --> 00:00:13.640
<v Speaker 1>can do your part by leaving us a review on iTunes, Spotify,

5
00:00:13.759 --> 00:00:16.879
<v Speaker 1>or wherever you get Security this Week. Also, you can

6
00:00:16.920 --> 00:00:19.399
<v Speaker 1>get an ad free feed by becoming a five dollars

7
00:00:19.399 --> 00:00:22.239
<v Speaker 1>a month patron. Go to Patreon dot Security this Week

8
00:00:22.320 --> 00:00:26.160
<v Speaker 1>dot com and sign up, and don't forget discord Discord

9
00:00:26.199 --> 00:00:28.839
<v Speaker 1>dot Security this Week dot com. Lots of good stuff

10
00:00:28.879 --> 00:00:32.439
<v Speaker 1>happening there. Yeah, I think that's it. So on with

11
00:00:32.560 --> 00:00:36.479
<v Speaker 1>the podcast. So this man wakes up in the hospital.

12
00:00:37.119 --> 00:00:40.479
<v Speaker 1>The phone rings. Doctor tells the man, I have really

13
00:00:40.479 --> 00:00:43.799
<v Speaker 1>bad news. You're very sick after your collapse yesterday. We

14
00:00:43.920 --> 00:00:49.880
<v Speaker 1>ordered several tests. You have avian flu ebola, your HIV positive,

15
00:00:50.000 --> 00:00:53.640
<v Speaker 1>and you have hepatitis. Wow. The guy says, what are

16
00:00:53.640 --> 00:00:56.640
<v Speaker 1>you gonna do? Doc replies, well, for starters, we're putting

17
00:00:56.679 --> 00:01:00.880
<v Speaker 1>you on a strict diet of only pizza. He says,

18
00:01:00.880 --> 00:01:03.280
<v Speaker 1>Will that really help me? Doc says no, but it's

19
00:01:03.320 --> 00:01:19.480
<v Speaker 1>the only thing I can fit under the door. Nothing

20
00:01:19.560 --> 00:01:23.799
<v Speaker 1>but serious, serious security talk here at Security this Week.

21
00:01:24.120 --> 00:01:26.640
<v Speaker 1>I'm Carl Franklin. That's Patrick Hines and Dwaine Laflatte.

22
00:01:26.920 --> 00:01:28.120
<v Speaker 2>Are we changing format?

23
00:01:29.680 --> 00:01:33.480
<v Speaker 1>I was gonna say that doesn't sound like all right,

24
00:01:33.519 --> 00:01:36.480
<v Speaker 1>we have six stories today. Let's start with this one.

25
00:01:36.760 --> 00:01:41.200
<v Speaker 1>US Cyber Agency SISSA. But you know SISSA, so we

26
00:01:41.239 --> 00:01:44.000
<v Speaker 1>had we had, we did have a Yeah, they do

27
00:01:44.079 --> 00:01:48.359
<v Speaker 1>the scores, right, US Cyber Agency SISSA exposed reams of

28
00:01:48.400 --> 00:01:50.920
<v Speaker 1>passwords and cloud keys to the open Web.

29
00:01:51.159 --> 00:01:52.959
<v Speaker 2>Yeah, they're supposed to be better than this is what

30
00:01:52.959 --> 00:01:53.680
<v Speaker 2>you're trying to say.

31
00:01:53.719 --> 00:01:57.599
<v Speaker 1>I think, yeah, yeah, I mean this is SISSA. They

32
00:01:57.599 --> 00:01:58.840
<v Speaker 1>give us the scores.

33
00:01:58.680 --> 00:02:03.239
<v Speaker 3>Cyber Cybersecurity, Infrastructure and Security Agency. There's a lot of

34
00:02:03.239 --> 00:02:05.280
<v Speaker 3>security in that name for someone who released a bunch

35
00:02:05.319 --> 00:02:05.920
<v Speaker 3>of passwords.

36
00:02:06.120 --> 00:02:08.120
<v Speaker 2>This never happened with Jen was running that show.

37
00:02:08.199 --> 00:02:11.080
<v Speaker 3>I know, right, Jen's got to come back West Point

38
00:02:11.120 --> 00:02:13.319
<v Speaker 3>Grad's right player of the guitar.

39
00:02:14.919 --> 00:02:15.400
<v Speaker 1>Yeah, I know.

40
00:02:15.840 --> 00:02:17.120
<v Speaker 3>I think she's happy where she is.

41
00:02:17.280 --> 00:02:18.759
<v Speaker 2>I think it's pretty geeky that we know that.

42
00:02:19.560 --> 00:02:20.960
<v Speaker 1>I didn't know you knew Jen.

43
00:02:21.560 --> 00:02:22.240
<v Speaker 2>She went to West FO.

44
00:02:22.439 --> 00:02:23.800
<v Speaker 1>You're on a first name basis with it.

45
00:02:23.919 --> 00:02:25.680
<v Speaker 3>We only wish we knew Jen. We knew not.

46
00:02:26.759 --> 00:02:31.400
<v Speaker 2>I'm very I'm very Kevin Bacon from Jen I know

47
00:02:31.439 --> 00:02:33.400
<v Speaker 2>a lot of people who know her. She knows a

48
00:02:33.439 --> 00:02:34.360
<v Speaker 2>lot of people that know me.

49
00:02:34.319 --> 00:02:35.199
<v Speaker 1>But I do not know her.

50
00:02:35.400 --> 00:02:37.240
<v Speaker 2>Okay, so wait, wait when Jenny Easterly?

51
00:02:37.319 --> 00:02:39.360
<v Speaker 3>Yeah, when were you at West Point?

52
00:02:39.439 --> 00:02:40.439
<v Speaker 2>I graduated eighty eight.

53
00:02:40.680 --> 00:02:43.360
<v Speaker 3>When did she graduate? You know, I think she was within.

54
00:02:43.240 --> 00:02:46.599
<v Speaker 2>A few years. I think we were there. You would

55
00:02:46.599 --> 00:02:47.400
<v Speaker 2>have to look it up to know.

56
00:02:47.639 --> 00:02:53.159
<v Speaker 1>Anyway, let's talk about this story. So the US Cybersecurity

57
00:02:53.199 --> 00:02:56.159
<v Speaker 1>Agency says I may have escaped a sizable security breach

58
00:02:56.719 --> 00:03:00.400
<v Speaker 1>thanks to a good faith security researcher who identified publy

59
00:03:00.479 --> 00:03:04.360
<v Speaker 1>exposed credentials that allowed access to government cloud and internal

60
00:03:04.400 --> 00:03:08.159
<v Speaker 1>agency system So were they compromised or were they not?

61
00:03:09.280 --> 00:03:12.159
<v Speaker 3>I mean, it's just as much a compromise as if

62
00:03:12.199 --> 00:03:15.280
<v Speaker 3>you take all of your passwords that you may have

63
00:03:15.439 --> 00:03:17.240
<v Speaker 3>and put them out on your public website.

64
00:03:17.240 --> 00:03:19.599
<v Speaker 1>All right, So nobody actually used them as far as

65
00:03:19.639 --> 00:03:20.240
<v Speaker 1>we know now.

66
00:03:20.319 --> 00:03:24.240
<v Speaker 3>So according to this, they're pretty sure that this cybersecurity

67
00:03:24.280 --> 00:03:28.159
<v Speaker 3>researcher late On I believe is his name. Okay, I'm

68
00:03:28.159 --> 00:03:33.000
<v Speaker 3>sure I'm butchering that found this before anybody else and

69
00:03:33.080 --> 00:03:36.240
<v Speaker 3>reported it relatively quickly, And it was first reported by

70
00:03:36.240 --> 00:03:38.520
<v Speaker 3>Brian Krabbs. We all know Brian Crabbs does a great job.

71
00:03:39.680 --> 00:03:42.240
<v Speaker 3>So moral of the story. The way this kind of

72
00:03:42.280 --> 00:03:46.159
<v Speaker 3>looks is there's a contractor doing work for SISSA. I'm

73
00:03:46.159 --> 00:03:49.080
<v Speaker 3>not entirely sure why he had a spreadsheet or sheheet

74
00:03:49.479 --> 00:03:53.199
<v Speaker 3>a spreadsheet of user names and passwords for valid government

75
00:03:53.280 --> 00:03:58.159
<v Speaker 3>insights and then went to make a GitHub commit and

76
00:03:58.280 --> 00:03:59.919
<v Speaker 3>committed it up to a public repo.

77
00:04:00.199 --> 00:04:03.439
<v Speaker 1>Got to be careful where you save those spreadsheets.

78
00:04:02.879 --> 00:04:04.520
<v Speaker 3>And then somebody saw it and save.

79
00:04:04.400 --> 00:04:06.599
<v Speaker 1>Them outside of the reposts.

80
00:04:07.039 --> 00:04:11.439
<v Speaker 3>Right exactly. Hey, listen, if you're vibe coding, mister contractor,

81
00:04:12.360 --> 00:04:14.879
<v Speaker 3>maybe ask the AI not to put secret stuff in

82
00:04:14.960 --> 00:04:16.639
<v Speaker 3>the in the directory that's coming public.

83
00:04:17.120 --> 00:04:19.360
<v Speaker 2>I'm pretty sure that's that's a good conclusion.

84
00:04:19.759 --> 00:04:20.759
<v Speaker 1>It was probably right.

85
00:04:20.800 --> 00:04:22.360
<v Speaker 3>There might have been a little vibe coding at all.

86
00:04:22.439 --> 00:04:25.199
<v Speaker 3>We're not confirming it here, but it's entirely possible.

87
00:04:25.240 --> 00:04:27.360
<v Speaker 1>You can neither confirm nor deny, but it does.

88
00:04:27.560 --> 00:04:31.000
<v Speaker 3>It does point out like you have a cybersecurity Infrastructure

89
00:04:31.040 --> 00:04:37.439
<v Speaker 3>agency department that's totally focused on you know, cyber and

90
00:04:37.439 --> 00:04:40.199
<v Speaker 3>and the right things to do, and they put our

91
00:04:40.240 --> 00:04:43.439
<v Speaker 3>recommendations around tabletop, you know, exercises you should do with

92
00:04:43.480 --> 00:04:47.480
<v Speaker 3>your organization, and you know, all sorts of really great

93
00:04:47.600 --> 00:04:50.279
<v Speaker 3>information about how to protect yourself as an organization. And

94
00:04:50.319 --> 00:04:53.759
<v Speaker 3>then you know, even they who are more cyber conscious

95
00:04:53.839 --> 00:04:56.360
<v Speaker 3>than most could have something like this happened.

96
00:04:56.399 --> 00:04:58.160
<v Speaker 1>So you never know.

97
00:04:58.240 --> 00:04:59.920
<v Speaker 2>So it'll be interesting if there's any followup for the

98
00:05:00.040 --> 00:05:03.319
<v Speaker 2>those were wondering. Jen At graduated two years after mem

99
00:05:03.800 --> 00:05:06.199
<v Speaker 2>nolascin ninety so wait, she would have been a plebe

100
00:05:06.279 --> 00:05:07.480
<v Speaker 2>when I was a junior.

101
00:05:07.519 --> 00:05:09.439
<v Speaker 3>When you were a junior, I would have been very mean,

102
00:05:09.680 --> 00:05:12.600
<v Speaker 3>so you could have you could have done mean things.

103
00:05:13.000 --> 00:05:15.759
<v Speaker 2>I was usually harassing my classmates because I was the

104
00:05:15.800 --> 00:05:17.839
<v Speaker 2>first sergeant, so I was more likely to be harassing

105
00:05:17.839 --> 00:05:18.560
<v Speaker 2>them than God.

106
00:05:18.600 --> 00:05:20.680
<v Speaker 1>I could have bumped into her in the hallway or

107
00:05:22.000 --> 00:05:24.160
<v Speaker 1>stolen her gaze over a cup of coffee.

108
00:05:24.279 --> 00:05:26.480
<v Speaker 2>Yeh, I just know that on LinkedIn. I think we

109
00:05:26.519 --> 00:05:27.680
<v Speaker 2>have a lot of people in common.

110
00:05:27.959 --> 00:05:34.319
<v Speaker 1>Interesting. Okay, anyway, let's move on. Cyber Unicorn Sierra Sierra

111
00:05:34.639 --> 00:05:38.959
<v Speaker 1>cy E r A acquires five month old startup Genie

112
00:05:39.040 --> 00:05:44.240
<v Speaker 1>Security and fifty million dollar deal. So it's an Israeli

113
00:05:44.319 --> 00:05:49.319
<v Speaker 1>startup with just five employees, joints cybersecurity company with acquisition Spree.

114
00:05:49.399 --> 00:05:51.079
<v Speaker 3>First off, they got a couple of things going for

115
00:05:51.160 --> 00:05:55.079
<v Speaker 3>him there is rarely, which means you know security, right,

116
00:05:55.199 --> 00:05:56.720
<v Speaker 3>I mean all your firewall.

117
00:05:56.319 --> 00:05:59.439
<v Speaker 2>Companies positive bias. Is that what you're saying, Yeah, exactly,

118
00:05:59.519 --> 00:06:03.240
<v Speaker 2>That's what I'm yeah. So this the reason this story

119
00:06:03.240 --> 00:06:06.160
<v Speaker 2>is here is because this market's a little crazy. People

120
00:06:06.240 --> 00:06:09.439
<v Speaker 2>don't know where cyber is going, whether it's going away,

121
00:06:09.519 --> 00:06:13.879
<v Speaker 2>which has been predicted for thirty years by people including

122
00:06:13.959 --> 00:06:18.319
<v Speaker 2>Dwayne and I at one point, and there's a lot

123
00:06:18.319 --> 00:06:20.360
<v Speaker 2>of fear. There's a lot of people who are trying

124
00:06:20.360 --> 00:06:22.920
<v Speaker 2>to figure out where it's going. I think it's going

125
00:06:23.000 --> 00:06:26.040
<v Speaker 2>to be more of the same. We've noticed that there

126
00:06:26.079 --> 00:06:29.519
<v Speaker 2>are more patches in every more vulnerabilities in every patch.

127
00:06:29.920 --> 00:06:32.680
<v Speaker 2>Things are accelerating, but it's been on that trajectory for

128
00:06:32.720 --> 00:06:35.600
<v Speaker 2>a while. This will be a big evolution in what

129
00:06:35.720 --> 00:06:39.519
<v Speaker 2>cyber means and what protection looks like. But I don't

130
00:06:39.519 --> 00:06:41.879
<v Speaker 2>think the industry itself goes away. I don't think the

131
00:06:41.879 --> 00:06:45.399
<v Speaker 2>industry automates to the head of a pin on AI

132
00:06:45.560 --> 00:06:47.839
<v Speaker 2>or anything like that. But it it's definitely changing. So

133
00:06:48.000 --> 00:06:50.560
<v Speaker 2>this is a sign of these times that a five

134
00:06:50.639 --> 00:06:55.720
<v Speaker 2>month old, five persons startup can sell for fifty million dollars.

135
00:06:57.120 --> 00:06:58.879
<v Speaker 2>Some of that's going to just be hyped, that's going

136
00:06:58.920 --> 00:07:00.360
<v Speaker 2>to wash away, and some of it going to be

137
00:07:00.480 --> 00:07:03.399
<v Speaker 2>they just have a really good idea or they're doing

138
00:07:03.480 --> 00:07:04.879
<v Speaker 2>things in a very interesting way.

139
00:07:05.040 --> 00:07:08.560
<v Speaker 3>So fifty million dollars five months start up, ten million

140
00:07:08.600 --> 00:07:12.360
<v Speaker 3>dollars a month they earned invaluation. That's on an idea,

141
00:07:12.480 --> 00:07:15.879
<v Speaker 3>not bad on an idea. So that's yeah, that's insane.

142
00:07:16.199 --> 00:07:19.279
<v Speaker 2>So this isn't really a news like that we normally cover,

143
00:07:19.399 --> 00:07:21.360
<v Speaker 2>but but it's it is. You're going to see a

144
00:07:21.399 --> 00:07:24.600
<v Speaker 2>lot more stories like this. There's a lot more you know,

145
00:07:24.680 --> 00:07:29.480
<v Speaker 2>the market punishing incumbents like like CrowdStrike and Carbon Black

146
00:07:29.879 --> 00:07:32.720
<v Speaker 2>because of an announcement of an AI that might come

147
00:07:32.759 --> 00:07:37.040
<v Speaker 2>out that might change things. Everybody's waiting for where the

148
00:07:37.079 --> 00:07:38.439
<v Speaker 2>chips are going to fall. I don't think we're going

149
00:07:38.480 --> 00:07:39.079
<v Speaker 2>to know this year.

150
00:07:39.279 --> 00:07:42.040
<v Speaker 3>Yeah, although, okay, there's gonna be a lot of awesome

151
00:07:42.040 --> 00:07:43.800
<v Speaker 3>things this year. I know, I know some of the

152
00:07:43.920 --> 00:07:45.319
<v Speaker 3>some of the things that we're working on are awesome.

153
00:07:45.360 --> 00:07:46.639
<v Speaker 2>Okay, and that should scare us all.

154
00:07:46.639 --> 00:07:47.839
<v Speaker 3>It's gonna be a lot of awesome things.

155
00:07:48.120 --> 00:07:50.040
<v Speaker 1>Yeah, things that we can't talk about.

156
00:07:50.279 --> 00:07:53.000
<v Speaker 3>Things we can't talk about, but things that are awesome.

157
00:07:53.160 --> 00:07:54.519
<v Speaker 2>Wow, it's getting through.

158
00:07:56.199 --> 00:07:59.120
<v Speaker 1>Oh, my god. All right, next story, Webworm deploys Echo

159
00:07:59.199 --> 00:08:05.399
<v Speaker 1>creep and graph worm backdoors using Discord and Microsoft graph API.

160
00:08:05.800 --> 00:08:08.639
<v Speaker 1>You know, if I just read that out of context

161
00:08:08.759 --> 00:08:13.439
<v Speaker 1>to my mom, she would think I'd lost my mind.

162
00:08:13.639 --> 00:08:16.600
<v Speaker 3>Oh wait, yeah, read this sentence, Carl.

163
00:08:16.360 --> 00:08:19.839
<v Speaker 1>Hey mom. Webworm deploys Echo creep and graph worm backdoors

164
00:08:19.920 --> 00:08:23.800
<v Speaker 1>using Discord and MS graph APIs plan.

165
00:08:23.680 --> 00:08:25.680
<v Speaker 3>Is don't judge in one one because you're having a stroke.

166
00:08:27.639 --> 00:08:29.920
<v Speaker 1>She just parachute in from over here.

167
00:08:29.759 --> 00:08:32.679
<v Speaker 3>And yeah, it doesn't get any better. The third paragraph

168
00:08:32.799 --> 00:08:36.440
<v Speaker 3>in a tax mounted by the group have leveraged remote

169
00:08:36.480 --> 00:08:38.759
<v Speaker 3>access trojans. All right, we all know what rats are, right.

170
00:08:39.679 --> 00:08:43.799
<v Speaker 3>Piece of malware allows somebody to access your system, like

171
00:08:44.120 --> 00:08:48.720
<v Speaker 3>ghost Rat nine to two rat aka the Hydrack and

172
00:08:48.960 --> 00:08:51.440
<v Speaker 3>mick Rat with cheese. The threat actor is said to

173
00:08:51.480 --> 00:08:55.440
<v Speaker 3>overlap with China's Nexus cluster, tracked as Phishmonger or Aquatic

174
00:08:55.519 --> 00:08:59.480
<v Speaker 3>Panda six Little Monkeys in the Space Pirates Six Little

175
00:08:59.519 --> 00:09:03.639
<v Speaker 3>Monkeys is best known for deploying ghost Rat. Like, what

176
00:09:03.720 --> 00:09:04.120
<v Speaker 3>the hell?

177
00:09:04.200 --> 00:09:05.240
<v Speaker 1>What do you think of that? Mom?

178
00:09:05.720 --> 00:09:10.320
<v Speaker 3>Exactly? It's it's like some sort of japanimation thing, like

179
00:09:10.360 --> 00:09:12.159
<v Speaker 3>we're I don't know what we're talking about. Anymore.

180
00:09:12.240 --> 00:09:15.200
<v Speaker 1>It's the most surreal sentence I've ever read on the internet.

181
00:09:15.519 --> 00:09:18.679
<v Speaker 3>Yeah, a paragraph rather six little monkeys working with the

182
00:09:18.720 --> 00:09:21.200
<v Speaker 3>phishmongers in the space prits. I mean, I thought I'd

183
00:09:21.240 --> 00:09:22.720
<v Speaker 3>never see it in my life, but there you go.

184
00:09:22.759 --> 00:09:25.200
<v Speaker 1>All right, So in English, what happened here?

185
00:09:27.000 --> 00:09:28.440
<v Speaker 2>So the space.

186
00:09:31.559 --> 00:09:35.759
<v Speaker 3>To follow me here. So all this is is this

187
00:09:35.799 --> 00:09:38.919
<v Speaker 3>is a quick warning that we've talked about commanding control

188
00:09:38.960 --> 00:09:40.600
<v Speaker 3>in the past, right, So, if you have a piece

189
00:09:40.639 --> 00:09:43.440
<v Speaker 3>of malicious software sitting on your network, it's probably reaching

190
00:09:43.440 --> 00:09:49.120
<v Speaker 3>out somewhere. Commanding control is much harder to detect on

191
00:09:49.159 --> 00:09:53.240
<v Speaker 3>your network if it's using valid channels. So, for example,

192
00:09:53.279 --> 00:09:56.320
<v Speaker 3>if I'm reaching out over DNS, or I'm reaching out

193
00:09:56.320 --> 00:10:00.159
<v Speaker 3>over web traffic or like, you probably won't pick that

194
00:10:00.240 --> 00:10:05.240
<v Speaker 3>up right now. Corporate networks generally inspect web traffic, right

195
00:10:05.279 --> 00:10:07.639
<v Speaker 3>so they can see what's inside web traffic, So you

196
00:10:07.679 --> 00:10:10.399
<v Speaker 3>don't want to use web traffic. Corporate networks a lot

197
00:10:10.399 --> 00:10:13.879
<v Speaker 3>of times will use secure DNS, so kind of hard

198
00:10:13.879 --> 00:10:15.600
<v Speaker 3>for you to breach that as well and use it

199
00:10:15.600 --> 00:10:19.039
<v Speaker 3>as a command control structure. But then again, corporate networks

200
00:10:19.039 --> 00:10:24.120
<v Speaker 3>will also use things like Microsoft Office, and they sometimes

201
00:10:24.200 --> 00:10:28.559
<v Speaker 3>will use chat programs like Discord, so it's harder to

202
00:10:28.600 --> 00:10:31.759
<v Speaker 3>inspect that traffic. So what this is saying is there's

203
00:10:31.759 --> 00:10:33.519
<v Speaker 3>a lot of threat actors out there that are now

204
00:10:33.759 --> 00:10:38.399
<v Speaker 3>piggybacking on Discord as a command and control which is

205
00:10:38.399 --> 00:10:39.960
<v Speaker 3>funny because we've been doing it for a year or quarter,

206
00:10:40.720 --> 00:10:45.159
<v Speaker 3>but piggybacking Discord for command and control because it's harder

207
00:10:45.200 --> 00:10:48.799
<v Speaker 3>to detect the traffic that's inside there, and also using

208
00:10:48.840 --> 00:10:54.759
<v Speaker 3>the Microsoft Graph API. If the Microsoft Graph API sounds

209
00:10:55.840 --> 00:10:58.960
<v Speaker 3>like it might be familiar, if you guys have been

210
00:10:59.000 --> 00:11:00.759
<v Speaker 3>listening to this show for a while, which we should.

211
00:11:00.840 --> 00:11:03.320
<v Speaker 1>We should tell everybody what it is. I mean, it's

212
00:11:03.360 --> 00:11:07.679
<v Speaker 1>basically the one API to rule them all for your accounts, right,

213
00:11:07.759 --> 00:11:11.240
<v Speaker 1>what could go wrong? It's it's basically gives you access

214
00:11:11.279 --> 00:11:15.519
<v Speaker 1>to all of your documents, your Excel, spreadsheets, your Mike

215
00:11:15.679 --> 00:11:19.159
<v Speaker 1>you know what is it? Three sixty Yeah, all that

216
00:11:19.279 --> 00:11:22.879
<v Speaker 1>stuff in one place. It's just one huge API for

217
00:11:23.080 --> 00:11:25.799
<v Speaker 1>you and your account to go get everything that you

218
00:11:25.879 --> 00:11:27.480
<v Speaker 1>can do on Microsoft's websites.

219
00:11:27.720 --> 00:11:29.960
<v Speaker 3>And there used to be, uh, there was a tactic

220
00:11:30.320 --> 00:11:33.879
<v Speaker 3>called token tactics. So if you guys look up token

221
00:11:33.919 --> 00:11:38.600
<v Speaker 3>tactics where you could actually request a user's graph API

222
00:11:38.759 --> 00:11:42.559
<v Speaker 3>through a sneaky social engineering way and then gain access

223
00:11:42.600 --> 00:11:46.240
<v Speaker 3>to their accounts, and then have the ability to renew

224
00:11:46.279 --> 00:11:49.600
<v Speaker 3>your token every ninety days that you contain, you'd still

225
00:11:49.679 --> 00:11:52.279
<v Speaker 3>maintain access to their to their accounts, their you know,

226
00:11:52.320 --> 00:11:56.679
<v Speaker 3>Microsoft Office Suite without them ever seeing you log in,

227
00:11:57.080 --> 00:11:59.320
<v Speaker 3>even if you change your password. So there's a lot

228
00:11:59.320 --> 00:12:01.080
<v Speaker 3>of really kind of cool things you could do with

229
00:12:01.120 --> 00:12:03.080
<v Speaker 3>the graph API. A while ago, some of that's been

230
00:12:03.120 --> 00:12:05.159
<v Speaker 3>shut down, but now it's being used for commanding control.

231
00:12:05.320 --> 00:12:07.360
<v Speaker 1>So hang on second, my interns at the door, what,

232
00:12:08.200 --> 00:12:12.000
<v Speaker 1>oh no, thanks, elliit Later he just brought me a micrat.

233
00:12:11.559 --> 00:12:19.360
<v Speaker 4>With cheese, sit down with the Space pirates in this

234
00:12:20.799 --> 00:12:27.039
<v Speaker 4>six little monkeys, Yeah exactly, mcrat.

235
00:12:26.679 --> 00:12:30.200
<v Speaker 1>All right, So you know, this is just a tale

236
00:12:30.240 --> 00:12:33.799
<v Speaker 1>of woe. There's nothing really that anybody can do about it.

237
00:12:33.879 --> 00:12:34.600
<v Speaker 1>Stuff happens.

238
00:12:34.759 --> 00:12:36.759
<v Speaker 3>Yeah, and I think a lot of it is like,

239
00:12:36.879 --> 00:12:41.879
<v Speaker 3>no matter how good you are at monitoring outbound traffic,

240
00:12:42.960 --> 00:12:45.480
<v Speaker 3>there's still gonna be ways that people can get past that.

241
00:12:45.600 --> 00:12:48.279
<v Speaker 3>So defense and depth, like Patrick is always talking about,

242
00:12:48.480 --> 00:12:53.720
<v Speaker 3>is key here, right, Don't just trust one outbound filtering

243
00:12:53.840 --> 00:12:55.879
<v Speaker 3>rule to make sure that oh we're not getting hit

244
00:12:55.919 --> 00:12:59.200
<v Speaker 3>with this this type of traffic, you know, you obviously

245
00:12:59.279 --> 00:13:02.679
<v Speaker 3>need point detection on laptops and desktops. You need to

246
00:13:02.679 --> 00:13:07.279
<v Speaker 3>make sure that if Discord is not a corporate communications

247
00:13:07.279 --> 00:13:12.279
<v Speaker 3>platform for you, heads up block it, right, That's probably

248
00:13:12.279 --> 00:13:12.919
<v Speaker 3>the safest thing.

249
00:13:12.919 --> 00:13:15.879
<v Speaker 2>So I'm going to say something very Dwayne esque that

250
00:13:16.080 --> 00:13:19.240
<v Speaker 2>I should probably have edited out, but I probably won't

251
00:13:19.440 --> 00:13:19.840
<v Speaker 2>if I.

252
00:13:20.320 --> 00:13:22.639
<v Speaker 3>So the sick way, do I have to get the lawyers? Now?

253
00:13:22.679 --> 00:13:23.799
<v Speaker 2>Should I play the music?

254
00:13:23.840 --> 00:13:24.240
<v Speaker 1>Patrick?

255
00:13:25.720 --> 00:13:33.840
<v Speaker 2>It's the signal protocol is published and you can write

256
00:13:33.919 --> 00:13:38.080
<v Speaker 2>your own rapper and use the signal protocol. Would that

257
00:13:38.159 --> 00:13:40.440
<v Speaker 2>be distinguishable? So if you get an organization that uses

258
00:13:40.519 --> 00:13:44.360
<v Speaker 2>signal and you had a agent or piece of code

259
00:13:44.360 --> 00:13:47.919
<v Speaker 2>that was using would that be discernible? So by the

260
00:13:48.080 --> 00:13:49.159
<v Speaker 2>by the perimeter.

261
00:13:49.360 --> 00:13:56.039
<v Speaker 3>Here will tell you the signal protocol is the way

262
00:13:56.039 --> 00:13:59.480
<v Speaker 3>that you can wrap the messages, but not necessarily the

263
00:13:59.519 --> 00:14:01.799
<v Speaker 3>ports on back end server and that sort of stuff.

264
00:14:01.840 --> 00:14:06.240
<v Speaker 3>So could I could I mimic the way signal actually

265
00:14:06.279 --> 00:14:10.879
<v Speaker 3>talks through the network, Probably you wouldn't be able to

266
00:14:10.879 --> 00:14:13.679
<v Speaker 3>intercept it. You're absolutely right, I mean, that's probably a

267
00:14:13.799 --> 00:14:20.480
<v Speaker 3>very secure way for you to transmit data. Honestly, even

268
00:14:20.559 --> 00:14:23.600
<v Speaker 3>using maybe something like the signal CLI on a rat

269
00:14:23.759 --> 00:14:26.039
<v Speaker 3>of some sort where you can just send messages through

270
00:14:26.039 --> 00:14:29.000
<v Speaker 3>a normal signal protocol and the signal.

271
00:14:28.679 --> 00:14:31.159
<v Speaker 1>Servers to idea.

272
00:14:31.279 --> 00:14:34.679
<v Speaker 3>Twayne, I like that, all right, signal.

273
00:14:34.759 --> 00:14:36.879
<v Speaker 1>Now you got to put the theme song in there somewhere.

274
00:14:39.080 --> 00:14:41.440
<v Speaker 1>All right, Well, take a break, okay, and we'll be

275
00:14:41.600 --> 00:14:44.960
<v Speaker 1>right back after these very very very very important messages.

276
00:14:48.679 --> 00:14:50.639
<v Speaker 1>And we're back. It's Security of this week. I'm Carl.

277
00:14:50.679 --> 00:14:53.240
<v Speaker 1>Let's Dwayne and Patrick, and we got a couple more

278
00:14:54.120 --> 00:14:58.360
<v Speaker 1>interesting stories here. Cisco warns of new critical s D

279
00:14:58.720 --> 00:15:03.120
<v Speaker 1>one flaw exploited in zero day attacks. And this is

280
00:15:03.159 --> 00:15:06.000
<v Speaker 1>a ten, isn't it? It's a ten.

281
00:15:06.720 --> 00:15:07.679
<v Speaker 2>They stuck the landing.

282
00:15:07.960 --> 00:15:12.320
<v Speaker 3>I know, right, well done? Uh yeah, I think this

283
00:15:12.360 --> 00:15:15.000
<v Speaker 3>is a ten because A not hard to exploit. B

284
00:15:15.159 --> 00:15:17.799
<v Speaker 3>you gain administrative access and get to manipulate the sd

285
00:15:17.879 --> 00:15:18.840
<v Speaker 3>WAN fabric and.

286
00:15:18.799 --> 00:15:20.120
<v Speaker 2>CE definitely on the internet.

287
00:15:20.200 --> 00:15:20.919
<v Speaker 1>People put it on.

288
00:15:20.879 --> 00:15:23.600
<v Speaker 3>The internet, right, so super accessible.

289
00:15:23.679 --> 00:15:26.559
<v Speaker 2>Well it's not really much good without the Internet.

290
00:15:26.720 --> 00:15:29.559
<v Speaker 3>Yeah, I got this awesome network that can't talk to anything.

291
00:15:30.320 --> 00:15:32.879
<v Speaker 3>The thing is a network at that point. Yeah, the

292
00:15:33.039 --> 00:15:36.399
<v Speaker 3>thing that I work, Yeah exactly, it's definitely a not work.

293
00:15:37.600 --> 00:15:41.399
<v Speaker 3>The thing I find fascinating about and we've seen several

294
00:15:41.440 --> 00:15:45.039
<v Speaker 3>styles of attacks like this is why oh, why oh,

295
00:15:45.080 --> 00:15:49.360
<v Speaker 3>why would you put management access because you have to

296
00:15:49.399 --> 00:15:53.080
<v Speaker 3>hit the management interface? Why would you put management access

297
00:15:53.279 --> 00:15:55.440
<v Speaker 3>out on the internet? And if you did for a

298
00:15:55.480 --> 00:15:59.159
<v Speaker 3>particular reason, why wouldn't you point it at a trusted

299
00:15:59.200 --> 00:16:02.440
<v Speaker 3>IP address, like oh, only my house IPEE can hit

300
00:16:02.480 --> 00:16:05.720
<v Speaker 3>this management interface on the internet so that I can

301
00:16:05.720 --> 00:16:08.440
<v Speaker 3>come and you know whatever. But it just it doesn't

302
00:16:08.440 --> 00:16:10.480
<v Speaker 3>make any sense to me when we see firewalls being

303
00:16:10.480 --> 00:16:13.240
<v Speaker 3>exploited remotely and you go, well, how's that possible? Firewalls

304
00:16:13.320 --> 00:16:15.840
<v Speaker 3>drop traffic? Oh unless you tell it. Yeah, listen to

305
00:16:16.000 --> 00:16:19.320
<v Speaker 3>management traffic on the internet, which still blows my mind.

306
00:16:19.440 --> 00:16:21.759
<v Speaker 1>Now I'm reading this and I don't see that there's

307
00:16:21.799 --> 00:16:24.440
<v Speaker 1>a patch available. But I do see that in this

308
00:16:24.519 --> 00:16:28.600
<v Speaker 1>is May twentieth when recording this, that SISA has added

309
00:16:28.759 --> 00:16:33.000
<v Speaker 1>this flaw to the Known Exploited Vulnerabilities Catalog, ordering federal

310
00:16:33.039 --> 00:16:37.759
<v Speaker 1>agents to patch affected devices by May seventeenth. Right, okay,

311
00:16:38.360 --> 00:16:41.399
<v Speaker 1>but I don't see any patch.

312
00:16:41.320 --> 00:16:44.480
<v Speaker 3>Any any listed patch now, So in this case, the

313
00:16:44.519 --> 00:16:50.519
<v Speaker 3>patch immediately is really a remediation step, so they're unplug it. Yeah, yeah, honestly,

314
00:16:50.879 --> 00:16:53.840
<v Speaker 3>you know you're not far off evacurate there, unplug it.

315
00:16:53.840 --> 00:16:57.240
<v Speaker 3>It's the the remediation step is don't put the management

316
00:16:57.360 --> 00:16:58.480
<v Speaker 3>interface on the internet.

317
00:16:58.600 --> 00:17:00.519
<v Speaker 2>Friends. Don't let friends manage from the internet.

318
00:17:00.600 --> 00:17:01.200
<v Speaker 1>Yeah, that's right.

319
00:17:02.039 --> 00:17:05.119
<v Speaker 3>And if you have to for some reason, then restrict

320
00:17:05.119 --> 00:17:05.759
<v Speaker 3>it to a non.

321
00:17:05.640 --> 00:17:07.039
<v Speaker 1>IP and use a VPN.

322
00:17:07.240 --> 00:17:09.519
<v Speaker 3>Yeah. Yeah, so that there's a bunch of different ways

323
00:17:09.519 --> 00:17:11.359
<v Speaker 3>that you can secure this so that people can't get

324
00:17:11.400 --> 00:17:13.759
<v Speaker 3>access to it. But yeah, this is being actively exploited.

325
00:17:13.759 --> 00:17:16.200
<v Speaker 3>That's one of the other reasons this is so high.

326
00:17:16.759 --> 00:17:18.720
<v Speaker 3>So if you are running I don't even think we

327
00:17:18.799 --> 00:17:21.680
<v Speaker 3>mentioned the CV this is CVE twenty twenty six two

328
00:17:21.720 --> 00:17:25.319
<v Speaker 3>one eight two. Yeah, if you are running a Cisco

329
00:17:25.519 --> 00:17:30.119
<v Speaker 3>Catalyst sd WAN controller, there is an authentication bypass and

330
00:17:30.119 --> 00:17:31.680
<v Speaker 3>you need to go out and make sure your management

331
00:17:31.759 --> 00:17:34.279
<v Speaker 3>interface is not accessible on the internet.

332
00:17:34.640 --> 00:17:36.759
<v Speaker 1>Just do it when you get to work. Man. Yeah, right,

333
00:17:36.759 --> 00:17:37.319
<v Speaker 1>come on, you know.

334
00:17:37.279 --> 00:17:39.680
<v Speaker 3>I didn't even tell you. Carl. On the Discord group,

335
00:17:39.720 --> 00:17:43.440
<v Speaker 3>we had a savvy listener hit us up about our

336
00:17:43.880 --> 00:17:45.279
<v Speaker 3>last recording.

337
00:17:45.480 --> 00:17:48.359
<v Speaker 1>Okay, and the and the text.

338
00:17:48.079 --> 00:17:52.400
<v Speaker 3>Goes something like this, Oh, lords of the iPhone, who

339
00:17:53.799 --> 00:17:57.640
<v Speaker 3>who was it during this recording of security this week?

340
00:17:57.880 --> 00:18:01.720
<v Speaker 3>Who had an Android device being out at about twenty

341
00:18:01.799 --> 00:18:02.519
<v Speaker 3>four minutes in.

342
00:18:02.759 --> 00:18:04.359
<v Speaker 1>Oh was that? And it was?

343
00:18:04.440 --> 00:18:06.240
<v Speaker 3>It was actually on my desk. I do I have

344
00:18:06.279 --> 00:18:09.039
<v Speaker 3>a sam and even named the device I do, I

345
00:18:09.039 --> 00:18:11.920
<v Speaker 3>have a Samsung Android device sitting on my desk.

346
00:18:11.680 --> 00:18:14.039
<v Speaker 1>Here started making happy noises, Yeah.

347
00:18:14.000 --> 00:18:17.400
<v Speaker 3>Making happy noises because we do a lot of testing, right,

348
00:18:17.440 --> 00:18:19.200
<v Speaker 3>tearing apart devices and that sort of stuff, and that

349
00:18:19.279 --> 00:18:21.400
<v Speaker 3>one was just happened to be charging on my desk

350
00:18:21.759 --> 00:18:24.000
<v Speaker 3>so I could tear it apart later. But yeah, so

351
00:18:24.839 --> 00:18:27.160
<v Speaker 3>that was funny. Though. Well, I'm well done. I think

352
00:18:27.200 --> 00:18:28.279
<v Speaker 3>that was larsk.

353
00:18:28.400 --> 00:18:31.000
<v Speaker 1>I think we got to send that personal lock pick set.

354
00:18:31.079 --> 00:18:33.440
<v Speaker 3>I think so I'm gonna do it. Yes, lock picks

355
00:18:33.480 --> 00:18:36.839
<v Speaker 3>to you, sir or ma'am, but lockpicks to you all right,

356
00:18:36.880 --> 00:18:38.039
<v Speaker 3>so I will hit you up privately.

357
00:18:38.200 --> 00:18:41.240
<v Speaker 1>Okay, we done with that story. Weird, terrible, but you

358
00:18:41.279 --> 00:18:42.319
<v Speaker 1>know what are you gonna do?

359
00:18:42.480 --> 00:18:42.839
<v Speaker 2>Patch?

360
00:18:42.920 --> 00:18:46.920
<v Speaker 1>All right? Next story, g seven countries release AI S

361
00:18:46.960 --> 00:18:50.640
<v Speaker 1>bomb guidance, so we know what software bill of materials is,

362
00:18:50.680 --> 00:18:53.839
<v Speaker 1>but now there's and there's a bomb for AI.

363
00:18:54.119 --> 00:18:57.680
<v Speaker 2>So basically here's the thing. A software bill of materials

364
00:18:57.880 --> 00:18:59.839
<v Speaker 2>is needed because we need to know what you have

365
00:19:00.359 --> 00:19:02.720
<v Speaker 2>in the military dependencies when you had when you were

366
00:19:02.759 --> 00:19:04.880
<v Speaker 2>defending something, you had to know what we were defending.

367
00:19:04.960 --> 00:19:07.200
<v Speaker 2>You to know what your inventory was, what your people were,

368
00:19:07.839 --> 00:19:10.000
<v Speaker 2>your vehicles, things like that. To defend you have to

369
00:19:10.000 --> 00:19:11.119
<v Speaker 2>have an inventory.

370
00:19:11.200 --> 00:19:15.920
<v Speaker 3>So it's not unlike if you're defending from an attacker, exactly, exactly.

371
00:19:16.240 --> 00:19:18.480
<v Speaker 2>So the software bill of materials is something we've been

372
00:19:18.519 --> 00:19:20.680
<v Speaker 2>talking about for a long time. Yeah, you don't know

373
00:19:20.720 --> 00:19:22.440
<v Speaker 2>what you have, you don't know how to protect it.

374
00:19:22.880 --> 00:19:27.640
<v Speaker 2>That also applies to crypto. Okay, so a C bomb

375
00:19:28.079 --> 00:19:30.839
<v Speaker 2>is a cryptographic bill of materials, meaning in order to

376
00:19:30.839 --> 00:19:33.680
<v Speaker 2>become quantum safe, see I work that in in order

377
00:19:33.720 --> 00:19:36.519
<v Speaker 2>to become quantum safe, I'm already asleep. You have to

378
00:19:37.079 --> 00:19:39.160
<v Speaker 2>you have to know where you're using crypto and what

379
00:19:39.240 --> 00:19:41.839
<v Speaker 2>kind of crypto you're using. Well, that is now true,

380
00:19:41.880 --> 00:19:45.440
<v Speaker 2>and it's painfully obvious that you need that for AI

381
00:19:45.559 --> 00:19:49.319
<v Speaker 2>as well, because shadow it T used to be a

382
00:19:49.359 --> 00:19:52.240
<v Speaker 2>problem with in the access days, in the mainframe days,

383
00:19:52.240 --> 00:19:54.079
<v Speaker 2>and we you know, those of us with gray hair

384
00:19:54.119 --> 00:19:55.920
<v Speaker 2>remember that, and the young people don't.

385
00:19:56.319 --> 00:19:58.880
<v Speaker 1>I tell everybody what shadow i T is.

386
00:19:58.920 --> 00:20:02.960
<v Speaker 2>Shadow it is. Hey, I need the powers that be

387
00:20:03.079 --> 00:20:04.920
<v Speaker 2>to help me solve this problem. And they're like, go

388
00:20:05.559 --> 00:20:08.039
<v Speaker 2>sit on an egg. I can't. I don't have time

389
00:20:08.039 --> 00:20:11.160
<v Speaker 2>for you today. So they go solve it themselves. And

390
00:20:11.200 --> 00:20:14.200
<v Speaker 2>so they vibe coding, or they're they're they're chatting, or

391
00:20:14.240 --> 00:20:16.920
<v Speaker 2>they have little devices that they bring the meetings that

392
00:20:17.000 --> 00:20:20.160
<v Speaker 2>are recording all the secrets and the NBA material and

393
00:20:20.200 --> 00:20:22.440
<v Speaker 2>it's sending out off to the cloud. If you don't

394
00:20:22.480 --> 00:20:25.000
<v Speaker 2>know what AI is inside the walls, you don't know

395
00:20:25.039 --> 00:20:26.960
<v Speaker 2>how to secure it and lock it down.

396
00:20:27.160 --> 00:20:32.359
<v Speaker 1>So we're talking about the LM hosts, the models, all

397
00:20:32.680 --> 00:20:33.200
<v Speaker 1>all of that.

398
00:20:33.480 --> 00:20:36.920
<v Speaker 2>Now everything you can talk to is potentially.

399
00:20:36.640 --> 00:20:39.880
<v Speaker 3>Yeah, take Zoom right now, what code basis they have

400
00:20:39.920 --> 00:20:41.599
<v Speaker 3>access to? I don't know if you guys have seen

401
00:20:41.640 --> 00:20:44.160
<v Speaker 3>the latest incarnation of Zoom. If you install it on

402
00:20:44.200 --> 00:20:47.680
<v Speaker 3>your desktop, if you fire up a Microsoft Teams meeting,

403
00:20:48.960 --> 00:20:52.519
<v Speaker 3>not Zoom, a Teams meeting, Zoom pops up and says,

404
00:20:52.599 --> 00:20:53.960
<v Speaker 3>do you want me to take notes?

405
00:20:54.000 --> 00:20:54.680
<v Speaker 1>I have seen that.

406
00:20:55.039 --> 00:20:55.880
<v Speaker 2>I did not see that.

407
00:20:56.039 --> 00:20:59.000
<v Speaker 3>Yeah, yeah, yeah. The latest one will now say anytime

408
00:20:59.039 --> 00:21:01.759
<v Speaker 3>you are in a video and or voice call, anytime

409
00:21:01.839 --> 00:21:03.480
<v Speaker 3>the mic pops up, it'll be like, do you want

410
00:21:03.480 --> 00:21:05.880
<v Speaker 3>me to take notes? I see, I see you're doing

411
00:21:05.920 --> 00:21:07.680
<v Speaker 3>a thing. I can take notes and that's all passing

412
00:21:07.720 --> 00:21:10.279
<v Speaker 3>through their AI. It's very h and you ask yourself,

413
00:21:10.839 --> 00:21:14.200
<v Speaker 3>so what AI are they using, and what are the ramifications?

414
00:21:14.240 --> 00:21:16.200
<v Speaker 2>And which Chinese cities it hosted it?

415
00:21:18.440 --> 00:21:22.160
<v Speaker 1>I think the word is province, But which province they

416
00:21:22.160 --> 00:21:23.920
<v Speaker 1>have cities? That's true?

417
00:21:24.000 --> 00:21:28.680
<v Speaker 3>No, no, just provinces. Uh so, yeah, needless to say,

418
00:21:29.519 --> 00:21:30.400
<v Speaker 3>I think it's important.

419
00:21:30.480 --> 00:21:32.839
<v Speaker 1>So why why is it called an AI S bomb

420
00:21:32.880 --> 00:21:34.359
<v Speaker 1>and not just an AI bomb?

421
00:21:34.480 --> 00:21:37.720
<v Speaker 2>It should be an A bomb, A bomb AI bill

422
00:21:37.720 --> 00:21:39.279
<v Speaker 2>of materials.

423
00:21:38.759 --> 00:21:42.039
<v Speaker 1>Right, I guess because software.

424
00:21:41.680 --> 00:21:46.319
<v Speaker 2>It's k I, not AI. Huh ok because KUNLUS is

425
00:21:46.480 --> 00:21:49.279
<v Speaker 2>artificial kul intelligence k E.

426
00:21:49.680 --> 00:21:50.319
<v Speaker 3>That's thanks.

427
00:21:50.440 --> 00:21:55.079
<v Speaker 1>So this is guidance from government agencies, from the group

428
00:21:55.079 --> 00:21:59.880
<v Speaker 1>of seven that jointly published this guidance to help organizations

429
00:22:00.079 --> 00:22:02.559
<v Speaker 1>create an S bomb for a So here's the thing.

430
00:22:02.599 --> 00:22:06.440
<v Speaker 2>We are woefully behind in S bomb. Yeah, and so

431
00:22:06.559 --> 00:22:10.039
<v Speaker 2>now we're just piling on and crypto bomb and A bomb.

432
00:22:10.039 --> 00:22:12.839
<v Speaker 3>And I was gonna say, it's it's on the queue.

433
00:22:12.920 --> 00:22:14.720
<v Speaker 3>We'll work on it in about ten or twelve years.

434
00:22:14.759 --> 00:22:16.680
<v Speaker 2>I think the only one we're up to speed with

435
00:22:16.759 --> 00:22:17.960
<v Speaker 2>is lip bomb. That's it.

436
00:22:18.559 --> 00:22:22.359
<v Speaker 3>Yeah, exactly, good call, good call, all right.

437
00:22:22.480 --> 00:22:28.039
<v Speaker 1>So the feature story is not about the man who

438
00:22:28.039 --> 00:22:31.720
<v Speaker 1>woke up in a hospital, but it's the first public

439
00:22:31.880 --> 00:22:37.519
<v Speaker 1>mac Os kernel memory corruption exploit on Apple M five.

440
00:22:37.880 --> 00:22:40.279
<v Speaker 1>And the reason it's a feature story is because you

441
00:22:40.319 --> 00:22:45.240
<v Speaker 1>don't really hear of problems with Max and mac Os

442
00:22:45.240 --> 00:22:45.960
<v Speaker 1>being attacked.

443
00:22:46.559 --> 00:22:49.880
<v Speaker 2>Or isn't it like designed to not have memory problems?

444
00:22:49.880 --> 00:22:53.240
<v Speaker 2>That's the whole Yeah, so yeah, valu wick, isn't it?

445
00:22:53.319 --> 00:22:56.799
<v Speaker 3>Yeah? Apple spent I don't know, five years and billions

446
00:22:56.799 --> 00:22:59.759
<v Speaker 3>of dollars on what they call Memory into Integrity and

447
00:22:59.759 --> 00:23:00.880
<v Speaker 3>Force m I E.

448
00:23:01.119 --> 00:23:01.920
<v Speaker 2>How's that working out?

449
00:23:02.240 --> 00:23:07.920
<v Speaker 3>Uh? Well, it's it's actually been pretty awesome up til now.

450
00:23:07.960 --> 00:23:09.920
<v Speaker 2>Somebody, we are.

451
00:23:09.880 --> 00:23:12.759
<v Speaker 1>The iPhone, the lords of the iPhone apparently.

452
00:23:12.440 --> 00:23:15.200
<v Speaker 3>Yeah, the low words of the iPhone say it's awesome.

453
00:23:15.880 --> 00:23:18.759
<v Speaker 3>Som i E is the culmination of an unprecedented design

454
00:23:18.759 --> 00:23:22.319
<v Speaker 3>and engineering effort spanning half a decade that combines unique

455
00:23:22.319 --> 00:23:26.240
<v Speaker 3>strengths of Apple silicon hardware and advanced operating system security

456
00:23:26.680 --> 00:23:30.039
<v Speaker 3>to make sure that memory corruption doesn't happen. And then

457
00:23:30.240 --> 00:23:32.000
<v Speaker 3>if you take a look at this article, there are

458
00:23:32.079 --> 00:23:35.000
<v Speaker 3>two guys standing in front of the Apple, you know,

459
00:23:35.440 --> 00:23:39.000
<v Speaker 3>the Apple signing Cooper Tino mm hmm. And if you

460
00:23:39.079 --> 00:23:40.960
<v Speaker 3>zoom in on that picture that's redacted.

461
00:23:42.039 --> 00:23:46.359
<v Speaker 1>Yeah, that's right. I wondered why the red square. It's

462
00:23:46.359 --> 00:23:47.920
<v Speaker 1>a big red square if you.

463
00:23:48.000 --> 00:23:50.680
<v Speaker 3>Read interestingly enough, if you read above it, it says

464
00:23:51.759 --> 00:23:55.240
<v Speaker 3>from type confusion to root. Okay, so they're using type

465
00:23:55.279 --> 00:23:57.279
<v Speaker 3>confusion and they say they're not going to publish anything

466
00:23:57.359 --> 00:24:00.880
<v Speaker 3>until uh, you know, until you into has been patched.

467
00:24:00.880 --> 00:24:02.680
<v Speaker 3>And then if you look at the first look at

468
00:24:02.680 --> 00:24:07.000
<v Speaker 3>the video, they actually, oddly enough in this video show

469
00:24:07.039 --> 00:24:10.359
<v Speaker 3>a bunch of the memory addresses that they're actually attacking.

470
00:24:11.480 --> 00:24:14.960
<v Speaker 3>So you can probably reasonably say, AI will look at

471
00:24:15.000 --> 00:24:19.319
<v Speaker 3>the picture and the video the spray that they're doing

472
00:24:19.359 --> 00:24:21.240
<v Speaker 3>here and say, oh, yeah, I know what they're attacking.

473
00:24:21.359 --> 00:24:24.960
<v Speaker 1>So the most interesting thing about this whole article is

474
00:24:25.000 --> 00:24:28.680
<v Speaker 1>that the engineers of the people that wrote the article,

475
00:24:28.920 --> 00:24:34.240
<v Speaker 1>working together with Mythos Preview, built a working exploit in

476
00:24:34.400 --> 00:24:40.440
<v Speaker 1>five days. Yeah, isn't so, you know, I guess they're

477
00:24:40.480 --> 00:24:41.079
<v Speaker 1>the good guys.

478
00:24:41.119 --> 00:24:43.079
<v Speaker 2>But did they go to arubafore the other three?

479
00:24:43.200 --> 00:24:48.200
<v Speaker 3>I mean, yeah, whats it so long? I don't even understand.

480
00:24:49.519 --> 00:24:52.039
<v Speaker 1>Says we wanted Early this week, we had a meeting

481
00:24:52.079 --> 00:24:55.039
<v Speaker 1>at Apple Park and Coupertino. While there, we also shared

482
00:24:55.079 --> 00:24:58.160
<v Speaker 1>with Apple our latest vulnerability research report, the first public

483
00:24:58.680 --> 00:25:02.000
<v Speaker 1>Maco S Colonel Memory cre exploit on M five Silicon

484
00:25:02.920 --> 00:25:06.039
<v Speaker 1>Surviving Mie. It was laser printed in honor of our

485
00:25:06.079 --> 00:25:09.359
<v Speaker 1>hacker friends. We wanted to report it in person instead

486
00:25:09.400 --> 00:25:12.200
<v Speaker 1>of getting buried in the submission flood that some unfortunate

487
00:25:12.240 --> 00:25:16.759
<v Speaker 1>poone to own participants just experience. Most respected hackers avoid

488
00:25:16.839 --> 00:25:21.319
<v Speaker 1>human interaction whenever possible, So this physical strategy may give

489
00:25:21.400 --> 00:25:23.920
<v Speaker 1>us a slight edge in the eternal race for five

490
00:25:23.960 --> 00:25:25.759
<v Speaker 1>minutes of faming glory on Twitter.

491
00:25:26.240 --> 00:25:26.839
<v Speaker 3>True story.

492
00:25:27.799 --> 00:25:29.880
<v Speaker 1>So this is the story of the exploit in our

493
00:25:29.920 --> 00:25:33.640
<v Speaker 1>field trip. Full technical details will be shared after Apple

494
00:25:33.759 --> 00:25:36.960
<v Speaker 1>fixes the vulnerabilities in attack path. Hopefully it won't take

495
00:25:37.000 --> 00:25:40.359
<v Speaker 1>our beloved company too long. We only budgeted one year

496
00:25:40.359 --> 00:25:46.319
<v Speaker 1>of domain registration fees for this attack. So it's basically

497
00:25:46.359 --> 00:25:50.960
<v Speaker 1>two guys who used and I haven't read far enough

498
00:25:51.000 --> 00:25:53.079
<v Speaker 1>to know where they were from, but they are.

499
00:25:53.160 --> 00:25:56.640
<v Speaker 2>So are they employees of Apple? Because you've got to

500
00:25:56.680 --> 00:25:58.960
<v Speaker 2>be with one of the companies or a contractor to

501
00:25:59.079 --> 00:25:59.880
<v Speaker 2>use myth those right.

502
00:25:59.799 --> 00:26:01.319
<v Speaker 1>Now, Yeah, that's what that's my question.

503
00:26:01.480 --> 00:26:08.400
<v Speaker 3>Yeah, are ways to sign up for mythos depending on

504
00:26:08.400 --> 00:26:11.799
<v Speaker 3>whether you're a reputable security researcher and that sort of stuff.

505
00:26:12.279 --> 00:26:14.680
<v Speaker 3>I'm gonna leave it at that. What's interesting is if

506
00:26:14.720 --> 00:26:19.599
<v Speaker 3>you click halfway through this article, there's this mad bugs link, yes,

507
00:26:19.839 --> 00:26:24.359
<v Speaker 3>where they talk about all of their AI exploits, like

508
00:26:24.480 --> 00:26:29.160
<v Speaker 3>using using Aida to find bugs in Ida, using Quawa.

509
00:26:29.519 --> 00:26:32.880
<v Speaker 3>How I got rooted on FreeBSD with a shell script.

510
00:26:32.960 --> 00:26:35.240
<v Speaker 3>All right, So the mac os one, right, So they

511
00:26:35.279 --> 00:26:38.880
<v Speaker 3>go through a bunch of places that your reverse engineering

512
00:26:38.920 --> 00:26:40.279
<v Speaker 3>tools are belonging to us.

513
00:26:40.359 --> 00:26:44.119
<v Speaker 1>So this is a private hacking security firms Califf. It's

514
00:26:44.119 --> 00:26:46.640
<v Speaker 1>a security firm from California, trying to keep the Internet

515
00:26:46.680 --> 00:26:49.759
<v Speaker 1>together by occasionally taking it apart.

516
00:26:50.519 --> 00:26:50.960
<v Speaker 3>Codex.

517
00:26:51.240 --> 00:26:55.480
<v Speaker 1>So they somehow got access to Mythos Mythos. Yeah, yeah.

518
00:26:55.519 --> 00:26:57.960
<v Speaker 2>It may be because they're working on some of the

519
00:26:58.160 --> 00:27:00.200
<v Speaker 2>maybe the contracts with somebody.

520
00:27:00.160 --> 00:27:02.599
<v Speaker 3>Yeah or not. I mean, honestly, you can. We could

521
00:27:02.599 --> 00:27:05.160
<v Speaker 3>apply for Mythos if we wanted to have access to Mythos.

522
00:27:05.240 --> 00:27:08.240
<v Speaker 3>It's not that big a deal. It's just not it's okay,

523
00:27:09.240 --> 00:27:12.359
<v Speaker 3>just not great. There are better ways than Mythos too.

524
00:27:13.079 --> 00:27:13.920
<v Speaker 3>I'm gonna leave it at that.

525
00:27:14.039 --> 00:27:16.240
<v Speaker 1>Yes, well, thank you, okay, yeah, thanks.

526
00:27:16.119 --> 00:27:16.960
<v Speaker 3>Going to stop talking.

527
00:27:17.279 --> 00:27:19.039
<v Speaker 1>Yeah, you should forward the lawyer rock jump on.

528
00:27:19.119 --> 00:27:20.680
<v Speaker 3>But there yeah, there are better models than.

529
00:27:21.079 --> 00:27:23.440
<v Speaker 1>Okay, anybody you want to make rat with cheese before

530
00:27:23.440 --> 00:27:24.599
<v Speaker 1>we sign off.

531
00:27:24.680 --> 00:27:26.359
<v Speaker 3>Let me ask my Space pirates.

532
00:27:26.480 --> 00:27:29.119
<v Speaker 1>Okay, Well that's it. That's all that happened that we

533
00:27:29.160 --> 00:27:32.839
<v Speaker 1>could find anyway in what happened last week, and we'll

534
00:27:32.880 --> 00:27:35.200
<v Speaker 1>talk to you next week on security this week, Bye bye,

535
00:27:35.240 --> 00:27:36.240
<v Speaker 1>thanks everybody, my guys,
