<img height="1" width="1" style="display:none" src="https://alb.reddit.com/snoo.gif?q=CAAHAAABAAoACQAAACi3UkU6AA==&amp;s=hMfJ_f7PVQOiL2csDznj0MZz_-_Sym2oeAYASWsHW4c=">

Rich Mills

Rich_Mills

Rich Mills

Coveros

Richard Mills has more than 25 years of experience in software engineering with a concentration on pragmatic software process and tools. Rich has a specific focus in Agile development methods and is passionate about DevOps, Continuous Integration, and Continuous Delivery. As the Solution Lead for DevOps at Coveros, Rich is dedicated to helping customers build software better, faster and more securely by coaching and mentoring in Agile development methodologies, automating software delivery (builds, tests, and deployment) and integrating strong security measures into development techniques. He has spent his career working in the areas of static and dynamic software analysis tools, configuration management, and continuous integration. Rich currently works as a Sr. DevOps Architect with Coveros and has been with the company since 2010, spending most of his time engaged with customers.

Session: DevSecOps - Pipeline Tooling for Continuous Security In Agile Projects

As we embrace DevOps to optimize our Agility, we start pushing working code toward production releases more frequently. Whether we are doing true "Continuous Deployment" straight to production or not, we no longer have time for slow, manual, late-lifecycle security assessments to determine if our code is going to put us on the front page of the newspaper (for the wrong reasons). What we need is a way to know that our code is secure enough to pass muster every day. What we need is continuous security.

The DevSecOps movement is about exactly that: shifting security assessment left and integrating it into the daily and sprint-ly cycles that DevOps has made popular. It means finding those touchpoints in our continuous integration/continuous delivery (CI/CD) pipeline where security tools can be inserted and run continuously against the software changes as they are made. It means using static code analysis, dynamic security testing, secure composition analysis of third party components, and platform vulnerability scanning to look at all aspects of security everyday. It means breaking builds and rejecting changes when developers introduce new security vulnerabilities.

In this talk, I present my successes and challenges with integrating security into DevOps pipelines to provide continuous assessment of security posture. I focus on my latest experiences building delivery pipelines for a containerized microservice-based project where we integrated an broad set of open source and commercial tools to gather and present security data. Specifically, I highlight:

* Touchpoints in your pipeline to asses security during build, deployment, and testing

* Tool categories needed with examples of open-source and commercial options

* Considerations to align tools with "security controls" for compliance

* Data gathering, reporting, and dashboarding to get an easy view of security status

* Team structures to encourage collaboration of security engineers with developers

This talk is perfect for people struggling with ways to integrate application security assessment into their Agile development process.