WEBVTT

1
00:00:03.520 --> 00:00:06.080
- Welcome to episode 434

2
00:00:06.080 --> 00:00:09.139
- of the Microsoft Cloud IT Pro podcast recorded

3
00:00:09.199 --> 00:00:11.699
- live on 08/10/2026.

4
00:00:11.839 --> 00:00:14.080
- This is a show about Microsoft three sixty

5
00:00:14.080 --> 00:00:16.164
- five and Azure from the perspective of IT

6
00:00:16.164 --> 00:00:18.324
- pros and end users, where we discuss a

7
00:00:18.324 --> 00:00:20.565
- topic or recent news and how it relates

8
00:00:20.565 --> 00:00:23.225
- to you. In this episode, Ben and Scott

9
00:00:23.285 --> 00:00:26.105
- provide their perspective on Project Perception,

10
00:00:26.484 --> 00:00:30.000
- Microsoft's latest AI security tool that provides you

11
00:00:30.000 --> 00:00:32.799
- with a workforce of AI agents. We discuss

12
00:00:32.799 --> 00:00:35.280
- what perception really is, what you need to

13
00:00:35.280 --> 00:00:37.600
- have to get started, and the agents and

14
00:00:37.600 --> 00:00:39.780
- tools that are contained within the product.

15
00:00:40.079 --> 00:00:41.859
- Join us as we unpack

16
00:00:42.239 --> 00:00:43.140
- Project Perception.

17
00:00:45.765 --> 00:00:47.445
- Scott, I was just I mentioned this to

18
00:00:47.445 --> 00:00:49.545
- you. I had a statement

19
00:00:49.925 --> 00:00:52.725
- that I made two weeks ago when we

20
00:00:52.725 --> 00:00:55.704
- recorded on the whole authentication and passkeys, and

21
00:00:55.880 --> 00:00:57.640
- we mentioned that you can go discuss with

22
00:00:57.640 --> 00:00:59.159
- us on Reddit. And somebody was like, hey,

23
00:00:59.159 --> 00:01:01.719
- Ben. You said something incorrect, and they called

24
00:01:01.719 --> 00:01:03.960
- me out on Reddit. So, yes, I made

25
00:01:03.960 --> 00:01:05.479
- a couple of comments. One, I said I

26
00:01:05.479 --> 00:01:07.500
- thought synced pass keys were tied to authenticator,

27
00:01:07.560 --> 00:01:09.159
- and I had it backwards in my head.

28
00:01:09.159 --> 00:01:11.444
- The device bound our authenticator. You can't do

29
00:01:11.444 --> 00:01:12.984
- synced pass keys in authenticator.

30
00:01:13.444 --> 00:01:13.944
- So,

31
00:01:14.405 --> 00:01:16.405
- yeah, I had it backwards in my head,

32
00:01:16.405 --> 00:01:16.905
- and

33
00:01:17.204 --> 00:01:19.605
- we were talking about one password. I also

34
00:01:19.605 --> 00:01:22.405
- discovered one password does work now for synced

35
00:01:22.405 --> 00:01:24.040
- pass keys. I just had a misconfiguration

36
00:01:24.340 --> 00:01:25.859
- of my tenant that was preventing me from

37
00:01:25.859 --> 00:01:27.939
- doing it. I think I have misconfiguration of

38
00:01:27.939 --> 00:01:30.180
- my tenant or my employees. I can you

39
00:01:30.180 --> 00:01:31.079
- make configuration

40
00:01:31.460 --> 00:01:33.620
- changes in your tenant? Not like that. They

41
00:01:33.620 --> 00:01:36.040
- don't let you go just add random

42
00:01:36.835 --> 00:01:37.335
- passkey

43
00:01:38.034 --> 00:01:40.275
- GUIDs to I don't even know. Is it

44
00:01:40.275 --> 00:01:42.194
- GUIDs? Is it GUIDs? Is it yeah. I

45
00:01:42.194 --> 00:01:44.835
- say GUID. You say GUID. I interchange them

46
00:01:44.835 --> 00:01:45.335
- sometimes.

47
00:01:45.954 --> 00:01:48.275
- You've got that whole Pan Panhandle thing going

48
00:01:48.275 --> 00:01:50.115
- on. Like, there there's a there there's a

49
00:01:50.115 --> 00:01:51.734
- little bit of an accent from the Panhandle.

50
00:01:51.795 --> 00:01:53.900
- Yeah. Usually, I say GUID, and then every

51
00:01:53.900 --> 00:01:55.420
- once in a while, I get that GUID

52
00:01:55.420 --> 00:01:57.819
- that sneaks in there. No. The AA GUID,

53
00:01:57.819 --> 00:01:59.500
- they don't let you just add those randomly

54
00:01:59.500 --> 00:02:01.100
- to your tenant? Probably not. Do you have

55
00:02:01.100 --> 00:02:01.600
- agents

56
00:02:01.980 --> 00:02:03.819
- scanning your tenant to look for those types

57
00:02:03.819 --> 00:02:05.980
- of things? I'm sure. I do. But, I

58
00:02:05.980 --> 00:02:07.034
- mean, what is an agent?

59
00:02:07.594 --> 00:02:09.055
- What is an agent?

60
00:02:09.355 --> 00:02:11.455
- What is a skill? What is AI?

61
00:02:13.915 --> 00:02:15.294
- Yes. You can pontificate.

62
00:02:16.395 --> 00:02:16.974
- Agent Smith? Agent

63
00:02:17.275 --> 00:02:19.294
- Smith? Oh, oh, no. We're gonna go Skynet.

64
00:02:19.355 --> 00:02:20.794
- Agent Smith. We're gonna go Skynet first. Oh,

65
00:02:20.794 --> 00:02:22.875
- Agent Smith. No. We can do Agent Smith.

66
00:02:22.875 --> 00:02:25.009
- Do you realize how old that movie is?

67
00:02:25.009 --> 00:02:27.569
- We talked about this before. Came out '99,

68
00:02:27.569 --> 00:02:29.750
- Scott. That that that We're going on twenty

69
00:02:29.810 --> 00:02:31.269
- seven years. Mhmm.

70
00:02:31.810 --> 00:02:33.269
- Yeah. Yeah. My my

71
00:02:33.569 --> 00:02:35.329
- we were watching a TV show the other

72
00:02:35.329 --> 00:02:36.310
- day, and

73
00:02:36.705 --> 00:02:38.645
- there was a line in there. It was

74
00:02:38.865 --> 00:02:41.425
- a it was a teenager talking to we're

75
00:02:41.425 --> 00:02:43.185
- watching a movie, but it was a teenager

76
00:02:43.185 --> 00:02:45.125
- talking to her parent.

77
00:02:45.585 --> 00:02:46.085
- And

78
00:02:46.544 --> 00:02:49.185
- her dad was born in 1980, like, from

79
00:02:49.185 --> 00:02:51.344
- the nineteen hundreds Like kinda kinda Yeah. And

80
00:02:51.344 --> 00:02:53.219
- and and she asked this quipped to her

81
00:02:53.219 --> 00:02:54.039
- dad that

82
00:02:54.580 --> 00:02:57.240
- you were born closer to 1940

83
00:02:57.620 --> 00:02:59.219
- than I was to 1980.

84
00:02:59.219 --> 00:03:00.659
- Meaning, like, when we were born, we were

85
00:03:00.659 --> 00:03:03.000
- closer to the forties than a kid today,

86
00:03:03.300 --> 00:03:05.000
- forty five, forty six years later,

87
00:03:05.335 --> 00:03:07.514
- would actually be to 1980.

88
00:03:07.655 --> 00:03:09.655
- That that was a really weird one for

89
00:03:09.655 --> 00:03:11.655
- me. It's like I'm I'm old in multiple

90
00:03:11.655 --> 00:03:12.155
- dimensions.

91
00:03:12.935 --> 00:03:14.375
- Yeah. I don't know that I wanna think

92
00:03:14.375 --> 00:03:16.135
- about that too hard. Yeah. I just wanna

93
00:03:16.135 --> 00:03:18.549
- pretend I'm still 20. Yeah. Well, I I

94
00:03:18.549 --> 00:03:19.669
- don't know that I know this could tear

95
00:03:19.669 --> 00:03:21.269
- all all my gray hair and everything, but

96
00:03:21.269 --> 00:03:23.110
- I got one more for you. Listen. You

97
00:03:23.110 --> 00:03:25.030
- hear that? The sound of silence? I don't

98
00:03:25.030 --> 00:03:27.430
- hear the sound of the kids. Are back

99
00:03:27.430 --> 00:03:28.090
- in school.

100
00:03:29.509 --> 00:03:31.030
- I get my house back. I get my

101
00:03:31.030 --> 00:03:33.335
- office back. How do you get how does

102
00:03:33.335 --> 00:03:35.435
- it feel to be back in silence?

103
00:03:35.814 --> 00:03:37.175
- It would be okay, except I got this

104
00:03:37.175 --> 00:03:39.435
- puppy behind me. So if he starts screeching,

105
00:03:39.574 --> 00:03:41.495
- you you you'll know why. Either he didn't

106
00:03:41.495 --> 00:03:43.175
- like the content or he really needed to

107
00:03:43.175 --> 00:03:45.414
- go outside. It is a cute new puppy.

108
00:03:45.414 --> 00:03:47.530
- Yeah. Alright. I will let you enjoy the

109
00:03:47.530 --> 00:03:49.610
- puppies. I'm not gonna enjoy the puppies. I

110
00:03:49.610 --> 00:03:51.689
- even had a good segue into agents. We

111
00:03:51.689 --> 00:03:54.090
- got distracted by puppies in square islands. Sorry.

112
00:03:54.090 --> 00:03:55.930
- I took you there. We'll get back. It's

113
00:03:55.930 --> 00:03:57.289
- okay. Human in the loop. Human in the

114
00:03:57.289 --> 00:04:00.104
- loop. We're back. Human striked. Okay. That was

115
00:04:00.104 --> 00:04:01.884
- quite the perception there, Scott, of

116
00:04:02.745 --> 00:04:03.245
- the

117
00:04:04.425 --> 00:04:07.305
- wow. Okay. So agents. Human in the loop,

118
00:04:07.305 --> 00:04:08.685
- a new product from Microsoft.

119
00:04:09.064 --> 00:04:10.985
- A new service? I don't know. At what

120
00:04:10.985 --> 00:04:13.164
- point in time, speaking of agents and skills,

121
00:04:13.224 --> 00:04:15.324
- what's a product now and what's a service?

122
00:04:15.550 --> 00:04:17.470
- I don't know anymore. Who knows? Up is

123
00:04:17.470 --> 00:04:19.949
- down. Up is down. Left is right. But,

124
00:04:19.949 --> 00:04:23.089
- yes. Prod Project Perception? Project Perception.

125
00:04:23.389 --> 00:04:26.189
- What are we perceiving? Project Perception. What are

126
00:04:26.189 --> 00:04:28.129
- we perceiving? We are perceiving

127
00:04:29.069 --> 00:04:30.370
- tenant security.

128
00:04:30.750 --> 00:04:31.250
- Like,

129
00:04:31.604 --> 00:04:34.004
- this is an interesting one. It is a

130
00:04:34.004 --> 00:04:35.305
- new security

131
00:04:36.004 --> 00:04:38.024
- product or service from Microsoft

132
00:04:38.485 --> 00:04:39.625
- and right from

133
00:04:40.324 --> 00:04:42.664
- the website for Project Perception, a workforce.

134
00:04:43.459 --> 00:04:45.620
- So now you aren't maybe this isn't even

135
00:04:45.620 --> 00:04:47.379
- a service or a product. It is a

136
00:04:47.379 --> 00:04:47.879
- workforce.

137
00:04:48.259 --> 00:04:49.639
- It's a workforce of specialized

138
00:04:50.339 --> 00:04:51.480
- AI agents,

139
00:04:51.860 --> 00:04:53.160
- red, blue, and green,

140
00:04:53.540 --> 00:04:56.520
- that reason across your security data tools, workflows

141
00:04:56.580 --> 00:04:59.805
- to expose gaps, investigate threats, remediate them, use

142
00:04:59.805 --> 00:05:02.285
- up the strategy, agents carry the load. So

143
00:05:02.285 --> 00:05:03.584
- this is an agentic

144
00:05:04.204 --> 00:05:04.704
- security

145
00:05:05.165 --> 00:05:06.384
- based service

146
00:05:06.925 --> 00:05:07.665
- from Microsoft

147
00:05:08.285 --> 00:05:09.584
- that you can

148
00:05:10.044 --> 00:05:12.204
- go in and enable at some point in

149
00:05:12.204 --> 00:05:15.759
- time. Right now, it's like a limited public

150
00:05:15.759 --> 00:05:16.259
- preview,

151
00:05:16.639 --> 00:05:17.139
- so

152
00:05:17.600 --> 00:05:20.639
- very selective in who can get access to

153
00:05:20.639 --> 00:05:23.839
- it. But all the documentation, the websites, everything

154
00:05:23.839 --> 00:05:26.384
- else is out there so that you can

155
00:05:26.384 --> 00:05:26.884
- now

156
00:05:27.264 --> 00:05:29.685
- enable agents to secure your environment.

157
00:05:30.064 --> 00:05:31.044
- Can you though?

158
00:05:31.345 --> 00:05:31.845
- Ish.

159
00:05:32.305 --> 00:05:33.685
- What is an agent, Scott?

160
00:05:34.384 --> 00:05:36.724
- I think that's one of the biggest things

161
00:05:36.944 --> 00:05:39.540
- that I I ran into this. But before

162
00:05:39.540 --> 00:05:41.620
- we get, like, too deep into that, maybe

163
00:05:41.620 --> 00:05:43.399
- we should talk a little bit about

164
00:05:44.660 --> 00:05:47.800
- what Project Perception, like, proposes to be and

165
00:05:48.019 --> 00:05:50.675
- what the agents it proposes to be

166
00:05:51.214 --> 00:05:53.855
- that are in this limited public preview that

167
00:05:53.855 --> 00:05:55.055
- are out there. And then we can maybe

168
00:05:55.055 --> 00:05:57.134
- come back a little bit to what is

