Book a consultation

HiveMQ Manufacturing: Plant Placement, Customers and Failure Modes

HiveMQ Security on an OT Network: Placement, TLS and Access Control

HiveMQ security on an OT network: DMZ placement, TLS, Enterprise Security Extension, ACLs, the 2018 exposure study and HiveMQ's certifications.

Vladimir Romanov


HiveMQ security on an OT network comes down to one placement question and three controls. The question is which zone the broker lives in and who is allowed to open a connection to it. The controls are encryption, authentication and topic-level authorisation. HiveMQ publishes no Purdue or IEC 62443 placement guidance that we found, so the placement advice below is our view, drawn from general segmentation practice. The controls and the security record are sourced to HiveMQ and dated. This page sits under HiveMQ manufacturing and is current as of November 2026.

Where a HiveMQ broker belongs on an OT network

Treat the broker as a conduit endpoint between zones, not as one more server. In IEC 62443 terms, a broker carries data between an OT zone and an IT zone, so it should be placed and authenticated as such. That reading is ours, not quoted guidance. See ISA/IEC 62443 for the standard and OT network segmentation in brownfield plants for getting there.

HiveMQ’s MQTT security fundamentals post on securing MQTT systems says internet-facing services such as an MQTT broker often reside in the DMZ, protected by an additional firewall. For a plant we would go further:

  1. Plant broker or Edge inside the OT zone (Level 3 or below), so machines, SCADA and historians never leave the zone.
  2. An outbound bridge to an IT-facing broker in a DMZ (Level 3.5). The bridge client is started from the OT side, so no firewall rule has to admit a connection from IT into OT.
  3. IT consumers connect only to the DMZ broker, with their own credentials and narrower topic rights.
  4. The management plane on an admin network. Control Center and APIs are a frequent weak point for brokers generally, so keep them off every data path.
A broker on an OT network: zones, firewalls and who connects to whom Three zones side by side: OT zone for Levels 0 to 3, a DMZ at Level 3.5 and an IT zone at Levels 4 and 5, separated by two firewalls. In the OT zone, PLCs feed a plant broker or HiveMQ Edge, and the management interfaces sit on an admin network. The plant broker opens an outbound bridge to an IT-facing broker in the DMZ. IT clients such as MES, ERP, Kafka and cloud services connect inward to the DMZ broker, never to the OT zone. OT zone (Levels 0 to 3) DMZ (Level 3.5) IT zone (Levels 4 and 5) PLCs and devices Plant broker or Edge TLS, client certificates Control Center and APIs admin network only IT-facing broker ESE roles and ACLs MES, ERP, analytics Kafka, cloud, historians subscribe over TLS Bridge starts from the OT side, outbound only IT clients connect in Firewall 1 Firewall 2 No rule lets an IT-zone client open a connection into the OT zone. The management plane stays off every data path.
Connections start from the inside out: the plant broker bridges to the DMZ, IT clients connect to the DMZ broker, and nothing from IT reaches OT. This is our pattern, not HiveMQ guidance.

The cost is a second broker and a bridge to run. That is bridging, and for a plant with only one or two IT consumers it can be more than the risk justifies. For a plant with a history of flat networks it usually is not. If you cannot draw your current zones, start with an OT network assessment.

Black-and-white view of a substation behind a chain-link fence beside utility poles
A perimeter fence is the physical version of a zone boundary: it protects only if everything that needs to cross it does so at a controlled gate.

Controls HiveMQ documents

TLS. We did not confirm which TLS versions and cipher suites the current broker supports, so check the current documentation. Client certificates matter in OT because they bind a connection to a device, not a shared password.

Enterprise Security Extension. A commercial extension for authentication and authorisation, with roles, users and permissions and realms of type SQL, JWT, LDAP, file and OAuth. HiveMQ’s documentation says authentication and authorisation can use different realms. Release 4.57 of 3 November 2026 added PEM certificate support for the TLS connections of the Enterprise Security Extension. See Enterprise Security Extension for the detail.

