Brain Polar Body
How much of the current security situation of the Internet of Things can be changed by the solution proposed by Google, and how much space can Google leave for reclamation in the fertile soil of Internet of Things security?
AES, already known as King, why not apply to the Internet of Things?
Before discussing Adiantum, we need to understand how our tablets, mobile phones and other products can ensure their own security before the emergence of the Internet of Things.
As a result of the dynasty change, AES replaced DES as a worldwide encryption standard. Intel even set aside a partition for AES operations when designing chips.
The popularization process of an encryption standard is usually like this: more and more terminal devices use the standard, resulting in the design of the underlying chips (this process can also be reversed), and eventually evolved into a standard application cost reduction, which everyone uses together.
So why does the AES standard fail to work on the Internet of Things?
The first problem is that, unlike the AES era, many terminals in the Internet of Things are not IT devices at all, and there is no so-called bottom design that adapts to a certain standard.
At the same time, even though AES greatly improves the performance-price ratio in design, it is still a heavy burden of encryption algorithm even for some current smartphones. For example, the ARM Cortex-A7 chip, which is widely used in low-end smartphones, hand rings and other products, is unable to support AES, resulting in unsatisfactory device experience and slow response when opening applications.
So for the devices with smaller devices and higher computational response speed, it is not suitable for the current AES standard.
Internet of Things Encrypted Blank Painting Paper, Google just click on the next dot
It is no exaggeration to say that the development of the Internet of Things brings an opportunity for encryption technology.
Obviously, Google wants to rely on the open source advantage of Android system to further control more standards, and even increase its voice in hardware chip design: Internet of Things devices using my system is a probability event, if I can provide a more adaptable encryption standard, it will not only be conducive to the advancement of common devices'interconnection and intelligent process, but also will. It will affect the chip that Google may launch in the future and the computing platform structure of AIot.
So it seems that Google's new encryption standard is almost inevitable.
The emergence of this encryption mode means two things: first, encryption will no longer be a hindrance to the cost reduction of Internet of Things chips; second, the chip design of IT devices such as PC and smartphone can continue to be optimized.
So in any case, Adiantum is just a chess piece buried by Google, an ink dot on the blank paper of Internet of Things encryption.
Open Source Performance in Closed-loop Ecology
Of course, Google is not the only role to address the security of the Internet of Things, and terminal encryption is not the only way to maintain the security of the Internet of Things. In communication technology, cloud, API interface including laws and regulations need to be multi-wire, so it seems that Google's most suitable model (Jing) imitation (Zhg) to (shou) should be non-Microsoft.
Like Google, Microsoft has a widely used operating system as a basic advantage, cloud service provisioning capabilities, and a high degree of artificial intelligence technology.
In terms of Internet of Things security, Microsoft has created a more closed ecosystem: customized microcontroller chips, cloud security service Azure Sphere and operating system Azure Sphere OS based on Linux, which maintain security from a complete Internet of Things operating chain of chips, clouds and operating systems. In addition, deep learning technology is used to simulate automated attacks to provide automated monitoring and repair of security problems.
So, if Google continues to consolidate its advantages in the field of Internet of Things security, the next step is probably to optimize the Android system for Internet of Things applications, introduce Adiantum control chips, and then complete the closed-loop in the cloud.
But the current trend is that both Google and Microsoft are doing open source in a closed-loop layout. Take Microsoft's Azure Sphere security service as an example. In addition to supporting its own cloud services, it also supports the services of AWS, Google Cloud, Oracle, IBM and other vendors. In addition to testing on Android systems, Google's Addenum encryption has also been tested on Linux systems, which are often used by Internet of Things devices.
But with the precedent of mobile phones and PC, it's hard to imagine the future of the Internet of Things as a harmonious, thriving open-source playground. Now it's so awkward to use an office software on Mac, let alone use Google's encryption mode on Microsoft's Internet of Things chip.
Today's tolerance between several manufacturers is more like a joint venture to contract fish ponds, wait for fish fattening before dividing the results. However, in any case, the security shackles of the Internet of Things will soon be released by joint efforts.