169
00:05:57.134 --> 00:05:58.435
- an agent and

170
00:05:59.134 --> 00:06:00.595
- what does, like, supervision

171
00:06:00.895 --> 00:06:01.555
- look like

172
00:06:01.855 --> 00:06:05.639
- in particularly context of project perception and what

173
00:06:05.639 --> 00:06:07.959
- they've released in this first iteration here? Yeah.

174
00:06:07.959 --> 00:06:10.459
- And even some of the onboarding of this,

175
00:06:10.519 --> 00:06:12.540
- I had to pull together.

176
00:06:13.319 --> 00:06:15.339
- Again, limited public preview,

177
00:06:15.639 --> 00:06:17.959
- all over the documentation, things are liable to

178
00:06:17.959 --> 00:06:18.459
- change,

179
00:06:19.004 --> 00:06:21.104
- But I had to pull together a few

180
00:06:21.245 --> 00:06:22.544
- different things

181
00:06:23.004 --> 00:06:25.004
- to figure out, like, what do you even

182
00:06:25.004 --> 00:06:27.644
- need or what does this look like from

183
00:06:27.644 --> 00:06:29.584
- an onboarding perspective? Because

184
00:06:30.444 --> 00:06:32.400
- you have the home page, and then when

185
00:06:32.400 --> 00:06:34.800
- you go down in the documentation and start

186
00:06:34.800 --> 00:06:36.500
- looking at it, it has

187
00:06:37.520 --> 00:06:38.340
- certain requirements.

188
00:06:38.800 --> 00:06:41.860
- So if this is something you're interested in,

189
00:06:42.080 --> 00:06:45.360
- just getting started with it and looking through

190
00:06:45.360 --> 00:06:46.340
- some of the prerequisites

191
00:06:46.720 --> 00:06:48.875
- is this is something that's gonna live in

192
00:06:48.875 --> 00:06:51.115
- the Microsoft Defender portal, so you'll need to

193
00:06:51.115 --> 00:06:55.035
- have access to Defender, Microsoft Defender XDR Got

194
00:06:55.035 --> 00:06:57.355
- security center. Defender. Yes. I can keep coming

195
00:06:57.355 --> 00:07:00.300
- up with acronyms. Yeah. Security.microsoft.com.

196
00:07:00.459 --> 00:07:02.879
- You do need to have a unified

197
00:07:03.259 --> 00:07:04.479
- role based access

198
00:07:04.939 --> 00:07:07.659
- control, RBAC? RBAC. This is this was a

199
00:07:07.659 --> 00:07:09.419
- new acronym that was popping up all over

200
00:07:09.419 --> 00:07:11.199
- the documentation for this one.

201
00:07:11.579 --> 00:07:13.740
- Yes. That needs to be enabled across all

202
00:07:13.740 --> 00:07:15.680
- Defender workflow or workloads.

203
00:07:16.354 --> 00:07:18.435
- You have to be a security admin, security

204
00:07:18.435 --> 00:07:18.935
- reader.

205
00:07:19.314 --> 00:07:21.154
- And then even as you get into some

206
00:07:21.154 --> 00:07:23.894
- of the agents then, it talks about,

207
00:07:24.514 --> 00:07:26.435
- I believe, with some of these agents, like

208
00:07:26.435 --> 00:07:28.454
- different licensing, you need to have

209
00:07:28.834 --> 00:07:31.235
- Defender for Cloud enabled to look at your

210
00:07:31.235 --> 00:07:31.735
- Azure

211
00:07:32.599 --> 00:07:34.220
- stuff. You need to have

212
00:07:34.759 --> 00:07:35.740
- certain prerequisites

213
00:07:36.360 --> 00:07:38.919
- for various workloads, so Defender for Office three

214
00:07:38.919 --> 00:07:39.819
- sixty five

215
00:07:40.120 --> 00:07:43.159
- plan two. If you wanna look at email

216
00:07:43.159 --> 00:07:43.819
- and collaboration

217
00:07:44.324 --> 00:07:46.485
- stuff, you need to have Defender for Cloud,

218
00:07:46.485 --> 00:07:47.625
- Defender for Containers.

219
00:07:48.004 --> 00:07:49.604
- If you're wanting to look at your Azure

220
00:07:49.604 --> 00:07:50.104
- cloud,

221
00:07:50.485 --> 00:07:53.365
- Defender or Entra ID p two, Defender for

222
00:07:53.365 --> 00:07:55.604
- Identity, Defender for Cloud apps to look at

223
00:07:55.604 --> 00:07:56.584
- identity alerts.

224
00:07:56.960 --> 00:07:58.800
- So this is one part that for me,

225
00:07:58.800 --> 00:08:00.720
- it's like all through the documentation, it take

226
00:08:00.879 --> 00:08:03.360
- talks about the licensing and Urbach and all

227
00:08:03.360 --> 00:08:05.520
- of that. But then when you go back

228
00:08:05.520 --> 00:08:08.560
- to the actual product page and you scroll

229
00:08:08.560 --> 00:08:09.759
- all the way down and you look at

230
00:08:09.759 --> 00:08:12.375
- how is project perception priced, then it comes

231
00:08:12.375 --> 00:08:13.975
- up with you pay for only what you

232
00:08:13.975 --> 00:08:14.714
- use measured

233
00:08:15.495 --> 00:08:17.035
- in security computing units.

234
00:08:17.415 --> 00:08:18.954
- The mythical the magical

235
00:08:19.254 --> 00:08:22.235
- SCU. Yeah. So good old security Copilot

236
00:08:22.694 --> 00:08:23.194
- SCUs.

237
00:08:23.574 --> 00:08:26.339
- So if this is something you're interested in,

238
00:08:26.660 --> 00:08:28.180
- much like some of the other things we've

239
00:08:28.180 --> 00:08:30.180
- talked about, this is not I would not

240
00:08:30.180 --> 00:08:33.399
- call this a low cost barrier to entry.

241
00:08:33.539 --> 00:08:36.360
- You're probably looking at you already have

242
00:08:36.820 --> 00:08:39.080
- Microsoft three sixty five e five

243
00:08:39.460 --> 00:08:41.235
- or at least a lot of the security

244
00:08:41.235 --> 00:08:43.715
- products from e five, and you're going to

245
00:08:43.715 --> 00:08:46.455
- be willing to pay for security compute units

246
00:08:46.754 --> 00:08:48.355
- to be able to go in and run

247
00:08:48.355 --> 00:08:51.715
- these agents. So that is my here's where

248
00:08:51.715 --> 00:08:53.475
- you go, how you wanna think about if

249
00:08:53.475 --> 00:08:55.299
- this is something you're interested in just from

250
00:08:55.299 --> 00:08:56.840
- a pure pricing, licensing,

251
00:08:57.299 --> 00:08:59.620
- onboarding perspective in that respect. It's got a

252
00:08:59.620 --> 00:09:00.360
- lot of

253
00:09:00.740 --> 00:09:03.059
- moving pieces and parts, and I think you

254
00:09:03.059 --> 00:09:05.059
- can see probably where it's, like, limited public

255
00:09:05.059 --> 00:09:07.620
- preview because it's for those folks out there

256
00:09:07.620 --> 00:09:09.315
- who are a little bit more in, like,

257
00:09:09.475 --> 00:09:12.115
- token maxi land or I think just kinda

258
00:09:12.115 --> 00:09:14.034
- some of the bleeding edge, like, really interested

259
00:09:14.034 --> 00:09:14.615
- in the

260
00:09:14.995 --> 00:09:17.634
- frontier programs and other things, like, that are

261
00:09:17.634 --> 00:09:19.715
- available today. Yeah. So once you turn all

262
00:09:19.715 --> 00:09:21.875
- that on, once you have everything licensed and

263
00:09:21.875 --> 00:09:24.669
- enabled and permission set, then you can go

264
00:09:24.669 --> 00:09:27.070
- start looking at these agents. Well, I mean,

265
00:09:27.070 --> 00:09:28.589
- I just get an AI that does it

266
00:09:28.589 --> 00:09:30.190
- all for me. Right? Yeah. You just tell

267
00:09:30.190 --> 00:09:32.429
- it go do your thing. Go be my

268
00:09:32.429 --> 00:09:36.429
- security team, my security workforce. Go be my

269
00:09:36.429 --> 00:09:37.570
- security workforce

270
00:09:38.084 --> 00:09:38.584
- indeed.

271
00:09:39.524 --> 00:09:40.024
- Well,

272
00:09:40.485 --> 00:09:42.245
- so so, yeah, you you get all this

273
00:09:42.245 --> 00:09:43.605
- stuff lit up. There is a lot of

274
00:09:43.605 --> 00:09:44.105
- licensing.

275
00:09:44.564 --> 00:09:46.584
- There is a lot of configuration.

276
00:09:47.365 --> 00:09:49.524
- I didn't see, like, configured this for me

277
00:09:49.524 --> 00:09:51.845
- agent as part of onboarding, so you do

278
00:09:51.845 --> 00:09:54.870
- have to go and kinda wrangle that, well,

279
00:09:54.870 --> 00:09:57.350
- altogether. But once you do get that going,

280
00:09:57.350 --> 00:09:58.730
- you get these

281
00:09:59.429 --> 00:10:02.389
- categories of agents, like, I guess, broadly. Right?

282
00:10:02.389 --> 00:10:04.950
- They group them into Yep. Red team, blue

283
00:10:04.950 --> 00:10:06.009
- team, and

284
00:10:06.389 --> 00:10:08.695
- green team. So red team,

285
00:10:09.075 --> 00:10:09.575
- traditional

286
00:10:10.115 --> 00:10:12.355
- kind of penetration side of things, like, out

287
00:10:12.355 --> 00:10:13.175
- there to

288
00:10:13.634 --> 00:10:14.134
- identify

289
00:10:15.154 --> 00:10:15.975
- what's exploitable

290
00:10:16.355 --> 00:10:17.175
- and potentially

291
00:10:17.634 --> 00:10:19.975
- exploit it, blue team to

292
00:10:21.075 --> 00:10:22.535
- monitor for those threats.

293
00:10:22.970 --> 00:10:24.490
- When they see them come through. Like, can

294
00:10:24.490 --> 00:10:26.590
- they reconstruct them, get through the path,

295
00:10:27.129 --> 00:10:29.690
- close any gaps? Like, if there was something

296
00:10:29.690 --> 00:10:32.090
- exploitable, like, hey. Let me come and close

297
00:10:32.090 --> 00:10:34.889
- those up real quick. And then green team

298
00:10:34.889 --> 00:10:35.389
- to

299
00:10:35.850 --> 00:10:36.350
- remediate

300
00:10:36.970 --> 00:10:37.870
- and harden

301
00:10:38.375 --> 00:10:39.595
- configuration. So

302
00:10:39.975 --> 00:10:42.315
- while blue team might be doing, like, active

303
00:10:42.534 --> 00:10:45.735
- monitoring, triaging alerts, things like that, green team's

304
00:10:45.735 --> 00:10:47.034
- out there kinda

305
00:10:47.335 --> 00:10:47.835
- constantly

306
00:10:48.214 --> 00:10:49.434
- analyzing your posture,

307
00:10:50.054 --> 00:10:51.575
- making sure to give you, like, a set

308
00:10:51.575 --> 00:10:52.075
- of

309
00:10:52.409 --> 00:10:53.629
- prioritized recommendations,

310
00:10:54.250 --> 00:10:56.809
- the things like that that are gonna help

311
00:10:56.809 --> 00:11:00.009
- you ultimately, like, harden that posture. So I

312
00:11:00.009 --> 00:11:02.110
- think that's, like, all good on the surface.

313
00:11:02.250 --> 00:11:04.089
- And you go like, Well, that would be

314
00:11:04.089 --> 00:11:05.850
- kind of interesting. Right? Like, so I've got

315
00:11:05.850 --> 00:11:07.304
- this thing that can get out there, and

316
00:11:07.304 --> 00:11:09.384
- it can try and Yep. Poke holes in

317
00:11:09.384 --> 00:11:10.044
- my configuration

318
00:11:10.585 --> 00:11:13.225
- and see what can actually get through. I've

319
00:11:13.225 --> 00:11:15.784
- got another piece over here that can kinda

320
00:11:15.784 --> 00:11:17.804
- monitor things and potentially

321
00:11:18.585 --> 00:11:19.085
- operationalize

322
00:11:19.705 --> 00:11:21.485
- that monitoring or that observability

323
00:11:22.040 --> 00:11:24.040
- and go close those gaps real quick. And

324
00:11:24.040 --> 00:11:25.559
- then I've got something else on the back

325
00:11:25.559 --> 00:11:27.720
- end that's kinda sitting more in a constant

326
00:11:27.720 --> 00:11:31.160
- loop and basically doing continuous improvement and run,

327
00:11:31.160 --> 00:11:33.340
- run, run, kinda like CICD

328
00:11:33.720 --> 00:11:36.585
- for your tenant configuration is what it sounds

329
00:11:36.585 --> 00:11:38.024
- like. I think it's very easy to say,

330
00:11:38.024 --> 00:11:40.105
- like, oh, hey. That's what it all reads

331
00:11:40.105 --> 00:11:41.485
- as. But, ultimately,

332
00:11:42.184 --> 00:11:45.784
- back to that original question of what is

333
00:11:45.784 --> 00:11:46.524
- an agent,

334
00:11:46.985 --> 00:11:48.509
- that that very much, like,

335
00:11:48.990 --> 00:11:50.049
- bleeds back into

336
00:11:50.910 --> 00:11:52.850
- what project perception

337
00:11:53.549 --> 00:11:54.690
- is here because,

338
00:11:55.070 --> 00:11:56.509
- like, that that that was the thing that

339
00:11:56.509 --> 00:11:57.629
- struck me. So you go out, you read

340
00:11:57.629 --> 00:11:58.910
- about it, you read the blog post, things

341
00:11:58.910 --> 00:12:00.029
- like that, you go through the docs, and

342
00:12:00.029 --> 00:12:01.995
- you're like, cool. And then you get down

343
00:12:01.995 --> 00:12:02.975
- to it, and

