1
00:00:00,160 --> 00:00:03,240
Today we're doing an MDR reality check.

2
00:00:03,520 --> 00:00:06,440
If you procure MDR services, what do you expect,

3
00:00:06,440 --> 00:00:09,920
what you want and what did you actually get in practice?

4
00:00:10,160 --> 00:00:11,240
Welcome to Threat Talks.

5
00:00:11,240 --> 00:00:12,480
My name is Lieuwe Jan Koning.

6
00:00:12,480 --> 00:00:17,560
And here from the head office at Venable in San Francisco at the RSA conference.

7
00:00:17,680 --> 00:00:22,520
Let's shed some light in the mystifying world of MDR vendors.

8
00:00:22,680 --> 00:00:25,680
Let's get on to it. Welcome to Threat Talks.

9
00:00:25,720 --> 00:00:29,200
Let's delve deep into the dynamic world of cybersecurity.

10
00:00:29,560 --> 00:00:32,560
I'm joined here today by my colleague Nicholai Piagentini.

11
00:00:32,760 --> 00:00:36,520
He is a technical enablement engineer here based out of San Francisco.

12
00:00:36,680 --> 00:00:38,040
Nick, welcome to the show.

13
00:00:38,040 --> 00:00:39,720
Thank you for having me. Great to have you back

14
00:00:39,720 --> 00:00:41,520
actually, yeah.

15
00:00:41,520 --> 00:00:42,680
So you've been in the space

16
00:00:42,680 --> 00:00:46,800
for in, well, around the Bay area for decades, actually.

17
00:00:46,840 --> 00:00:48,560
Yeah, over 20 years. Over 20 years.

18
00:00:48,560 --> 00:00:48,720
Yeah.

19
00:00:48,720 --> 00:00:53,480
You've seen many, many vendors and, well, your kids go to the same school

20
00:00:53,480 --> 00:00:55,280
as all those other people that work everywhere.

21
00:00:55,280 --> 00:01:00,240
So, yeah, you have a very good view on what's out here in terms of vendors,

22
00:01:00,240 --> 00:01:03,680
in terms of profiles of MDR, XDR, MDR, whatever it is.

23
00:01:03,720 --> 00:01:07,240
MDDR, MDR yeah, what they do, what they don't do especially.

24
00:01:07,400 --> 00:01:12,120
So yeah, you're my first choice, actually, to talk to you about what

25
00:01:12,160 --> 00:01:15,160
customer expectations are when procuring an MDR service

26
00:01:15,160 --> 00:01:18,680
and and what the reality actually is, and if there's a gap.

27
00:01:18,680 --> 00:01:22,840
So and we'll leave the audience with a few pointers

28
00:01:23,000 --> 00:01:26,080
what to what to look for and what to be careful about when selecting one.

29
00:01:26,200 --> 00:01:29,720
So yeah, what would you say is something

30
00:01:29,720 --> 00:01:33,000
that organizations really expect? Yeah.

31
00:01:33,040 --> 00:01:35,200
So I think it's really interesting in that MDR

32
00:01:35,200 --> 00:01:37,200
can mean a lot of things to different vendors, right.

33
00:01:37,200 --> 00:01:39,520
It's not how would you define them. The standardized her

34
00:01:41,200 --> 00:01:43,640
managed detection and response.

35
00:01:43,640 --> 00:01:46,880
Yet we often will see tools that are not managed

36
00:01:46,880 --> 00:01:49,560
really in any way and don't actually cover any response. Right.

37
00:01:49,560 --> 00:01:51,280
Maybe it's just detection or that.

38
00:01:51,280 --> 00:01:54,120
And so as a result, it's not really a clear tool.

39
00:01:54,120 --> 00:01:57,240
I think when customers go through the booth,

40
00:01:57,280 --> 00:02:01,440
talk to somebody selling some kind of MDR XDR solution,

41
00:02:01,480 --> 00:02:06,080
they think what they're getting is a single pane of glass, one place

42
00:02:06,080 --> 00:02:06,680
to consume

43
00:02:06,680 --> 00:02:11,240
all their logs that could be related to security in any way that can apply

44
00:02:11,560 --> 00:02:14,360
logic and analysis to them, enrich

