Navigating the New Landscape of Embedded Systems Security

The world of embedded systems is changing fast. From increasingly stringent regulations to the growing sophistication of cyberattacks, developers face mounting pressure to build secure, reliable devices. This isn't just about avoiding headlines; it's about ensuring safety, maintaining trust, and building a sustainable future for connected technology. So, what are the key trends and how can you stay ahead of the curve?

The EU Cyber Resilience Act: A Game Changer

The EU's Cyber Resilience Act (CRA) is a major development that will impact manufacturers of embedded devices. The CRA mandates a proactive approach to vulnerability management, requiring manufacturers to actively seek, address, and openly report vulnerabilities. This includes releasing devices free of known vulnerabilities and providing timely security updates throughout the product's lifecycle.

What does this mean in practice? A few key requirements stand out:

• Software Bill of Materials (SBoM): Identifying all components and potential vulnerabilities becomes essential.
• Prompt Security Updates: Security patches need to be released separately from functional updates.
• Automated Testing: Regular testing is a must.
• Vulnerability Disclosure: Fixed vulnerabilities must be publicly disclosed.
• Coordinated Vulnerability Disclosure Policy (CVDP): Manufacturers need a clear CVDP, often facilitated by a security.txt file on their website.

Failure to comply with these requirements could result in significant penalties, not to mention reputational damage.

Microservices: A Path to Enhanced Security and Resilience

One architectural approach gaining traction in the embedded world is the use of microservices. Extracting microservices from a modular monolith can offer several advantages, particularly in the context of operator terminals for machines. OEMs have a tendency to reinvent the wheel, but microservices offer readily available solutions with technology-agnostic interfaces.

The benefits are compelling:

• Reduced Time to Market: Microservices allow you to leverage existing solutions.
• Improved Security: Isolating functions that require higher privileges enhances overall security.
• Enhanced Resilience: Breaking down systems into independent processes improves resilience.

This shift aligns with the open-closed principle, minimizing interface-breaking changes and making systems more adaptable. It’s about moving away from implementation steps and embracing behavior-driven tasks.

Toolchain as a Security Ally

Your development toolchain can be a powerful weapon in the fight against vulnerabilities. By leveraging compiler warnings, static analysis, and program augmentations, you can detect and prevent a wide range of security issues.

Consider these techniques:

• Integer Warnings: Catch potential integer-related errors.
• Memory Safety Checks: Identify memory corruption issues.
• Format String Analysis: Prevent format string vulnerabilities.
• Thread Safety Analysis: (Using Clang) Ensure thread safety in concurrent applications.

Furthermore, program augmentations like Fortify Source, stack buffer overflow protection, and sanitizers can detect runtime issues that might otherwise slip through the cracks. Some are even advocating a shift from system-on-modules (SoM) to solutions-on-modules. For non-microcontroller projects, explore additional protections like stack clash protection, shadow stack, address space layout randomization (ASLR), and control flow Integrity (CFI). These are useful tools for improving the security of your embedded systems.

RISC-V and Safety-Critical Systems

The RISC-V architecture is emerging as a viable option for safety-critical systems. Its benefits are numerous, including reduced system complexity, precise documentation of hardware-software interface specifications, deterministic execution, and the ability to implement dissimilar redundancy. The availability of safety-certified IP cores and components, along with a growing ecosystem of hardware and software suppliers, further strengthens the case for RISC-V. All things to consider if you're looking to achieve compliance in industries like aerospace and automotive.

The Elephant in the Room: Architectural Coupling

It's worth pausing to consider the bigger picture. One perspective suggests that software failures in the automotive industry might stem from poor architectural cohesion and coupling. High bandwidth communications, publish/subscribe models, and centralized hardware and software architectures can inadvertently encourage high coupling and low cohesion. It’s a complex issue. While SDVs (Software Defined Vehicles) aren't doomed, architectural and software engineering challenges need addressing.

Safeguarding Connected Devices: A Continuous Process

Securing connected devices isn't a one-time fix; it's an ongoing process. Industry leaders emphasize incorporating security into product development from the outset, securing transport and data, and locking down hardware based on data sensitivity. This holistic approach is crucial for building resilient and trustworthy systems.

The Bottom Line

The embedded systems landscape is evolving rapidly, driven by new regulations, emerging technologies, and increasingly sophisticated threats. By embracing proactive vulnerability management, exploring architectural innovations like microservices, leveraging your toolchain effectively, and paying attention to architectural considerations, you can navigate this complex terrain and build secure, reliable, and compliant devices.

Want to learn more about building memory-safe and secure embedded systems? Contact our team today to see how formal verification can help.