344
00:12:03.995 --> 00:12:05.674
- the the things that I was saying of,

345
00:12:05.674 --> 00:12:07.914
- hey. Let's do the the whole red, blue,

346
00:12:07.914 --> 00:12:09.855
- green, and it's a little bit more automated.

347
00:12:09.914 --> 00:12:12.634
- Turns out it's really heavy on human in

348
00:12:12.634 --> 00:12:15.289
- the loop. Everything is actually manually triggered,

349
00:12:16.789 --> 00:12:19.589
- and and and effectively read only, like, with,

350
00:12:19.589 --> 00:12:22.230
- like, one or two caveats, but pretty much

351
00:12:22.230 --> 00:12:24.009
- across the board, read only.

352
00:12:24.389 --> 00:12:26.329
- And if that's the case

353
00:12:26.815 --> 00:12:29.215
- and you're kinda like, you're doing all the

354
00:12:29.215 --> 00:12:31.215
- supervision and you're doing all the monitoring and

355
00:12:31.215 --> 00:12:32.894
- it is very heavy on human loop, is

356
00:12:32.894 --> 00:12:34.735
- it truly agentic, or is it more like

357
00:12:34.735 --> 00:12:37.075
- a set of capabilities that you've been provided

358
00:12:37.215 --> 00:12:40.495
- maybe as, like, a security engineer within your

359
00:12:40.495 --> 00:12:40.995
- organization

360
00:12:41.429 --> 00:12:43.830
- to go and kinda help you have additive

361
00:12:43.830 --> 00:12:47.190
- tools to understand your environment configuration, things like

362
00:12:47.190 --> 00:12:48.629
- that. I can see where it goes in

363
00:12:48.629 --> 00:12:51.589
- the future, but it's it's hard to to

364
00:12:51.669 --> 00:12:53.210
- today to to kinda

365
00:12:53.524 --> 00:12:55.365
- be able to, like, really wrangle it together.

366
00:12:55.365 --> 00:12:57.044
- And then I wonder back to the whole

367
00:12:57.044 --> 00:12:58.965
- pricing aspect of it. Like, is it worth

368
00:12:58.965 --> 00:13:00.745
- it? Like, what are you getting here?

369
00:13:01.445 --> 00:13:02.804
- I kinda walked away at the end. And

370
00:13:02.804 --> 00:13:04.644
- I know this is a little flippant of

371
00:13:04.644 --> 00:13:05.845
- me, but, like, you walk away at the

372
00:13:05.845 --> 00:13:07.080
- end of, like, there's a bunch of, like,

373
00:13:07.160 --> 00:13:09.160
- scripts and things out there that help you

374
00:13:09.160 --> 00:13:12.040
- evaluate your environment already. Like, what's additive here

375
00:13:12.040 --> 00:13:13.720
- that you're getting out of it? I have

376
00:13:13.720 --> 00:13:16.279
- done some of this type of stuff even

377
00:13:16.279 --> 00:13:17.420
- using existing

378
00:13:17.960 --> 00:13:20.279
- AI. So I think seeing some of this

379
00:13:20.279 --> 00:13:22.674
- and having it built in was a little

380
00:13:22.674 --> 00:13:25.394
- intriguing to me. I think as I look

381
00:13:25.394 --> 00:13:26.134
- at this,

382
00:13:26.595 --> 00:13:28.615
- certain agents are probably

383
00:13:29.634 --> 00:13:31.875
- I probably get different value from different agents

384
00:13:31.875 --> 00:13:34.194
- in this. And maybe we dive into them

385
00:13:34.194 --> 00:13:36.360
- like the red team agent. Like you said,

386
00:13:36.360 --> 00:13:38.299
- that's gonna be identifying the weakness.

387
00:13:38.919 --> 00:13:40.299
- This one to me is

388
00:13:40.679 --> 00:13:42.460
- I think there's some value here,

389
00:13:42.919 --> 00:13:45.179
- but I think you also have some limitations

390
00:13:45.399 --> 00:13:47.879
- here. This one, when you go look through

391
00:13:47.879 --> 00:13:50.934
- it, Microsoft has the recon agent that's on

392
00:13:50.934 --> 00:13:53.575
- the red team. There's multiple agents. There there's

393
00:13:53.654 --> 00:13:56.215
- Right. There's multiple agents under these different teams.

394
00:13:56.215 --> 00:13:59.174
- Yeah. Under the teams categories. Yes. So yeah.

395
00:13:59.174 --> 00:14:01.254
- So so as we go through this, it's

396
00:14:01.254 --> 00:14:04.409
- like, yeah. Red team has recon agent, blue

397
00:14:04.409 --> 00:14:05.309
- team has

398
00:14:05.769 --> 00:14:06.509
- four agents,

399
00:14:07.049 --> 00:14:09.929
- and green team has one agent under it.

400
00:14:09.929 --> 00:14:12.589
- So you could also potentially see, like, additional

401
00:14:12.889 --> 00:14:15.070
- capabilities being introduced over time

402
00:14:15.450 --> 00:14:18.294
- and having that stuff come through. But yeah.

403
00:14:18.294 --> 00:14:20.554
- So so maybe we start with the recon

404
00:14:20.654 --> 00:14:21.914
- agent out there

405
00:14:22.375 --> 00:14:25.495
- scouting around. These are always interesting. Right? Recon

406
00:14:25.495 --> 00:14:29.115
- agent to me because it's simulating attack behavior,

407
00:14:29.575 --> 00:14:30.955
- trying to expose vulnerabilities

408
00:14:31.654 --> 00:14:32.154
- that

409
00:14:32.889 --> 00:14:35.929
- adversaries could exploit. It's looking at things like

410
00:14:35.929 --> 00:14:37.389
- mapping attack paths,

411
00:14:37.850 --> 00:14:40.089
- looking at choke points in your configuration. It

412
00:14:40.089 --> 00:14:41.149
- does have vulnerability

413
00:14:41.529 --> 00:14:44.570
- code scanning in there. I think maybe that

414
00:14:44.570 --> 00:14:46.889
- one jumps out at me a little bit,

415
00:14:46.889 --> 00:14:49.445
- exposes detection gaps, but it's all simulated.

416
00:14:49.985 --> 00:14:52.144
- Right? And this is the part where you

417
00:14:52.144 --> 00:14:55.045
- start thinking of you can only get so

418
00:14:55.184 --> 00:14:57.105
- far, I think, in a simulation. You can

419
00:14:57.105 --> 00:14:59.425
- only hit an API so many times before

420
00:14:59.425 --> 00:15:01.125
- you actually would have to make a configuration

421
00:15:01.425 --> 00:15:03.690
- change, like, to go through the next step.

422
00:15:04.570 --> 00:15:06.409
- So while I think it can find

423
00:15:06.889 --> 00:15:08.970
- it's almost like it could find surface level

424
00:15:08.970 --> 00:15:11.129
- stuff, but it has a limit to the

425
00:15:11.129 --> 00:15:13.210
- depth that it could go to. Because if

426
00:15:13.210 --> 00:15:14.990
- you have to expose one vulnerability,

427
00:15:15.610 --> 00:15:17.529
- how can it know that if it maybe

428
00:15:17.529 --> 00:15:19.254
- gets past the first layer, that it can

429
00:15:19.254 --> 00:15:19.995
- move laterally?

430
00:15:20.375 --> 00:15:23.595
- Or if it exploits the certain code vulnerability,

431
00:15:24.454 --> 00:15:26.214
- how does it know if it can keep

432
00:15:26.214 --> 00:15:29.095
- taking the next step? Like, this is maybe

433
00:15:29.095 --> 00:15:32.375
- that first line. Maybe some of the AI

434
00:15:32.375 --> 00:15:33.950
- stuff can kinda say, well, if I can

435
00:15:33.950 --> 00:15:35.389
- get past here, then I can go do

436
00:15:35.389 --> 00:15:37.409
- this, then this. It's

437
00:15:38.029 --> 00:15:39.709
- but I also think there's some value here.

438
00:15:39.709 --> 00:15:42.190
- Some of the other things I've done with

439
00:15:42.190 --> 00:15:44.029
- some of my other AI tools and looking

440
00:15:44.029 --> 00:15:46.125
- at this is taking some of the correlation

441
00:15:46.125 --> 00:15:48.845
- too between like what's known out there going

442
00:15:48.845 --> 00:15:50.365
- out looking at the web. What are known

443
00:15:50.365 --> 00:15:53.085
- CVEs out there? What are known exploits? What

444
00:15:53.085 --> 00:15:55.485
- are some of those things that are known

445
00:15:55.485 --> 00:15:56.384
- to be exploitable?

446
00:15:57.100 --> 00:15:59.259
- Do you see them in the configuration of

447
00:15:59.259 --> 00:16:01.440
- my tenant where an exploit from over here

448
00:16:01.580 --> 00:16:03.360
- could be used over here in my tenant?

449
00:16:04.139 --> 00:16:05.820
- The red team to me, a lot of

450
00:16:05.820 --> 00:16:06.480
- the investigatory

451
00:16:08.540 --> 00:16:09.040
- probing,

452
00:16:09.355 --> 00:16:11.835
- I think there's a level, but I also

453
00:16:11.835 --> 00:16:13.455
- think there's a lot of

454
00:16:13.835 --> 00:16:17.134
- correlations and maybe looking at things from different

455
00:16:17.355 --> 00:16:17.855
- angles

456
00:16:18.315 --> 00:16:20.235
- where you can get some value from AI

457
00:16:20.235 --> 00:16:21.595
- here. I think it's back to the whole

458
00:16:21.595 --> 00:16:23.274
- what's an agent thing. I think it's interesting

459
00:16:23.274 --> 00:16:25.600
- that they called it an agent because, like

460
00:16:25.600 --> 00:16:27.279
- like, there is I'm not arguing that there's

461
00:16:27.279 --> 00:16:28.959
- not value in it, but I think the

462
00:16:28.959 --> 00:16:30.100
- presentation's interesting.

463
00:16:30.720 --> 00:16:33.120
- So if you go and read the docs

464
00:16:33.120 --> 00:16:35.199
- and you start hopping in and you say,

465
00:16:35.199 --> 00:16:37.360
- okay. What's the recon agent and what's it

466
00:16:37.360 --> 00:16:39.939
- do? It's very clearly positioned

467
00:16:40.524 --> 00:16:41.024
- as

468
00:16:41.565 --> 00:16:43.024
- a single pane of glass

469
00:16:43.485 --> 00:16:43.985
- across

470
00:16:44.684 --> 00:16:47.644
- multiple Defender products. Right? So so this is

471
00:16:47.644 --> 00:16:49.964
- additive to Defender. So Defender is kinda the

472
00:16:49.964 --> 00:16:52.044
- base. It's out there. It's what protects you.

473
00:16:52.044 --> 00:16:54.089
- So so that's number one is it's a

474
00:16:54.089 --> 00:16:56.490
- little kinda like it is that little canned

475
00:16:56.490 --> 00:16:58.329
- reporting kinda thing, right, of saying, hey. Let's

476
00:16:58.329 --> 00:17:00.829
- go down the path, analyze your environment configuration.

477
00:17:01.129 --> 00:17:02.649
- I think where the AI thing comes in

478
00:17:02.649 --> 00:17:03.850
- and where it's a little bit less of

479
00:17:03.850 --> 00:17:05.529
- a canned report, but it's still very much

480
00:17:05.529 --> 00:17:06.974
- a report at the end of the day,

481
00:17:07.134 --> 00:17:09.134
- is the ability to go look at your

482
00:17:09.134 --> 00:17:10.434
- specific tenant configuration.

483
00:17:10.734 --> 00:17:12.355
- Let's say, the configuration

484
00:17:13.054 --> 00:17:13.554
- for

485
00:17:13.934 --> 00:17:16.035
- maybe one of your subscriptions in Azure.

486
00:17:16.414 --> 00:17:19.775
- It's able to hop through that subscription specifically

487
00:17:19.775 --> 00:17:21.154
- and kinda do

488
00:17:21.855 --> 00:17:22.355
- more

489
00:17:23.019 --> 00:17:23.759
- more pivots

490
00:17:24.140 --> 00:17:25.519
- and kinda what if analysis

491
00:17:25.980 --> 00:17:26.880
- than a traditional,

492
00:17:27.180 --> 00:17:29.900
- alright, go check this binary, if this, then

493
00:17:29.900 --> 00:17:30.400
- that,

494
00:17:30.779 --> 00:17:32.539
- kind of thing. I think that's where AI

495
00:17:32.539 --> 00:17:33.819
- helps out these things. It makes it a

496
00:17:33.819 --> 00:17:35.259
- little bit more of a choose your own

497
00:17:35.259 --> 00:17:35.759
- adventure.

498
00:17:36.115 --> 00:17:37.575
- But, ultimately, getting to

499
00:17:37.875 --> 00:17:39.174
- that single

500
00:17:39.474 --> 00:17:40.774
- pane of glass

501
00:17:41.315 --> 00:17:43.154
- that that's out there, I think even that

502
00:17:43.154 --> 00:17:44.615
- single pane of glass is

503
00:17:45.234 --> 00:17:47.414
- interesting the way it's kinda presented

504
00:17:47.794 --> 00:17:49.394
- back to you. So, like, when you go

505
00:17:49.394 --> 00:17:50.375
- and run these things,

506
00:17:51.000 --> 00:17:53.400
- you you don't get a traditional dashboard. Like,

507
00:17:53.400 --> 00:17:54.519
- it's not like you get, like, a Power

508
00:17:54.519 --> 00:17:56.680
- BI report or anything like that. You get

509
00:17:56.680 --> 00:17:59.500
- a bunch of markdown files in a kinda

510
00:17:59.720 --> 00:18:01.400
- known format. But if you were to run

511
00:18:01.400 --> 00:18:03.080
- it against my tenant and then run it

512
00:18:03.080 --> 00:18:05.720
- against your tenant, we should get different sets

513
00:18:05.720 --> 00:18:07.184
- of we get the same set of output

514
00:18:07.184 --> 00:18:09.744
- mark markdown files, but with different guidance in

