Rune Hillebo Wiinberg & Johan Callmyr
Security by design – what does it actually mean for embedded products?
Security by design has become one of those expressions that appears almost everywhere in discussions about connected products. It sounds sensible. Build security into the product from the beginning rather than adding it later. But what does that actually mean when you are developing an embedded product? It starts before the first line of production code is written.
Begin with the product, not the technology
The temptation when discussing cybersecurity is to jump directly to solutions. Encryption. Secure Boot. Firewalls. Certificates. But the right starting point is understanding the product and its risks.
What does it connect to? What information does it process? What would happen if someone gained unauthorized access? Which interfaces are exposed? How will the device be updated? And how long is it expected to remain in operation?
A cybersecurity risk assessment can help answer these questions and define an appropriate level of protection. Only then does it make sense to decide which security mechanisms are needed.

Establish trust from the start
For many embedded devices, one important element is the Root of Trust.
The Root of Trust provides a foundation that the system can rely on when establishing security. Together with Secure Boot, it can help ensure that only validated software is allowed to run during startup.
The principle is relatively easy to understand. Before trusting the software, verify that it is what you expect it to be. The Root of Trust can validate the bootloader. The validated bootloader can then establish a Chain of Trust, allowing subsequent stages of the boot process to be verified.
This makes it more difficult for unauthorized software to insert itself into the startup process.
Protect the keys to the product
Security often depends on keys and certificates. They can be used to verify software, authenticate communication and establish trust between different parts of a system. That also makes them valuable.
Secure key storage therefore becomes an important consideration in many embedded systems. Depending on the product and hardware architecture, solutions may involve technologies such as a Trusted Execution Environment or Trusted Platform Module.
But storage is only part of the challenge. Keys and certificates have lifecycles too. They may expire or need to be replaced. The organization needs a controlled way to provision, store and update them. Again, good cybersecurity combines technology with processes.
Less can be more
Security by design also means thinking carefully about what the product should not do. Every active service, open interface and unnecessary software component can potentially expand the attack surface. Hardening a product therefore involves reviewing functionality and disabling or restricting what is not required.
Applications can also be confined so they operate with limited permissions rather than having unrestricted access to the system. The goal is not to make the product difficult to use.
It is to ensure that every function and access level has a reason to exist.
Plan for secure updates
No product remains frozen in time. New features may be introduced. Bugs need to be fixed. Vulnerabilities will be discovered. A secure product architecture therefore needs to consider software updates.
Prevas solution within Industrial Linux, for example, uses an A/B partition approach where the system can switch between software partitions during updates. The purpose is to maintain a functional version while changes are introduced.
Depending on the product, firmware signing and encrypted update bundles can provide additional layers of protection.
But technology is only one part of an update strategy. Updates also need to be tested and qualified before deployment.
Know when something changes
Even a well-designed product can be affected by vulnerabilities discovered years after release. CVE monitoring helps identify known vulnerabilities relevant to the software used in a system.
That information gives product teams an opportunity to respond. The important word is opportunity.
A vulnerability alert still needs to be evaluated in the context of the actual product. Is the affected component being used? Is the vulnerable functionality exposed? What is the potential consequence? Is an update necessary?
This requires knowledge of both the software and the product environment.
Security by design is really security for life
Perhaps the most useful way to think about security by design is not as a collection of technical features, but as preparation for change.
Products change. Threats change. Software changes. Requirements change.
The architecture and processes surrounding a connected product need to be able to handle that reality. Secure Boot, protected keys, hardening and secure updates are important tools.
But the bigger achievement is creating a product that can be understood, maintained and protected throughout its lifecycle. That is what turns security by design from a buzzword into good engineering.
explore
Explore Cybersecurity Insights
- From cybersecurity requirements to a working medical product – the Ably Medical story
Rune Hillebo Wiinberg & Johan Callmyr

- Cybersecurity doesn’t end when your product leaves R&D
Rune Hillebo Wiinberg & Johan Callmyr

- Connected product? EN 18031 may be more relevant than you think
Rune Hillebo Wiinberg & Johan Callmyr

- Security by design – what does it actually mean for embedded products?
Rune Hillebo Wiinberg & Johan Callmyr

Some Areas of Expertise
About the Authors
Rune Hillebo Wiinberg is Head of Cybersecurity at Prevas and has worked professionally with embedded and secure, connected products since 2007. With experience across energy, medical technology and defense, he advises customers at all levels of the organization, helping bridge business priorities, regulatory requirements and technical product development.
Johan Callmyr is a Software Architect with more than 20 years of experience in C++ and embedded device software. He combines technical expertise with his experience in software architecture, technical leadership, cybersecurity, and development in regulated environments like medtech. As a Software Architect and Software Lead, he helps customers build robust, secure, and safe software solutions for complex products.