5 Simple Strategies for Building Security Into Your DevOps Process

Source – veracode.com

Securing any development framework – whether Waterfall, Agile or DevOps – requires changes of culture, process, and technology. But unlike the straightforward flow of Waterfall, where security comes at the end of the process, it’s less clear where security fits in Agile and DevOps.

As Securosis analyst Adrian Lane points out, Agile development includes “whatever work gets done in a sprint and does not bend to security, so you need to bend security to fit Agile.” Likewise, moving from DevOps to DevSecOps requires processes that incorporate security throughout the development lifecycle. In this blog post, we present some strategies for integrating security within your DevOps process, offered by Veracode expert Colin Domoney.

1. Establish strong feedback loops

DevOps guru Gene Kim’s “Three Ways” of DevOps encourage team autonomy, with high levels of communication, responsibility, accountability, and continuous learning. Processes must incorporate strong feedback loops between development and security teams.

2. Perform regular code reviews

Code reviews boost developer learning and accountability, promote transparency, and reduce the risk of deploying bad code to production. Security champions within your development teams can lead these efforts.

3. Experiment with security exercises

Security exercises like capture the flag and red team/blue team competitions are fun ways to expose vulnerabilities and build a culture of security awareness. Friendly competitions can be motivating and encourage knowledge-sharing within and between teams.

4. Measure and benchmark performance

Shorter feedback loops don’t happen on their own – you need telemetry and metrics. Measuring security along with traditional metrics like performance helps developers continuously improve secure coding skills.

5. Implement procedures for dealing with problems

For example, developers should know how to roll back to a previous version if a serious problem occurs. Canary releases for a limited set of customers can identify problems early. Also consider policies for developers to escalate issues to the security team.

Leave a Reply