515
00:18:09.744 --> 00:18:11.664
- each one. The markdown files to me makes

516
00:18:11.664 --> 00:18:12.884
- sense because

517
00:18:13.505 --> 00:18:15.424
- one of the other things, like, if we

518
00:18:15.424 --> 00:18:17.345
- wanna go take this the next step, is

519
00:18:17.345 --> 00:18:18.484
- you get all this markdown.

520
00:18:19.105 --> 00:18:21.799
- It does talk about, and this is maybe

521
00:18:21.799 --> 00:18:23.640
- where some of that value comes in with

522
00:18:23.640 --> 00:18:24.140
- project

523
00:18:24.519 --> 00:18:27.000
- perception, is it can take the output of

524
00:18:27.000 --> 00:18:28.920
- one agent and feed it to the next

525
00:18:28.920 --> 00:18:31.000
- agent. Which you kinda need. Right? Like, if

526
00:18:31.000 --> 00:18:33.044
- you're gonna go and say, hey. I found

527
00:18:33.044 --> 00:18:35.605
- something wrong in your configuration. You kinda wanna

528
00:18:35.605 --> 00:18:37.044
- pass that off to the next thing to

529
00:18:37.044 --> 00:18:39.845
- have it evaluate. Say, like, okay. Is this

530
00:18:39.845 --> 00:18:41.365
- important? Where does it land? And that's where

531
00:18:41.365 --> 00:18:43.605
- kinda, like, the blue and green come in.

532
00:18:43.605 --> 00:18:45.869
- We'll just say, hey. Let's go what's prioritization

533
00:18:46.329 --> 00:18:48.250
- look like here? Like, that's the responsibility of

534
00:18:48.250 --> 00:18:50.429
- the green team agent. It's not the responsibility

535
00:18:50.649 --> 00:18:52.649
- of any of the blue team agents that

536
00:18:52.649 --> 00:18:54.089
- are out there that are kinda doing active

537
00:18:54.089 --> 00:18:55.690
- triage or things like that. Yeah. And that's

538
00:18:55.690 --> 00:18:57.609
- where that red team it's like, we've gone

539
00:18:57.609 --> 00:18:59.609
- in. We've done the recon. We figured out

540
00:18:59.609 --> 00:19:01.335
- all these things. Now let's pass it over

541
00:19:01.335 --> 00:19:02.634
- to that blue team agent.

542
00:19:03.414 --> 00:19:05.515
- And this one, there's the most in here

543
00:19:05.734 --> 00:19:06.954
- where you have

544
00:19:07.335 --> 00:19:08.855
- four agents in the blue team. You have

545
00:19:08.855 --> 00:19:11.035
- the triage agent, you have the attack

546
00:19:11.494 --> 00:19:11.994
- investigation

547
00:19:12.454 --> 00:19:12.954
- agent,

548
00:19:13.255 --> 00:19:15.029
- the threat intelligence agent,

549
00:19:15.670 --> 00:19:16.490
- and the detection

550
00:19:16.789 --> 00:19:19.029
- authoring agent. And I think this is one

551
00:19:19.029 --> 00:19:20.630
- where that red team agent can then take

552
00:19:20.630 --> 00:19:22.710
- those marks down to the blue team and

553
00:19:22.710 --> 00:19:24.789
- pass it over to the triage agent, where

554
00:19:24.789 --> 00:19:26.250
- this agent can now

555
00:19:26.710 --> 00:19:27.210
- go

556
00:19:27.904 --> 00:19:29.204
- take all of that

557
00:19:29.585 --> 00:19:30.085
- information.

558
00:19:31.505 --> 00:19:32.325
- This is where

559
00:19:33.024 --> 00:19:35.524
- I have mixed feelings on this because

560
00:19:35.825 --> 00:19:38.065
- the triage agent it would be interesting to

561
00:19:38.065 --> 00:19:39.664
- see how it passes. The triage agent has

562
00:19:39.664 --> 00:19:42.839
- defined classifies and triages as alerts in Defender

563
00:19:42.980 --> 00:19:45.559
- for different workloads, for different alert types.

564
00:19:45.940 --> 00:19:48.039
- It does have some things like autonomous

565
00:19:48.339 --> 00:19:50.839
- triage. It has some learning based on feedback,

566
00:19:51.139 --> 00:19:52.119
- record classification.

567
00:19:52.659 --> 00:19:53.879
- But if your

568
00:19:54.500 --> 00:19:55.639
- red team agent

569
00:19:56.184 --> 00:19:57.164
- is read only,

570
00:19:57.625 --> 00:20:01.464
- it shouldn't, in theory, actually trigger any alerts

571
00:20:01.464 --> 00:20:04.765
- in Defender because it's not taking any actions,

572
00:20:04.984 --> 00:20:07.464
- I don't think. Maybe it would. Maybe it

573
00:20:07.464 --> 00:20:08.205
- would try

574
00:20:09.119 --> 00:20:10.799
- like, what is a read only agent, I

575
00:20:10.799 --> 00:20:12.720
- guess, Scott? Is it actually gonna try to

576
00:20:12.720 --> 00:20:15.440
- log in? Is it gonna try, like, brute

577
00:20:15.440 --> 00:20:18.000
- forcing a password a little bit? In my

578
00:20:18.000 --> 00:20:20.799
- mind, that's not really read only. It's doing

579
00:20:20.799 --> 00:20:22.099
- a little bit more writing.

580
00:20:22.474 --> 00:20:25.115
- And to really get things to trigger in

581
00:20:25.115 --> 00:20:25.615
- Defender,

582
00:20:25.994 --> 00:20:27.434
- you have to do that type of stuff.

583
00:20:27.434 --> 00:20:29.515
- It would be nice to see this evolve

584
00:20:29.515 --> 00:20:30.734
- a little bit where

585
00:20:31.195 --> 00:20:34.234
- maybe the red the recon agent is allowed

586
00:20:34.234 --> 00:20:36.059
- to poke at your tenant a little bit

587
00:20:36.059 --> 00:20:38.619
- more. Microsoft's running it all, it would be

588
00:20:38.619 --> 00:20:41.680
- able to recognize it and flag it accordingly

589
00:20:42.380 --> 00:20:45.119
- so that blue team agent could actually

590
00:20:45.660 --> 00:20:47.339
- like, you could see a little bit more

591
00:20:47.339 --> 00:20:50.505
- of a simulated attack versus just a, let's

592
00:20:50.505 --> 00:20:52.345
- go read all the configuration. It's what I

593
00:20:52.345 --> 00:20:53.865
- was kind of planning for. It was like,

594
00:20:53.865 --> 00:20:55.464
- hey. When do these things get out? What

595
00:20:55.464 --> 00:20:57.884
- if we get a little more proactive? But

596
00:20:58.025 --> 00:21:00.204
- e even touching things can be a little

597
00:21:00.345 --> 00:21:02.585
- touchy sometimes when they were not there. So

598
00:21:02.585 --> 00:21:04.904
- if you look at these agents and so

599
00:21:04.904 --> 00:21:07.210
- so per agent, there's a configuration,

600
00:21:08.070 --> 00:21:10.230
- and that configuration comes with a set of

601
00:21:10.230 --> 00:21:10.730
- permissions

602
00:21:11.029 --> 00:21:12.630
- that are gonna be layered into the graph

603
00:21:12.630 --> 00:21:15.029
- and your tenant and other things that are

604
00:21:15.029 --> 00:21:16.009
- out there. So

605
00:21:16.309 --> 00:21:18.330
- if you look at, like, the recon agent,

606
00:21:18.595 --> 00:21:19.315
- it's a

607
00:21:19.795 --> 00:21:22.134
- it's it gets some pretty privileged

608
00:21:22.515 --> 00:21:24.755
- role assignments. Like, it does get user read

609
00:21:24.755 --> 00:21:27.495
- all. It gets group member read all, application

610
00:21:27.715 --> 00:21:30.355
- read all, delegated permissions read all, audit log

611
00:21:30.355 --> 00:21:31.015
- read all,

612
00:21:31.529 --> 00:21:32.890
- things that are out there. It also gets

613
00:21:32.890 --> 00:21:35.309
- a bunch of Azure RBAC assignments.

614
00:21:35.769 --> 00:21:37.850
- So you have to kinda go through, add

615
00:21:37.850 --> 00:21:39.789
- a subscription scope, and

616
00:21:40.090 --> 00:21:42.490
- assign these things down or assign it at

617
00:21:42.490 --> 00:21:44.250
- a higher level, like a management group, something

618
00:21:44.250 --> 00:21:46.204
- like that. Let it bleed through. But it

619
00:21:46.204 --> 00:21:46.865
- gets reader,

620
00:21:47.164 --> 00:21:50.365
- specifically Key Vault reader and Log Analytics reader,

621
00:21:50.365 --> 00:21:51.184
- as well as

622
00:21:51.565 --> 00:21:53.724
- security reader that are out there. So I

623
00:21:53.724 --> 00:21:56.045
- think even going through and just kinda poking

624
00:21:56.045 --> 00:21:58.204
- at things, maybe it'll set some things off

625
00:21:58.204 --> 00:22:01.059
- depending on how your environment's configured and what

626
00:22:01.059 --> 00:22:02.980
- it is. But Right. I really look at

627
00:22:03.140 --> 00:22:05.240
- like, today, like, the red team

628
00:22:05.940 --> 00:22:08.919
- agent would be out there analyzing your environment.

629
00:22:09.299 --> 00:22:11.079
- It's gonna, like, tell you

630
00:22:11.539 --> 00:22:13.855
- what the broad scope of maybe think about,

631
00:22:13.855 --> 00:22:15.214
- like, a funnel. Like, you're always gonna be

632
00:22:15.214 --> 00:22:18.015
- funneling it down. So broad set of things

633
00:22:18.015 --> 00:22:19.855
- that are out here. The blue team is

634
00:22:19.855 --> 00:22:21.535
- gonna be sitting out there and saying, like,

635
00:22:21.535 --> 00:22:23.695
- okay. What are my tasks I need to

636
00:22:23.695 --> 00:22:26.015
- go? What do I need to triage that's

637
00:22:26.015 --> 00:22:28.350
- out there? If I and this is where

638
00:22:28.350 --> 00:22:30.190
- maybe, like, even, like, the red agent goes

639
00:22:30.190 --> 00:22:31.630
- away a little bit is, like, you have

640
00:22:31.630 --> 00:22:34.029
- things like an attack investigation agent. So that

641
00:22:34.029 --> 00:22:35.789
- could be super helpful, right, because you've got

642
00:22:35.789 --> 00:22:37.309
- an active tenant. And you're out there. You

643
00:22:37.309 --> 00:22:38.509
- don't need the red team to come in

644
00:22:38.590 --> 00:22:39.950
- Yep. And look at things like that, tell

645
00:22:39.950 --> 00:22:41.315
- you about misconfigured

646
00:22:42.015 --> 00:22:42.515
- users,

647
00:22:43.054 --> 00:22:44.194
- anonymous logins,

648
00:22:44.734 --> 00:22:46.194
- all all those kinds of things.

649
00:22:46.494 --> 00:22:48.174
- So, yeah, you get that funnel, pass it

650
00:22:48.174 --> 00:22:49.615
- to blue team, and then, you get a

651
00:22:49.615 --> 00:22:51.375
- little bit more of the the the green

652
00:22:51.375 --> 00:22:53.294
- team expertise to say, like, hey. Here's what

653
00:22:53.294 --> 00:22:54.274
- we're gonna prioritize

654
00:22:55.240 --> 00:22:56.779
- to go and fix

655
00:22:57.079 --> 00:22:59.000
- that's out there, which is interesting. Like, the

656
00:22:59.000 --> 00:23:01.319
- green team is really focused on prioritization. Like,

657
00:23:01.319 --> 00:23:04.299
- there's one agent today. It's the posture prioritization

658
00:23:04.759 --> 00:23:05.259
- agent.

659
00:23:05.880 --> 00:23:06.380
- Like,

660
00:23:06.759 --> 00:23:09.404
- like, the says it on the tin where

661
00:23:09.404 --> 00:23:11.644
- it's gonna go and what it's gonna do

662
00:23:11.644 --> 00:23:12.225
- for you.

663
00:23:13.565 --> 00:23:16.045
- If you are managing file storage today, you've

664
00:23:16.045 --> 00:23:19.164
- probably felt the pressure. Refresh cycles are harder

665
00:23:19.164 --> 00:23:22.305
- to plan, costs and complexity are increasing, especially

666
00:23:22.525 --> 00:23:24.865
- as file workloads scale across regions.

667
00:23:25.200 --> 00:23:28.480
- That's why Microsoft customers trust Nasuni as an

668
00:23:28.480 --> 00:23:30.099
- Azure certified software.

669
00:23:30.480 --> 00:23:33.519
- Nasuni provides a global file system designed for

670
00:23:33.519 --> 00:23:34.819
- enterprise scale environments,

671
00:23:35.200 --> 00:23:38.640
- keeping file data secure, governed, and accessible across

672
00:23:38.640 --> 00:23:41.714
- Azure environments without added infrastructure complexity.

673
00:23:42.174 --> 00:23:45.294
- It's the foundation to keep your unstructured data

674
00:23:45.294 --> 00:23:48.575
- stable even as your infrastructure evolves. To see

675
00:23:48.575 --> 00:23:50.575
- how much you could save while keeping your

676
00:23:50.575 --> 00:23:56.069
- initiatives on track, visit nasuni.com/tco.

677
00:23:56.230 --> 00:24:00.889
- That's nasuni.com/tco.

678
00:24:01.990 --> 00:24:04.950
- I like the attack investigation agent. That if

679
00:24:04.950 --> 00:24:07.190
- I was gonna just from the title without

680
00:24:07.190 --> 00:24:09.335
- having played with these, look at these, I

681
00:24:09.335 --> 00:24:11.174
- can see a lot of value with the

682
00:24:11.174 --> 00:24:11.994
- attack investigation

683
00:24:12.295 --> 00:24:12.795
- agent.

684
00:24:13.494 --> 00:24:15.095
- I would like it to see it get

685
00:24:15.095 --> 00:24:17.174
- to a better price point. You need a

