Is that something from the Firemon side that you guys, because you have that, those other integrations, the context and the visibility that you're putting some of those pieces together and streamlining pieces of that?

I think you had mentioned some of the stats that we were talking about earlier, and that comes from a product that allows us, one of our modules that allows us to extend key security performance indicators in a dashboard-type fashion online.

throughout the organization so that we can invite other stakeholders to the party, so to speak.

So now we can provide them statistical information or telemetry that's specific to their role in the organization and the goals that they have, rather than having to give them access to the platform and teach them how to use it and And they don't have to be a Firemon user or a Firemon administrator.

We give them their own custom dashboard.

And then we populate that dashboard in real time with the key security performance indicators that's important to them.

We also use AI to drive insights into that so they know exactly what they're using, what they're looking at there, what it means.

Do you have an idea of what the next two to three years are going to look like?

Even at the time of deployment

... at, you know, the 25...

Firemon's been around 25 years, and over those 25 years, and I've been there for a good part of that, but, um, I can say without reservation, uh, the, the, the 69% number you mentioned of unused rules, I always used to say 30 to 40% is kind of what we often, before we had some kind of hard telemetry around it, um, is what I would say.

And it wasn't unusual to engage with a new client and find, you know, start looking at their firewalls, fire- firewalls two weeks in, three weeks in, and find that, you know, they had, um, you know, 40%, 50% of the policy unused over time.

But one of the things that I, I can say for sure, if you don't challenge that unnecessary complexity within the environment, if you're not looking at those unused rules, duplicate rules, shattered rules, overly permissive rules, things like that, there's a couple things that are gonna happen.

One is risk is definitely going to go up.

The probability of human error is going to go up.

Is that something from the Firemon side that you guys, because you have that, th- those other integrations, the context and the visibility, that you're putting some of those pieces together and streamlining pieces of that?

Even at the time of deployment

...

the 25, Firemon's been around 25 years, and over those 25 years, and I've been there for a good part of that, but, um, I can say without reservation, uh, the, the, the 69% number you mentioned of unused rules, I always used to say 30 to 40% is kind of what we often, before we had some kind of hard telemetry around it, um, is what I would say.

And it wasn't unusual to engage with a new client and find, you know, start looking at their firewalls, fire- firewalls two weeks in, three weeks in and find that, you know, they had, um, you know, you know, 40%, 50% of the policy unused over time.

But one of the things that I, I can say for sure, if you don't challenge that unnecessary complexity within the environment, if you're not looking at those unused rules, duplicate rules, shattered rules, overly permissive rules, things like that, there's a couple things that are gonna happen.

One is risk is definitely going to go up.

The probability of human error is going to go up.

Is that something from the Firemon side that you guys, because you have that, th- those other integrations, the context and the visibility, that you're putting some of those pieces together and streamlining pieces of that?

We sampled.

Absolutely.

A little taste.

[whooshing] We'll get back to D&D in a second.

Being brought to you by Chevy.

Chill week is right around the corner, and you know what that means.

No schedules, no plans, just more of the good stuff.

It's a five.

I would like to use one full max on a, an implosion of this potion shop.

Absolutely, now is a great time to do it, I would say.

It automatically deals 24 damage, that means, to everybody in the shop.

Not to yourself.

The shatter spell doesn't hit you, the collapse might hit you, though.

So you set off the shatter spell.

Istrid immediately takes 24 damage, but 'cause she...

And by the way, don't- we can't forget we made our name.