Chris Romeo — DevSecOps Fails

Robert and I decided to talk about an article I wrote called "DevOps security culture: 12 fails your team can learn from". We hope you enjoy this walkthrough of the 12 fails. If we missed any, hit us up on Twitter and let us know what we should add to the list. At Security Journey, we believe security is every developer's job. We work with our customers to help them build long-term sustainable security culture amongst all their developers. Our approach is to provide security education that's conversational, Quick, hands-on, and fun. We don't do lectures. Instead, we let the experts talk about what's important.

The Application Security Podcast is brought to you by Security Journey.

About Security Journey
Hey folks, for this episode, Robert and I decided to talk about an article I wrote called DevOps Security Culture: 12 Fails Your Team Can Learn From.
→ Learn more about Security Journey

Connect with Chris Romeo:
→ Chris Romeo on LinkedIn
→ OWASP Dependency-Check

Mentioned in this episode:
→ OWASP Dependency-Check
→ Threat Modeling Manifesto
→ Julien Vehent
→ TechBeacon
→ Matthew Coles
→ Jim Routh on Twitter

Follow the Application Security Podcast:
➜ Home
➜ X
➜ LinkedIn
➜ YouTube
➜ Instagram
➜ Facebook

Chapters:
00:00 Meet Chris Romeo: Chris Romeo — DevSecOps Fails
02:15 Yeah, I got the opportunity to write this article for TechBeacon
05:30 That's okay. Yeah, I mean, that's in the article I talk
07:33 The other frustration I have with the infinity graph is I
09:55 I've come to the conclusion now that if you want to
13:02 Yeah. As I look across the industry, and I've used a
14:44 I mean, we've got shift left, we've got shift right. I
17:48 Overcomplicating anything sets you up for failure, right
20:12 Number 9, noisy security tools. How are they noisy
23:09 It's a fail if you don't do it. Can you believe
25:08 That's pretty— I mean, recently, that's, that's very relevant, right