686
00:24:17.174 --> 00:24:18.695
- lot for this one. Right? Can you come

687
00:24:18.695 --> 00:24:20.214
- back to what do you need to turn

688
00:24:20.214 --> 00:24:22.369
- on to get all this stuff going? This

689
00:24:22.369 --> 00:24:23.590
- one's like XDR,

690
00:24:24.289 --> 00:24:25.110
- EU fives

691
00:24:25.890 --> 00:24:29.029
- for all the categories of attacks, identity attacks,

692
00:24:29.250 --> 00:24:29.750
- and

693
00:24:30.210 --> 00:24:32.950
- kind of cloud and compute side of things.

694
00:24:33.170 --> 00:24:35.170
- Kinda looking at a lot. Right? The cloud

695
00:24:35.170 --> 00:24:37.414
- side, you got Defender for cloud, Defender for

696
00:24:37.414 --> 00:24:37.914
- containers.

697
00:24:38.295 --> 00:24:40.555
- You got the identity side with Entra

698
00:24:41.015 --> 00:24:43.174
- where you need Defender for cloud apps, Defender

699
00:24:43.174 --> 00:24:46.315
- for identity, ID p twos. This one actually

700
00:24:46.455 --> 00:24:48.615
- calls out you need the e five license,

701
00:24:48.615 --> 00:24:50.369
- the M365E5.

702
00:24:50.450 --> 00:24:51.890
- But I have a lot of clients, and

703
00:24:51.890 --> 00:24:53.809
- I say the value of this one, I

704
00:24:53.809 --> 00:24:55.730
- have not a lot. I have a few

705
00:24:55.730 --> 00:24:56.230
- clients.

706
00:24:56.609 --> 00:24:59.329
- They're relatively small. Right? They don't have, like,

707
00:24:59.329 --> 00:25:00.150
- a dedicated

708
00:25:00.849 --> 00:25:03.589
- security team. They don't have a dedicated SOC,

709
00:25:03.734 --> 00:25:04.234
- but

710
00:25:04.615 --> 00:25:06.934
- they're big enough that they are maybe running

711
00:25:06.934 --> 00:25:10.154
- e fives, they're running Defender for endpoint,

712
00:25:11.255 --> 00:25:12.474
- they're Intune enrolled,

713
00:25:12.934 --> 00:25:15.914
- and something gets triggered. Some type of

714
00:25:16.375 --> 00:25:18.855
- not necessarily it's a known attack, but something

715
00:25:18.855 --> 00:25:21.210
- in Defender is triggered as a potential attack.

716
00:25:21.429 --> 00:25:23.829
- Defender is great. It is not the most

717
00:25:23.829 --> 00:25:25.049
- intuitive interface

718
00:25:25.750 --> 00:25:27.690
- for a IT generalist

719
00:25:28.230 --> 00:25:30.309
- to dig through, to figure out if they

720
00:25:30.309 --> 00:25:32.329
- need to be worried about a particular

721
00:25:32.710 --> 00:25:34.894
- alert or incident or something that is raised

722
00:25:34.894 --> 00:25:37.214
- in Defender. If Microsoft could figure out a

723
00:25:37.214 --> 00:25:38.355
- way to really

724
00:25:38.894 --> 00:25:40.575
- lower the cost of this, so some of

725
00:25:40.575 --> 00:25:41.634
- these SMB

726
00:25:42.654 --> 00:25:43.394
- type of

727
00:25:43.775 --> 00:25:44.275
- companies

728
00:25:44.654 --> 00:25:46.970
- could leverage this to help them with an

729
00:25:46.970 --> 00:25:49.609
- investigation of certain alerts and incidents raised in

730
00:25:49.609 --> 00:25:51.529
- their tenant. I think there's a lot of

731
00:25:51.529 --> 00:25:53.149
- value there in helping

732
00:25:53.769 --> 00:25:56.269
- what I I will say more IT generalists

733
00:25:56.809 --> 00:25:57.309
- understand

734
00:25:58.250 --> 00:26:00.250
- what they should be worried about or concerned

735
00:26:00.250 --> 00:26:02.855
- about when different alerts are raised in Defender.

736
00:26:02.914 --> 00:26:05.795
- And I think that's where this one fits

737
00:26:05.795 --> 00:26:08.115
- in the blue team is when you actually

738
00:26:08.115 --> 00:26:10.914
- have an attack, not taking inputs from the

739
00:26:10.914 --> 00:26:13.335
- red team, but actually looking at attacks

740
00:26:13.660 --> 00:26:14.799
- and trying to

741
00:26:15.420 --> 00:26:16.559
- help people identify

742
00:26:17.660 --> 00:26:20.140
- what actually is going on there, helping them

743
00:26:20.140 --> 00:26:23.839
- understand the attack path, the replaying the attack,

744
00:26:24.380 --> 00:26:25.599
- giving them a summary,

745
00:26:26.295 --> 00:26:29.195
- looking through what was the result of the

746
00:26:29.414 --> 00:26:29.914
- incident,

747
00:26:30.535 --> 00:26:33.835
- what were the different MITRE attack techniques that

748
00:26:34.055 --> 00:26:36.634
- we're seeing, like, what are all the different

749
00:26:36.775 --> 00:26:38.394
- components of the attack

750
00:26:39.009 --> 00:26:41.089
- to help someone understand that, like I think

751
00:26:41.089 --> 00:26:44.470
- that one's there. There's the threat intelligence agent.

752
00:26:44.690 --> 00:26:45.190
- Threat

753
00:26:45.490 --> 00:26:45.990
- intelligence

754
00:26:46.769 --> 00:26:48.470
- agent. I struggle with this one.

755
00:26:49.170 --> 00:26:51.170
- Yeah. Why why is that? How is this

756
00:26:51.170 --> 00:26:53.250
- different than a secure score? That would be

757
00:26:53.250 --> 00:26:54.934
- it in a summary. Threat

758
00:26:55.234 --> 00:26:56.454
- Intelligence is

759
00:26:56.755 --> 00:26:57.894
- looking at reports

760
00:26:58.274 --> 00:26:59.595
- or no. Maybe it wasn't this one. Maybe

761
00:26:59.595 --> 00:27:01.234
- it was the green one. No. It's more

762
00:27:01.234 --> 00:27:02.434
- the green one. Threat intel

763
00:27:03.474 --> 00:27:06.134
- I but I think this is still somewhat

764
00:27:06.194 --> 00:27:06.855
- of a

765
00:27:07.259 --> 00:27:10.220
- secure score A little bit. Ish. Very very

766
00:27:10.220 --> 00:27:11.200
- much so. So

767
00:27:11.660 --> 00:27:12.640
- it's taking

768
00:27:13.339 --> 00:27:14.640
- kinda public signals

769
00:27:15.019 --> 00:27:18.080
- and public reports and then identifying them out

770
00:27:18.140 --> 00:27:19.519
- against in environments

771
00:27:20.204 --> 00:27:22.525
- that are out there. So or I guess

772
00:27:22.525 --> 00:27:24.204
- your environment. This is where it comes down

773
00:27:24.204 --> 00:27:24.704
- to,

774
00:27:25.005 --> 00:27:26.365
- like, is it a report at the end

775
00:27:26.365 --> 00:27:28.284
- of the day? Like, yes. It's a report.

776
00:27:28.284 --> 00:27:29.265
- You get some markdown,

777
00:27:30.204 --> 00:27:32.220
- comes out of it, things like that. What

778
00:27:32.220 --> 00:27:34.619
- do I go and do with that? Then

779
00:27:34.619 --> 00:27:36.940
- it's up to you to to figure it

780
00:27:36.940 --> 00:27:39.200
- out. It's interesting what the different reports

781
00:27:39.500 --> 00:27:40.559
- give back.

782
00:27:41.259 --> 00:27:43.519
- So, like, if you look at, like, the

783
00:27:43.819 --> 00:27:44.319
- attack

784
00:27:44.825 --> 00:27:47.704
- investigation agent, for example, like, one of the

785
00:27:47.704 --> 00:27:50.984
- primary things that it's intended to do is

786
00:27:50.984 --> 00:27:51.724
- give you

787
00:27:52.025 --> 00:27:53.865
- a little bit of guidance. So it has

788
00:27:53.865 --> 00:27:55.704
- a a classification in the report, like an

789
00:27:55.704 --> 00:27:57.789
- incident verdict. So I'm gonna give you a

790
00:27:57.789 --> 00:28:00.690
- classification that says, is this a true positive,

791
00:28:00.750 --> 00:28:04.350
- a false positive, or benign with transparent reasoning?

792
00:28:04.350 --> 00:28:05.789
- So that can be a little helpful. Right?

793
00:28:05.789 --> 00:28:07.309
- Like, they drive you a little bit further

794
00:28:07.309 --> 00:28:08.049
- down, like,

795
00:28:08.750 --> 00:28:10.750
- something that maybe, like, a human doesn't need

796
00:28:10.750 --> 00:28:13.045
- to take a a hard decision on, but

797
00:28:13.045 --> 00:28:15.285
- can be human in the loop, things like

798
00:28:15.285 --> 00:28:17.205
- that. And that that's a little bit different

799
00:28:17.205 --> 00:28:19.765
- than, like, the threat intelligence agent, which is

800
00:28:19.765 --> 00:28:22.085
- still gonna give you your executive summary, all

801
00:28:22.085 --> 00:28:23.945
- all that kind of stuff. But

802
00:28:24.325 --> 00:28:24.485
- it's,

803
00:28:25.440 --> 00:28:27.619
- kinda just give you a a a profile

804
00:28:28.079 --> 00:28:30.179
- of a potential threat actor

805
00:28:30.720 --> 00:28:32.960
- and things that are out there. Interestingly, it

806
00:28:32.960 --> 00:28:34.640
- does do a little bit of kinda like

807
00:28:34.640 --> 00:28:38.079
- the attack investigation agent or maybe even like

808
00:28:38.079 --> 00:28:41.524
- that Rihan agent is doing. It's also kinda

809
00:28:41.585 --> 00:28:44.384
- looking for, like, indicators in your environment. So

810
00:28:44.384 --> 00:28:46.464
- if you're thinking about, like, identity logins, things

811
00:28:46.464 --> 00:28:49.204
- like that, like, that's looking at IP addresses,

812
00:28:49.345 --> 00:28:50.325
- domain names,

813
00:28:50.944 --> 00:28:52.005
- e email addresses.

814
00:28:52.359 --> 00:28:53.019
- And then

815
00:28:53.880 --> 00:28:55.880
- it's trying to leverage, because, again, Defender all

816
00:28:55.880 --> 00:28:57.480
- under the hood. Right? You've got this common

817
00:28:57.480 --> 00:28:59.559
- core platform in there. Yep. Pull in, like,

818
00:28:59.559 --> 00:29:01.579
- enrichment data from Defender.

819
00:29:02.039 --> 00:29:02.940
- So if there's,

820
00:29:04.279 --> 00:29:06.634
- any kind of known attack vectors, things like

821
00:29:06.634 --> 00:29:08.315
- that out there, it'll be able to classify

822
00:29:08.315 --> 00:29:10.315
- it against your environment. But to your point,

823
00:29:10.315 --> 00:29:12.075
- like, couldn't I just go and maybe look

824
00:29:12.075 --> 00:29:13.994
- at Secure Score or another dashboard? And, like,

825
00:29:13.994 --> 00:29:15.755
- that that stuff should be kinda screaming at

826
00:29:15.755 --> 00:29:17.355
- me to say go fix it. Maybe this

827
00:29:17.355 --> 00:29:18.634
- gives you a little bit more. The other

828
00:29:18.634 --> 00:29:20.480
- one that I feel like is kinda similar

829
00:29:20.480 --> 00:29:22.639
- to this is you already have and maybe

830
00:29:22.639 --> 00:29:24.980
- this is a superset. You already have vulnerability,

831
00:29:25.359 --> 00:29:28.639
- the vulnerability assessment, vulnerability management as well that's

832
00:29:28.639 --> 00:29:31.460
- in Defender that's already looking at your environment

833
00:29:31.599 --> 00:29:34.240
- and telling you where you're vulnerable, where you

834
00:29:34.240 --> 00:29:34.740
- have

835
00:29:35.105 --> 00:29:36.484
- users, machine software,

836
00:29:37.424 --> 00:29:39.525
- settings that are creating vulnerabilities

837
00:29:39.904 --> 00:29:40.644
- in your

838
00:29:41.025 --> 00:29:43.424
- environment. Again, maybe that's just one of the

839
00:29:43.424 --> 00:29:46.065
- items that feeds into this, but some of

840
00:29:46.065 --> 00:29:48.224
- these I feel like it's maybe a little

841
00:29:48.224 --> 00:29:48.965
- bit of a

842
00:29:49.289 --> 00:29:52.490
- stretch to say we need this agent doing

843
00:29:52.490 --> 00:29:54.670
- it because a lot of that functionality

844
00:29:55.049 --> 00:29:55.549
- is

845
00:29:55.930 --> 00:29:57.930
- already there to a certain extent. But you

846
00:29:57.930 --> 00:29:59.369
- kinda, like, want it to go just a

847
00:29:59.369 --> 00:30:01.769
- little bit more. Right? Give me the report,

848
00:30:01.769 --> 00:30:03.464
- take the output. Like, let me do something.

849
00:30:03.544 --> 00:30:05.784
- So so so, like, threat intelligence, for example.

850
00:30:05.784 --> 00:30:07.625
- Another one of the outputs that it has,

851
00:30:07.625 --> 00:30:09.464
- some of the artifacts. So you get this

852
00:30:09.464 --> 00:30:11.865
- markdown report that comes out. It also gives

853
00:30:11.865 --> 00:30:15.005
- you a bunch of kinda ready to go

854
00:30:15.304 --> 00:30:18.799
- Kusto queries, KQL queries for your Defender XDR

855
00:30:18.799 --> 00:30:19.299
- telemetry.

856
00:30:19.679 --> 00:30:21.679
- So that that's cool. Right? Like, not everybody

857
00:30:21.679 --> 00:30:24.559
- is a KQL expert, let alone understanding, like,

