{"id":6260,"date":"2024-11-15T08:36:02","date_gmt":"2024-11-15T14:36:02","guid":{"rendered":"https:\/\/www.darkreading.com\/application-security\/lessons-from-osc-r-on-protecting-the-software-supply-chain"},"modified":"2024-11-15T08:36:02","modified_gmt":"2024-11-15T14:36:02","slug":"lessons-from-oscr-on-protecting-the-software-supply-chain","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/11\/15\/lessons-from-oscr-on-protecting-the-software-supply-chain\/","title":{"rendered":"Lessons From OSC&R on Protecting the Software Supply Chain"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

COMMENTARY<\/span><\/span><\/p>\n

The complexity of today’s software development \u2014 a mix of open source and third-party components, as well as internally developed code \u2014 has resulted in an abundance of vulnerabilities for attackers to exploit throughout the software supply chain.<\/span><\/p>\n

We’ve seen the direct effects of software supply chain attacks in incidents like the MOVEit and SolarWinds breaches, revealing that no industry sector, size of company, or stage of software development is immune. According to a survey from Enterprise Strategy Group (ESG), 91% of organizations experienced at least one <\/span>software supply chain security incident in 2023<\/a><\/span>, and 2024 hasn’t seemed any better.<\/span><\/p>\n

Security teams are overwhelmed by the task of sorting through, assessing, and prioritizing the mitigation of tens of thousands of alerts to discern those that pose real risk from those that are benign. In 2023, a group of AppSec experts addressed this problem by launching the <\/span>Open Software Supply Chain Attack Reference (OSC&R)<\/a><\/span>, a freely available, MITRE ATT&CK-like framework to help organizations gain a deeper understanding of their software supply chain vulnerabilities.<\/span><\/p>\n

The OSC&R community’s inaugural <\/span>report<\/a><\/span>, “OSC&R in the Wild: A New Look at the Most Common Software Supply Chain Exposures,” offers a comprehensive analysis of the severity of vulnerabilities across the software supply kill chain. Based on a nine-month analysis of over 100 million alerts, tens of thousands of code repositories, and 140,000 real-world applications, it examines the risk to software supply chains and probes the alignment between the vulnerabilities found in the wild and the focus of AppSec teams today.<\/span><\/p>\n

The research offers some eye-opening statistics, including that 95% of organizations have at least one high, critical, or apocalyptic risk in their software supply chain, with the average organization having nine such issues. What’s more, the OSC&R data shows that many of the most common software supply chain vulnerabilities are tied to fundamental security controls, such as authentication, encryption, publicly available information in logs, and the principle of least privilege. Following are some of the most important takeaways from the report.<\/span><\/p>\n

1. Watch for Run-Time Exposure<\/h2>\n

One in five applications was found to contain high, critical, or apocalyptic runtime vulnerabilities during the execution phase of an attack. This makes them prime targets for attackers. Because the most significant software vulnerabilities tend to surface in later attack stages, it’s crucial to catch issues early in the software development life cycle.<\/span><\/p>\n

As such, AppSec and DevOps teams should aim to strengthen application runtime security. This can be accomplished by integrating continuous monitoring and <\/span>real-time protection mechanisms<\/a><\/span> that focus on the later stages of an attack, when the damage potential is greatest.<\/span><\/p>\n

2. It’s Worth Fixing Older Vulnerabilities<\/h2>\n

While newer vulnerabilities may grab headlines, older vulnerabilities remain the most common attack vectors when it comes to supply chain security. Techniques like command injection (15.4% of applications), sensitive data in log files (12.4% of applications), and cross-site scripting (11.4% of applications) \u2014 as well as slow-burn vulnerabilities like <\/span>CVE-2024-3094<\/a><\/span>, which targeted the compression utility <\/span>XZ Utils<\/a><\/span> in major Linux distributions \u2014 still wreak havoc in unpatched systems. Attackers continue to successfully use historical tactics and techniques, showing that “old school” vulnerabilities present significant and persistent risks.<\/span><\/p>\n

To counter these tactics and techniques and drive down the opportunity for attack, organizations should regularly review and update legacy systems and codebases to patch known vulnerabilities. Further, implementing a robust vulnerability management program that includes continuous scanning for both old and emerging threats will harden software to known risks.<\/span><\/p>\n

3. Vulnerabilities That Span Multiple Attack Stages Amplify Damage<\/h2>\n

In the OSC&R report data analysis, 36% of applications were found to be vulnerable to exploits in the initial access attack stage, with many overlapping across multiple stages of attack. Indeed, vulnerabilities in initial access stages often open the door for more severe threats, such as persistence and execution exploits.<\/span><\/p>\n

The data underscores the need for AppSec and DevOps team to bolster defenses across all stages of the attack life cycle, not just in initial phases. Organizations should adopt multilayered security solutions that can detect and neutralize threats at various stages of the kill chain to prevent attackers from <\/span>moving laterally within systems<\/a><\/span> and causing widespread cyber and business damage.<\/span><\/p>\n

Next Steps for AppSec Teams<\/h2>\n

One of the questions the inaugural OSC&R report sought to answer was whether what AppSec and DevOps teams focus on matched the vulnerabilities found in the wild. The data reveals that this is not yet the case. Progress is being made, but the high volume of vulnerabilities passing through the supply chain into live applications, and the large percentage of organizations that report supply chain security incidents, indicate that greater focus on proactive software security measures is needed.<\/span><\/p>\n

In addition, organizations need to do a better job of looking systemically at both their software development processes and the attack lifecycle to identify the places most likely to be at risk. But historical data alone is not the answer. Organizations must implement the tools and processes that give them holistic visibility of their supply chain \u2014 from the build stage all the way through runtime, and including the development and testing environments, which are occasionally overlooked.<\/span><\/p>\n

Further, it’s clear that focusing on one or two stages of software development or one stage of the attack lifecycle isn’t enough. Businesses must adopt a multilayered, full-lifecycle AppSec strategy \u2014 accompanied by tools that can unify all stages \u2014 to reduce the probability of attack.<\/span><\/p>\n

Development and security teams now have a reference they can use to map their programs to known attack vectors and tactics. OSC&R, in effect, sets the foundation for operating a streamlined software security program that reduces the number of vulnerabilities that reach production, enhancing the resiliency of the organization as a whole and easing the fears of breach due to software flaws.<\/span><\/p>\n

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

COMMENTARY The complexity of today’s software development \u2014 a mix<\/p>\n","protected":false},"author":12,"featured_media":6261,"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-6260","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\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=1800%2C1012&ssl=1",1800,1012,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=1536%2C864&ssl=1",1536,864,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=1800%2C1012&ssl=1",1800,1012,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=1024%2C576&ssl=1",1024,576,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?resize=825%2C575&ssl=1",825,575,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.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\/11\/lessons-from-oscr-on-protecting-the-software-supply-chain.jpg?fit=1800%2C1012&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/6260","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=6260"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/6260\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/6261"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=6260"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=6260"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=6260"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}