Topics of Interest: Automatic Vulnerability Remediation: The Trusted and Secure Road ...
summary
Claims that automatic remediation generates safe, human‑looking code, preserves functionality, and measurably reduces unattended issues; demonstrates fixes for SQL injection and path traversal by inserting sanitizers or switching to prepared statements, integrates detection outputs (serif example) with CI/CD or IDE workflows, and can emit pull requests with automated pull request validation or IDE edits. Operational data highlights developer/APSec ratios of 50 to 100 to 1 and repair cycles that otherwise stretch to months.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:21Paving a Secure Road to Developer Happiness A Realistic Objective?
- 4:25Addressing Proprietary Code Security Issues General Challenges • Remediation of security issues can be an extremely taxing process
- 11:03The Promise of Auto Remediation 1 Better software security
- 14:17Auto Remediation: Trustworthiness
- 22:24Code for Remediation
- 25:39Auto Remediation: Suitability and Challenges Cases where auto remediation may fit best
- 28:13Auto Remediation: Concerto in A Major for Keyboard and Orchestration
related talks
01h 06mEscaping Vulnerability Hell: Bridging the Gap Between Developers and Security Teams
20mHow to Use Your Vulnerabilities to Train Your Developers on Security
33mAutomated security: face your vulnerabilities
45mEradicating Vulnerability Classes by Shelving SAST and Embracing Secure Defaults and Invariants
41mSkillful, Scalefull Fullstack Security in a State of Constant Flux
27mHow to implement Security as Code?
44mVulnerability Management that developers won't hate
32mResilient Secure Software Development Through Insights Learned from Adversarial Attack Campaigns