858
00:30:24.559 --> 00:30:26.980
- the schemas as they hop across maybe, like,

859
00:30:27.119 --> 00:30:29.119
- a set of tables and log analytics related

860
00:30:29.119 --> 00:30:31.244
- to Azure over to your security environment. Like,

861
00:30:31.325 --> 00:30:32.224
- that that stuff's,

862
00:30:32.765 --> 00:30:35.005
- like, can be weird to poke at. And

863
00:30:35.005 --> 00:30:36.845
- unless you, like, really know the schemas or

864
00:30:36.845 --> 00:30:38.924
- have internalized them, like, I could see that

865
00:30:38.924 --> 00:30:41.164
- being super helpful, but, like, why can't you

866
00:30:41.164 --> 00:30:43.244
- just go run those queries for me? Like,

867
00:30:43.244 --> 00:30:44.444
- so great. So you gave me a bunch

868
00:30:44.444 --> 00:30:46.549
- of ready to use Kusto queries that are

869
00:30:46.549 --> 00:30:48.230
- scoped to my environment that are gonna help

870
00:30:48.230 --> 00:30:49.849
- me search for indicators

871
00:30:50.150 --> 00:30:51.830
- of threats in my environment. Why don't I

872
00:30:51.830 --> 00:30:53.509
- just go run like, keep running it. Right?

873
00:30:53.509 --> 00:30:54.730
- Keep running it in a loop,

874
00:30:55.190 --> 00:30:57.190
- come back, and then kinda give me the

875
00:30:57.190 --> 00:30:59.605
- outputs, and let's go from there. So you

876
00:30:59.605 --> 00:31:01.845
- can see, like, the potential. Like, I think

877
00:31:01.845 --> 00:31:03.125
- this is where they would go with it,

878
00:31:03.125 --> 00:31:05.204
- but who knows? It's expensive to run it

879
00:31:05.204 --> 00:31:06.265
- in a loop, Scott.

880
00:31:06.884 --> 00:31:09.924
- That's gonna cost me both arms and legs

881
00:31:09.924 --> 00:31:11.579
- instead of just one arm and a leg.

882
00:31:11.579 --> 00:31:12.079
- Yeah.

883
00:31:13.339 --> 00:31:15.419
- But I do agree. Like, it would be

884
00:31:15.419 --> 00:31:17.679
- good to see it a little bit more

885
00:31:17.980 --> 00:31:18.480
- proactive,

886
00:31:19.179 --> 00:31:19.679
- automated

887
00:31:20.220 --> 00:31:22.779
- type of stuff. The other one are you

888
00:31:22.779 --> 00:31:24.859
- ready to move on to the detection authoring

889
00:31:24.859 --> 00:31:27.335
- agent? This is another one that intrigues me.

890
00:31:27.335 --> 00:31:29.174
- This one, I would say I can also

891
00:31:29.174 --> 00:31:30.794
- see a little more value here

892
00:31:31.095 --> 00:31:31.595
- of

893
00:31:32.054 --> 00:31:33.274
- this one is

894
00:31:33.815 --> 00:31:35.515
- to help you build

895
00:31:36.134 --> 00:31:37.914
- exactly what that sounds, detections.

896
00:31:38.375 --> 00:31:40.710
- What type of logic do you need to

897
00:31:40.710 --> 00:31:42.710
- have? What type of rules do you need

898
00:31:42.710 --> 00:31:43.690
- to have in place?

899
00:31:44.070 --> 00:31:46.250
- How should you be looking at your data

900
00:31:46.789 --> 00:31:48.250
- to help create

901
00:31:49.029 --> 00:31:50.410
- detections in your environment?

902
00:31:50.710 --> 00:31:51.210
- And

903
00:31:51.595 --> 00:31:53.035
- this one, to your point earlier about some

904
00:31:53.035 --> 00:31:55.115
- of the KQL and the schemas and generating

905
00:31:55.115 --> 00:31:58.414
- that, a lot of detection alerts right now

906
00:31:58.555 --> 00:31:59.934
- are based off

907
00:32:00.795 --> 00:32:03.275
- of KQL queries that you write or you

908
00:32:03.275 --> 00:32:05.970
- get from content packs and Sentinel where you

909
00:32:05.970 --> 00:32:07.970
- have all your data going in there, but

910
00:32:07.970 --> 00:32:09.750
- you need to write your

911
00:32:10.369 --> 00:32:13.650
- KQL queries and build your I completely am

912
00:32:13.650 --> 00:32:15.170
- blanking on the name of what they are

913
00:32:15.170 --> 00:32:17.809
- right now in Sentinel, but essentially your automated

914
00:32:17.809 --> 00:32:20.025
- triggers. It sees this data. It runs this

915
00:32:20.025 --> 00:32:22.684
- workbook every five minutes, fifteen minutes, hour,

916
00:32:22.984 --> 00:32:24.984
- but it still requires you to author all

917
00:32:24.984 --> 00:32:25.565
- of that.

918
00:32:25.865 --> 00:32:26.605
- This one

919
00:32:27.224 --> 00:32:27.724
- is

920
00:32:28.345 --> 00:32:31.404
- designed really to help people create

921
00:32:31.769 --> 00:32:32.990
- KQL based

922
00:32:33.289 --> 00:32:33.789
- detections,

923
00:32:34.410 --> 00:32:34.910
- map

924
00:32:35.450 --> 00:32:37.789
- detection coverage to MITRE attacks,

925
00:32:38.410 --> 00:32:41.950
- tune their detection methods. Especially your alerting logic.

926
00:32:42.089 --> 00:32:44.670
- Right. It's helping you build your alerting logic

927
00:32:44.765 --> 00:32:46.765
- in a way that maybe you don't need

928
00:32:46.765 --> 00:32:48.845
- to go in and understand all of that

929
00:32:48.845 --> 00:32:50.065
- logic to the

930
00:32:50.365 --> 00:32:52.625
- level of depth that you need to now.

931
00:32:52.684 --> 00:32:54.125
- I look at this kinda like how I

932
00:32:54.125 --> 00:32:56.365
- use AI to write PowerShell scripts. I can

933
00:32:56.365 --> 00:32:57.825
- go write a PowerShell script.

934
00:32:58.140 --> 00:33:00.220
- Sometimes it's easier just to let AI figure

935
00:33:00.220 --> 00:33:02.059
- out the logic and the tweaks and the

936
00:33:02.059 --> 00:33:04.380
- little nuances of it. I think this is

937
00:33:04.380 --> 00:33:05.900
- the same way. You can still go write

938
00:33:05.900 --> 00:33:08.000
- KQL. You can go write all of this.

939
00:33:08.220 --> 00:33:10.480
- This just helps with some of the nuances

940
00:33:10.539 --> 00:33:12.080
- and helps you refine

941
00:33:12.859 --> 00:33:13.839
- how you detect

942
00:33:14.515 --> 00:33:16.134
- or how you detect more alerts,

943
00:33:16.434 --> 00:33:18.914
- potential compromises in your environment, which I think

944
00:33:18.914 --> 00:33:19.894
- can be a good thing.

945
00:33:20.835 --> 00:33:23.234
- It can be very nuanced to write these

946
00:33:23.234 --> 00:33:23.734
- things

947
00:33:24.035 --> 00:33:26.275
- where you don't give so many false positives

948
00:33:26.275 --> 00:33:27.484
- that you just start ignoring them. I think

949
00:33:27.484 --> 00:33:27.529
- you're still a little and that's where it's

950
00:33:27.529 --> 00:33:28.134
- human in the loop. Right? Like, you're

951
00:33:31.190 --> 00:33:31.430
- depending on those

952
00:33:32.309 --> 00:33:33.830
- and so the agents, because it's a funnel,

953
00:33:33.830 --> 00:33:35.430
- they're meant to they are meant to feed

954
00:33:35.430 --> 00:33:37.990
- into each other. So but you you're sitting

955
00:33:37.990 --> 00:33:40.230
- there coming out of that threat intelligence agent,

956
00:33:40.230 --> 00:33:41.369
- which had those classifications,

957
00:33:41.670 --> 00:33:42.945
- like false

958
00:33:43.325 --> 00:33:45.724
- positive, true or or, yeah, false positive, true

959
00:33:45.724 --> 00:33:48.285
- positive, benign, and then you're taking it and

960
00:33:48.285 --> 00:33:51.085
- kind of passing it through passing parts of

961
00:33:51.085 --> 00:33:52.684
- it through, I guess, because you're kinda left

962
00:33:52.684 --> 00:33:53.424
- with, like,

963
00:33:53.884 --> 00:33:55.884
- the threat intelligence agent seems like it's giving

964
00:33:55.884 --> 00:33:58.200
- you a KQL to go and look and

965
00:33:58.200 --> 00:33:59.579
- hunt a little bit for yourself.

966
00:33:59.880 --> 00:34:02.759
- And then something like the detection authoring agent

967
00:34:02.759 --> 00:34:04.779
- is coming in. It's taking that

968
00:34:05.079 --> 00:34:08.039
- it's taking that report, and then it's still

969
00:34:08.039 --> 00:34:10.215
- generating you yet another set of

970
00:34:10.535 --> 00:34:11.035
- alerting

971
00:34:11.335 --> 00:34:13.894
- and detection logic that then you would go

972
00:34:13.894 --> 00:34:14.394
- and

973
00:34:14.695 --> 00:34:16.614
- deploy in your environment if you so choose.

974
00:34:16.614 --> 00:34:18.875
- Because, again, there's gonna be more, like, rationalization

975
00:34:19.175 --> 00:34:20.715
- here for you to say, hey.

976
00:34:21.015 --> 00:34:22.695
- Is this thing that the agent's telling me

977
00:34:22.695 --> 00:34:24.614
- something that I actually wanna go do? And

978
00:34:24.614 --> 00:34:26.699
- then that would make it very secure. Right?

979
00:34:26.699 --> 00:34:28.219
- You're sitting out there looking at a number

980
00:34:28.219 --> 00:34:29.739
- of, like, the what what I have to

981
00:34:29.739 --> 00:34:31.500
- do now? Like, a is still at 800

982
00:34:31.500 --> 00:34:33.420
- or I don't even know. I haven't paid

983
00:34:33.420 --> 00:34:35.019
- attention to, like, what the boundary is. But,

984
00:34:35.019 --> 00:34:36.699
- like, you're looking at a number, right, that

985
00:34:36.699 --> 00:34:38.619
- really doesn't have any meaning, and then you

986
00:34:38.619 --> 00:34:40.894
- gotta take a step back and figure out.

987
00:34:41.195 --> 00:34:42.974
- So, hopefully, some of these reports

988
00:34:43.275 --> 00:34:44.554
- come with them come with some of that

989
00:34:44.554 --> 00:34:46.235
- stuff. I would have loved to have seen,

990
00:34:46.235 --> 00:34:48.715
- like, sample reports in the documentation or something

991
00:34:48.715 --> 00:34:50.074
- like that, but they didn't have any of

992
00:34:50.074 --> 00:34:51.594
- that. They just give you the schemas, the

993
00:34:51.594 --> 00:34:54.130
- reports, or the high levels. What's gonna come

994
00:34:54.130 --> 00:34:55.910
- out of it? And then the final one,

995
00:34:55.969 --> 00:34:57.650
- green team. Ready to move on to green

996
00:34:57.650 --> 00:34:59.510
- team? The posture prioritization

997
00:35:00.210 --> 00:35:01.969
- agent. This is the one I was thinking

998
00:35:01.969 --> 00:35:03.670
- of that I'm like, this is just the

999
00:35:03.809 --> 00:35:05.590
- agentic agentic version

1000
00:35:05.969 --> 00:35:08.885
- of the Secure Score. This helps teams and

1001
00:35:08.885 --> 00:35:09.385
- stakeholders

1002
00:35:10.005 --> 00:35:12.804
- understand what to fix first and why. In

1003
00:35:12.804 --> 00:35:13.925
- my mind, that was the whole point of

1004
00:35:13.925 --> 00:35:15.925
- the Secure Score. Like, let me go look

1005
00:35:15.925 --> 00:35:17.684
- through the Secure Score and find where I'm

1006
00:35:17.684 --> 00:35:19.204
- the most vulnerable or where I can get

1007
00:35:19.204 --> 00:35:20.965
- the most bang for my buck in terms

1008
00:35:20.965 --> 00:35:23.309
- of fixing and use the Secure Score to

1009
00:35:23.469 --> 00:35:25.630
- prioritize it. Maybe this takes it a little

1010
00:35:25.630 --> 00:35:28.289
- step further. It's looking at the inputs of

1011
00:35:28.829 --> 00:35:29.809
- where are

1012
00:35:30.750 --> 00:35:32.289
- attacks being seen,

1013
00:35:33.070 --> 00:35:34.050
- what is

1014
00:35:34.910 --> 00:35:35.890
- some of the

1015
00:35:36.324 --> 00:35:37.144
- attack investigation

1016
00:35:37.445 --> 00:35:38.664
- or the threat intelligence,

1017
00:35:39.045 --> 00:35:39.785
- the detection,

1018
00:35:40.244 --> 00:35:42.184
- authoring that you're writing.

1019
00:35:42.565 --> 00:35:44.724
- Is this taking inputs from the blue team

1020
00:35:44.724 --> 00:35:45.785
- to kinda reprioritize?

1021
00:35:46.324 --> 00:35:47.925
- Because the one thing I would say about

1022
00:35:47.925 --> 00:35:49.545
- Secure Score is

1023
00:35:50.000 --> 00:35:52.719
- it was very much, is this configuration on,

1024
00:35:52.719 --> 00:35:54.880
- and how many users, how many machines, etcetera,

1025
00:35:54.880 --> 00:35:56.559
- is it applied to? You just get a

1026
00:35:56.559 --> 00:35:58.019
- number. The prioritization

1027
00:35:58.880 --> 00:36:00.179
- of Secure Score

1028
00:36:00.719 --> 00:36:01.219
- wasn't

1029
00:36:02.364 --> 00:36:03.425
- necessarily based

1030
00:36:04.045 --> 00:36:06.445
- on what I would say real world data,

