DevSecOps and Legacy Applications
summary
Claims CI_CD is the practical first step to DevSecOps for legacy systems and that progress comes from sequencing: process mapping to find low hanging fruit, add source control and branching, then test automation, static and dynamic scans with automated ticketing, CI to build artifacts, CD to deploy, and monitoring. Recommends pilots, change management, and keeping institutional knowledge. Describes building DevSecOps accelerators that spin up and down environments and enforce security and compliance via infrastructure as code, which the uploader says shortens delivery and reduces manual downtime.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:32Definitions
- 6:06CICD Pipeline
- 9:02Legacy Applications
- 10:58Why Consider DevSecOps
- 14:36Legacy Application Challenges
- 18:04Implementing DevSecOps
- 20:45Sequencing DevSecOps
- 23:40Conclusion
related talks
30mDevSecOps: More Than Just Pipelines
31mWhy SecDevOps is the new way in Cybersecurity?
36mHow to Turn DevOps into DevSecOps
30mThe 3 Ways of DevSecOps – Making Shift Happen
06mDevSecOps – Security Throughout the DevOps Pipeline
23mDevSecOps - By Any Other Name
16mIntroduction to DevSecOps
36mUnderstanding the Sec in DevSecOps: Beyond Just Shifting Left