In its own words, this paper calls for:

- an addition to the critical infrastructure information technology sector,

- a cloud computing tax to fund critical U.S. cyber defense

- U.S.-sponsored governance for emerging cybersecurity solutions like Rust, and

- a U.S.-sponsored open source library verification service.

Some relevant quotes:

- Cloud sales tax:

-- "A cloud computing tax is long overdue, and it must be collected to secure the software supply chain for American consumers."

-- "A cloud sales tax would put the cost of securing open source for U.S. economic stability on the companies that have proﬁted the most from open source software—its biggest consumers. The Open Source Trust can offer ﬁnancial support to open source communities, allow for more free-ﬂowing exploration of our technology frontier, and close a gaping hole in America’s economic stability."

- "A public-private partnership effort to build an actionable cookbook for memory-safety migration would be a better ﬁrst step than urging technology manufacturers to use the one available today." ... "CISA should partner with early Rust adopters to identify their insights, costs, and wins and visibly incorporate that data into the roadmap guidance." ... "CISA should lead an initiative to create this cookbook for memory-safety migration starting with Rust, where there is little institutional knowledge available today, and this work should be funded by the Open Source Trust."

- Because Rust's memory safety and analysis tools are limited, and because engineers "need education and tools to know when to use [unsafe Rust] and how to mitigate the risks 'unsafe Rust' introduces," CISA SEI should "receive Open Source Trust funding to continue their research and development and (a) reduce the limitations of the Rust compiler, (b) audit the Rust compiler’s correctness in assessing the memory safety of Rust code, and (c) develop both static and dynamic analysis tools for safe and unsafe Rust."

- Also, CISA should "receive additional Open Source Trust funding to support rapid, in-depth development of standards across package repositories, compilers, and build tools" to mitigate the the security problems that come from one person controlling a crate that thousands depend on.

This isn't that important, but it's interesting, because I have often heard complaints here that Rust is hard to read.

"Rust is also the easiest programming language to sight-read. Engineers reading new code are like musicians reading unfamiliar sheet music. There are always recognizable elements, but the theme, pace, and key may be outside of the player’s experience. In software, those unfamiliar elements can take a developer through a complicated maze of dependencies and logic trees, and Rust makes the trail of logic in a program easier to follow. Researchers have concluded that Rust has a signiﬁcantly lower cognitive complexity than C, C++, Python, JavaScript, and TypeScript (all languages studied), “meaning that [Rust] can guarantee the highest understandability of source code compared to all others.” As a result, software maintainers can understand unfamiliar Rust code far more quickly than code wri0en in many other popular languages."

They cite this study: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7959618/