45
00:02:14,360 --> 00:02:17,360
those logs, preprocess them,

46
00:02:17,600 --> 00:02:22,200
act as an extension or force multiplier to their SOC, right,

47
00:02:22,240 --> 00:02:26,640
and then provide automated or extremely clear remediation.

48
00:02:26,720 --> 00:02:31,400
Help them with any kind of maybe auditing right or compliance,

49
00:02:31,720 --> 00:02:35,160
and ultimately provide them with a data

50
00:02:35,200 --> 00:02:38,840
lake of their logs for look back right.

51
00:02:38,880 --> 00:02:41,360
Or for threat hunting historically.

52
00:02:41,360 --> 00:02:44,360
And so this is "M" for many is

53
00:02:44,360 --> 00:02:48,160
it doesn't mean managing the outcomes of the events

54
00:02:48,160 --> 00:02:52,360
or like managing the threat that is that is there and remediating it.

55
00:02:52,360 --> 00:02:56,640
Or does it mean managing the fact that logs are being collected?

56
00:02:56,680 --> 00:03:01,360
The answer is yes because different vendors it means and or question.

57
00:03:01,400 --> 00:03:01,760
Yeah.

58
00:03:01,760 --> 00:03:06,360
I think what we find is that many of them do not see the management

59
00:03:06,360 --> 00:03:11,520
as a human in the loop, which really, you mean is supposed to mean expectations.

60
00:03:11,520 --> 00:03:14,320
You mean or what? What's being offered in the expectations, right?

61
00:03:14,320 --> 00:03:15,920
They see it as just a tool

62
00:03:15,920 --> 00:03:18,040
that pulls these logs together and provides this enhancement.

63
00:03:18,040 --> 00:03:21,040
They do not envision specifically maybe

64
00:03:21,080 --> 00:03:24,080
another SOC engineer as part of it,

65
00:03:24,160 --> 00:03:26,880
which is unfortunate because that's really the best way to deploy it, right?

66
00:03:26,880 --> 00:03:29,760
You need a human in the loop for that, at least for now.

67
00:03:29,760 --> 00:03:32,840
Now, in current state of AI, certainly, absolutely.

68
00:03:32,840 --> 00:03:35,120
Now with the current state of AI, no. Okay.

69
00:03:35,120 --> 00:03:36,880
And what about the scope of things?

70
00:03:36,880 --> 00:03:40,640
I mean, because MDR typically what we see in Vietnam is that is

71
00:03:40,640 --> 00:03:44,720
an endpoint solution that now has an MDR type surface on top of it.

72
00:03:44,720 --> 00:03:48,920
So it's EDR endpoint detection and response becoming MDR or network

73
00:03:48,920 --> 00:03:53,040
detection and response becoming MDR or XDR becoming MDR.

74
00:03:53,240 --> 00:03:55,440
Yeah. Or data detection in response. Yeah, yeah.

75
00:03:55,440 --> 00:03:59,000
Every vendor skins it for what they do, right?

76
00:03:59,320 --> 00:04:01,840
If every if you only have a hammer, everything's a nail, right.

77
00:04:01,840 --> 00:04:05,400
So whatever the vendor does that becomes kind of that first letter there.

78
00:04:05,440 --> 00:04:08,160
But it is always pitched as a single pane of glass. Right.

79
00:04:08,160 --> 00:04:10,040
That term gets so overused.

80
00:04:10,040 --> 00:04:13,680
But the reality is so the expectation is that the scope is everywhere.

81
00:04:13,680 --> 00:04:18,000
So that it system that's the endpoint, that is the network that is the OT as well

82
00:04:18,000 --> 00:04:19,600
probably. Well, I mean,

83
00:04:19,600 --> 00:04:22,360
very few vendors would actually say that because they don't cover it.

84
00:04:22,360 --> 00:04:27,000
But yeah, the implication is that this should be the tool you use to consume

85
00:04:27,000 --> 00:04:32,280
your logs, apply logic to it, maybe AI, right, and have a clear outcomes, right?

86
00:04:32,280 --> 00:04:35,480
Adoption in noise, all of those features.

87
00:04:35,880 --> 00:04:37,000
But the reality is

