• • • IOT • • •
Secure firmware update mechanisms are essential. Updates must be authenticated, integrity-checked and delivered securely across constrained networks, requiring robust cryptographic signing, secure key management and resilient delivery processes. Security must also be embedded into the
software development lifecycle (SDLC). Vulnerability scanning, penetration testing and validation of third-party components such as open-source libraries prevent weaknesses from reaching production. At the same time, Software Bills of Materials (SBOMs) are becoming critical for supply chain transparency, enabling manufacturers to track dependencies and respond more effectively to emerging risks.
Applying security by design,
default and demand Historically, IoT security was treated as an extension of IT security or addressed after deployment through patching and monitoring. That approach is no longer sufficient, as regulatory frameworks such as the Cyber Resilience Act (CRA) and NIS2 place greater responsibility on manufacturers and solution providers to ensure devices are secure by design and remain secure over time.
In response, the industry is converging around a set of principles:
• Security by design – Security must be embedded into device architecture from the
outset. This includes leveraging hardware-based security features such as secure elements, trusted execution environments and hardware roots of trust. These capabilities establish device identity, enable secure boot and protect firmware integrity.
• Security by default – Security features must be enabled and configured when devices are deployed. This includes enforcing encryption, authentication and secure communication protocols as standard. From an engineering perspective, this requires careful attention to provisioning and configuration to avoid insecure deployments.
• Security by demand – Customers and regulators increasingly expect demonstrable security as a prerequisite. Procurement decisions now include compliance requirements, certifications and evidence of secure development practices.
The challenge of end-to-end IoT security
While these principles strengthen security at the device level, they do not address the complexity of IoT environments. Industrial IoT systems span multiple layers, including device, network and cloud-based applications, each with different security requirements.
Many connected devices operate outside traditional enterprise boundaries, meaning threats
may not be detected by standard IT security tools. At the same time, approaches designed for enterprise IT do not always translate effectively to embedded or operational technology environments.
Addressing this requires a more integrated approach. Security must be considered across the system, aligning device design, network monitoring and application-layer controls. This involves continuous monitoring, behavioural analysis and improved visibility across the IoT stack to identify anomalies and mitigate risks in real time.
Implications for
engineering teams For engineers, these developments reinforce treating security as a foundational design principle. This includes integrating hardware-based security early in development, ensuring secure provisioning, designing robust update mechanisms and maintaining visibility throughout the device lifecycle.
As IoT adoption expands, security is becoming inseparable from reliability, safety and compliance. Embedding these principles into engineering processes will be essential to delivering resilient systems that meet both operational and regulatory expectations.
https://www.aeris.com
electricalengineeringmagazine.co.uk
ELECTRICAL ENGINEERING • APRIL 2026 31
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40
