In this post
What does “shift left” mean?
It means finding security problems earlier in the life of a change, when they are cheaper to fix. A flaw caught in a pull request takes minutes to correct, while the same flaw found after release can take days and may already have been exploited.
Which checks belong in the pipeline?
Common ones are secret scanning, dependency and licence scanning, static analysis of code, scanning of container images and infrastructure definitions, and tests that exercise the running application. Each should give fast, clear feedback to the developer who made the change.
How do you avoid slowing teams down?
Run quick checks on every change and slower ones less often, tune rules to reduce false alarms, and make failures easy to understand. If developers learn to ignore the tool because it is noisy, it protects nothing.
What does shared responsibility look like?
Developers own the security of what they build and fix findings in their own code. Security staff provide guidance, tooling and threat modelling, and set policy. Operations teams manage access, patching and monitoring.
How do you measure progress?
Track how long findings stay open, how many reach production, and how quickly you can ship a fix. These show whether security is keeping pace with delivery, whereas counting alerts or scans only measures activity.
Sources and further reading
- OWASP. DevSecOps Guideline. owasp.org/www-project-devsecops-guideline/.
- NIST. SP 800-218, Secure Software Development Framework. csrc.nist.gov.
IICTP is an independent technical credentialing body.