DevOps culture makes things happen faster. Faster delivery, faster testing, faster release. On one hand, it adds control over what is going on in the infrastructure. You can recover faster. You can redeploy your compromised app components. You can roll back to the previous build. On the other hand, fast changes mean fast decisions. Some security vulnerabilities can pass through automatic testing. Some DevOps tools may be compromised also. We experienced a security issue when malware infected Jenkins server of one of our clients and deployed cryptocurrency mining software on all available hosts.
Why should organizations integrate security into DevOps?
Flexibility comes at a price of constant changes. To control what is constantly changing we need to incorporate security as a process. The only way to make fast-paced software development secure is to integrate security into the whole delivery lifecycle. Architecture, infrastructure, development, build and deployment, testing, releasing, feedback gathering, support, and patching processes should include security as one of the main considerations.
What steps need to be taken to do this?
Security experts are rare on the market. But you can start with defining people known as the Security Champions in every Scrum team. Those people will take responsibility for security during the development process.
Second, you should insert the Threat Modeling process into your backlog refinement. This will help to model threats to the next release features and create tests for them.
Based on the Threat Modeling you should create automatic test security gates and put them into the delivery pipeline.
Also, Security Champions should include security questions into the code review procedure.
Add continuous monitoring and continuous remediation processes to continuous integration, testing, and deployment.
< ..
Support the originator by clicking the read the rest link below.