88
00:04:37,000 --> 00:04:41,240
it is very hard to find a tool that does all that you need in one.

89
00:04:41,240 --> 00:04:44,440
You'll end up with multiple MDR, right?

90
00:04:44,440 --> 00:04:44,840
Whatever.

91
00:04:44,840 --> 00:04:48,760
Whatever you want to put in front of it was really removes the advantage of it.

92
00:04:49,280 --> 00:04:51,480
Yeah, because then you end up with multiple.

93
00:04:51,480 --> 00:04:53,600
But there's a thing called platform mission for that.

94
00:04:53,600 --> 00:04:55,640
Right? It's a made up word. But yes.

95
00:04:57,040 --> 00:04:57,640
Yeah, yeah

96
00:04:57,640 --> 00:05:01,800
it's the idea of but well that's a term that can be thrown out that implies

97
00:05:01,840 --> 00:05:04,840
things all working together cleanly, natively.

98
00:05:05,360 --> 00:05:10,200
No one has accomplished that even within large security companies, right?

99
00:05:10,240 --> 00:05:13,760
Companies that cover many different aspects of cybersecurity,

100
00:05:14,040 --> 00:05:17,840
they are really unable to pull all of their own logs together to one place.

101
00:05:17,880 --> 00:05:20,280
Why is that? You mean you think?

102
00:05:20,280 --> 00:05:23,240
I think it's because many of these logs have very different context.

103
00:05:23,240 --> 00:05:27,680
Many times they've come, so it's always been hard product or exposition.

104
00:05:27,680 --> 00:05:30,400
That's a different thing. It's an integration problem then. Yeah.

105
00:05:30,400 --> 00:05:33,400
You know there's there's the idea that I can consume all the logs.

106
00:05:33,480 --> 00:05:36,520
I could theoretically create a tool that takes any log I send it.

107
00:05:36,560 --> 00:05:38,360
Yeah. It's called a sim, right, right.

108
00:05:38,360 --> 00:05:39,440
Just throw everything at it.

109
00:05:39,440 --> 00:05:39,760
Yeah.

110
00:05:39,760 --> 00:05:41,320
Can I provide that same level

111
00:05:41,320 --> 00:05:44,720
of enhancement and intelligence to every kind of log that comes in?

112
00:05:45,080 --> 00:05:47,400
And if we look at the industry, the answer is no.

113
00:05:47,400 --> 00:05:52,600
They have very powerful tools around their own vendor ecosystem of logs.

114
00:05:53,160 --> 00:05:57,520
But when you move beyond that, you get very low fidelity information

115
00:05:57,520 --> 00:05:58,720
coming it right.

116
00:05:58,720 --> 00:06:01,400
They're unable to contextualize all the fields

117
00:06:01,400 --> 00:06:02,920
the same way they could from their own logs,

118
00:06:02,920 --> 00:06:07,000
and they are unable to apply the same kind of rigorous analysis to it.

119
00:06:07,000 --> 00:06:09,840
Do you think it's because it's really hard to do the analysis?

120
00:06:09,840 --> 00:06:13,920
So say, say you have a firewall for brand A and for brand B and then the,

121
00:06:14,800 --> 00:06:16,920
the MDR servers or the data lake is from

122
00:06:16,920 --> 00:06:20,280
one of those two vendors, and they support the other vendor less indeed.

123
00:06:20,280 --> 00:06:21,760
But they could probably.

124
00:06:21,760 --> 00:06:25,680
Or is it is it that hard to think or is it is it a matter of trying

125
00:06:25,680 --> 00:06:28,440
to convince your customer to use all the products in your portfolio?

126
00:06:28,440 --> 00:06:33,000
A platform could also be making one vendor and everything, so say for that as well.

127
00:06:33,040 --> 00:06:35,640
I mean, it's easier to deal with one vendor.

128
00:06:35,640 --> 00:06:37,400
Yeah, the one throat to choke.

129
00:06:37,400 --> 00:06:39,000
I've heard that phrase.

130
00:06:39,000 --> 00:06:40,040
It's definitely true.

131
00:06:40,040 --> 00:06:42,080
The real problem comes right?

132
00:06:42,080 --> 00:06:45,040
That when we have this idea of how can we work with all these logs,

