Turbocharge your development with agile security
summary
mx51 shifts vulnerability checks left into CI/CD using Terraform-declared environments, EKS, Amazon Inspector and Sysdig Secure local scanning, enforces a policy that blocks critical/high CVSS ≥7 if a fix exists, and reduces production surprises by reporting images-only reporting prioritized by exploit, reachability and age. The result: ~5% of builds fail early, patch timeliness and SOC2-aligned remediation improve, engineering velocity and culture remain unchanged while high-risk vulnerabilities are blocked — a concrete guardrails beat gates outcome.
AI-written summary · about
chapters (7)
- 0:00Introduction to agile security
- 1:39Vulnerability management at mx51
- 9:14Guardrails beat gates approach
- 13:49Pragmatism wins engagement
- 16:42Empathy generates efficiency
- 20:41Outcomes and next steps
- 22:06Q&A and closing
related talks
22mSecurity vs Dev Experience Threat … or Opportunity
07mCI/CD Evolution: Ensuring Security and Overview During Rapid Growth
42mContinuous Security: Integrate security tools into your DevOps Pipeline
19mApplication Security at High Velocity
39mSecurity Tooling in Your DevOps Pipeline
37mPlatform and Security Engineering
40mDevSecOps Guide to Bulletproof Your Development Workflow
36mThe Road To Being Rugged