Why do Software Flaws Persist so Long After Being Discovered?

  • Date 05 Jun 2019

Why do Software Flaws Persist so Long After Being Discovered?

05 Jun 2019, 12:00 - 12:25

Strategy Talks

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:

  1. Understand the most prevalent software vulnerabilities and flaws
  2. Learn what flaw persistence is and why it becomes a factor in overall application security
  3. Take stock of how application security fits into risk management
  4. Gain knowledge and insight into DevSecOps practices and how they can reduce risk
  5. Learn how to bring security and development teams together with less friction



  • Paul Farrington




    Paul Farrington is a Security Architect at Veracode, an industry leader in application security solutions. He advises CTOs, CISOs, technical project...

Business Issues covered

  1. What will this session help you to do?
    • Demonstrate thought-leadership to ensure security is high for corporate agenda & capex justified‎
    • Select best fit products and solutions from the wide selection of vendors and products available‎


We use cookies to operate this website and to improve its usability. Full details of what cookies are, why we use them and how you can manage them can be found by reading our Privacy & Cookies page. Please note that by using this site you are consenting to the use of cookies.