{"id":1236120,"date":"2025-03-01T10:34:00","date_gmt":"2025-03-01T15:34:00","guid":{"rendered":"https:\/\/www.prime-wow.com\/?p=1236120"},"modified":"2025-03-01T10:34:00","modified_gmt":"2025-03-01T15:34:00","slug":"google-calls-for-measurable-memory-safety-standards-for-software","status":"publish","type":"post","link":"https:\/\/www.prime-wow.com\/?p=1236120","title":{"rendered":"Google Calls for Measurable Memory-Safety Standards for Software"},"content":{"rendered":"
Memory safety bugs are “eroding trust in technology and costing billions,” argues a new post on Google’s security blog \u2014 adding that “traditional approaches, like code auditing, fuzzing, and exploit mitigations \u2014 while helpful \u2014 haven’t been enough to stem the tide.” <\/p>\n

So the blog post calls for a “common framework” for “defining specific, measurable criteria for achieving different levels of memory safety assurance.” The hope is this gives policy makers “the technical foundation to craft effective policy initiatives and incentives promoting memory safety” leading to “a market in which vendors are incentivized to invest in memory safety.” (“Customers will be empowered to recognize, demand, and reward safety.”) <\/p>\n

In January the same Google security researchers helped co-write an article noting there are now strong memory-safety “research technologies” that are sufficiently mature: memory-safe languages (including “safer language subsets like Safe Buffers for C++”), mathematically rigorous formal verification, software compartmentalization, and hardware and software protections. (With hardware protections including things like ARM’s Memory Tagging Extension and the (Capability Hardware Enhanced RISC Instructions, or “CHERI”, architecture.) Google’s security researchers are now calling for “a blueprint for a memory-safe future” \u2014 though Importantly, the idea is “defining the desired outcomes rather than locking ourselves into specific technologies.” <\/p>\n

Their blog post this week again urges a practical\/actionable framework that’s commonly understood, but one that supports different approaches (and allowing tailoring to specific needs) while enabling objective assessment:<\/p>\n

At Google, we’re not just advocating for standardization and a memory-safe future, we’re actively working to build it. We are collaborating with industry and academic partners to develop potential standards, and our joint authorship of the recent CACM call-to-action marks an important first step in this process… This commitment is also reflected in our internal efforts. We are prioritizing memory-safe languages, and have already seen significant reductions in vulnerabilities by adopting languages like Rust in combination with existing, wide-spread usage of Java, Kotlin, and Go where performance constraints permit. We recognize that a complete transition to those languages will take time. That’s why we’re also investing in techniques to improve the safety of our existing C++ codebase by design, such as deploying hardened libc++. <\/p>\n

This effort isn’t about picking winners or dictating solutions. It’s about creating a level playing field, empowering informed decision-making, and driving a virtuous cycle of security improvement… The journey towards memory safety requires a collective commitment to standardization. We need to build a future where memory safety is not an afterthought but a foundational principle, a future where the next generation inherits a digital world that is secure by design.
\nThe security researchers’ post calls for “a collective commitment” to eliminate memory-safety bugs, “anchored on secure-by-design practices…” One of the blog post’s subheadings? “Let’s build a memory-safe future together.” <\/p>\n

And they’re urging changes “not just for ourselves but for the generations that follow.”<\/p>\n

\n<\/a>
\n<\/a><\/p>\n<\/div>\n

Read more of this story<\/a> at Slashdot.<\/p>\n