133
00:06:45,040 --> 00:06:47,040
a company is not heavily incentivized

134
00:06:47,040 --> 00:06:50,520
financially to provide detailed support for their competitors tools.

135
00:06:50,880 --> 00:06:51,080
Right.

136
00:06:51,080 --> 00:06:55,000
There's always that need that desire for your field to upsell, right.

137
00:06:55,040 --> 00:06:56,040
Land and expand.

138
00:06:56,040 --> 00:06:56,320
Okay.

139
00:06:56,320 --> 00:06:59,320
You're using our firewall, but somebody else's endpoint.

140
00:06:59,400 --> 00:07:00,640
Sure, we'll support that.

141
00:07:00,640 --> 00:07:04,480
But look what you'll get if you remove that other vendors endpoint

142
00:07:04,480 --> 00:07:05,520
and come to our endpoint.

143
00:07:05,520 --> 00:07:08,760
Look how cleanly we stitch these logs together.

144
00:07:08,880 --> 00:07:09,200
Right.

145
00:07:09,200 --> 00:07:12,560
If they could provide that clear visibility

146
00:07:12,600 --> 00:07:15,840
regardless of the vendor and have nowhere to expand.

147
00:07:15,880 --> 00:07:16,160
Right.

148
00:07:16,160 --> 00:07:17,800
And as from a business perspective,

149
00:07:17,800 --> 00:07:20,800
from a security outcomes perspective, that's great.

150
00:07:20,800 --> 00:07:21,920
Everybody should be doing that.

151
00:07:21,920 --> 00:07:23,760
That is the way we should do things.

152
00:07:23,760 --> 00:07:26,320
From a business unit perspective. No one's going to do that.

153
00:07:26,320 --> 00:07:29,920
The reality isn't that everything I mean, you have acquisitions, there's

154
00:07:30,000 --> 00:07:30,600
point processes.

155
00:07:30,600 --> 00:07:34,200
You sometimes need certain features or lagging behind in a certain feature.

156
00:07:34,200 --> 00:07:36,920
So you'll reality is that you do end up with different families.

157
00:07:36,920 --> 00:07:39,640
You have to no one has a full stack across everything.

158
00:07:39,640 --> 00:07:41,120
No one, even a really big audience.

159
00:07:41,120 --> 00:07:42,920
Hey, what about lock retention?

160
00:07:42,920 --> 00:07:46,840
I mean, one of the things that I hear a lot, at least, is that you want

161
00:07:46,880 --> 00:07:50,000
for forensic, for example, you want long term storage.

162
00:07:50,040 --> 00:07:52,240
Yeah, yeah, yeah, we need three months. We need seven months.

163
00:07:52,240 --> 00:07:53,240
We need a year. Right?

164
00:07:53,240 --> 00:07:55,240
We need seven years. Whatever it might be.

165
00:07:55,240 --> 00:07:58,440
I think what amuses me the most about this right

166
00:07:58,480 --> 00:08:01,480
is within our industry, in the concepts of storage.

167
00:08:01,480 --> 00:08:07,000
We have really great, mature ways of tracking hot storage,

168
00:08:07,000 --> 00:08:11,080
warm storage, cold storage that can become very cost effective, right?

169
00:08:12,360 --> 00:08:15,040
Cold storage S3 is trivial, right?

170
00:08:15,040 --> 00:08:18,800
The cost to store stuff that's not quick to read or write to.

171
00:08:19,640 --> 00:08:23,040
Then we get to your MDR or whatever it is.

172
00:08:23,160 --> 00:08:26,160
Now all these logs are going to a vendor data lake.

173
00:08:26,480 --> 00:08:29,280
They're all effectively hot storage because they want to be able

174
00:08:29,280 --> 00:08:31,440
to search them, perform tasks on them.

175
00:08:31,440 --> 00:08:35,560
So you're looking at the highest price for terabyte of storage.

176
00:08:36,040 --> 00:08:39,400
There's an extra add on because you're not just buying it straight from whatever

177
00:08:39,400 --> 00:08:40,200
storage vendor, right.

178
00:08:40,200 --> 00:08:43,200
You're buying it through your MDR product.

