Guy Guzner

in a way that we can do a lot of the processing and the CPU intensive activities using compute resources that are running on the browser extension that is on a customer machine so we don't need to run them in our cloud. That has been very effective because we were able to add tens and hundreds of thousands of users to our environment and you hardly see an impact.

in a way that we can do a lot of the processing and the CPU intensive activities using compute resources that are running on the browser extension that is on a customer machine so we don't need to run them in our cloud. That has been very effective because we were able to add tens and hundreds of thousands of users to our environment and you hardly see an impact.

in a way that we can do a lot of the processing and the CPU intensive activities using compute resources that are running on the browser extension that is on a customer machine so we don't need to run them in our cloud. That has been very effective because we were able to add tens and hundreds of thousands of users to our environment and you hardly see an impact.

Another decision was also based on that, is that we don't want to be in the data path. Because that was also a thing that we did in Fireglass. And once you go in public cloud and you need to pay for inbound bandwidth and everything, AWS, that becomes really expensive.

Another decision was also based on that, is that we don't want to be in the data path. Because that was also a thing that we did in Fireglass. And once you go in public cloud and you need to pay for inbound bandwidth and everything, AWS, that becomes really expensive.

Another decision was also based on that, is that we don't want to be in the data path. Because that was also a thing that we did in Fireglass. And once you go in public cloud and you need to pay for inbound bandwidth and everything, AWS, that becomes really expensive.

So we've built this in a way that we just need to be in the control path of the traffic, just capture metadata, but then transactions and sessions don't really need to go through our product.

So we've built this in a way that we just need to be in the control path of the traffic, just capture metadata, but then transactions and sessions don't really need to go through our product.

So we've built this in a way that we just need to be in the control path of the traffic, just capture metadata, but then transactions and sessions don't really need to go through our product.

I'm really proud of the architecture that we've built, taking the best practices from several sources. And then there's a lot of unique IP in our product. One of the things that I'm really excited about is what we call zero touch integration.

I'm really proud of the architecture that we've built, taking the best practices from several sources. And then there's a lot of unique IP in our product. One of the things that I'm really excited about is what we call zero touch integration.

I'm really proud of the architecture that we've built, taking the best practices from several sources. And then there's a lot of unique IP in our product. One of the things that I'm really excited about is what we call zero touch integration.

And that's a patent pending technology where we're able to integrate with SaaS applications without the administrator having to create and maintain that integration themselves.

And that's a patent pending technology where we're able to integrate with SaaS applications without the administrator having to create and maintain that integration themselves.

And that's a patent pending technology where we're able to integrate with SaaS applications without the administrator having to create and maintain that integration themselves.

What we're doing is we're using our browser extension footprint to become not just passive in collecting data, but also active in generating requests into the application backend, reusing the trust that is already created by a user going to that environment.

What we're doing is we're using our browser extension footprint to become not just passive in collecting data, but also active in generating requests into the application backend, reusing the trust that is already created by a user going to that environment.

What we're doing is we're using our browser extension footprint to become not just passive in collecting data, but also active in generating requests into the application backend, reusing the trust that is already created by a user going to that environment.

And then it enables us to collect data about all the other identities that are being used in that application, the posture of that application, and whether there are any gaps there.

And then it enables us to collect data about all the other identities that are being used in that application, the posture of that application, and whether there are any gaps there.