Three Paths To Memory Safety for Embedded
Memory problems are a constant worry for teams developing software for embedded systems. Whether you are building a doorbell, a self-driving car, a printer or an airplane. As much as 70% of security vulnerabilities are due to memory issues. On top of that, a lot of effort is spent on trying to find as many problems during development as possible. And still, problems always slip through.
In this presentation, we will look at three paths to memory safety that provide increasing guarantees and make software more safe and secure:
- The memory safe subset of the MISRA C/C++ rules that catch defects before they are merged into your main branch
- Rust as a memory and type safe language that prevents memory corruption
- Ada SPARK as a memory and type safe language with provable absence of runtime errors and optional provable functional correctness.
For each of the options, we will look at how easy it is to adapt, what the benefits are, what type of guarantees you can derive from the technology as well as some actual use cases of the technology in real-world projects.
This is a must-watch presentation if you are building embedded systems that have to be safe and secure and if you are wondering on how to make your systems more memory safe.


No comments or questions yet. Be the first to start the conversation!