179
00:08:43,320 --> 00:08:43,480
Right?

180
00:08:43,480 --> 00:08:47,880
So now it is doubly expensive for terabyte, and you have no way of

181
00:08:47,880 --> 00:08:52,240
of pushing it off to warm cold storage, let alone data.

182
00:08:52,240 --> 00:08:52,920
Salvatore. Right.

183
00:08:52,920 --> 00:08:58,760
So we get to that afterwards is so expensive to consume data into

184
00:08:59,360 --> 00:09:03,040
because it's always more logs that you have than that you anticipate

185
00:09:03,160 --> 00:09:06,120
that your that your ROI tool recalculated.

186
00:09:06,120 --> 00:09:09,200
And how often do you have to do a look back for seven years or seven months

187
00:09:09,200 --> 00:09:12,440
or even three months, like, do you need to spend this if you just you

188
00:09:12,600 --> 00:09:16,240
if you if you discover that there's some kind of Chinese guy already

189
00:09:16,240 --> 00:09:18,040
in your network for three years, you might want to.

190
00:09:18,040 --> 00:09:19,880
Yeah, yeah, I want to see what I did exactly.

191
00:09:19,880 --> 00:09:21,280
But where do you want to spend that money?

192
00:09:21,280 --> 00:09:23,320
Do you, do you store everything with that in mind?

193
00:09:23,320 --> 00:09:27,000
And you end up spending so much money on storage, right.

194
00:09:27,000 --> 00:09:30,840
It's really one of the areas that balloons the cost of these solutions, right?

195
00:09:30,880 --> 00:09:32,440
When you start looking at the storage,

196
00:09:33,440 --> 00:09:34,560
despite having

197
00:09:34,560 --> 00:09:38,480
very inexpensive, high performance storage options available.

198
00:09:38,520 --> 00:09:38,880
Right.

199
00:09:38,880 --> 00:09:41,520
But they are outside of that vendor ecosystem.

200
00:09:41,520 --> 00:09:43,760
So you mentioned a couple of things in terminal expectations.

201
00:09:43,760 --> 00:09:45,880
It's a single pane of glass is important.

202
00:09:45,880 --> 00:09:50,480
One cross vendor that is an expectation or a requirement,

203
00:09:52,040 --> 00:09:55,400
a scope that's broad for not just networking or just endpoint,

204
00:09:55,400 --> 00:09:56,400
but actually everything.

205
00:09:56,400 --> 00:09:57,280
Because that's

206
00:09:57,280 --> 00:10:00,880
if you buy something you get you get a single pane of glass dashboard.

207
00:10:00,880 --> 00:10:03,200
You expect it to have truly organization.

208
00:10:03,200 --> 00:10:06,360
You don't have to go to another dashboard and have another subsection of it.

209
00:10:06,600 --> 00:10:07,560
Anything else there?

210
00:10:07,560 --> 00:10:08,800
I mean, yeah,

211
00:10:08,800 --> 00:10:11,000
there's the idea that it will provide some turnkey

212
00:10:11,000 --> 00:10:13,040
sort of compliance and remediation. Right.

213
00:10:13,040 --> 00:10:16,160
So I think a lot of times the idea of playbooks gets tied in

214
00:10:16,280 --> 00:10:17,280
to this.

215
00:10:17,280 --> 00:10:19,520
We detect it. And now we can trigger these playbooks.

216
00:10:19,520 --> 00:10:25,440
And certainly walking through the floor of the expo these last days,

217
00:10:26,920 --> 00:10:27,560
the stories that are

218
00:10:27,560 --> 00:10:31,280
told is always about, oh we do this out of the box, very turnkey.

219
00:10:31,320 --> 00:10:33,000
Everything works together.

220
00:10:33,000 --> 00:10:37,480
As you dig into that, you find that there are very few turnkey solutions out of it.

221
00:10:37,480 --> 00:10:39,760
And you ultimately it's important to be turnkey.

222
00:10:39,760 --> 00:10:42,760
I mean, if I don't know, station needs to be.

223
00:10:43,560 --> 00:10:45,360
Obviously it was very small organizations.

224
00:10:45,360 --> 00:10:48,360
Maybe they don't have the expertise to build out the playbooks.

