Avsnitt
-
Security debt – which is defined as aging and accumulating flaws in software -- is a lot like credit card debt. You can throw money at the balance, but if you don’t stop spending, you’re never going to actually get out of debt.
In this episode of A Hard Look at Software Security, Chris Wysopal, Chief Technology Officer with Veracode, will join us to continue our conversation on software scanning with focus on the accumulating security debt in applications caused by persistent flaws in long-term time frames.
Listeners will learn more about:
Why there is less security debt in organizations that scan their code more than 300 times per year
How to know if security debt is meaningful
Best practices for incorporating scanning into the process
Produced by IDG Communications, Inc., in association with Veracode. -
The latest Veracode State of Software Security report reveals that scanning early, often, and steadily helps you fix more flaws faster while not contributing to security debt. The report finds 56 percent of software flaws eventually get fixed. While 76 percent of high severity flaws are addressed by developers, half of the applications showed a net reduction in flaws over the sample time frame.
In this episode of a Hard Look at Software Security, Paul Farrington, chief technology officer for the Europe, Middle East, and Asia regions for Veracode, will dive deeper into those numbers and discuss when development teams should consider scanning and why.
Listeners will learn more about:
The stage at which development teams should engage in software scanning
DevSecOps culture and how to enable it
Where DevSecOps is heading in the future
Produced by IDG Communications, Inc., in association with Veracode. -
Saknas det avsnitt?
-
AppSec awareness has grown in a decade. In Veracode’s State of Software Security report, Volume one, most of the conversation was around trying to explain and advocate for application security. Today, far less of that is necessary and more emphasis is put on talking about how to build an effective, mature application security program.
In this episode of a Hard Look at Software Security, Chris Wysopal, Chief Technology Officer with Veracode, will discuss positive AppSec signs – and what they mean for security best practices.
Listeners will learn more about:
Factors influencing the change in application security programs
What the State of Software Security report uncovers when it comes to current AppSec efforts
Why awareness about AppSec risk has grown, but actual risk reduction still has room for improvement
Produced by IDG Communications, Inc., in association with Veracode. -
The average number of days to fix software flaws was at 59 days in the first Veracode State of Software report from ten years ago. Today, it’s jumped to 171 days in the latest 2019 report.
While typical median fix times haven't gotten worse in 10 years – they have remained about the same - security debt is getting much deeper.
In this episode of a Hard Look at Software Security, Chris Eng, Vice President of Research with Veracode, will discuss relevance of the findings on median time to remediate flaws - and where organizations may stand when it comes to their own security debt.
Listeners will learn about:
Why security debt is getting much deeper
If fixes are based on flaw severity or exploitablilty
Why the source of an application affects fix speed of remediation
Produced by IDG Communications, Inc., in association with Veracode. -
According to the latest State of Security Software report from Veracode, the retail industry has the lowest average number of unaddressed security flaws. Government and education have the largest “iceberg“ of security debt lurking below the surface. Financial services firms have the best fix rate among all industries.
In this episode of a Hard Look at Software Security, Tim Jarrett, Senior Director of Product Management with Veracode, will discuss security debt across industries, and what is influencing their flaw fix rates.
Listeners will learn more about:
The differences in software security across sectors
Why the government and education sectors have a so-called iceberg of security debt
The details on why finance has the best fix rate
Produced by IDG Communications, Inc., in association with Veracode. -
Security debt - defined as aging and accumulating flaws in software - is emerging as a significant pain point for organizations across industries.
In this first episode of our second season of a Hard Look at Software Security, Tim Jarrett, Senior Director of Product Management with Veracode, will discuss what factors are behind security debt and how security managers can arm themselves with this knowledge to tackle the problem.
Listeners will learn about:
How cross-site scripting is contributing to security debt and why it’s noteworthy
Findings on how organizations are prioritizing fixes
Why security debt is not being discussed enough among security professionals
Produced by IDG Communications, Inc., in association with Veracode. -
A security champion serves as the voice of the developer while satisfying the needs of the business from a security perspective. In this episode we dig deeper into details on the role of the security champion and what effect having a champion can have on development and security. Listeners will learn about: • How to identify a security champion in your organization • What benefits can be expected from having a security champion • Suggestions for getting started with a security champion program
-
In this episode we discuss the latest findings on flaw fix rates in enterprises. Chris Eng, Vice President of Research, Veracode, offers perspective on what figures in the State of Software Security report reveal about the troubling amount of time it takes to address the majority of vulnerabilities. Listeners will learn about: • Average enterprise fix rates at one week and one month • Why enterprises still struggle with vulnerable open source components in software • What business can can do to mitigate risks associated with open source flaws
-
In this episode, we’ll discuss why enterprises still struggle with the occurrence of vulnerable open source components within their software - and what they can do to mitigate these risks. Listeners will learn more about: • The landscape of open source software today compared to internally developed code in enterprises • Why risk from open source components is an issue in most enterprises • The factors behind the friction between the process of DevOps and security
-
In this episode, we learn about changes in application security and the partnership between development and security. Chris Wysopal, Chief Technology Officer and Co-Founder of Veracode, joins us to discuss the synergy between these teams – and what best practices help create a solid devsecops program. Listeners will learn more about: • The factors behind the evolving relationship between development and security • What this change means for secure coding in the future • Action items for creating a security-first culture in the enterprise
-
In this episode, we will look at the emergence of DevSecOps in the enterprise. Tim Jarrett, Senior Director of Product Marketing with Veracode, joins us to explain the goal of building security into the software development process at the outset. Listeners will learn more about: • What research says about the effectiveness of DevSecOps • The core principles of DevSecOps • What is holding DevSecOps back from going mainstream? • Predictions on where this practice is heading in the future
-
In the first episode of the series, we are joined by Chris Eng, Vice President of Research at Veracode. We’ll detail highlights of the Veracode State of Software Security Volume 9 report and discuss what the findings reveal in terms of the progress companies are making with fixing flaws. How are factors like flaw severity, business criticality of applications, and exploitability of the flaws impacting how companies view vulnerabilities? We’ll also examine information about industry performance, differences by region, third-party component risks, and vulnerability trends to give security and development teams a holistic view of the state of software security.