1031
00:36:06.445 --> 00:36:08.925
- real world analytics, and what's going on in

1032
00:36:08.925 --> 00:36:11.565
- your tenant other than a settings offer on

1033
00:36:11.565 --> 00:36:14.445
- across x number of people. So maybe this

1034
00:36:14.445 --> 00:36:16.989
- helps with a little bit more real time

1035
00:36:16.989 --> 00:36:17.489
- prioritization,

1036
00:36:18.109 --> 00:36:20.269
- taking in a few more signals other than

1037
00:36:20.269 --> 00:36:23.069
- just is a configuration on or off. But

1038
00:36:23.069 --> 00:36:25.469
- this is going to not go in and

1039
00:36:25.469 --> 00:36:27.309
- make fixes for you, going back to your

1040
00:36:27.309 --> 00:36:29.309
- human in the loop, the read only, it's

1041
00:36:29.309 --> 00:36:31.585
- just going to tell you here's the order

1042
00:36:31.585 --> 00:36:33.265
- you should go apply all these settings or

1043
00:36:33.265 --> 00:36:35.025
- fix all these things in your environment. The

1044
00:36:35.025 --> 00:36:37.344
- other thing we should maybe talk about here

1045
00:36:37.344 --> 00:36:39.844
- as we're kinda getting towards the end is

1046
00:36:39.985 --> 00:36:42.545
- orchestrating these things or pushing them together. It's

1047
00:36:42.545 --> 00:36:44.579
- great. So you you get all these agents

1048
00:36:44.579 --> 00:36:45.559
- that are out there.

1049
00:36:45.860 --> 00:36:47.480
- Like, what does it look like

1050
00:36:48.579 --> 00:36:50.840
- to run them? I think the the

1051
00:36:51.220 --> 00:36:52.820
- the most interesting one to me was probably

1052
00:36:52.820 --> 00:36:55.700
- the playbook things or the playbook play. Go

1053
00:36:55.700 --> 00:36:58.094
- go and kick these things off. So if

1054
00:36:58.094 --> 00:37:01.295
- you did have something in the Defender portal

1055
00:37:01.295 --> 00:37:02.974
- pop up, so you get an incident to

1056
00:37:02.974 --> 00:37:04.974
- where you get an alert that pops up,

1057
00:37:04.974 --> 00:37:06.894
- you can go run these playbooks, and then

1058
00:37:06.894 --> 00:37:08.675
- the playbooks act as orchestrators

1059
00:37:09.054 --> 00:37:11.614
- for the underlying agent definitions that are out

1060
00:37:11.614 --> 00:37:12.755
- there. So they can kinda

1061
00:37:13.099 --> 00:37:15.679
- go start the flywheel for you, but then

1062
00:37:15.820 --> 00:37:17.980
- you'll still be human in the loop for

1063
00:37:17.980 --> 00:37:19.659
- kinda those decisions along the way that we

1064
00:37:19.659 --> 00:37:21.739
- talked about. Yep. And these are very much

1065
00:37:21.900 --> 00:37:23.739
- this is something I would love to be

1066
00:37:23.739 --> 00:37:25.440
- able to start playing with. Maybe

1067
00:37:25.739 --> 00:37:28.045
- once it becomes generally available, I'll just spin

1068
00:37:28.045 --> 00:37:29.364
- it up for a few days to play

1069
00:37:29.364 --> 00:37:31.684
- with it. But Playbooks very much came from

1070
00:37:31.684 --> 00:37:34.105
- Security Copilot. Like, people already have

1071
00:37:34.405 --> 00:37:36.964
- Security Playbooks in there running a series Yeah.

1072
00:37:36.964 --> 00:37:38.744
- I mean, you can see the evolution here.

1073
00:37:39.410 --> 00:37:41.170
- Like, this is just I feel like this

1074
00:37:41.170 --> 00:37:44.849
- is even further integrating Security Copilot into where

1075
00:37:44.849 --> 00:37:46.289
- people work. Now you don't have to go

1076
00:37:46.289 --> 00:37:48.309
- over there, you can go trader these playbooks,

1077
00:37:48.690 --> 00:37:51.190
- tie in these agents that, I mean, realistically,

1078
00:37:51.890 --> 00:37:54.369
- maybe are a part of Security Copilot or

1079
00:37:54.369 --> 00:37:56.114
- this is the next

1080
00:37:56.414 --> 00:37:58.195
- iteration of Security Copilot

1081
00:37:58.494 --> 00:38:01.934
- within your environment. But, yeah, the playbooks look

1082
00:38:01.934 --> 00:38:04.355
- like they're gonna be that main

1083
00:38:04.815 --> 00:38:07.295
- that main service that you're gonna go use

1084
00:38:07.295 --> 00:38:08.835
- or that main functionality

1085
00:38:09.215 --> 00:38:11.670
- that you're gonna use to go trigger all

1086
00:38:11.670 --> 00:38:15.030
- these prompts and these agents from various areas

1087
00:38:15.030 --> 00:38:17.909
- within Defender or within your environment. Defender then

1088
00:38:17.989 --> 00:38:19.829
- it's interesting. It becomes part of that single

1089
00:38:19.829 --> 00:38:21.670
- pane of glass as well, which it was

1090
00:38:21.670 --> 00:38:22.969
- meant to be anyway. So

1091
00:38:23.269 --> 00:38:24.789
- you you can kinda come at it a

1092
00:38:24.789 --> 00:38:26.409
- couple different ways. Exactly.

1093
00:38:27.164 --> 00:38:30.364
- Anything else? Sessions? I mean, sessions are just

1094
00:38:30.364 --> 00:38:32.765
- monitoring your agent work. Session, just like any

1095
00:38:32.765 --> 00:38:35.565
- session in AI. But it's interesting. I'm curious

1096
00:38:35.565 --> 00:38:37.324
- to see where this goes. I am curious

1097
00:38:37.324 --> 00:38:39.184
- to get my hands on it and

1098
00:38:39.644 --> 00:38:40.969
- use it sparingly

1099
00:38:41.269 --> 00:38:43.130
- so I don't run out of money. But

1100
00:38:43.590 --> 00:38:45.829
- and to see to your point where agents

1101
00:38:45.829 --> 00:38:48.230
- are going, this is still very much a

1102
00:38:48.230 --> 00:38:49.369
- lot of read only.

1103
00:38:49.750 --> 00:38:50.250
- As

1104
00:38:50.550 --> 00:38:53.609
- these get better and better, is there a

1105
00:38:53.909 --> 00:38:55.050
- point we get to

1106
00:38:55.394 --> 00:38:57.015
- where an alert gets detected

1107
00:38:57.554 --> 00:38:59.795
- in one of the, I guess, the blue

1108
00:38:59.795 --> 00:39:02.355
- team agents would be detecting them and then

1109
00:39:02.355 --> 00:39:04.195
- triggering off a green team agent where it

1110
00:39:04.195 --> 00:39:05.894
- actually can go in and

1111
00:39:06.275 --> 00:39:09.315
- make the resolution, make the fix to whatever

1112
00:39:09.315 --> 00:39:11.079
- the issue is? We were talking about it

1113
00:39:11.079 --> 00:39:12.519
- earlier. I feel like I'd still be a

1114
00:39:12.519 --> 00:39:14.199
- little nervous of that. There's a whole weird

1115
00:39:14.199 --> 00:39:16.460
- thing here. Right? So so do you trust

1116
00:39:16.519 --> 00:39:18.839
- these identities? So so, like, that recon agent

1117
00:39:18.839 --> 00:39:20.599
- is out there, but it's it's got a

1118
00:39:20.599 --> 00:39:23.255
- bunch of those graph permissions. Like, okay. Hey.

1119
00:39:23.255 --> 00:39:25.655
- And it's got Azure subscription scope rules in

1120
00:39:25.655 --> 00:39:28.055
- it. So, sure, they're read only, but it

1121
00:39:28.055 --> 00:39:29.434
- does expose your configuration.

1122
00:39:29.815 --> 00:39:30.315
- Like,

1123
00:39:30.695 --> 00:39:32.474
- what what happens if that configuration,

1124
00:39:33.094 --> 00:39:35.414
- like, report doesn't get published to the right

1125
00:39:35.414 --> 00:39:35.914
- place?

1126
00:39:36.230 --> 00:39:39.109
- There's a big question about who supervises these

1127
00:39:39.109 --> 00:39:39.609
- things.

1128
00:39:39.909 --> 00:39:42.469
- So if you're gonna be, like, human in

1129
00:39:42.469 --> 00:39:43.849
- the loop for these things

1130
00:39:44.150 --> 00:39:46.630
- and you're gonna be supervising it, I think

1131
00:39:46.630 --> 00:39:49.670
- you'd want those folks to have kinda the

1132
00:39:49.670 --> 00:39:51.984
- same or greater permissions than the agent. Right?

1133
00:39:51.984 --> 00:39:53.265
- You wouldn't want the agent to be able

1134
00:39:53.265 --> 00:39:54.625
- to run away past that? Yeah. Because you

1135
00:39:54.625 --> 00:39:56.164
- wanna be able to go in and validate

1136
00:39:56.465 --> 00:39:58.144
- some of the data coming back, I think.

1137
00:39:58.144 --> 00:39:59.664
- I would. But what does that look like

1138
00:39:59.664 --> 00:40:00.804
- in a world of,

1139
00:40:01.264 --> 00:40:04.085
- like, junior to senior level, like,

1140
00:40:04.920 --> 00:40:07.960
- folks in your security operations center. Like, if

1141
00:40:07.960 --> 00:40:09.800
- you're sitting out there, typically, like, junior folks

1142
00:40:09.800 --> 00:40:11.319
- are gonna be, like, very scoped down in

1143
00:40:11.319 --> 00:40:13.319
- their permission. Like, now you can't have them

1144
00:40:13.319 --> 00:40:15.400
- fully monitor the agent because, one, they could

1145
00:40:15.400 --> 00:40:17.474
- be exposed to configuration they're not supposed to,

1146
00:40:17.875 --> 00:40:20.914
- and, two, they don't have the same rights

1147
00:40:20.914 --> 00:40:22.934
- as as they need to anyway.

1148
00:40:23.315 --> 00:40:25.235
- And then I think it will be interesting

1149
00:40:25.235 --> 00:40:27.894
- as more, like, activity based things come in.

1150
00:40:27.954 --> 00:40:30.355
- So where you can maybe do things like,

1151
00:40:30.355 --> 00:40:32.675
- oh, say, like, disable a user account based

1152
00:40:32.675 --> 00:40:33.559
- on, on, like, anomalous

1153
00:40:34.019 --> 00:40:36.280
- logins or things like that today.

1154
00:40:36.739 --> 00:40:38.340
- Where do you start to kinda peel back

1155
00:40:38.340 --> 00:40:38.840
- permissions

1156
00:40:39.300 --> 00:40:41.699
- or become more permissive, I guess, in in

1157
00:40:41.699 --> 00:40:43.380
- what you put out there? And when do

1158
00:40:43.380 --> 00:40:45.940
- you start to kinda tear down approval gates?

1159
00:40:45.940 --> 00:40:47.480
- Because if you go through the documentation,

1160
00:40:48.035 --> 00:40:49.394
- one of the things that'll pop up a

1161
00:40:49.394 --> 00:40:50.775
- couple times is

1162
00:40:51.795 --> 00:40:52.535
- the suggestion,

1163
00:40:53.394 --> 00:40:55.075
- not like the discrete guidance to go do

1164
00:40:55.075 --> 00:40:56.695
- this, but it is definitely a suggestion

1165
00:40:57.315 --> 00:41:00.594
- to just reduce, like, approval gates and some

1166
00:41:00.594 --> 00:41:03.075
- of the friction that's there for those agents.

1167
00:41:03.075 --> 00:41:05.530
- So, like, hey. It's proven. Like, I I

1168
00:41:05.530 --> 00:41:06.889
- had to do this thing. It feels like

1169
00:41:06.889 --> 00:41:08.730
- it's deterministic, and it's out there. Is it

1170
00:41:08.730 --> 00:41:09.949
- gonna be truly deterministic?

1171
00:41:10.250 --> 00:41:12.010
- Right. Who knows? Maybe it is today, but

1172
00:41:12.010 --> 00:41:13.849
- is it when, like, the next underlying, like,

1173
00:41:13.849 --> 00:41:16.269
- foundation model comes out or things like that?

1174
00:41:16.585 --> 00:41:18.664
- Oh, that that's the other one to think

1175
00:41:18.664 --> 00:41:21.644
- about is I didn't see any place where

1176
00:41:22.344 --> 00:41:23.324
- it's explicitly

1177
00:41:24.105 --> 00:41:24.925
- called out

1178
00:41:25.304 --> 00:41:25.804
- what

1179
00:41:26.105 --> 00:41:26.605
- models

1180
00:41:27.065 --> 00:41:30.130
- these agents use under the hood. It's kinda

1181
00:41:30.130 --> 00:41:31.670
- hand wavy. It talks about, like,

1182
00:41:31.969 --> 00:41:32.469
- OpenAI

1183
00:41:33.090 --> 00:41:35.909
- Foundry models, Azure OpenAI Foundry models,

1184
00:41:36.610 --> 00:41:39.670
- but which ones and what's out there. Because

1185
00:41:40.130 --> 00:41:42.210
- very much, like, sometimes, like, the model does

1186
00:41:42.210 --> 00:41:43.510
- have a big play

1187
00:41:43.889 --> 00:41:44.389
- in

1188
00:41:44.929 --> 00:41:48.265
- what type of output you're going to get

1189
00:41:48.265 --> 00:41:50.265
- from the same set of inputs. Right? Like,

1190
00:41:50.265 --> 00:41:51.785
- you'd be as structured as you wanna be

1191
00:41:51.785 --> 00:41:53.325
- in that agent configuration

1192
00:41:53.704 --> 00:41:56.105
- and and flow of it. But throwing it

1193
00:41:56.105 --> 00:41:59.005
- against, like, GPT five five versus

1194
00:41:59.625 --> 00:42:02.179
- the new five six, like, Sol Luna Terra

1195
00:42:02.179 --> 00:42:04.579
- stuff, like, gives you very different results. So

