Independent security layer

A security layer that is agnostic to the underlying technology is highly important. It means that as a business you are unbiased towards the use of any specific technologies to solve your business problems. You can let your needs, competence and budgetary constraints guide your technology strategies and chose the best platforms for your needs. And, you are not locking yourself into a specific supplier or product suite, at least not from a security point of view.

Hop-by-Hop securityBut there’s more to this than just supplier lock-in. It is also about complexities. Different technologies and suppliers also have different security solutions. All with their own management principles and tools making systems and management complex and vulnerable.

Take for instance the “normal” cloud. You communicate with your cloud providers servers over an encrypted tunnel (TLS, VPN or similar). The data is protected in this tunnel through some sort of user authorization and certificate. But when reaching the cloud it is decrypted and exposed in clear text until it is stored in a, sometimes encrypted, database. The security is then managed through (at least) two management systems with the need to trust the provider and their staff to manage their part of your security needs. This is called hop-by-hop security:

There are even some technologies that lack their own security technologies. That is most visible in the Internet of Things where many of the necessary technologies come from Operation Technologies (OT) and Machine-to-Machine (M2M), like for instance one of the most common communication protocols MQTT. How do you add simple but strong security solutions to such technologies?

The Hyker SDK provides a single security model that eliminates many of these issues. By locking down the data completely from the generating source device to the consuming devices you remove the need to rely on specific suppliers, processes, and technology implementations.

Hyker SDK and service is technology, protocol and device agnostic

Hyker is Platform Agnostic
There are multiple cloud providers, IoT platforms, and network technology suppliers on the market today, such as Amazon, Microsoft, Cisco, Google Firebase, Etherium Blockchain, and while they all have their unique advantages, and some with more significant disadvantages, to be platform agnostic means to be capable of using any platform a customer chooses. Hyker encrypts and decrypts the data in the endpoints. The data is not accessible anywhere centrally by a provider of any sort, disregarding the different security models or technologies they might have implemented.

Hyker is Protocol Agnostic
There is certainly an issue of protocols in the world of IoT as mentioned above. How can devices communicate effectively if they’re speaking different protocols? How can data from multiple protocols all protect their data in a unified model? How can they speak the same encryption? Like the famed tower of Babel, one of IoT’s biggest hurdles is to help devices, protocols, and data sets all work together on a common protocol, or with translating brokers, to make communication happen seamlessly. Therefore, to be protocol agnostic the security cannot be reliant on a protocol or communication pattern. Hyker supports any protocol a customer chooses.

Hyker is Device Agnostic
Just as protocols and platforms pose a problem for interoperability and communication, so do the devices themselves. To be device agnostic means that one isn’t limited to one type of device. To be device agnostic is to be flexible to use any device a customer chooses. Hyker SDK supports many development platforms, tools, and languages. Depending on the platform, like Android, iOS, Windows, .NET, Linux and many more, we provide you with our SDK in a compatible compiled format for the developers to integrate into the application for its targeted platforms.


With Hyker it is all about the Application, not the underlying technology. The application owns the security, proactively protects the data and manages data access rights, not the components that make up the application.