Securing tomorrow's software: the need for memory safety standards

The post advocates a shift to standardized memory safety across the software industry, proposing a technology-neutral framework with tiered assurance levels (akin to SLSA) to enable objective assessment, procurement incentives, and policy alignment. It highlights growing use of memory-safe languages (e.g., Rust, Kotlin) and complementary hardware protections (ARM MTE, CHERI), calls for practical guidance on integrating unsafe code where necessary, and outlines Google’s commitments (Secure by Design whitepaper, memory safety strategy, prioritizing memory-safe languages, and deploying hardened libc++).