How to Make IoT Devices More Secure？

时间： 2021-11-26 来源：Silicon Labs

技术问答

As exciting as the world of IoT may be, it comes with risks, particularly with regards to device and data security. In fact, one of the hardest tasks that IoT device designers face is enabling the security protocols and practices necessary to ensure that they’re creating products that are not only functional and valuable but safe to use.

Unfortunately, the security track record for many previous IoT devices is not good. We've undoubtedly all read or seen stories about costly network intrusions or other nefarious digital activities whose root cause ends up being traced back to some type of connected device with poor (or even no) security. The problem had become so bad that it inspired multiple governments around the world to create legislation demanding that digital devices adhere to certain security protocols.

The end result is an enormously complex patchwork of legal requirements and regulatory demands being placed on IoT devices that make it difficult for anyone to track. For IoT device makers—many of whom understand how challenging it is to enable good security in their devices—these legislative demands are essentially adding insult to injury.

But as frustrating and onerous as all the various regulatory requirements for IoT devices may be, the simple truth is they exist for a valid reason. Bringing connected devices into our homes and businesses unquestionably does increase the potential attack surface that hackers and other cybercriminals can leverage for things like ransomware and other dangerous outcomes. And many of the early IoT devices were so badly lacking in security capabilities that they probably shouldn’t be in active use anymore.

Thankfully, a number of companies and industry organizations have stepped up their efforts to create products, frameworks and certification programs to help IoT device makers navigate the often choppy waters of IoT security. The ioXt (Internet of Secure Things) Alliance, for example, has put together numerous device security profiles to help engineers and designers meet all the necessary requirements and follow security best practices for their devices. The organization consists of over 450 executives from more than 35 companies and includes Google, Amazon, Facebook (now Meta), T-Mobile, Comcast and SILICON LABS. In addition, chip IP industry leader Arm has created the PSA Certified program, a certification program that provides a security checkmark of approval across several different levels. Companies like Silicon Labs now seek these certifications to show their commitment; for instance their EFRxG21B SoCs with Secure Vault are the first chips in the world to achieve Arm PSA Level 3 certification – PSA Certified's highest level of IoT security protection. These and other efforts go a long way towards standardizing and improving security practices and implementations across a wide range of connected IoT devices.

Another benefit of these types of security profiles and certifications is that component makers can do the hard work of ensuring that their chips meet the necessary requirements and then device makers who choose to use those chips in their designs can “inherit” the benefits of their labor. So, for example, if a company builds a smart light bulb or other device using an ioXt or PSA-certified component, the majority of the work necessary to get the device certified is already done. All the device manufacturer needs to do is a simple delta certification against the existing ecosystem security profile for that device category and their work is done. Not only does this give the manufacturer the ability to market the benefits of their security capabilities, it ensures that end-users of the device will have better, safer experiences.

Part of the challenge that the IoT industry has faced is that requirements and expectations around security have shifted and matured a great deal over the past few years. One key example is the move to Zero Trust principles. While in the past, devices behind a gateway or firewall were presumed to be trustworthy, experience has shown that isn't the case. With Zero Trust-driven security practices, no devices are presumed to be trustworthy—regardless of their location on the network—and their device identity needs to be authenticated before they're allowed to join and send data over a network.

This type of profoundly different approach to security isn't something that many existing devices can easily adapt to. Instead, it needs to be built into the device (and the chips powering them) from the start. In order to address this need, companies have made enhancements to their manufacturing practices in order to enable this. Silicon Labs, for example, has started something they call CPMS (Custom Part Manufacturing Service) to securely provision chips with unique digital identities and digital certificates using their Secure Vault technology. These essentially function as a root of trust for the chip (and any device that uses it), allowing customers to provision their chips securely themselves before the chips even leave the factory. This way, customers have a footprint they can track throughout the entire chips' journey.

It's clear that IoT security challenges aren't going to be disappearing anytime soon, but it is good to see multiple efforts to make those issues surmountable.

发送到邮箱 |
+1 赞 0
收藏
评论 0
| 转发至：

本文由董慧转载自Silicon Labs，原文标题为:Making IoT Devices More Secure，本站所有转载文章系出于传递更多信息之目的，且明确注明来源，不希望被转载的媒体或个人可与我们联系，我们将立即进行删除处理。

全部评论（0）

暂无评论

【经验】教你如何修改EFR32MG系列SOC ZigBee工程的CCA阈值

