Executive Summary
Open-source software (OSS) is incorporated deeply into our digital ecosystem, across functions ranging from instant messaging to critical infrastructure. Though OSS is not necessarily riskier than commercial software, OSS security is critical given its prevalence in our rapidly changing digital environment and the complexity of implementing cybersecurity guidelines in the OSS space. The decentralized nature of OSS development and of the open-source community itself poses unique challenges to the uniform application of cybersecurity practices, which in turn makes regulation or other government engagement difficult.
This paper evaluates voluntary technical standards â here including widely adopted industry best practices as well as formal voluntary consensus standards developed by Standards Developing Organizations (SDOs) â as a potential mechanism for securing OSS. Voluntary standards are naturally suited to the decentralized nature of OSS and present a viable pathway forward for improving cybersecurity. Fourteen interviews with professionals in the open-source security and standards spaces reveal two key dynamics within OSS that impact standardization of OSS security: financial incentives and culture. Furthermore, interviewees identify the uptake of standards â as opposed to the design of standards â as a key inflection point that may benefit from formalized U.S. government support and put forth several policy suggestions.
U.S. policymakers interested in advancing the cybersecurity of OSS through standards should consider three policy recommendations identified in this paper: firstly, concerted government outreach to the OSS community; secondly, leveraging financial incentives to encourage cybersecurity; and thirdly, establishing government-managed repositories of standards to ease standards uptake.
Given the increasing role of OSS in powerful technologies like artificial intelligence (AI), it is critical that the government develop a clear strategy to enhance OSS cybersecurity. As technology becomes more capable, the ramifications of security incidents may become even more profound. To prevent or address such incidents, policymakers must develop interventions that are both effective and suited to the unique characteristics of the OSS space. This paper endeavors to inform policymakers about these unique characteristics and provide actionable pathways for future policy.
Introduction
In our digitized world, open-source software (OSS) has become ubiquitous, accounting for 80%-90% of all existing software.1âThe Linux Foundation and Harvardâs Lab for Innovation Science Release Census for Open Source Software Security,â The Linux Foundation, February 18, 2020, https://www.linuxfoundation.org/press/the-linux-foundation-and-harvards-lab-for-innovation-science-release-census-for-open-source-software-security. OSS, loosely defined as software that is developed openly and collaboratively and is freely accessible for individuals to edit and download, is vital to key functions ranging from everyday texting to critical infrastructure. Part of the popularity of OSS is due to its accessibility and opportunity for innovation, but its decentralization can make cybersecurity difficult. In particular, conducting oversight, enforcing best practices for security, and determining liability in the event of a breach can be challenging in OSS. Moreover, recent developments such as the increasing popularity of open-source and open-weight large language models like Metaâs Llama and hugely impactful cyberattacks like Log4Shell and SolarWinds highlight the need for improved security practices in OSS.2Llama is Metaâs flagship large-language mode (LLM). It is not completely open-sourced, since the full details of its training and construction are not publicly available, but its model weights are public, and it is freely downloadable with adjustable weights. Log4Shell is a widespread critical vulnerability in an OSS program, and it is described in deeper detail later in this paper. The SolarWinds breach is a commercial software incident found in 2020.
How can policymakers support OSS security despite the difficulty of applying traditional, liability-driven forms of regulation? This paper will examine the utility of voluntary technical standards as a tool for enhancing the security of OSS and identify potential ways for the U.S. government to leverage standards in its cybersecurity efforts.
Notes
- 1âThe Linux Foundation and Harvardâs Lab for Innovation Science Release Census for Open Source Software Security,â The Linux Foundation, February 18, 2020, https://www.linuxfoundation.org/press/the-linux-foundation-and-harvards-lab-for-innovation-science-release-census-for-open-source-software-security.
- 2Llama is Metaâs flagship large-language mode (LLM). It is not completely open-sourced, since the full details of its training and construction are not publicly available, but its model weights are public, and it is freely downloadable with adjustable weights. Log4Shell is a widespread critical vulnerability in an OSS program, and it is described in deeper detail later in this paper. The SolarWinds breach is a commercial software incident found in 2020.