Last week, we hosted the "Building a chain of trust in IoT" webinar, led by Jim Carver, in ARM's Meet the Experts webinar series. If you missed the event, you can access the webinar recording now and learn more about to learn more about the various challenges which must be addressed in order to develop, deploy and maintain a trusted IoT device.
You can also find a followup pdf here, including links to mbed documentation and other useful resources.
Q & A Followup
As promised during the webinar, Jim wanted to follow up with comprehensive responses to a few of the attendee questions he received. Due to the large number of questions, he wasn’t able to answer all of them during the webinar itself.
By 2020,the number of devices connected will increase, will cloud capacity pose an issue in future?
No, the mbed cloud is designed to be scalable with the ability to seamlessly add capacity as demand increases.
Can mbed Cloud have my devices directly communicate with my 3rd party cloud or does my data and information all have to go through your mbed Cloud bridges?
Custom designed applications can easily communicate directly with mbed Cloud using our REST APIs, bridges are designed to implement connection to legacy systems or 3rd party cloud applications which to not conform to the mbed Cloud API structure.
How to debug mbed OS?
mbed OS can be debugged like any microcontroller using standard development tools like Keil development tools from ARM. “mbed Enabled” development boards all have debug interface capabilities compatible with most popular offline development tools along with the drag and drop programming interfaces so no expensive JTAG debug pods are required.
When will a Linux client be available?
Our Linux client will be available later this year as part of the mbed Cloud general availability release.
Where is the mbed Cloud hosted? Can it be hosted on in house server?
Today mbed Cloud is hosted on public cloud infrastructure. Soon it will be available for deployment on either private cloud instances or in house servers.
Is the ARM security solution solely focused on mbed OS? What about non-OS IoT devices?
Implementation of strong security on devices running without an OS would be extremely difficult and will require extensive security experience and a thorough knowledge of threat modelling. The entire purpose of mbed OS to provide developers with a properly designed and tested system to relieve them of the burden of designing security themselves. This allows deployment of products with strong security with greatly reduced time to market.
Thanks to all our attendees for their interest, we hope that you gleaned some new insights into security in IoT! Keep an eye out for further ARM webinars on the Online Events page at arm.com.