DevSecOps has become the ultimate marketing buzzword, and is often suggested as a silver bullet to solve all software security issues. But what happens when things go wrong? This talk will cover what to do if you run into any of the most common pitfalls: false positives, slow tooling, lack of other SDLC security activities, unfixed bugs and lack of training & knowledge.
Outline:
Set the stage: Define DevOps and DevSecOps, give a few examples, so that everyone is on the same page - 3 mins
State problem: DevSecOps is not a silver bullet and it is not the only security activity you should be doing (the entire SDLC deserves security attention, not just the testing/deployment phase. Even if its the most fun one).
5 common pitfalls, and how to solve them
1) Untuned tools - False Positives
- Why we need to tune our tools, I will cover SCA, Secret Scanning, DAST and SAST (vendor agnostic for all of them) and give tuning tips and advice to avoid false positives
2) Slow tools
- Explain the need for speed and that it is absolutely unacceptable to have security make the pipeline take more than twice as long, then how to speed things up as well as how to put your tools at different points in the SDLC (unit tests, scanning with local host, and upon repository checkin), so that you’ve already solved as many problems as you can before the CI/CD even starts
3) Security activities are ONLY in the pipeline
- List of all places in the SDLC there should be security, with a page-page summary (perfect for taking pictures of to summarize)
Requirements: Sec requirements for whatever you are building
4) Not fixing anything
Tips on how to build buy-in with management and devs to get them to fix what you find, how to prioritize, then negotiate. Ensuring your bugs are in front of the devs, by using the same bug tracker and automating the sending of the bugs
5) No training (for sec, dev and/or ops)
Explain problem of lack of training and knowledge in this area, and need for consulting, training and/or hiring to ensure your team makes excellent decisions, processes and software!
Conclusion: summarize, with a 1 page picture-slide
Free resources to help: #CyberMentoringMonday, WHP community, WHP podcast, awesome books on DevOps, then my personal blog