225
00:10:48,840 --> 00:10:51,240
We should definitely see generative AI or other tools, right.

226
00:10:51,240 --> 00:10:53,640
Making things easier.

227
00:10:53,640 --> 00:10:55,440
But it's certainly what sold right.

228
00:10:55,440 --> 00:10:57,080
And if someone's buying their MDR,

229
00:10:57,080 --> 00:11:00,520
basically the thought that they will have automated tools to handle

230
00:11:00,520 --> 00:11:02,480
all of their situations and compliance needs,

231
00:11:02,480 --> 00:11:05,360
they're going to be sadly, sadly disappointed.

232
00:11:05,360 --> 00:11:06,120
Okay.

233
00:11:06,120 --> 00:11:08,400
Well, let's let's let's talk about a couple of requirements

234
00:11:08,400 --> 00:11:12,880
then that you should have some things that you questions that you need to ask

235
00:11:13,120 --> 00:11:14,680
when talking to an MD provider.

236
00:11:14,680 --> 00:11:19,920
I mean, because you say it may be costly to have long term storage, it may be

237
00:11:21,440 --> 00:11:22,560
narrowly scoped, etc..

238
00:11:22,560 --> 00:11:24,640
What do you think?

239
00:11:24,640 --> 00:11:26,520
What would be your top three of things

240
00:11:26,520 --> 00:11:29,800
that you need to be careful, given the space of the

241
00:11:30,400 --> 00:11:34,760
I mean the obvious ones like like you need to respond to a known

242
00:11:35,000 --> 00:11:39,480
a block list or high that everybody has that that is not a not something that

243
00:11:40,560 --> 00:11:41,520
narrows the field.

244
00:11:41,520 --> 00:11:43,000
A little bit. But yeah. Yeah.

245
00:11:43,000 --> 00:11:48,880
So I'd say first of all understand the difference in performance and features.

246
00:11:49,000 --> 00:11:53,640
When you look at a vendor ecosystem log or the external log to that.

247
00:11:53,680 --> 00:11:57,200
Right, you were going to have different performance on those two.

248
00:11:57,200 --> 00:11:59,920
They're going to have enrichments, different detail.

249
00:11:59,920 --> 00:12:01,800
How much different what is it.

250
00:12:01,800 --> 00:12:03,040
You should actually see it.

251
00:12:03,040 --> 00:12:03,240
Yeah.

252
00:12:03,240 --> 00:12:05,280
You just test it out and then and then on purpose

253
00:12:05,280 --> 00:12:09,400
and make put a product in a log, sort in and see what happens.

254
00:12:09,440 --> 00:12:11,040
Is it able to link it to other things.

255
00:12:11,040 --> 00:12:14,040
And it stitched that together with other logs that are meaningful.

256
00:12:14,040 --> 00:12:17,040
And then I think the second thing is do you have tiered storage.

257
00:12:17,120 --> 00:12:19,360
Do we have this hot warm cold?

258
00:12:19,360 --> 00:12:21,880
Unless you are fine with one month or yeah,

259
00:12:21,880 --> 00:12:23,800
you're fine for a very short window, right? Yeah.

260
00:12:23,800 --> 00:12:27,160
That would be okay. And then I think maybe

261
00:12:28,600 --> 00:12:31,480
the one thing we haven't really mentioned back to that

262
00:12:31,480 --> 00:12:34,560
M is there a human in the loop option?

263
00:12:35,280 --> 00:12:35,480
Yeah.

264
00:12:35,480 --> 00:12:37,600
To escalate things to who do I ask you to.

265
00:12:37,600 --> 00:12:40,000
Yeah, it's my responsibility. My SOCk.

266
00:12:40,000 --> 00:12:41,600
Do you have a SOCk that can help me?

267
00:12:41,600 --> 00:12:43,320
Is there somebody in the loop?

268
00:12:43,320 --> 00:12:46,560
And is that person experienced? Right?

269
00:12:46,600 --> 00:12:49,280
What kind of person am I reaching out to?

270
00:12:49,280 --> 00:12:51,760
Is there someone who's just going to put my question to an LLM

271
00:12:51,760 --> 00:12:54,840
and then read those answers back to me, because then I could do that, right?

