#221: As an application developer, how often do you receive spreadsheets of findings from your security team? Do you drop everything you’re doing and work your way through the 57,239 findings during your existing sprint? Our guess is probably not. Even if you did, how would you know where to start? Just because a finding is marked as critical does not mean that it’s exploitable.

In this episode, we speak with Ravid Circus, CPO at Seemplicity, about how you should be handling and remediating these security problems. Hint: it’s not by using spreadsheets, but rather it needs to be in your day to day work.

Ravid’s contact information:

LinkedIn: https://www.linkedin.com/in/ravid-circus-302a8/

YouTube channel:

https://youtube.com/devopsparadox/

Books and Courses:

Catalog, Patterns, And Blueprints

https://www.devopstoolkitseries.com/posts/catalog/

Review the podcast on Apple Podcasts:

https://www.devopsparadox.com/review-podcast/

Slack:

https://www.devopsparadox.com/slack/

Connect with us at:

https://www.devopsparadox.com/contact/

DOP 221: Treat Security Like a Bug With Seemplicity 40:37 Share

DevOps Paradox

Shownotes Transcript

DOP 221: Treat Security Like a Bug With Seemplicity