How to Harness Dev and Their Native Tools to Accelerate DevSecOps
summary
Shows where application security fits into developers’ existing workflows and native tools by mapping security controls onto the development pipeline. Includes a concrete case study and a short demo of a developer pipeline using automated DevOps processes to make appsec iterative, automated, and embedded.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:10Problem: Even Basic Application Security Testing is Hard
- 4:48THENEWSTACK
- 7:41New Attack Surfaces of Cloud Native
- 8:51Is Security a Square Peg in a Round Hole of DevOps?
- 12:10Integration Complexity of Toolchains Slows Down Teams
- 13:07DevOps Complexity Inhibits Auditability... and Introduces More Security Risk
- 14:13The advantage of a Single Application for DevOps
- 15:19Focus on leaders in Continuous Integration (CI)
- 16:06Continuous Application Security = a United Workflow
- 19:30Seamlessly Test for Vulnerabilities within the Developer Workflow
- 24:09Automate, allowing security to focus on exceptions
- 36:33New Attack Surfaces Will Require New Approaches
- 40:22Apply What You Have Learned Today
related talks
13mEffective Application Security Testing for DevOps
42mA practical approach to DevSecOps
50mSeamless Integration of Security Practices into the DevOps Pipeline
49mDevSecOps but Secure! Developing More Securely, Continuously
01h 02mDevSecOps for Developers: How To Start
23mTrue DevSecOps with People, Processes, and Technologies
31mWhy SecDevOps is the new way in Cybersecurity?
16mIntroduction to DevSecOps