Skip to content

house · Committee report

H. Rept. 118-160

SECURING OPEN SOURCE SOFTWARE ACT OF 2023

2023-07-27

Committees

Associated legislation

Text

Purpose and Summary

Open source software is a critical part of our digital infrastructure. A secure, healthy, vibrant, and resilient open source software ecosystem is crucial for ensuring the national security and economic vitality of the United States. However, due to both the unique strengths of open source software and inconsistent historical investment in open source software security, there exist unique challenges in securing open source software. H.R. 3286 requires the Cybersecurity and Infrastructure Security Agency (CISA) to publish a framework to assess the most critical open source software libraries used in the Federal government and requires CISA to assess the feasibility of creating a voluntary pilot program to assess open source software usage across critical infrastructure. The bill also requires CISA to hire from and build relationships with the open source community to help mitigate vulnerabilities like the one in Log4j and allow the Federal government to more swiftly response when vulnerabilities are discovered.

Background and Need for Legislation

Open source software is the bedrock of the digital ecosystem. Virtually every computer in the world relies on open source code that is distributed for free and maintained by the open source community, consisting of a group of individuals and organizations that develop and maintain open source software. The collaborative nature of open source software offers opportunities for innovation and societal advancement, but also poses security challenges, as highlighted by the Log4j vulnerability's impact on millions of computers worldwide. Log4j is a very widely used piece of open source software. In December 2021, a new vulnerability, called a zero day, was discovered within Log4j, resulting in cyber risk to millions of devices across the globe. At the time, cyber professionals described the vulnerability as the worst many had seen in their careers. The Securing Open Source Software Act of 2023 is a direct response to the threats posed by the Log4j vulnerability. This bill aims to address these security challenges by authorizing a number of activities at the Cybersecurity and Infrastructure Security Agency (CISA) to support the security of open source software. The Federal government is one of the largest users of open source software in the world and must both manage its own risk and, in turn, contribute back to the security of open source software. The framework required in the Securing Open Source Software Act of 2023 will be used by CISA to evaluate the government's posture and better position federal agencies to securely use open source software. While use of the framework is voluntary for the private sector, the bill requires CISA to conduct a study and consider a voluntary pilot program to assess the open source software components used in critical infrastructure. These steps will allow CISA and public and private sector partners to assess, manage, and reduce risks to support the secure usage of open source software.

Hearings

The Committee held the following hearing in the 118th Congress that informed H.R. 3286: On April 27, 2023, the Subcommittee on Cybersecurity and Infrastructure Protection held a hearing entitled ``CISA 2025: The State of American Cybersecurity from CISA's Perspective.'' The Subcommittee received testimony from the Honorable Jen Easterly, Director, Cybersecurity and Infrastructure Security Agency.

Committee Consideration

The Committee met on May 17, 2023, a quorum being present, to consider H.R. 3286 and ordered the measure to be favorably reported to the House, as amended, by voice vote.

Committee Votes

