The majority of global organizations (54%) suffered a software supply chain attack over the past year, and most are unable to keep up with the growing risk landscape. This is according to “The State of Software Supply Chain Security Risk” report, released recently by Synopsys, Inc. and the Ponemon Institute, which also found that 50% of organizations took more than a month to respond to an attack. One in five say that their organization is not effective in its ability to detect and respond to these attacks.
The data also shows that AI is becoming ubiquitous across the software development life cycle. The majority of security professionals (52%) say their development teams leverage AI tools to generate code, specifically, OpenAI Codex (50%), ChatGPT (45%) and GitHub Copilot (43%). While the use of AI creates efficiencies by automating decision-making, findings indicate that concerningly few protections are put in place. Only a third (32%) of organizations have processes to evaluate AI-generated code for license, security, and quality risks.
Survey respondents also cited a worrisome lack of commitment from decision-makers when mitigating these issues. Only 39% say their organization’s leaders are highly committed to reducing the risk of malware in software supply chains. Even though 45% of security professionals say supply chain compromises such as SolarWinds have led to increased investment in software supply chain security, only 38% say resources dedicated to securing the supply chain are sufficient or very sufficient.
“Supply chain attacks are becoming more prevalent across organizations globally, yet this report highlights the sustained weaknesses in existing software development processes and security standards,” said Jason Schmitt, general manager, Synopsys Software Integrity Group. “Attackers are getting more sophisticated and thus finding more weaknesses that allow them to explore a supply chain where they can steal sensitive data, plant malware, and control systems. Particularly with the rise of AI-generated code, security teams need to maintain visibility into applications, and continuously evaluate IP, security threats, and code quality to reduce risk.”
Additional key findings include:
- Organizations forgoing SBOM implementation: Software Bills of Materials (SBOMs) are critical to ensuring a secure software supply chain but only 35% of security professionals say their organizations produce them. Furthermore, only 40% say they immediately stop the use of software if the supplier doesn’t provide a requested SBOM. The main reasons organizations generate SBOMs are general dependency and vulnerability management (50%), industry regulations (39%), customer requirements (38%), and government requirements (38%).
- Open source vulnerabilities remain a huge risk: Nearly two-thirds (65%) of respondents say they use open source software, although less than half of respondents (47%) say their organizations are very or highly effective in securing it in the supply chain.