272
00:12:55,040 --> 00:12:56,640
Is it someone who knows my environment?

273
00:12:56,640 --> 00:12:59,720
And these are things that are outside of the technical side of it.

274
00:12:59,760 --> 00:13:00,000
Right.

275
00:13:00,000 --> 00:13:03,240
And many vendors really don't go far beyond the technical right.

276
00:13:03,280 --> 00:13:04,920
They don't have any concept.

277
00:13:04,920 --> 00:13:07,640
It's more of an alert copy paste machine, more or less. Yeah.

278
00:13:07,640 --> 00:13:09,240
They're like, we don't know what you're doing with your SOCk.

279
00:13:09,240 --> 00:13:11,600
You have your own processed air. Go ahead and use it.

280
00:13:11,600 --> 00:13:15,080
But then that makes this not your single pane of glass, not your one place to go.

281
00:13:15,120 --> 00:13:15,480
Right.

282
00:13:15,480 --> 00:13:18,840
But just another dashboarding tool that you have to use.

283
00:13:18,880 --> 00:13:19,520
Okay.

284
00:13:20,720 --> 00:13:23,240
You mentioned a little bit data sovereignty.

285
00:13:23,240 --> 00:13:25,480
Yes. And I think this becomes more and more important.

286
00:13:25,480 --> 00:13:30,240
But that's a very European or Canadian thing I'd say it certainly not a U.S.

287
00:13:30,280 --> 00:13:31,720
thing. Right.

288
00:13:31,720 --> 00:13:35,480
Though initially it always has been right, which is why it's not as common

289
00:13:35,480 --> 00:13:36,280
a term here.

290
00:13:36,280 --> 00:13:39,800
So we were beginning to see states implementing requirements.

291
00:13:40,040 --> 00:13:42,560
Right. Federal government has certain requirements.

292
00:13:42,560 --> 00:13:46,400
Data sovereignty doesn't necessarily mean the US government can't see it.

293
00:13:46,640 --> 00:13:50,080
It means that if the US government is a customer, they control who sees it.

294
00:13:50,120 --> 00:13:50,360
Right.

295
00:13:50,360 --> 00:13:54,120
And this is going to become so important because so many of these tools now

296
00:13:54,320 --> 00:13:57,480
consume these logs into the vendors cloud,

297
00:13:58,440 --> 00:14:01,840
where they can apply all you don't know where the cloud is and they can,

298
00:14:01,880 --> 00:14:06,840
they can and country but which yeah, don't know where it's going to be.

299
00:14:06,840 --> 00:14:09,240
It's going to have your fiction is actually important.

300
00:14:09,240 --> 00:14:10,280
Jurisdiction is important.

301
00:14:10,280 --> 00:14:12,240
Who operationally controls it.

302
00:14:12,240 --> 00:14:14,920
Is that your vendor or your vendor. Vendor.

303
00:14:14,920 --> 00:14:17,080
Exactly, exactly. And we can see it.

304
00:14:17,080 --> 00:14:19,680
And that that can no longer be a question mark.

305
00:14:19,680 --> 00:14:20,200
Right?

306
00:14:20,200 --> 00:14:23,000
I think for a long time you could get by without that in the US market.

307
00:14:23,000 --> 00:14:25,320
Right. Because it wasn't a question people were taught to ask.

308
00:14:25,320 --> 00:14:29,440
But I've been seeing more and more of that question coming up in the US market.

309
00:14:29,480 --> 00:14:29,880
Right.

310
00:14:29,880 --> 00:14:32,600
People are recognizing that they need to own their data, right?

311
00:14:32,600 --> 00:14:37,000
They need sovereignty over their logs, which represent

312
00:14:37,240 --> 00:14:40,000
very proprietary data about the organization.

313
00:14:40,000 --> 00:14:42,560
Yeah. Especially if you indeed log everything.

314
00:14:42,560 --> 00:14:44,640
Yeah. Which we want to do. Right.

315
00:14:44,640 --> 00:14:48,520
Like the the value of it is in how much it consumes.

316
00:14:48,720 --> 00:14:49,600
Right. Yeah.

317
00:14:49,600 --> 00:14:52,480
I don't need it to be really good with a small subset of logs.