1196
00:42:04.579 --> 00:42:06.039
- my understanding of this

1197
00:42:06.500 --> 00:42:09.000
- based on the blog post,

1198
00:42:09.380 --> 00:42:11.000
- and I didn't see it in the documentation,

1199
00:42:11.219 --> 00:42:13.400
- is that it is very much a

1200
00:42:14.099 --> 00:42:14.599
- multimodel

1201
00:42:15.224 --> 00:42:17.085
- where it might be using some OpenAI,

1202
00:42:17.704 --> 00:42:19.405
- it might be using some Claude.

1203
00:42:19.704 --> 00:42:22.345
- It also looks like it is using and

1204
00:42:22.345 --> 00:42:25.005
- we didn't even talk about this, the MAI.

1205
00:42:25.224 --> 00:42:27.545
- I don't know how you pronounce Microsoft's models

1206
00:42:27.545 --> 00:42:30.045
- now. May, my, the CyberOne

1207
00:42:30.505 --> 00:42:31.859
- Flash, which is Microsoft's

1208
00:42:32.480 --> 00:42:33.699
- new security model

1209
00:42:34.239 --> 00:42:36.900
- that they claim it scored better above Mythos.

1210
00:42:37.119 --> 00:42:39.039
- I think all of these companies run their

1211
00:42:39.039 --> 00:42:39.780
- own benchmarks

1212
00:42:40.400 --> 00:42:42.320
- on their own models. Your mileage is gonna

1213
00:42:42.320 --> 00:42:45.199
- vary with benchmarks and what are out there.

1214
00:42:45.199 --> 00:42:46.099
- Yeah. On

1215
00:42:46.505 --> 00:42:48.425
- how it is, but it does say it

1216
00:42:48.744 --> 00:42:50.664
- oh, here. It does. Project perception will take

1217
00:42:50.664 --> 00:42:52.905
- advantage of that Cyber One Flash model from

1218
00:42:52.905 --> 00:42:55.785
- Microsoft that they created. For which parts? For

1219
00:42:55.785 --> 00:42:57.864
- what? For which parts? It doesn't say I

1220
00:42:57.864 --> 00:42:59.545
- don't know. I don't know. I don't know.

1221
00:42:59.545 --> 00:43:00.369
- I don't know. I don't know. I don't

1222
00:43:00.369 --> 00:43:00.561
- know. I don't know. I don't know. I

1223
00:43:00.561 --> 00:43:02.699
- don't know. I like my kids. Ask me

1224
00:43:02.699 --> 00:43:05.260
- impossible questions. Where all your SCU cost is

1225
00:43:05.260 --> 00:43:07.340
- coming from. It's all hidden away under the

1226
00:43:07.340 --> 00:43:08.400
- hood. That's

1227
00:43:08.699 --> 00:43:11.179
- my understanding is I don't know that they're

1228
00:43:11.179 --> 00:43:13.500
- publishing the model because I mean, do do

1229
00:43:13.500 --> 00:43:15.179
- they even know which one gets passed off

1230
00:43:15.179 --> 00:43:17.340
- to which model, or is this one of

1231
00:43:17.340 --> 00:43:17.840
- those

1232
00:43:18.515 --> 00:43:20.375
- where there's, like, the initial

1233
00:43:20.914 --> 00:43:21.414
- foundational

1234
00:43:22.195 --> 00:43:24.594
- model that initially prompts it, and then the

1235
00:43:24.594 --> 00:43:27.394
- agents go out to find the right model

1236
00:43:27.394 --> 00:43:29.875
- based on the tasks they wanna do? There

1237
00:43:29.875 --> 00:43:31.335
- is some blurriness

1238
00:43:31.635 --> 00:43:34.389
- there in which models it's using where. Other

1239
00:43:34.389 --> 00:43:36.650
- than that, it is gonna use Microsoft's model,

1240
00:43:37.030 --> 00:43:37.530
- its

1241
00:43:37.989 --> 00:43:40.869
- aspects of it. How that propagates out to

1242
00:43:40.869 --> 00:43:41.530
- other ones

1243
00:43:41.909 --> 00:43:42.809
- is absolutely

1244
00:43:43.349 --> 00:43:43.849
- vague.

1245
00:43:44.309 --> 00:43:46.329
- I think it's gonna take some time to

1246
00:43:46.505 --> 00:43:48.744
- figure it all out. Yes. Yeah. No single

1247
00:43:48.744 --> 00:43:50.905
- model will be optimal for every security task.

1248
00:43:50.905 --> 00:43:52.905
- Cyber defense requires the right model for the

1249
00:43:52.905 --> 00:43:54.445
- right problem at the right time.

1250
00:43:54.744 --> 00:43:57.144
- Project perception, the right model is determined by

1251
00:43:57.144 --> 00:44:00.525
- the combination of quality, reliability, latency, and cost

1252
00:44:00.860 --> 00:44:02.460
- rather than relying on a single model, blah

1253
00:44:02.460 --> 00:44:04.699
- blah blah blah blah. So it is using

1254
00:44:04.699 --> 00:44:07.900
- a slew of models that it picks based

1255
00:44:07.900 --> 00:44:10.460
- on some rules Microsoft has in place. Yeah.

1256
00:44:10.460 --> 00:44:12.380
- Got it. Interesting. But we will have that,

1257
00:44:12.380 --> 00:44:13.440
- the blog post.

1258
00:44:13.820 --> 00:44:15.420
- So there's the blog post out there. There's

1259
00:44:15.420 --> 00:44:16.079
- the Microsoft

1260
00:44:16.699 --> 00:44:17.875
- web web page out there that we'll have

1261
00:44:17.875 --> 00:44:19.255
- in the show notes, and then

1262
00:44:19.554 --> 00:44:20.855
- all the learned documentation

1263
00:44:21.234 --> 00:44:23.234
- is already available. So you can go read

1264
00:44:23.234 --> 00:44:24.214
- all about this,

1265
00:44:24.674 --> 00:44:28.034
- see everything, you just can't get access to

1266
00:44:28.034 --> 00:44:30.355
- it yet. They do have a button for

1267
00:44:30.355 --> 00:44:31.414
- contact sales

1268
00:44:31.940 --> 00:44:33.320
- where you would normally

1269
00:44:33.700 --> 00:44:35.700
- go to, like, buy a preview or get

1270
00:44:35.700 --> 00:44:37.780
- started with it. Anytime a website tells me

1271
00:44:37.780 --> 00:44:39.940
- to contact sales, I think of this isn't

1272
00:44:39.940 --> 00:44:40.840
- gonna be cheap.

1273
00:44:41.700 --> 00:44:42.519
- That's just

1274
00:44:42.980 --> 00:44:44.440
- Yeah. My pre programming.

1275
00:44:45.045 --> 00:44:47.045
- So I'm excited to get my hands on

1276
00:44:47.045 --> 00:44:48.164
- it and try it out and see what's

1277
00:44:48.164 --> 00:44:49.684
- in there at some point in time. I

1278
00:44:49.684 --> 00:44:51.204
- don't know when that will be. We'll have

1279
00:44:51.204 --> 00:44:52.885
- a follow-up episode when we can actually play

1280
00:44:52.885 --> 00:44:53.864
- with it. Follow-up.

1281
00:44:54.484 --> 00:44:57.704
- Ben Ben plays with agents in the clap.

1282
00:44:57.890 --> 00:45:00.289
- Yeah. No. I think it'll it'll be interesting

1283
00:45:00.289 --> 00:45:01.510
- to see how it forms

1284
00:45:01.809 --> 00:45:04.210
- over time and, well, how, like, how the

1285
00:45:04.210 --> 00:45:04.710
- manifestations

1286
00:45:05.410 --> 00:45:06.469
- of those agents

1287
00:45:06.769 --> 00:45:09.670
- change. Like I said, they're very they're very

1288
00:45:09.730 --> 00:45:10.949
- high level today,

1289
00:45:11.324 --> 00:45:13.484
- and it's gonna be it's gonna be quite

1290
00:45:13.484 --> 00:45:15.565
- the journey to see them go from being

1291
00:45:15.565 --> 00:45:18.364
- able to affect, like, tenant configuration changes, things

1292
00:45:18.364 --> 00:45:19.804
- like that. It's like a hard no and

1293
00:45:19.804 --> 00:45:20.945
- read only to

1294
00:45:21.484 --> 00:45:23.565
- more broad yeses and what can be out

1295
00:45:23.565 --> 00:45:25.019
- there and be done with it. With that,

1296
00:45:25.099 --> 00:45:26.539
- I have a meeting coming up. I would

1297
00:45:26.539 --> 00:45:28.719
- love to hear other people's thoughts on this

1298
00:45:28.780 --> 00:45:30.480
- if somebody listening actually

1299
00:45:30.940 --> 00:45:33.019
- is in the public preview and has access

1300
00:45:33.019 --> 00:45:34.699
- to it and you're allowed to talk about

1301
00:45:34.699 --> 00:45:36.300
- it. Feel free to reach out. Like I

1302
00:45:36.300 --> 00:45:38.000
- said, this past week, we had some discussion

1303
00:45:38.059 --> 00:45:40.335
- on Reddit about some of these things on

1304
00:45:40.335 --> 00:45:42.195
- the MS Cloud IT Pro

1305
00:45:42.494 --> 00:45:45.775
- subreddit. Feel free to discuss on LinkedIn as

1306
00:45:45.775 --> 00:45:47.074
- well. Would love to

1307
00:45:47.375 --> 00:45:50.114
- chat with people there and get people's thoughts.

1308
00:45:50.414 --> 00:45:52.869
- Also, Scott, if there is anybody that's gonna

1309
00:45:52.869 --> 00:45:55.110
- be at TechCon three sixty five in Seattle

1310
00:45:55.110 --> 00:45:56.250
- the end of August,

1311
00:45:56.550 --> 00:45:59.510
- it'll be, like, two weeks after this episode

1312
00:45:59.510 --> 00:46:01.030
- comes out. I will be out there doing

1313
00:46:01.030 --> 00:46:02.949
- a few sessions and would love to connect

1314
00:46:02.949 --> 00:46:05.130
- with anybody that will be out in

1315
00:46:05.625 --> 00:46:07.144
- Seattle at the end of August for that

1316
00:46:07.144 --> 00:46:09.304
- conference. Got any codes or anything for them?

1317
00:46:09.304 --> 00:46:10.985
- I do have a code. I just I

1318
00:46:10.985 --> 00:46:13.224
- should know what it is. Oh, I shoulda

1319
00:46:13.224 --> 00:46:14.184
- looked it up. It is

1320
00:46:14.824 --> 00:46:16.344
- it can be in the show notes. I

1321
00:46:16.344 --> 00:46:19.190
- think it's I'm not going to even

1322
00:46:20.050 --> 00:46:21.409
- make one up. Kinda put you on the

1323
00:46:21.409 --> 00:46:23.170
- spot, so we'll put it in the show

1324
00:46:23.170 --> 00:46:25.889
- notes. There's two Bens you did. We'll put

1325
00:46:25.889 --> 00:46:27.329
- it in the show notes. There's two Bens,

1326
00:46:27.329 --> 00:46:28.849
- and I can't remember if I'm Ben or

1327
00:46:28.849 --> 00:46:30.449
- Ben too. I mean, you are well, you

1328
00:46:30.449 --> 00:46:32.234
- are Ben as well. That's okay. I am

1329
00:46:32.234 --> 00:46:33.914
- Ben as well, and I was trying to

1330
00:46:33.914 --> 00:46:36.014
- find one of my posts here that

1331
00:46:36.315 --> 00:46:37.355
- oh, here it is. I know where I

1332
00:46:37.355 --> 00:46:39.594
- can find it. Oh, super quick. How quick

1333
00:46:39.594 --> 00:46:42.174
- can I go? I found a post that

1334
00:46:42.315 --> 00:46:44.094
- has my code.

1335
00:46:44.635 --> 00:46:46.880
- Ben200BEN,

1336
00:46:46.880 --> 00:46:48.720
- and then the number 200. We'll save you

1337
00:46:48.720 --> 00:46:51.760
- $200. In February. And TekCon in Seattle? TekCon

1338
00:46:51.760 --> 00:46:53.760
- in Seattle. Yep. August

1339
00:46:53.760 --> 00:46:54.720
- '28.

1340
00:46:54.720 --> 00:46:56.420
- Alright. Well, thanks for

1341
00:46:57.039 --> 00:46:59.015
- sitting on. It's always good to walk through

1342
00:46:59.015 --> 00:47:00.695
- a spec sheet with you here, Ben. Yes.

1343
00:47:00.695 --> 00:47:02.614
- For sure. Thank you. Thank you for your

1344
00:47:02.614 --> 00:47:05.575
- perspective on perception. Perception. Okay. Your perception of

1345
00:47:05.575 --> 00:47:07.815
- perception. We're we're gonna get all we're gonna

1346
00:47:07.815 --> 00:47:09.195
- get all twisted around.

1347
00:47:09.655 --> 00:47:12.070
- Alright. It's Monday. Go enjoy your meetings. Thanks,

1348
00:47:12.070 --> 00:47:13.369
- Ben. Alright. Thanks, Scott.

1349
00:47:15.349 --> 00:47:17.589
- If you enjoyed the podcast, go leave us

1350
00:47:17.589 --> 00:47:19.829
- a five star rating in iTunes. It helps

1351
00:47:19.829 --> 00:47:21.589
- to get the word out so more IT

1352
00:47:21.589 --> 00:47:23.670
- pros can learn about Office three sixty five

1353
00:47:23.670 --> 00:47:24.464
- in and Azure.

1354
00:47:24.925 --> 00:47:26.525
- If you have any questions you want us

1355
00:47:26.525 --> 00:47:28.764
- to address on the show, or feedback about

1356
00:47:28.764 --> 00:47:31.085
- the show, feel free to reach out via

1357
00:47:31.085 --> 00:47:33.264
- our website, Twitter, or Facebook.

1358
00:47:33.565 --> 00:47:35.484
- Thanks again for listening, and have a great

1359
00:47:35.484 --> 00:47:35.984
- day.