Alex Rebert

Alex Rebert

@ayper.bsky.social

Memory Safety @ Google. Previously co-founder of Mayhem Security (formerly known as ForAllSecure). Opinions here are my own.

174 followers212 following4 posts

Alex Rebert reposted

David Adrian
@dadrian.io

I wrote a post about how security undervalues preventing problems, and how this can be exasperated by AI and the vulnpocalypse, even though AI should actually make robustness much easier for defenders. Read it here: dadrian.io/blog/posts/w...

dadrian.ioPlaying whack-a-mole is losingI want to juxtapose two classes of people in the security industry on the defender side of security engineering for products. The first are the Security as Identity people. This goes back to the secur...

Alex Rebert reposted

Sophie Schmieg
@sophieschmieg.infosec.exchange.ap.brid.gy

Don't like what I'm posting? Become my boss and tell me to cut it out! Or just become my boss and be cool, that's also possible and encouraged. https://www.linkedin.com/jobs/view/4453027170/

linkedin.comGoogle hiring Engineering Director, Product Security, Core in Zurich, Zurich, Switzerland | LinkedInPosted 1:35:05 AM. Note: By applying to this position you will have an opportunity to share your preferred working…See this and similar jobs on LinkedIn.

Alex Rebert reposted

Zardus
@zardus.bsky.social

Can we translate all C to Rust? The susceptibility of C to memory corruption has long been a cybersecurity pain point, and coding agents can free us of it. Read on for my recent experiments in this space, and apt & docker repos that you can pull rust-converted libraries from!

Alex Rebert reposted

jeffvanderstoep.bsky.social
@jeffvanderstoep.bsky.social

With Rust development surpassing C++ in the Android platform in 2025, we can start making reliable comparisons. Rollback rates, code review latency, vulnerability density, and a CVE with a twist. security.googleblog.com/2025/11/rust...

security.googleblog.comRust in Android: move fast and fix thingsPosted by Jeff Vander Stoep, Android Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in ...
Alex Rebert
@ayper.bsky.social

We're joining forces with industry & academia to call for memory safety standardization: security.googleblog.com/2025/02/secu.... It's a recognition that memory unsafety is no longer a niche technical problem but a societal one, impacting everything from national security to personal privacy.

security.googleblog.comSecuring tomorrow's software: the need for memory safety standardsPosted by Alex Rebert, Security Foundations, Ben Laurie, Research, Murali Vijayaraghavan, Research and Alex Richardson, Silicon For decades,...

Alex Rebert reposted

erbbysam
@erbbysam.bsky.social

🛡️💸 We've revamped our Patch Rewards Program, extending its scope and increasing rewards for security patches – with a particular focus on memory safety, including bonus multipliers! bughunters.google.com/blog/5273064...

bughunters.google.comBlog: Level Up Your Open Source Karma (And Your Wallet) by Improving SecurityThis blog post takes you through everything you need to know about the Patch Rewards Program, including our newly introduced focus on memory safety (including reward multipliers!), recently increased ...

Alex Rebert reposted

Chandler Carruth
@chandlerc.blog

Had a bunch of thoughts about the recent safety stuff, way more than fit in social media post... Blog post story time! (It's a bit of a ramble, sorry about that...) chandlerc.blog/posts/2024/1... #LLVM #Clang #MemorySafety

chandlerc.blogStory-time: C++, bounds checking, performance, and compilersRecently, several of my colleagues at Google shared the story of how we are retrofitting spatial safety onto our monolithic C++ codebase: https://security.googleblog.com/2024/11/retrofitting-spatial-s...
Alex Rebert
@ayper.bsky.social

Excited to share our latest blog post on memory safety! We’re tackling spatial safety in our massing C++ codebase by hardening live++ by default. It adds bounds checks to things like std::vector, preventing a fair bit of out-of-bounds vulnerabilities: security.googleblog.com/2024/11/retr...

security.googleblog.comRetrofitting Spatial Safety to hundreds of millions of lines of C++Posted by Alex Rebert and Max Shavrick, Security Foundations, and Kinuko Yasada, Core Developer Attackers regularly exploit spatial mem...
Alex Rebert
@ayper.bsky.social

This improves spatial safety across Google’s services, including performance-critical components of Search, Gmail, Drive, YouTube, and Maps. We’ve already seen it disrupt a red team exercise, reduce segfaults by 30%, and improve code correctness.

Alex Rebert
@ayper.bsky.social

The best part? It’s incredibly cost-effective, with an average performance overhead of just 0.3%. So there’s really no reason not to do it if you’re running C++ code :)

You are up to date.