Isolate OT and IT. Keep Data Flowing

DMZ support built for industrial networks

  • Isolate OT and IT. Keep Data Flowing
    Isolate OT and IT. Keep Data Flowing

NIS 2 and NIST CSF 2.0 are clear: production and corporate networks must be segregated. NIST SP-800-82 goes further, calling for at least three zones — OT, IT, and a DMZ between them — with firewalls ensuring no direct link exists between control and corporate networks.

Standard protocols fall short here. OPC UA is too complex to daisy-chain reliably across a DMZ — information is lost in the first hop. MQTT can be chained, but its QoS guarantees don't propagate, so users at the end of the chain won't know their data is inconsistent.

Cogent DataHub tunnel/mirroring was purpose-built for DMZ connections. It mirrors the full data set at every node in the chain, with guaranteed consistency from source to user. If a connection drops, every downstream client knows immediately. When it's restored, data quality returns to Good across every link — no manual intervention required.

All connections are outbound-only. No inbound firewall ports. No VPN. No attack surface.

Find out more

Disclaimer: Content published by TIM Global Media, including text, images, and videos, is either created in-house or provided by Suppliers/Manufacturers with their approval. Suppliers/Manufactures warrant that their materials do not infringe third-party rights and agree to indemnify and hold TIM Global Media harmless from any related claims.

Share with: