DataHub Solves Common MQTT to the Cloud Challenges

This Looks Easy, Until Cybersecurity IT Has It's Say!

Many users think that it's okay to take an MQTT device on a protected plant network and send it to a cloud service. 

The problem is that would require your secure, protected operations network to have direct, unrestricted access to the internet which can present a serious security problem. 

Due rising cybersecurity risks, more and more operations networks have no direct access at all to the Internet, but perhaps there is a DMZ or a proxy that has to be handled? 

So what do you do?  Read on to learn more.

Secure Operations MQTT Broker to Cloud Service, but How? 

You may have MQTT devices inside your secure operations network that publish data to an MQTT Broker inside your firewall and now you want to get that data to the cloud. 

Problems

1. The cloud service is not a MQTT client
2. Even it were you would not want to let that client reach into your network by exposing open ports (Learn why opening ports is worse than you realize!)
3. Going back to the start, that operations computer should not have direct internet access without going through a DMZ or proxy.

But maybe someone has suggested to just put another MQTT broker in the DMZ as shown next?

DataHub MQTT in the DMZ Solves the Problem 

All you need is to put a DataHub MQTT Client in the DMZ. 

• DataHub can read from the MQTT broker on the operations side
• Then the DataHub in the DMZ can publish that data to the Cloud Service