Virtual Session: DevSecOps - Whose Job Is It Anyway?

Sponsored by RSAC

On-Demand Viewing

Now more than ever, the notion that security is everyone’s responsibility is starting to resonate across the entire IT team. But responsibility does not equate with ownership, let alone budget. Any project where “everyone is responsible” but no one owns it, and different people pay for it, is doomed. This is the conundrum facing us in DevSecOps.  

For the most part it is still the security team choosing the security tool. But more than ever using DevSecOps tools falls to the Development, Ops and DevOps teams. Whose budget does it come from. In a bit of keystone cop’s comedy, usually everyone points the finger at the other guy to pay for it. This is not a recipe for success. How can we change the fundamentals to make DevSecOps have a higher chance of success? 

In this virtual session, we'll look at the ways to create a culture that promotes a shared role in security. Plus, learn how to evaluate DevSecOps tools that can help your organization release more secure software. 

1. What you can do to make sure you pick the right DevSecOps tools
2. How can you instill a culture of security is everyone’s responsibility
3. How to determine who “owns” the DevSecOps program
4. Ulitmately release more secure software.

Alan Shimel

Derek Weeks