DevSecOps is the practice of building security checks into every step of making and shipping software, rather than bolting a security review on at the end. Done well, it means you ship just as often, with far fewer nasty surprises on release day.
What DevSecOps means
DevOps brought development and operations together, so the people who write code and the people who run it share one pipeline and one goal: ship small changes often and safely. DevSecOps adds security to that partnership. Developers, security specialists and operations engineers all own security, and the checks they rely on run automatically, wherever the work happens.
The key word is 'every'. Security isn't a gate at the end of the process that a separate team guards. It is a set of small, automated checks spread across writing code, committing it, building it and deploying it. Each one is quick and focused, and each one catches a different kind of mistake.
Why security can't be the last step
In a traditional setup, code is written, tested and packaged, and only then handed to a security team for a review or a penetration test. That model has three problems.
- Late findings are expensive. A leaked password found weeks after it was committed has to be rotated, every copy of the repository is suspect, and the fix competes with a release deadline.
- Reviews become bottlenecks. When one team must sign off on everything, releases queue up behind it, and people start looking for ways around the review.
- Context is lost. By the time a finding arrives, the developer has moved on. Fixing a problem in code you wrote an hour ago is far easier than in code you wrote last month.
Moving checks earlier is often called shifting left, because if you draw the delivery process as a line from 'write code' on the left to 'running in production' on the right, the checks move towards the left-hand end.
Where the checks run
A DevSecOps pipeline layers several kinds of check, each at the point where it is cheapest to run.
Wondering how this was made? How we make these