prevent all vulnerabilities. Companies that make software must have the freedom to innovate, but
they must also be held liable when they fail to live up to the duty of care they owe consumers,
businesses, or critical infrastructure providers. Responsibility must be placed on the stakeholders
most capable of taking action to prevent bad outcomes, not on the end-users that often bear the
consequences of insecure software nor on the open-source developer of a component that is
integrated into a commercial product. Doing so will drive the market to produce safer products and
services while preserving innovation and the ability of startups and other small- and medium-sized
businesses to compete against market leaders.
The Administration will work with Congress and the private sector to develop legislation
establishing liability for software products and services. Any such legislation should prevent
manufacturers and software publishers with market power from fully disclaiming liability by
contract, and establish higher standards of care for software in specific high-risk scenarios. To begin
to shape standards of care for secure software development, the Administration will drive the
development of an adaptable safe harbor framework to shield from liability companies that securely
develop and maintain their software products and services. This safe harbor will draw from current
best practices for secure software development, such as the NIST Secure Software Development
Framework. It also must evolve over time, incorporating new tools for secure software
development, software transparency, and vulnerability discovery.
To further incentivize the adoption of secure software development practices, the Administration
will encourage coordinated vulnerability disclosure across all technology types and sectors; promote
the further development of SBOMs; and develop a process for identifying and mitigating the risk
presented by unsupported software that is widely used or supports critical infrastructure. In
partnership with the private sector and the open-source software community, the Federal
Government will also continue to invest in the development of secure software, including memorysafe languages and software development techniques, frameworks, and testing tools.
S TRATEGIC O BJECTIVE 3.4: U SE F EDERAL G RANTS AND
O THER I NCENTIVES TO B UILD IN S ECURITY
Federal grant programs offer strategic opportunities to make investments in critical infrastructure
that are designed, developed, fielded, and maintained with cybersecurity and all-hazards resilience in
mind. Through programs funded by the Bipartisan Infrastructure Law, the Inflation Reduction Act,
and the CHIPS and Science Act, the United States is making once-in-a-generation investments in
our infrastructure and the digital ecosystem that supports it. This Administration is committed to
making investments in a manner that increases our collective systemic resilience.
The Federal Government will collaborate with SLTT entities, the private sector, and other partners
to balance cybersecurity requirements for applicants with technical assistance and other forms of
support. Together, we can drive investment in critical products and services that are secure- and
resilient-by-design, and sustain and incentivize security and resilience throughout the lifecycle of
21
NATIONAL CYBERSECURITY STRATEGY
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents