IoT security is the area of endeavor concerned with safeguarding connected devices and networks in the Internet of things (IoT). The MXChip IoT DevKit comes with STSAFE-A100 secure chip from STMicroelectronics to fulfill the secure needs on the device end. With STSAFE, credentials such as WiFi password, connection strings for the cloud services and other confidential data are able to be securely stored in it. This article explains secure levels provided on IoT DevKit using STSAFE.
The STSAFE-A100 consists of a full turnkey solution with a secure operating system running on the latest generation of secure microcontrollers.
On the chip, it employs data partitions to be used to store critical data such as Wi-Fi SSID, Wi-Fi password and IoT hub connection string safely. Credential data can be isolated in those partitions. To read and write those partitions, a developer uses
dataZoneIndex for operating on specific partition. See API Reference to learn about using it on Arduino.
Enable the secure channel
By default, the security chip is not enabled. It means the data you store on EEPROM is in plain text. There are two ways to enable it:
enable_secure 1command in Configurition Mode.
enableHostSecurityChannel()function in Arduino. see API reference.
After enabled, the IoT DevKit will negotiate a key with secure chip. The key will be stored at both IoT DevKit and secure chip side. All data as well as the read / write operations on I2C will then be encrypted.
Notice: Enable the security chip with caution. Using drag and drop to upgrade firmware will make data saved in EEPROM will no longer be readable immediately after enabling the security channel. This is a design with the security chip to ensure data can not be breached.
The status between enabling and disabling the security channel.
The difference of the data commuinication between IoT DevKit and the security chip (EEPROM).