Dev vs Sec – Who's Responsible For The Ops?

September 15, 2022
Dev vs Sec – Who's Responsible For The Ops?
Description

The State of AppSecOps Report found "reducing developer friction" was a top 3 priority for security leaders. A common contributor is the volleying of security responsibilities, especially with infrastructure-as-code—a gray area that often has security and dev teams pointing fingers. To get willing collaboration, security teams need to practice carrot tactics and better understand the expectations and environments their developers are facing.

Resources

About the Guest

Mark Lambert
Mark Lambert
VP of Products, Armorcode
Linkedin Logo
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor
Read more
Mark Lambert
Mark Lambert
VP of Products, Armorcode
Linkedin Logo
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor
Read more

Watch the episode here

Available on:

Episode 2

Dev vs Sec – Who's Responsible For The Ops?

The State of AppSecOps Report found "reducing developer friction" was a top 3 priority for security leaders. A common contributor is the volleying of security responsibilities, especially with infrastructure-as-code—a gray area that often has security and dev teams pointing fingers. To get willing collaboration, security teams need to practice carrot tactics and better understand the expectations and environments their developers are facing.

Resources

Subscribe for updates

Please enter a business email
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.