{"id":6556,"date":"2024-12-10T09:00:01","date_gmt":"2024-12-10T15:00:01","guid":{"rendered":"https:\/\/www.darkreading.com\/vulnerabilities-threats\/lessons-largest-software-supply-chain-incidents"},"modified":"2024-12-10T09:00:01","modified_gmt":"2024-12-10T15:00:01","slug":"lessons-from-the-largest-software-supply-chain-incidents","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/12\/10\/lessons-from-the-largest-software-supply-chain-incidents\/","title":{"rendered":"Lessons From the Largest Software Supply Chain Incidents"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

In 2011, <\/span>Marc Andreessen coined a phrase<\/a><\/span> we’re now all familiar with: “Software is eating the world.” More than 13 years later, the expression still rings true. The world runs on software, and each day it continues to transform industries and fuel the global economy. Companies are generating more software \u2014 faster than ever before \u2014 in order to keep up in today’s dynamic and ultracompetitive business landscape.<\/span><\/p>\n

Innovation is a beautiful thing, but the increased volume and velocity with which software is being built and delivered creates more opportunities for something to go wrong in the software supply chain. Over the past decade, we’ve seen this happen time and time again.<\/span><\/p>\n

Around this time last year, <\/span>Okta disclosed<\/a><\/span> that it had experienced a significant security breach, where bad actors gained access to private customer data through its support management system, highlighting the dangers of third-party risk. In 2020, the <\/span>SolarWinds platform update mechanism was compromised<\/a><\/span> and used to send malicious software that impacted more than 18,000 of its customers. And back in 2017, <\/span>Equifax suffered a massive breach<\/a><\/span> due to a failure to patch a known security flaw in its software.<\/span><\/p>\n

This is just a small sampling of the types of software supply chain attacks that have plagued organizations over the past decade. Unfortunately, these attacks show no signs of slowing down \u2014 quite the opposite, actually.<\/span><\/p>\n

Research indicates<\/a><\/span> software supply chain attacks are occurring at a rate of one successful attack every two days, and <\/span>Gartner predicts<\/a><\/span> that by 2025, 45% of organizations will have experienced a software supply chain attack. Alarmingly, <\/span>one report<\/a><\/span> found that there has been a staggering 742% increase in these attacks over the past three years.<\/span><\/p>\n

The uptick in software supply chain attacks can be attributed to a combination of several factors. Often, organizations simply don’t realize the breadth of their exposure. As software shops move toward more sophisticated software delivery and consumption models (e.g., continuous integration\/continuous delivery [CI\/CD] and cloud), their supply chains become more vulnerable. Additionally, typical attack vectors have become increasingly difficult to exploit (thanks to vendors incorporating more sophisticated security measures into platforms and software), which has forced bad actors to uncover new vulnerabilities and become more creative in their attacks. More recently, the spike in adoption of generative AI (GenAI) tools like coding assistants has created new and difficult-to-monitor security gaps. At the same time, attackers are leveraging GenAI themselves to carry out more sophisticated attacks at a higher volume.<\/span><\/p>\n

Enterprises must urgently find a balance between creating and releasing high-quality software quickly, while upholding a high level of security at each link in the software supply chain.<\/span><\/p>\n

Here’s how they can maintain security without impeding innovation:<\/span><\/p>\n

Thoroughly Vet Vendors on an Ongoing Basis (and Treat GenAI Tools With the Same Level of Scrutiny)<\/h2>\n

If anything can be learned from Okta’s breach, it’s that third-party vendors must be carefully vetted if they’re to be trusted with private customer data and other sensitive information. Too often, development shops assume that the third-party code they consume is a black box.<\/span><\/p>\n

Organizations need to look at each vendor’s software bill of materials (SBOMs) so they’re aware of any open source or third-party components of their code and can therefore identify possible vulnerabilities. They should also assess the vendor’s track record for security and review its policies, procedures, and certifications.<\/span><\/p>\n

Vetting vendors shouldn’t be a box the organization checks at the beginning of their engagement and then forgets about. The vetting process must be<\/span> <\/span><\/span>ongoing: Organizations should continually be asking questions and keeping a pulse on the vendor’s new offerings, policies, compliance certifications, and more.<\/span><\/p>\n

Of note, GenAI tools should be subjected to the same level of scrutiny as third-party vendors. Organizations need visibility into how the large language model (LLM) works, what data it was trained on, whether the model is open or closed, and how user inputs and generated content are collected and used. They’ll also need to assess the accuracy and quality of the code the LLM generates, as well as have a plan in place to mitigate any inaccurate or buggy code it produces.<\/span><\/p>\n

Consume Open Source Projects Carefully<\/h2>\n

Open source projects are critical for rapid development and innovation, but organizations need to be very careful about how they consume open source code. Last year alone, researchers found <\/span>245,032 malicious packages<\/a><\/span> in open source projects available for public download. Open source repositories are a prime target for bad actors, who can wreak havoc by attacking a single package that, in turn, impacts an entire ecosystem of companies and their customers.<\/span><\/p>\n

Organizations should use code only from open source projects that adhere to strict compliance frameworks, such as the <\/span>OpenSSF Scorecard<\/a><\/span>, <\/span>System Package Data Exchange<\/a><\/span> (SPDX), and <\/span>OpenVEX<\/a><\/span>. This ensures they have visibility into the security hygiene of the project before they borrow its code. Additionally, organizations should adopt a software composition analysis (SCA) solution and have a plan in place to address any open source vulnerabilities, should they emerge.<\/span><\/p>\n

Evaluate the Security of Your Entire Software Delivery Process<\/h2>\n

There’s no silver bullet for securing the software supply chain. Organizations must diligently evaluate the security of <\/span>each step <\/span><\/span>of the software delivery process \u2014 including design, development, testing, deployment, maintenance, and beyond.<\/span><\/p>\n

By infusing security measures throughout the CI\/CD pipeline, companies can identify and remediate vulnerabilities early in the development process so they don’t lead to a full-blown breach down the line. They can accomplish this through automated security solutions that flag potential issues and source composition analysis (SCA) tools that scan code for known vulnerabilities, and by implementing source code access controls to prevent unauthorized access.<\/span><\/p>\n

The security cat-and-mouse game is never over. As the industry works diligently to expand its knowledge and strengthen security, attackers are just as hard at work planning and carrying out nefarious activities. The software supply chain is a growing target, and organizations need to take special care to safeguard it. By carefully vetting vendors, mindfully consuming open source, and securing the entire software delivery process, organizations can strike a balance between driving innovation and maintaining software supply chain security.<\/span><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

In 2011, Marc Andreessen coined a phrase we’re now all<\/p>\n","protected":false},"author":12,"featured_media":6557,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-6556","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=1800%2C1013&ssl=1",1800,1013,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=1800%2C1013&ssl=1",1800,1013,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/12\/lessons-from-the-largest-software-supply-chain-incidents.jpg?fit=1800%2C1013&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/6556","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=6556"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/6556\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/6557"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=6556"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=6556"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=6556"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}