A manufacturer asks how shifting security left in the development process saves money and boosts productivity. Speaker B doesn't answer in this clip, but Speaker A makes clear that catching security problems early is foundational, not optional.
How can this approach about shifting left improve cybersecurity? Just to talk about that. And more importantly, really save manufacturers money that they can then invest in other projects and other priorities that they've got. Because it's kind of like a lot of this is foundational and necessary.
Yeah.
So do you have any examples you can share about that as well?
Yeah, absolutely. I'm tempted to answer the second part of the question first because I'll stop right there. Yeah, exactly. No, I think when you talk about security, it's the same as anything else, right? We have to think about, well, what's the budget? Who's going to actually implement this? What resources, time, and money are we going to actually apply to this initiative? And, you know, the question then is, well, how important is this to the organization? And so the way we think about security and how shifting left can really drive a lot of productivity gains and why it's a value-add is that, That it's not just security that you're getting from adopting these principles. It's also being able to understand change management, have backups of your system, have a system of record. And so the overall goal is, well, can I actually reduce downtime by applying a lot of these DevOps-like principles into my environment? We think the answer is yes. I think we've seen the impact of our software on end customers already. I think a small anecdote is a defense manufacturer we're working with where a controls engineer previously was making changes. They would deploy the changes to some system. They would then see when they come— when it comes time to do their annual audit, well, okay, I, I've got this change. This is not secure. We have to go back. We have to change, you know, revert this change effectively. And that's ultimately going to lead to downtime. When you think about what it would look like to shift left and how our software actually helped this end customer was they were able to understand what the security impact of their changes were going to be. while they were developing them. And that's a complete mindset shift to say, well, now I'm not going to have to revert changes. Now I'm going to understand the impact on risk and safety of the changes before I actually make them and deploy them into my environment. And so really, you can think and tie it back to, well, how much time did they save by not having to revert that at the next quarterly or annual audit?
