A new story from Cloud Security Podcast by Google
If stock originally was and talked about this a lot, it was more like centralized. People sitting in the room 24/7 in dark rooms with screens lining their eyes. It's not really the case so much. It's very distributed, very geographically spread. And also needs to include not just the local teams and the remote teams, but also service providers that can collaborate together with the security operation teams. That makes sense. And I think to me this is definitely showing the evolution of the technology over some number of years, which kind of reminds me of my analyst days, right? When I was writing, I think one of the first garden papers and sore, I did say quote that adoption some would face his headwinds because I've seen organizations that struggled with processes so they couldn't automate what they didn't have and they were other challenges. You've lived through all this built in creating developing market and selling this sort of tool. So what have we learned trying to get sore adopted in your history? And the history I think goes from 2015 to, well, today. So 7 years of trying to soar how did the workout? What did you learn? I see what you did there. Good question. I think, first of all, is the platforms themselves obviously evolved. And this is a new technology. I was always, as you go to enterprise, it goes through some process where you need to get used to it, have defined projects for it, assigned resources for it, just get more experience with the platform. But really as we kind of went through building the system itself and product, we didn't notice that it's more difficult. Of course, to deploy at the beginning and to get things operational. And we spent, I would say years in figuring out how to accelerate what we call time to value. Which basically materializes in many areas of the product, it's the ease of pulling the data in. It's the ease of using the integrations. It's the ease of building the playbooks and the workflows it's essentially getting the system integrated in starting to see value from it and starting to run different use cases. As fast as possible, where you don't necessarily need to rely on only engineers. And you can slowly read first at the beginning, source. And I think this is also why there was more headwinds. These were new systems. They, of course, designed first to help engineer the process. And then slowly added more and more capabilities to simplify, but the process of implementing this, because really the security operations, I think, through the journey that it's worked with Thor moved from being really clunky and every organization would invent their own will, processes were broken. There was no automation. So you didn't just have to implement a platform, you also have to implement a process for the operation. I think this was one of the things that was also making it more complicated. And as source systems evolved,.