Synopsis "RUST FOR MEMORY-SAFE SYSTEMS PROGRAMMING"
Your C/C++ code has a bug in it right now. You just haven't crashed yet. Buffer overflows, Use-after-free, Dangling pointers. These aren't edge cases, they're the single largest root cause of critical security vulnerabilities in production software today, and they're the reason CISA and the NSA have told every software manufacturer in the country to have a memory-safety roadmap in place. If you write systems code in C or C++, that roadmap starts with you. This book is your roadmap. Rust for Memory-Safe Systems Programming doesn't teach Rust as an abstract language exercise. It follows one real project, SentinelGuard; a security telemetry platform, from an empty directory to a working system running as a Linux daemon, a cloud service on AWS, firmware on a microcontroller, and a library inside an Android app. Every chapter builds on the last. Every code sample actually compiles and runs, and where something couldn't be verified live (real AWS infrastructure, physical hardware), the book tells you so plainly, instead of pretending. You'll walk away able to: Eliminate the exact bug classes; buffer overflows, use-after-free, data races, that make C and C++ a compliance liability Migrate a legacy C/C++ codebase incrementally, without betting your team's roadmap on a risky full rewrite Generate real SBOMs and license-compliance reports with cargo-deny and cargo-cyclonedx, and map them directly to CISA's published guidance Ship Rust across every surface that matters, Linux daemons, AWS Lambda and DynamoDB, no_std embedded firmware, and Android via JNI/UniFFI, from one shared, tested codebase Fuzz, test, and verify your code the way a production security team actually does it, not the way a tutorial pretends to This is not a syntax primer. It assumes you already know how to program and gets straight to what matters: the ownership model that makes Rust's guarantees possible, and the systems-level engineering judgment that turns "the compiler didn't complain" into "this is actually production-ready." Whether you're an engineering lead staring down a memory-safety mandate, a C/C++ developer future-proofing your career, or a security engineer who needs to actually understand what a clean cargo-audit run does and doesn't prove, this book was built for the exact moment you're in right now. The migration to memory-safe systems programming isn't coming. It's already the industry's default. Get ahead of it.