Open-source options. The extension catalogue lists File RBAC and Deny Root Wildcard Subscriptions as open-source extensions. The second stops a client subscribing to #, which in Sparkplug and UNS deployments is the way one credential reads everything.

Edge. The OPC UA adapter documents basic and X.509 authentication and security policies up to AES256_SHA256_RSAPSS. The S7 adapter requires PUT/GET access on the PLC. That is a PLC-side setting with its own risk, which is our reading and which we did not check against Siemens documentation.

Exposed brokers: what the studies show

Trend Micro, with Eurecom and Politecnico di Milano, published a study on 4 December 2018. Using Shodan for discovery, it found hundreds of thousands of MQTT and CoAP hosts combined reachable on public addresses, counted 17,226 MQTT brokers in Asia-Pacific alone, and found exposed data including taxi bookings and a PLC leaking telemetry through an open broker: control system names, process details and a maintenance request. The authors note their keyword grouping was not exhaustive and results were vetted by hand. The figures are eight years old, and we gathered no 2026 scan.

The misconfiguration themes across exposure research are consistent: no authentication, TLS without client authentication, wildcard subscriptions for any client, default ports on cloud addresses, retained messages leaking history and no topic-level access control. Each is a configuration, not a product defect. A broker that is secure by default can still be exposed by one firewall rule.

HiveMQ’s security record

We list only what HiveMQ’s own pages confirm.

  • CVE-2023-39410 is a dependency advisory (an Apache Avro version before 1.13) that HiveMQ’s knowledge base says affects HiveMQ 4.23, 4.24.0 and 4.24.1, rated low severity, with a fix in 4.25 or later.
  • CVE-2020-13821, a cross-site scripting issue in the Control Center, was fixed in 4.3.3 (27 May 2020), which also required updated Enterprise Security and Kafka extensions.
  • HiveMQ’s knowledge base states it is not affected by CVE-2022-42889, because HiveMQ does not use the interpolation feature.
  • HiveMQ’s changelog index lists a security release dated 23 October 2026 titled for the eMudhra certificate authority compromise, covering Platform 4.56.1, 4.55.2 and 4.28.31, Operator 2.3.1 and Edge 2026.15. The index describes them as addressing the compromise of eight intermediate CA certificates from eMudhra and shows nothing more, so we cannot say what changed in each release.

What this does not show. Every long-lived broker has a CVE history, and a count is not a quality ranking. A better test is the time from disclosure to a fixed release and the clarity of the advisory, which you can check on HiveMQ’s pages. Subscribe to the advisories and keep an upgrade path, which the monthly cadence helps with.

Certifications and what they cover

ItemWhat is sourcedScope caution
ISO/IEC 27001Blog of 25 March 2024: scope covers development, operations, support, products and customer support; products named as on-premise, Cloud, extensions and brokerEdge is not named. HiveMQ’s July 2024 SOC 2 release cites ISO/IEC 27001:2013; a move to the 2022 version is not confirmed. Check the certificate
SOC 2 Type IIAnnounced 18 July 2024, all five Trust Services Criteria, auditor Insight Assurance, following SOC 2 Type I in January 2024The announcement ties the result to HiveMQ’s controls generally, not to a named product
CSA STARHiveMQ Cloud listed at Level 1 (self-assessment, created or renewed 11 December 2025) and at Level 2 (certification, 24 November 2025)Level 1 is a self-assessment listing
IEC 62443None foundA different thing: it assesses products and processes against OT requirements

These certify HiveMQ’s company and its cloud service, not your plant’s deployment. A company certification is evidence for vendor qualification, not proof that your deployment complies with any rule, so read each one that way.

A short review list

  • Is any listener reachable from outside the plant or from a flat IT network?
  • Can any client subscribe to #?
  • Does every device have its own credential, ideally a client certificate?
  • Is the management interface on an admin network?
  • Are old versions still running while the monthly releases move on?

Where it gets hard