Clause 3(b) of rule XIII requires the Committee to list the recorded votes on the motion to report legislation and amendments thereto. No recorded votes were requested during consideration of H.R. 3286. Committee Oversight Findings In compliance with clause 3(c)(1) of rule XIII, the Committee advises that the findings and recommendations of the Committee, based on oversight activities under clause 2(b)(1) of rule X, are incorporated in the descriptive portions of this report. Correspondence With Other Committees House of Representatives, Committee on Oversight and Accountability, Washington, DC, July 18, 2023. Hon. Mark Green, Chairman, Committee on Homeland Security, Washington, DC. Dear Chairman Green: I write concerning H.R. 3286, the Securing Open Source Software Act of 2023. This bill contains provisions within the jurisdiction of the House Committee on Oversight and Accountability. As a result of your having consulted with me concerning the provisions of the bill that fall within our Rule X jurisdiction, I agree to forgo consideration of the bill, so the bill may proceed expeditiously to the House floor. The Committee takes this action with our mutual understanding that by foregoing consideration of H.R. 3286 we do not waive any jurisdiction over the subject matter contained in this or similar legislation, and we will be appropriately consulted and involved as the bill or similar legislation moves forward so we may address any remaining issues within our Rule X jurisdiction. The House Committee on Oversight and Accountability also reserves the right to seek appointment of an appropriate number of conferees to any House-Senate conference involving this or similar legislation and requests your support of any such request. Finally, I would ask that a copy of our exchange of letters on this matter be included in the bill report filed by the Committee on Oversight and Accountability. I appreciate your commitment to also include these letters in the Congressional Record during floor consideration of H.R. 3286. Sincerely, James Comer, Chairman, House Committee on Oversight and Accountability. House of Representatives, Committee on Homeland Security, Washington, DC, July 18, 2023. Hon. James Comer, Chairman, Committee on Oversight and Accountability, Washington, DC. Dear Chairman Comer: Thank you for your letter regarding H.R. 3286, the ``Securing Open Source Software Act of 2023,'' of which the Committee on Oversight and Accountability received an additional referral. I appreciate your support in bringing this legislation before the House of Representatives, and that the Committee on Oversight and Accountability will forego further consideration of the bill. The Committee on Homeland Security concurs with the mutual understanding that by foregoing consideration of this bill at this time, the Committee on Oversight and Accountability does not waive jurisdiction over the subject matter contained in this legislation in the future. In addition, should a conference on this bill be necessary, I would support your request to have the Committee on the Oversight and Accountability represented on the conference committee. I will include our letters on H.R. 3286 in the Committee report on this measure and in the Congressional Record during floor consideration of this bill. I look forward to working with you on this legislation and appreciate your cooperation on this matter. Sincerely, Mark E. Green, MD, Chairman. Congressional Budget Office Estimate, New Budget Authority, Entitlement Authority, and Tax Expenditures With respect to the requirements of clause 3(c) of rule XIII and section 308(a) of the Congressional Budget Act of 1974, and with respect to the requirements of clause 3(c)(3) of rule XIII and section 402 of the Congressional Budget Act of 1974, the Committee adopts as its own the estimate of any new budget authority, spending authority, credit authority, or an increase or decrease in revenues or tax expenditures contained in the cost estimate prepared by the Director of the Congressional Budget Office. [GRAPHIC(S) NOT AVAILABLE IN TIFF FORMAT] The bill would Require assessments of open-source software used by federal agencies Direct the Cybersecurity and Infrastructure Security Agency to hire open-source software analysts Require several reports and studies about the effectiveness of open-source software assessments Estimated budgetary effects would mainly stem from Testing information systems for open-source software vulnerabilities Assessing federal network security Hiring open-source software analysts Areas of significant uncertainty include Anticipating the contract costs of software assessments Predicting staffing requirements Bill summary: H.R. 3286 would authorize the Cybersecurity and Infrastructure Security Agency (CISA) to improve the security of open-source software, or computer code that is publicly available for anyone to use or modify. The bill would require the agency to identify and mitigate vulnerabilities in open-source software used by federal agencies. Under the bill, CISA would conduct annual assessments of the security of commonly used open-source software. Estimated Federal cost: The estimated budgetary effects of H.R. 3286 are shown in Table 1. The costs of the legislation fall within budget function 050 (national defense). TABLE 1.--ESTIMATED BUDGETARY EFFECTS OF H.R. 3286 ---------------------------------------------------------------------------------------------------------------- By fiscal year, millions of dollars-- ---------------------------------------------------------------- 2023 2024 2025 2026 2027 2028 2023-2028 ---------------------------------------------------------------------------------------------------------------- Open-Source Software Assessments Estimated Authorization.................... 0 0 6 6 6 6 24 Estimated Outlays.......................... 0 0 6 6 6 6 24 CISA Open-Source Staff Estimated Authorization.................... 0 2 4 4 4 4 18 Estimated Outlays.......................... 0 2 4 4 4 4 18 Total Changes Estimated Authorization.................... 0 2 10 10 10 10 42 Estimated Outlays.......................... 0 2 10 10 10 10 42 ---------------------------------------------------------------------------------------------------------------- Basis of estimate: For this estimate, CBO assumes that H.R. 3286 will be enacted in 2023 and that CISA would begin to implement most of the bill's requirements in 2025. CBO expects that the costs to implement H.R. 3286 would include the salaries and benefits of additional federal staff and procurement of new software. Outlays are based on historical spending patterns for existing or similar programs. Spending subject to appropriation: CBO estimates that implementing the bill would cost $42 million over the 2023-2028 period. Such spending would be subject to the availability of appropriated funds. Open-source software assessments. CISA currently operates programs to identify and mitigate threats to federal information systems. H.R. 3286 would require CISA to assess open-source software used by the federal government for security vulnerabilities. Under the bill, CISA would review the supply chain histories of open-source applications to identify any potential cybersecurity vulnerabilities in the underlying code. CISA would be required to share its findings so that software users could remediate any weaknesses. Using information from CISA, CBO expects that the agency would implement this program by procuring new software and tools capable of scanning for vulnerabilities in open-source code used by federal agencies. On the basis of similar acquisition programs, CBO estimates that the cost to acquire and annually update those tools would total $24 million over the 2023-2028 period. CISA open-source staff. H.R. 3286 would require CISA to publish a framework for the secure adoption and management of open-source software in the information networks and devices of federal, state, and private-sector entities. CISA also would provide information about vulnerabilities in open-source software. CBO anticipates that the framework and vulnerability assessments would be updated annually. CBO expects that CISA would need 20 open-source software analysts beginning in 2024 at an average annual cost of about $175,000 per employee. On that basis and accounting for the effects of anticipated inflation, CBO estimates that salaries and benefits of those employees would total $18 million over the 2023-2028 period. Uncertainty: Areas of uncertainty in this estimate include predicting the acquisition timeline to support assessments at federal agencies and critical infrastructure operators. CBO anticipates that CISA would be able to procure and deploy the necessary software to assess federal open-source software in the 2023-2028 period. The budgetary effects of the bill could be millions of dollars higher or lower than CBO's estimate if the time needed to deploy these tools differs from CBO's estimate. The budgetary effects of the bill also would depend on accurately predicting the number of additional employees that would be needed at CISA to satisfy the requirements of the bill. Costs would be moderately larger or smaller than this estimate depending on how the number of hired analysts differs from CBO's estimate. Pay-as-you-go considerations: None. Increase in long-term net direct spending and deficits: None. Mandates: None. Previous CBO estimate: On April 6, 2023, CBO transmitted a cost estimate for S. 917, the Securing Open Source Software Act of 2023, as ordered reported by the Senate Committee on Homeland Security and Governmental Affairs on March 29, 2023. The estimated cost of S. 917 is higher than the cost of H.R. 3286 because the former bill would authorize a federal pilot program that would not be authorized by the latter. Estimate prepared by: Federal costs: Aldo Prosperi; Mandates: Brandon Lever. Estimate reviewed by: David Newman, Chief, Defense, International Affairs, and Veterans' Affairs Cost Estimates Unit; Kathleen FitzGerald, Chief, Public and Private Mandates Unit; Chad Chirico, Deputy Director of Budget Analysis. Phillip L. Swagel, Director, Congressional Budget Office. Federal Mandates Statement The Committee adopts as its own the estimate of Federal mandates prepared by the Director of the Congressional Budget Office pursuant to section 423 of the Unfunded Mandates Reform Act of 1995. Duplicative Federal Programs Pursuant to clause 3(c) of rule XIII, the Committee finds that H.R. 3286 does not contain any provision that establishes or reauthorizes a program known to be duplicative of another Federal program. Statement of General Performance Goals and Objectives Pursuant to clause 3(c)(4) of rule XIII, the objective of H.R. 3286 is to require CISA to undertake certain responsibilities to ensure the security of open source software use in the Federal government. Congressional Earmarks, Limited Tax Benefits, and Limited Tariff Benefits In compliance with rule XXI, this bill, as reported, contains no congressional earmarks, limited tax benefits, or limited tariff benefits as defined in clause 9(d), 9(e), or 9(f) of rule XXI. Advisory Committee Statement No advisory committees within the meaning of section 5(b) of the Federal Advisory Committee Act (5 U.S.C. Sec. 1004) were created by this legislation. Applicability to the Legislative Branch The Committee finds that H.R. 3286 does not relate to the terms and conditions of employment or access to public services or accommodations within the meaning of section 102(b)(3) of the Congressional Accountability Act. Section-by-Section Analysis of the Legislation Section 1. Short title This section designates the name of the bill as the ``Securing Open Source Software Act of 2023''. Section 2. Open source software duties Subsection (a) amends section 2201 of Subtitle A of title XXII of the Homeland Security Act of 2002 to define the terms ``open source software'', ``open source software community'', and ``open source software component''. This subsection also amends section 2202 of Subtitle A of title XXII of the Homeland Security Act by amending the responsibilities of the Director of the Cybersecurity and Infrastructure Security Agency (CISA) to include supporting the secure usage and deployment of software, including open source software, in the software development lifecycle at Federal agencies. This subsection also adds Section 2220F of Subtitle A of title XXII, which establishes the duties of the Director of CISA regarding open source software security. Section 2220F: Subsection (a) defines the term ``software bill of materials''. Subsection (b) requires that the Director employs individuals who, to the greatest extent practicable, have expertise and experience participating in the open source software community. Subsection (c) establishes duties of the Director regarding open source software security, which includes performing outreach and engagement to secure open source software, supporting Federal efforts to secure open source software, and serving as a public point of contact for the security of open source software. Subsection (c) also requires the Director to conduct an assessment of critical open source software components. The Director must publish a framework to assess the risk of open source software components, incorporating government, industry, and open source software community frameworks and best practices. The Director must determine every year whether updates to the framework are needed. In developing the framework, the Director must consult with open source community members and Federal agencies. Subsection (c) then directs the Director to perform an assessment of the most critical open source software components used on high-value assets, as defined by Office of Management and Budget Memorandum M-19-03, Strengthening the Cybersecurity of Federal Agencies by enhancing the High Value Asset Program, using the established framework. The Director shall automate the assessment to the greatest extent practicable. The Director shall publish tools developed to conduct the assessment and shall share the results of the assessment with appropriate entities. Subsection (c) also directs the Director to study the feasibility of conducting the assessment for critical infrastructure entities. If the Director determines the assessment to be feasible, the Director may conduct a voluntary pilot assessment with 1 or more critical infrastructure sectors. The Director shall submit a report to Congress following the study and the pilot. If the Director conducts the pilot, the pilot shall be sunset 2 years after the commencement of the pilot. Subsection (c) requires the Director to report to Congress not later than 1 year after the date of enactment of the section, and every 2 years thereafter for the next seven years. The Director shall make a version of such reports publicly available. Subsection (c) also requires the Director to brief and consult with the National Cyber Director, as appropriate. Subsection (b) amends the table of contents to insert the new section 2220F, as added by Subsection (a). Subsection (c) authorizes CISA to create a subcommittee on software security, including open source software security, to the CISA Cybersecurity Advisory Committee. Subsection (d) states that nothing in this Act or the amendments made by this act shall be construed to provide any additional regulatory authority to any agency described therein. Changes in Existing Law Made by the Bill, as Reported In compliance with clause 3(e) of rule XIII of the Rules of the House of Representatives, changes in existing law made by the bill, as reported, are shown as follows (existing law proposed to be omitted is enclosed in black brackets, new matter is printed in italics, and existing law in which no change is proposed is shown in roman): HOMELAND SECURITY ACT OF 2002 SECTION 1. SHORT TITLE; TABLE OF CONTENTS. (a) Short Title.--This Act may be cited as the ``Homeland Security Act of 2002''. (b) Table of Contents.--The table of contents for this Act is as follows: Sec. 1. Short title; table of contents. * * * * * * * TITLE XXII--CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY * * * * * * * Subtitle A--Cybersecurity and Infrastructure Security * * * * * * * Sec. 2220F. Open source software security duties. * * * * * * * TITLE XXII--CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY * * * * * * * Subtitle A--Cybersecurity and Infrastructure Security SEC. 2200. DEFINITIONS. Except as otherwise specifically provided, in this title: (1) Agency.--The term ``Agency'' means the Cybersecurity and Infrastructure Security Agency. (2) Appropriate congressional committees.--The term ``appropriate congressional committees'' means-- (A) the Committee on Homeland Security and Governmental Affairs of the Senate; and (B) the Committee on Homeland Security of the House of Representatives. (3) Cloud service provider.--The term ``cloud service provider'' means an entity offering products or services related to cloud computing, as defined by the National Institute of Standards and Technology in NIST Special Publication 800-145 and any amendatory or superseding document relating thereto. (4) Critical infrastructure information.--The term ``c

Source: https://api.congress.gov/v3/committee-report/118/hrpt/160