Silicon Labs公司的EFR32MG系列SOC单芯片已被广泛应用于智能家居市场产品中。对于ZigBee协议栈，无论单播还是广播，数据包在发送之前MAC层会检测CCA(Clear Channel Assessment )，如果检测到接收信号强度低于阈值，数据包就不发送。因此需要根据实际情况来设置合理的CCA阈值，本文就指导大家来设置EFR32MG系列SOC的CCA阈值。

设计经验发布时间 : 2019-01-31

【经验】EFR32xg SoC的Bin，S37，EBL和HEX目标文件有什么不同?

我们在使用Silicon Labs EFR32xg SoC开发 EmberZnet 时发现，当我们的固件编译结束之后可以得到各种各样的结果，包括 S37，GBL，HEX和BIN格式的目标文件，那么这些文件到底有什么区别的？在什么情况下我们要用到对应的文件呢？本文将具体介绍。

设计经验发布时间 : 2020-07-11

【经验】Matter入门指导3：基于GSDK创建Matter - SoC Lighting over Thread工程

本文主要介绍使用EFR32MG24 Breakout Board，基于GSDK创建Matter - SoC Lighting over Thread工程的方法，我们后面会使用这个工程的固件来做Matter over Thread灯设备的控制实验。

设计经验发布时间 : 2023-05-18

Silicon Labs（芯科科技） Wi-Fi 芯片和模块选型指南

目录- Wi-Fi SoC and Module Selector Guide Wi-Fi Lineup Wi-Fi Development Kits IoT Wi-Fi Technology Leader Wi-Fi Applications Company Profile

型号- SLEXP8022A,SIWX915,RS9116,WF200,SIWX917,RS9116X-DB-EVK1,RS9116X-SB-EVK1,RS9116X-SB-EVK2

选型指南 - SILICON LABS - 2023/10/3 PDF 英文下载

Silicon Labs SiWx917，一款功耗超低的Wi-Fi 6 SoC，嵌入式闪存高达8MB

SiWx917 SoC是功耗超低的Wi-Fi 6 SoC，非常适合使用Wi-Fi®、蓝牙、Matter和IP网络实现安全云连接的超低功耗IoT无线设备。它是需要延长电池寿命的电池供电设备的最佳选择。

产品发布时间 : 2024-09-19

【IC】芯科科技MG26多协议SoC功能全面提升，迎合Matter over Thread开发代码增长需求

SILICON LABS近期针对Matter开发的扩展需求发布了MG26多协议SoC新品，通过提升了两倍的闪存和RAM容量以及GPIO，同时添加了人工智能和机器学习（AI/ML）硬件加速器来帮助开发人员满足未来更严苛的Matter物联网应用需求，包括增加对新的设备类型和安全功能增强等的支持。

产品发布时间 : 2024-04-25

EFR32FG25 Gecko Wireless SoC Family Data Sheet

型号- EFR32FG25B111F1152IM56-B,EFR32FG25A221F1920IM56-B,EFR32FG25A211F1920IM56-B,EFR32FG25B222F1920IM56-B,EFR32FG25B121F1152IM56-B,EFR32FG25A111F1152IM56-B,EFR32FG25A121F1152IM56-B,EFR32FG25B221F1920IM56-B,EFR32FG25B212F1920IM56-B,EFR32FG25B222F1920IM56-BR,EFR32FG25B211F1920IM56-B,EFR32FG25

数据手册 - SILICON LABS - Rev. 1.0 - January, 2023 PDF 英文下载查看更多版本

EFR32FG28 Wireless SoC Family Data Sheet

型号- EFR32FG28A120F1024GM48-A,EFR32FG28A010F1024GM48-A,EFR32FG28B310F1024IM48-A,EFR32FG28A110F1024GM48-A,EFR32FG28A110F1024GM68-A,EFR32FG28B310F1024IM68-A,EFR32FG28A322F1024IM68-AR,EFR32FG28B320F1024IM68-A,EFR32FG28A122F1024GM68-A,EFR32FG28A112F1024GM68-A,EFR32FG28B312F1024IM68-A,EFR32FG28A122F1024GM48-A,EFR32FG28B312F1024IM48-A,EFR32FG28,EFR32FG28B322F1024IM68-A,EFR32FG28B320F1024IM48-A,EFR32FG28A112F1024GM48-A,EFR32FG28B322F1024IM48-A,EFR32FG28A120F1024GM68-A,EFR32FG28A010F1024GM68-A

数据手册 - SILICON LABS - Rev. 1.1 - October, 2023 PDF 英文下载查看更多版本