How long term servicing helps OEMs maintain IoT security
A recent wave of cold chain cyberattacks on refrigerators, freezers, and even blood banks across Europe has destroyed produce costing €millions. But it was the seemingly random nature of the attacks, not just their scope, that raised questions. Similar attacks on a smaller scale could have been mistaken for a bug.
Where it started
Sometime on October 11th, 2026, internet-connected refrigerators and freezers in hundreds of French supermarkets were set to defrost by hackers. Initial reports stated that while the supermarket chains differed, the refrigeration regulator systems were essentially identical. Apparently, the regulator’s manufacturer had recommended replacing the units when they reached end of life and were no longer supported several years earlier.
The incident, which has since been confirmed as a cyberattack, confused observers because it didn’t target any financial equipment, such as point-of-sale terminals. Instead, it set the refrigeration units to defrost, in some cases reaching +50°C and starting fires, causing more damage.
Had the cyberattack been restricted to one refrigerator, one supermarket or one chain, or even launched over several weeks, it could have confused investigators even more. If those investigations hadn’t quickly uncovered the true nature of the widespread failure, it may even have been mislabelled as a bug.
If reports are accurate, the actual cause of the initial attack was a default username still set to ‘admin’ and an easily guessed password. Today, most installers would recognise this as a vulnerability, but some of the controllers in question reached end of life 10 years ago. That suggests they were installed sometime before 2016, when the need for stronger online security was still being debated. Today, the need for strong online security is unquestioned. Any connected device still in service but no longer supported with software updates is a potential attack surface waiting to be discovered.
The requirements of the European Union’s Cyber Resilience Act (CRA) become fully applicable on December 11th, 2027. As of September 11th, 2026, manufacturers with products on the market in the EU must now report exploited vulnerabilities when they become aware of them. That includes legacy systems like the refrigeration regulator.
If a hacker discovers a vulnerability in a legacy product and subsequently exploits it, even if the device is no longer manufactured, sold, or supported, the manufacturer must report it as soon as they become aware of it. That describes what happened with the recent cyberattack in France.
How cyberattacks are changing design practices
The need to prove online resilience will impose deeper scrutiny at every stage of design. Any latent bug in a connected product that results in unexpected behaviour risks being interpreted as a cyberattack, even if it doesn’t present a vulnerability.
Under EU law, knowledge of an exploited vulnerability now triggers a series of events for the manufacturer that costs them time, money and perhaps reputational damage. No manufacturer will want to risk unnecessary damage to their brand, but if a bug makes it into production, the world may see it as a vulnerability.
Whether using default usernames was a feature that became a bug, that became a vulnerability, is open to debate. The truth is, exploiting the default username on refrigeration units is not an isolated example; anecdotal evidence suggests that default security credentials may be standard operating procedure for some OEMs, even today.
Legislating against poor online security will work. Any vulnerabilities identified during the design process will be addressed. Features that introduce vulnerabilities will also be identified, such as allowing default usernames and passwords to remain unchanged after a device has been put into service.
Taking control of your online security
Part of the challenge of maintaining online security is updating the product’s software after it has shipped. Choosing the right platform that has long-term support for security updates is the real key. Vulnerabilities in the software stack can be patched, typically before they are discovered and exploited.
Although the CRA doesn’t mandate the use of operating systems with long-term support and over-the-air firmware (FOTA) security updates, it is the most pragmatic approach for OEMs seeking to protect their products, companies, and reputations.
In practice, security software updates will be mandatory throughout a connected product’s lifecycle. Digital products that are not directly connected to the internet may still be subject to the CRA’s requirements if they connect to other products or networks through wired interfaces.
Over-the-air updates became popular for adding new features to products after the sale, creating additional revenue streams for manufacturers. Today, the feature is used extensively for delivering security updates.
Most embedded products use 3rd-party software, in the form of operating systems, middleware and device drivers. The application provides the differentiation. OEMs typically focus developer resources on the application. If the underlying stack is secure, the application is inarguably the software component least likely to introduce a vulnerability.
Not all operating systems offer long-term support for security updates. In fact, the majority do not, particularly open-source operating systems. That puts the burden of maintenance firmly on the OEM and, with legislation on its way, that burden cannot be ignored.
Maintenance, in this situation, means monitoring the database of common vulnerabilities and exposures (www.cve.org), vendor advisories (such as those provided by the Microsoft Security Response Centre) and, potentially, an aggregator of vulnerability notifications.
The simpler solution is to use an operating system from a manufacturer that manages those security updates as part of long-term support. Commercially supported versions cover both proprietary and open-source operating systems.
Avnet Silica offers a range of Microsoft Windows licenses, including long-term service channel (LTSC) versions that come with 10 years of security updates. Windows 11 IoT Enterprise 2024 LTSC is the latest version from Microsoft and includes features designed for embedded and IoT devices:
- System Guard, attack surface area reduction and Windows Security App
- Flexible OS deployment
- Windows Sandbox and Microsoft Defender Application Guard
Windows 11 IoT Enterprise runs on both Arm64 and x86-64 architectures, with full application portability between both platforms. That flexibility, supported by 10 years of security updates, puts Windows 11 IoT Enterprise ahead of other operating systems.
If you’re planning a new embedded design and would like to discuss your software security requirements, contact Avnet Silica.

Contact Us
Need local assistance for your Microsoft Embedded Solution? Let us know!