Wind River Studio and HPE ProLiant DL110 Gen10 Plus servers, based on Intel® architecture technology, combine to make a powerful platform for 5G virtualized radio access networks (vRAN).

Four Drivers of Digital Transformation at the Intelligent Edge and the Key Questions That Will Help Architect Your Success

Today’s device makers are caught between two opposing trends. On the one hand, legacy code continues to run in deployed systems. On the other hand, development tools — and developers — have continued to evolve. The challenge is how to bridge today’s developers to yesterday’s systems. In this case, legacy refers to software that was written quite a few years ago. The code still does what it is supposed to do; however, silicon, development tools, libraries, RTOSes, and even programming languages have changed substantially during this time. Consider an application such as an industrial robot, with a lifecycle of eight to 10 years. The equipment and software upon which the system was developed may not even be actively supported anymore. The problem is only magnified for more complex systems, such as airplanes. In addition to having a longer lifecycle (on the order of 30+ years), these systems are really collections of many individually developed systems that must interoperate. Further complicating even simple maintenance of these systems is the constant need for upgrades and improvement of operational capabilities. Consider the pace of change in terms of IoT security. Connected devices must receive regular security updates to keep them secure from hackers. Devices a decade or older must also maintain a sufficient level of security, even though they were not necessarily designed to do so. And this is only one aspect of the system. For example, communication technology and protocols continue to advance, and, somehow, these systems need to be able to continue to integrate with the new systems coming online, especially those in the cloud.

When selecting hardware, it often comes down to functionality versus cost. However, the growing importance of security and privacy in a world of intelligent systems strongly impacts hardware; clients now consider hardware security capabilities as well as their constraints. And some hardware (a given medical device, for example) is not connected to the internet, which causes a different problem: Software updates can be difficult to implement. Any vulnerability on such a device will remain there until the firmware is manually updated — and such updates may never be available. These challenges increase in devices with a long service life, such as a medical pacemaker or the control system in a nuclear power plant. Hardware can also face challenges from those who refurbish old systems and resell them online. The reseller may not have properly wiped the device of all past data, or the device may have been hacked or could contain vulnerabilities that were never addressed. The use of nonvolatile memory to store program code and configuration data can also lead to security challenges during device recycling, as it can retain sensitive information such as login details. This hardware can easily be reverse-engineered. This paper provides an overview of the different levels of attack on hardware devices, then reviews the various ways of using software to protect these devices.

SICHERHEIT MUSS JEDES EINZELNE ENDGERÄT IM GESAMTEN LEBENSZYKLUS UMFASSEN