Alan Martinovic
Eystein Stenberg has over 10 years of experience in security and systems management as a developer, a support engineer, a technical account manager, and now as a product manager. He has been in the front line of some of the largest production environments in various roles and has in-depth knowledge of the challenges in systems security in a real-world context.
His writing credits include “Distributing a Private Key Generator in Ad Hoc Networks” and believes in products that have an obsessive focus on one use case and solves the problem comprehensively, intuitively, and with ease.
Eystein Stenberg holds a Master’s Degree in Mathematics with a focus in cryptography from the University of Tromsø, Norway.
Session
When deploying IoT devices to the field, they become inherently difficult to access physically. In the ideal case the devices always work predictably and you have an approach to do OTA software updates in a controlled manner, so you can systematically improve your device fleet over time, by fixing bugs, security issues and adding new features.
In the real world, even if you do your due diligence and planning, strange things will happen to individual devices in the field. Your customers will contact you and ask why the product is not working according to their expectations. Is there something wrong with the device, software applications or the expectations/usage of the customer? This needs to be addressed right away, your customer is waiting. But where to start?
Remote access is a common term used for different features, for example remote terminal, that will enable efficiently diagnosing such issues remotely. Based on research on solutions used across many different IoT product companies, we will go through the most common needs around Remote access. We will also survey different open source technologies, including system applications and network protocols, that can be used for remote access purposes and compare them.