Why do Software Flaws Persist so Long After Being Discovered?

No ratings

Presented at InfoSecurityEurope 2019 by

Paul Farrington

It takes time to fix security flaws. But developers simply can’t wave a magic wand over the portfolio to fix the majority of flaws in an instant, or even a week, or a month. In addition, many other factors come into play – product release cycles, quality assessment, and business criticality of applications – that change the rate at which certain vulnerabilities are fixed. Paul Farrington, security architect at Veracode, will present data from the annual State of Software Security Report, with a focus on how European companies compare to U.S.-based companies in fixing flaws.Learning Outcomes:Understand the most prevalent software vulnerabilities and flawsLearn what flaw persistence is and why it becomes a factor in overall application securityTake stock of how application security fits into risk managementGain knowledge and insight into DevSecOps practices and how they can reduce riskLearn how to bring security and development teams together with less friction