The Four Horsemen of DevSecOps
summary
OCBC Bank’s DevSecOps recipe centers on four concrete defenses: Security Architecture Design review, SAST/DAST/IAST and Nexus Firewall plus Coverity/Black Duck/Veracode/Fortify scans, container image and runtime scanning with VPC, encryption tokens and MFA, and continuous compliance with automated auditing and auto‑healing. Examples include using VDI to prevent data exfiltration, scanning third‑party binaries before repository ingestion, quarantining vulnerable containers with blue‑green rollouts, and measuring SLAs for near‑real‑time detection — covering roughly 75–80% of typical DevSecOps risk.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:47Major Security Challenges in DevOps Journey
- 6:13Secure Design Review
- 13:37Secure Code and Binary Review
- 18:45Container and Cloud Security
- 25:29Continuous Compliance
related talks
30mDevSecOps: More Than Just Pipelines
44mThe Implementation and Practice of DevSecOps
32mHow to fit Sec into DevOps without Security team
30mThe 3 Ways of DevSecOps – Making Shift Happen
30mSecuring DevOps using OWASP DevSecOps Tools
42mThe Challenge and Solutions to Implement DevSecOps into Large Banks
45mDevSecOps : add Security to your DevOps!
31mDevSecOps, or How to Integrate Security into DevOps Practices