Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

We are excited to announce the launch of Veracode Threat Research, a new initiative to counter software supply chain threats. Thanks to the acquisition of Phylum, Inc., we are now equipped with cutting-edge technology and a wealth of expertise to revolutionize how we secure the open-source ecosystem and protect your developers from novel attacks.

How much innovation could you reinvest in with 80% developer productivity recapture? My guess is: a lot. As a VP of Product at a security company, I’ve seen firsthand how making it easier for developers to manage security findings can help them focus on delivering value faster. Let me share with you about the developer security experience that can transform development workflows for increased productivity.

Security posture management has become exponentially more complex for organizations developing and managing a vast ecosystem of applications. Evolving architectures like microservices, hybrid cloud infrastructures, and frequent release cycles introduce constant change and challenges. Amid these growing challenges are the existing security gaps organizations are struggling to address.

Security teams are overwhelmed. Whether it’s alert overload, a growing backlog of vulnerabilities, or fragmented security data, there’s no finish line in sight. The State of Software Security 2025 report reveals that security debt is rising and flaws times are increasing. Meanwhile, the traditional tools many teams leverage fail to provide the context needed to track risks across the application lifecycle and, importantly, to prioritize them.

The State of Software Security (SoSS) 2025: A New View of Maturity, our 15th year publishing the report, highlights a critical shift in how organizations approach security maturity. This transition focuses on major risks and uses continuous feedback loops to identify and mitigate them. Key metrics such as flaw prevalence, fix capacity, fix speed, debt prevalence, and open-source debt are essential for benchmarking and improving security maturity.

Software supply chain security risks are mounting. As noted in Veracode’s State of Software Security (SoSS) report, organizations of all sizes are drowning in security debt, and a large portion of the critical debt can be attributed to third-party vulnerabilities.

AI coding assistants like GitHub Copilot are transforming the way developers write software, boosting productivity, and accelerating development cycles. However, while these tools generate code more efficiently, they also introduce new risks more efficiently—potentially embedding security vulnerabilities that could lead to severe breaches down the line. What is your plan for reducing risk from the vast amount of insecure code coming through agentic AI in software development?

The Digital Operational Resilience Act (DORA) is a landmark regulation designed to enhance the digital resilience of financial institutions in the EU. Effective from January 17, 2025, DORA mandates the development and maintenance of a robust ICT risk management framework. Here’s an overview of the five pillars and how the right software security measures can help you comply.

The Latin “vera” indicates truth or reality. When Veracode was founded, this was the essence of our focus – finding truth in code. And specifically, binaries; hence the original brand rooted with the “01”. Seventeen years later, we remain committed to our vision – a World where software is developed secure from the start – but to do so today, we are expanding our view, solidifying our point of view, and modernizing how you see us.

The rise of emerging open-source threats presents a growing risk to organizations as attackers increasingly exploit vulnerabilities in widely used libraries, frameworks, and tools. In fact, most Software Composition Analysis (SCA) tools on the market today are unable to keep up with the volume of new overtly malicious activities in the open-source ecosystem.