IoT Blog Written By Experts For Experts

A container enables an application to be packaged and isolated with its runtime environment.

The 1960s was the decade in which the car industry, first in the US and eventually across the whole world, found itself at the center of concerns about safety and the high numbers of deaths and injuries caused by collisions on the road

The practice of containerization developed first in server-side and enterprise computing environments, providing a way to isolate applications in highly complex systems, and allow flexible, fast modification or updating without disrupting the entire system.

Doesn’t it make sense to learn from the security mistakes that others have made, and avoid the pain which they had to go through in putting their mistake right?

Why identity is the foundation of IoT security The basic elements of security protection for IoT devices are familiar to most developers: A device must be safe from the risk of tampering, side-channel attacks, and other forms of physical attack A device must run authentic firmware which is protected against unauthorized changes The data on the device must be protected from unauthorized access, both at rest and in transit The device’s firmware must be capable of being updated remotely to maintain its protection against emerging cyber threats For a deeper dive into the fundamentals of securing connected devices, check out our guide on IoT security.

The challenge of scaling embedded Linux product development Developers of connected embedded and IoT products face a set of challenges which developers of enterprise computing systems or mobile phone apps do not experience

Foundations first: putting the basics of IoT security in place As Embedded and Internet of Things (IoT) devices grow in capability, making them more secure has become a critical priority for product manufacturers to master

IoT device management, applied to embedded devices based on a Linux® operating system (OS), is an important function for maintaining the performance and security of a fleet of devices in the field: it is the set of functions which allows for over-the-air (OTA) software upgrades and security patches throughout the life of an IoT or edge product.

It’s ironic that the mechanism used to deliver security updates to installed devices can itself make an entire fleet of devices vulnerable to attack.

Gather ‘round, developers, and listen to a chilling tale of digital terror. In the shadowy realm of the internet the Mirai botnet lurks ‐ a nightmare born from the most mundane of vulnerabilities .