Explaining the nuances and security considerations one must be mindful of when deploying software updates to connected devices, to ensure the security and integrity of devices deployed in the wild.
A key requirement for connected devices/IoT is the ability to deploy software updates. Data breaches are occurring on a regular basis and extending devices outside the firewall perimeter increases the attack surface. There are on average 1-25 bugs/defects per 1,000 lines of code. The good news is that security breaches are largely preventable. The Center of Internet Security estimates that 80-90% can be prevented through swift software updates and patching, which are necessary in order to:
- Deploy bug fixes
- Patch security vulnerabilities
- Deliver new features
In this video, Northern.tech's Eystein Stenberg presents a talk for the Linux Foundation on key considerations when deploying software updates for connected devices.
Tags:
OTA
Related resources
Some similar resources you may also be interested in
Economics of software update systems: Measuring the total cost of ownership for building and buying solutions
Business best practice dictates that organizations focus resources on areas that create market differentiation. Areas that are not a direct source of competitive advantage — such as enabling unique customer experiences or creating new revenue streams — are likely to be infrastructure or operational rather than strategic.
OTA Updates in the Wild: Lessons from the Field - Jana Perić - NDC TechTown 2025
Mender Customer Engineer Jana Perić shares lessons from real-world deployments on building secure and robust OTA software update infrastructure that holds up in the field.
Build or buy: Defining a secure & robust software update infrastructure
At their essence, software updates are simple – transfer data from one place to another. But, just as a tent, a bicycle, or a recreational player differ from a house, a car, or an Olympic athlete, production-grade software updates fit for enterprise commercial products are different. The qualifying process surrounding software updates is the difference. Baseline best practices for production-grade software updates focus on the minimum standards required for most commercial environments and enterprise products.