318
00:14:52,480 --> 00:14:55,080
That's uninteresting to me as a security practitioner.

319
00:14:55,080 --> 00:14:55,480
Right.

320
00:14:55,480 --> 00:14:56,760
If I'm going to have a place

321
00:14:56,760 --> 00:14:58,520
that's looking at my logs, it must look at all of them.

322
00:14:58,520 --> 00:15:02,680
So we should also talk a little bit about the future of MDR,

323
00:15:02,720 --> 00:15:06,480
how it is changing, because so far what you've been saying is a lot about

324
00:15:06,560 --> 00:15:10,560
collecting logs, responding to things that are broken.

325
00:15:10,680 --> 00:15:12,320
And although the M is

326
00:15:13,400 --> 00:15:14,080
assumes a little

327
00:15:14,080 --> 00:15:17,240
bit like we're going to do something about it, not really.

328
00:15:17,240 --> 00:15:22,520
What we see in for a pure MDR product is more is really like a like a thing.

329
00:15:22,600 --> 00:15:26,160
Yes, indeed, it will tell you how things are bad.

330
00:15:26,160 --> 00:15:27,440
And I was joking.

331
00:15:27,440 --> 00:15:31,080
It gives you the perfect report like, hey, this is this is why you should be fired.

332
00:15:31,080 --> 00:15:33,000
Because. Yeah. Oh, I thought I saw the whole thing.

333
00:15:33,000 --> 00:15:34,360
It was terrible.

334
00:15:34,360 --> 00:15:35,240
They got everything.

335
00:15:35,240 --> 00:15:36,320
I had a conversation.

336
00:15:36,320 --> 00:15:38,800
I may have

337
00:15:38,800 --> 00:15:41,440
shared this story before, but I remember talking to a CISO

338
00:15:41,440 --> 00:15:45,200
that said, hey, we got breached and all my.

339
00:15:45,640 --> 00:15:47,120
And we didn't know what hit us.

340
00:15:47,120 --> 00:15:49,480
I mean, it was out there, we had to pay ransom

341
00:15:49,480 --> 00:15:51,840
and we didn't know how they got in, what data they had.

342
00:15:51,840 --> 00:15:52,880
We knew nothing.

343
00:15:52,880 --> 00:15:57,320
So then we invested in an MDR product and now we actually saw everything.

344
00:15:57,320 --> 00:15:59,680
The next time it happened, we know who clicked on the link.

345
00:15:59,680 --> 00:16:02,560
We we know which data was accessed when it was happened,

346
00:16:02,560 --> 00:16:04,280
how much it was everything.

347
00:16:04,280 --> 00:16:07,280
And I asked him, but you still got breached, right?

348
00:16:07,320 --> 00:16:12,240
So but let's, let's, let's talk about that next time in a follow up episode.

349
00:16:12,240 --> 00:16:16,240
What we believe that the future of MDR, because it's a bright future

350
00:16:16,280 --> 00:16:19,280
might be it might be dark now, but the future, the future is bright.

351
00:16:19,320 --> 00:16:21,040
I'll hold you to that for next time.

352
00:16:21,040 --> 00:16:23,160
Thank you very much to our audience. Thank you very much.

353
00:16:23,160 --> 00:16:28,000
If you don't want to miss that next time episode about what the future of MDR.

354
00:16:28,000 --> 00:16:29,080
Press the subscribe button.

355
00:16:29,080 --> 00:16:31,040
And there's also a like button there.

356
00:16:31,040 --> 00:16:33,200
We would appreciate you press the button as well

357
00:16:33,200 --> 00:16:34,840
because it helps us spread the word.

358
00:16:34,840 --> 00:16:37,560
But for now, thank you very much and hope to see you next week.

359
00:16:37,560 --> 00:16:38,480
All right.

360
00:16:38,480 --> 00:16:43,720
Thank you for listening to Threat Talks, a podcast by ON2IT cybersecurity and AMS-IX.

361
00:16:43,720 --> 00:16:46,080
Did you like what you heard? Do you want to learn more?

362
00:16:46,080 --> 00:16:50,120
Follow Threat Talks to stay up to date on the topic of cybersecurity.