Conferences and supporting programme
Protect Your System by Isolating Your Keys from Software: The Importance of Hardware-based Security
Hackers’ ultimate goal is to obtain access to systems remotely. Successful remote attacks open the possibility of replicating in large numbers and can create large scale damage, such as that in the DDoS attack in October 2016. Efficient hackers will attack the weakest point of the system—for IoT this is often the hardware at the end node. This weakness frequently emanates from modest expectations of security needed for simple devices such as light bulbs when they are not connected, persisting in scenarios when they are connected to the IoT. Companies must protect their brand and ensure their revenue streams are not only protected, but growing. After the DDoS attacks, streaming of information stopped which led to the loss of millions of the dollars in revenue overnight for companies relying on digital content. Authentication is (or should be) the root of every secure connection to a cloud service. The foundation of authentication relies on private keys being placed in a system (provisioned) and how securely stored they are in that system. Isolating the private keys from software and application cores is the most crucial architectural concept for a strong authentication, therefore, security must start with a hardware-based implementation. Secure elements are the equivalent of safes where companies places their secrets (aka. their private keys necessary for IoT authentication). The creation of a secure element, and how it stores and protects keys will be discussed. The example will also demonstrate how this implementation is scalable to nearly any system and will reduce the customers’ risks and project costs while accelerating their time to market.
--- Date: 28.02.2018 Time: 11:00 AM - 11:30 AM Location: Conference Counter NCC Ost