没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
2024 Open Source Security
and Risk Analysis Report
Your guide to securing your
open source supply chain
| Open Source Security and Risk Analysis Report 2024 | 2
Table of Contents
3 | Executive Summary
3 | About the 2024 OSSRA
4 | Overview
6 | Open Source Vulnerabilities and Security
7 | Taking Action to Prevent Vulnerabilities from Entering Your Software Supply Chain
8 | Eight of the Top 10 Vulnerabilities Can Be Traced Back to One CWE
9 | Why Some BDSAs Don’t Have CVEs
10 | Vulnerabilities by Industry
11 | Open Source Licensing
12 | Understanding License Risk
14 | Protecting Against Security and IP Compliance Risk Introduced by AI Coding Tools
15 | Operational Factors Affecting Open Source Risk
15 | Open Source Consumers Need to Improve Maintenance Practices
16 | Findings and Recommendations
17 | Creating a Secure Software Development Framework
17 | Knowing What’s in Your Code
18 | Terminology
18 | Contributors
| Open Source Security and Risk Analysis Report 2024 | 3
This report offers recommendations to help creators and consumers of open source software manage it responsibly, especially
in the context of securing the software supply chain. Whether a consumer or provider of software, you are part of the software
supply chain, and need to safeguard the applications you use from upstream as well as downstream risk. In the following pages,
we examine
• Persistent open source security concerns
• Why developers need to improve at keeping open source components up-to-date
• The need for a Software Bill of Materials (SBOM) for software supply chain management
• How to protect against the security and IP compliance risk introduced by AI coding tools
For nearly a decade, the major theme of the “Open Source Security and Risk Analysis” (OSSRA) report has been Do you know
what’s in your code? In 2024, it’s a question more important than ever before. With the prevalence of open source and the rise in
AI-generated code, more and more applications are now built with third-party code.
Without a complete view of what’s in your code, neither you, your vendors, nor your end users can be condent about what risks
your software may contain. Securing the software supply chain begins with knowing what open source components are in your
code, as well as identifying their respective licenses, code quality, and potential vulnerabilities.
About the 2024 OSSRA
In this, its ninth edition, the 2024 OSSRA report delivers an in-depth look at the current state of open source security,
compliance, licensing, and code quality risks in commercial software. The ndings in this report are presented with the goal of
helping security, legal, risk, and development teams better understand the open source security and license risk landscape.
This report uses data from the Synopsys Black Duck
®
Audit Services team’s analysis of anonymized ndings from 1,067
commercial codebases across 17 industries during 2023. The Audit Services team has helped security, development, and
legal teams around the world strengthen their security and license compliance programs for over 20 years. The team audits
thousands of codebases for our customers each year, with the primary aim of identifying software risks during merger and
acquisition (M&A) transactions.
The audits also provide a comprehensive, accurate Software Bill of Materials covering the open source, third-party code, web
services, and application programming interfaces (APIs) in an organization’s applications. The Audit Services team relies on
data from the Black Duck KnowledgeBase™ to identify potential license compliance and security risks. Sourced and curated by
the Synopsys Cybersecurity Research Center (CyRC), the KnowledgeBase includes data on more than 7.8 million open source
components from over 31,000 forges and repositories.
The OSSRA report highlights the prevalence of open source in software as well as the potential dangers of not properly
managing it. Open source is the foundation for all applications that businesses and consumers rely on today. Identifying,
tracking, and managing open source effectively is critical to a successful software security program—as well as a key element
to strengthening the security of the software supply chain.
Executive
Summary
| Open Source Security and Risk Analysis Report 2024 | 4
Overview
14% of the
codebases assessed
for risk contained
vulnerabilities
older than 10 years
10
years
49% of the codebases
assessed for risk
had components that
had no development
activity in the
past 24 months
24
months
2.8 years was
the mean age of
vulnerabilities
in the codebases
assessed for risk
2.8
years
12
months
1% of the codebases
assessed for risk had
components that were at
least 12 months behind
on code maintainer
updates/patches
936 codebases underwent risk assessments
1,067 codebases scanned in 2023
= 10 codebases
of codebases assessed for risk contained vulnerabilities
of codebases assessed for risk contained high-risk vulnerabilities
84%
74%
of the codebases assessed for risk contained components that were
10 versions or more behind the most current version of the component
91%
31%
of the total codebases
contained open source
with no license or a
custom license
53%
of the total
codebases contained
license conflicts
96%
of the total
codebases
contained
open source
77%
of all code in the
total codebases
originated from
open source
剩余17页未读,继续阅读
资源评论
Pooling
- 粉丝: 0
- 资源: 274
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功