Credentials multiply: devices, hosts, IT consumers, bridges and operators each need their own, with roles narrow enough to be useful. Rotation of certificates across hundreds of PLC gateways is the work nobody budgets for. Legacy devices that speak MQTT without TLS push you to terminate them at an Edge gateway. Back to HiveMQ manufacturing and the HiveMQ hub. Sibling: Ignition and HiveMQ.

Frequently asked questions

Where should a HiveMQ broker sit on an OT network?

In our view, a plant broker at Level 3 inside the OT zone, bridging outbound to an IT-facing broker in a DMZ at Level 3.5, with IT clients connecting only to the DMZ. HiveMQ publishes no Purdue or IEC 62443 placement guidance that we found, so this is our pattern, drawn from general segmentation practice.

Does HiveMQ have IEC 62443 certification?

We found no HiveMQ IEC 62443 certification or statement for the broker. HiveMQ documents ISO/IEC 27001, SOC 2 Type II and, for HiveMQ Cloud, a CSA STAR Level 1 listing. Those certify the company's practices and service, not a product's conformance to 62443.

What does HiveMQ's Enterprise Security Extension do?

It is a commercial extension that adds authentication and authorisation to the broker through realms such as SQL, JWT, LDAP, file and OAuth, with roles and permissions on topics. HiveMQ's documentation says authentication and authorisation can come from different realms. Open-source alternatives exist for simple file-based roles.

How common are exposed MQTT brokers?

A Trend Micro study published on 4 December 2018, with Eurecom and Politecnico di Milano, found hundreds of thousands of MQTT and CoAP hosts reachable on public addresses, including a PLC leaking telemetry through an open broker. The figures are from 2018, and we gathered no 2026 count.

Is HiveMQ Cloud ISO 27001 and SOC 2 certified?

HiveMQ says it holds ISO/IEC 27001 with a scope covering on-premise, Cloud, extensions and broker, and announced SOC 2 Type II on 18 July 2024 without naming products. The CSA STAR registry lists HiveMQ Cloud at Level 1. HiveMQ's July 2024 SOC 2 release cites ISO/IEC 27001:2013; a move to the 2022 version is not confirmed, so check the certificate.

References and further reading

  1. MQTT and CoAP: Security and Privacy Issues in IoT and IIoT Communication Protocols · Trend MicroPublished 4 December 2018. The exposure figures cited here are from this study.
  2. Understanding HiveMQ ISO/IEC certification and information security management · HiveMQPublished 25 March 2024: scope text.
  3. HiveMQ earns SOC 2 Type 2 compliance · HiveMQAnnounced 18 July 2024.
  4. HiveMQ Cloud on the CSA STAR registry · Cloud Security Alliance
  5. HiveMQ extensions · HiveMQEnterprise Security Extension, File RBAC and Deny Root Wildcard Subscriptions.
  6. CVE-2023-39410 knowledge base entry · HiveMQA dependency advisory affecting HiveMQ 4.23.
  7. Securing MQTT Systems - MQTT Security Fundamentals · HiveMQFirewalls and the DMZ; says internet-facing services such as an MQTT broker often reside there.
  8. Apache Commons Text CVE-2022-42889 vulnerability · HiveMQStates HiveMQ is not affected because it does not use the interpolation feature.
  9. CISA and UK NCSC joint guidance on securing OT systems · CISAPublished 29 September 2025. Does not name MQTT.

← Manufacturing

Have a project that needs technical ownership?

Send us the situation. If it is not something we should take on, we will say so.

The Plant-Side Brief

The weekly brief for the people who own a plant’s control systems.

One email every Wednesday for engineering and operations leaders responsible for controls, SCADA, MES and OT networks. Skim the top in two minutes; read the Deep Dive when you have fifteen.

  • One modernization problem, worked through to cost, risk and a schedule you can defend. The Deep Dive.
  • End-of-support dates before they reach your plant Windows, servers, controllers and HMI software. Lifecycle Watch.
  • A checklist your engineers can run that week not a framework to admire. Field Kit.
  • Every number sourced, no vendor agenda we are paid by plants, never by vendors.