Collect at the edge. Process local. Send outbound only.
Secure industrial data collection means the data leaves the plant without the plant becoming reachable. EmberNet collects at the edge, processes locally, and sends outbound only over TLS 443 to a zero-trust mesh. Where a device runs a Flux service, the collector dials it over Flux and the device never needs an exposed port at all. No firewall rule is added, no inbound port is opened, and the control network stays dark to the outside.
Four steps. No inbound connections.
Every decision in this architecture is about keeping the control network dark. Here is how the data moves, in order.
- 01
Collect at the edge
Read-only collectors run on the EmberNet edge node. They connect to the PLCs, sensors, and gateways you configure, read the values you specify, and close. No writes, no broadcasts, no scanning. The device does not know the difference between a configured poll and a watchdog.
- 02
Process locally
The edge node processes the data before it moves. Filtering, aggregation, unit conversion, and anomaly detection all run on the node. Only what you need leaves the plant.
- 03
Send outbound only
Data leaves the plant over EmberFLUX on port 443, initiated from the edge node. The plant network takes no inbound connection. No firewall rule is added. No VPN gateway is installed. The control network stays dark to the outside.
- 04
Present in one console
EmberCORE receives the data and makes it available across every site in one operational view. Time-series data goes to your historian. Alerts go to your team. SIEM integrations go outbound from EmberCORE, never inbound to the plant.
Where EmberNet sits in a Purdue-model plant.
The Purdue Reference Model for Control Hierarchy is the standard way to describe which systems sit at which tier in an industrial network. Here is where EmberNet fits.
| Level | Name | EmberNet's role at this level |
|---|---|---|
| Level 0 | Field devices | The PLCs, sensors, meters, and actuators EmberNet reads |
| Level 1 | Basic control | Where the EmberNet edge node sits and collectors run |
| Level 2 | Area supervisory | SCADA and DCS; EmberNet reads from here too |
| Level 3 | Site operations | EmberFLUX overlay exits here, outbound only |
| Level 4 | Business logistics | EmberCORE console; historian and SIEM forwarding |
EmberFLUX creates the outbound path from Level 2 to Level 4. It does not create an inbound path in the other direction. That is the architecture decision that keeps the control network segmented.
Which requirements the architecture speaks to, and which it does not.
IEC 62443 is the standard for industrial automation and control system security. Here is an honest account of what the EmberNet data collection architecture addresses.
Addressed. The outbound-only transport and zero-trust overlay address SR 5.1 (network segmentation) and SR 5.2 (zone boundary protection) in IEC 62443-3-3. The read-only collector constraint addresses SR 2.1 (authorization enforcement). The immutable OS and auto-rollback patching address SR 7.6.
Not addressed. EmberNet does not address IEC 62443-2-4 supplier security requirements or the full IEC 62443-4 device security requirements, which are the OEM's responsibility. It does not replace a security management system under IEC 62443-2-1.
We use the standard's language in eighteen places across our documentation. If your compliance team needs specifics, the docs are the authoritative source. See the docs.
Collect when there is no link.
The collection apps run on the edge node itself, so collecting data does not depend on a cloud service.
When the link drops, the node keeps collecting and keeps its own local history. Whether readings headed upstream survive the outage depends on the app. HotLoop Edge queues them on disk, in order, and sends them when the link returns, which suits remote sites on satellite or cellular uplinks.
We tested it on EmberRTOS 0.1.6 in our lab, with HotLoop Edge reading a simulated plant at 100 readings a second and the uplink cut for more than eleven minutes. The local history had no gaps, and all 95,000 readings reached the upstream broker in order, with none lost and none counted as dropped.
The queue has a limit, 64 MiB by default, which is roughly forty minutes at that rate. A longer outage or a faster plant drops the oldest readings first, and Edge counts every one in its diagnostics instead of dropping them silently. A power cut or crash while the link is still up can cost the readings from about one poll that were not yet confirmed.
Answers for the security and compliance review.
How does EmberNet collect industrial data without exposing the plant network?
EmberNet collects data at the edge node using read-only collectors over the industrial protocol the device already speaks. The data is processed locally on the edge node. When it needs to leave the plant, it goes outbound over EmberFLUX on port 443 to a zero-trust overlay. No inbound port is opened on the plant network, and no firewall rule is added.
Where does EmberNet sit in the Purdue Model?
EmberNet edge nodes sit at Level 1 and Level 2 of the Purdue Model, on the plant network with the PLCs and SCADA systems they read. EmberFLUX creates an outbound-only overlay from Level 2 to Level 4 and above, so data moves up without opening an inbound path down into the control network.
Which IEC 62443 requirements does the EmberNet architecture address?
The outbound-only transport and zero-trust overlay address IEC 62443-3-3 SR 5.1 (network segmentation) and SR 5.2 (zone boundary protection). The read-only collector constraint addresses SR 2.1 (authorization enforcement). The immutable OS and auto-rollback patching address SR 7.6 (network and security configuration settings). EmberNet does not address requirements in IEC 62443-2-4 (supplier security requirements) or the full IEC 62443-4 device security requirements, which are the responsibility of the device OEM.
What happens when the connection to the cloud is lost?
The node keeps working. EmberRTOS has no cloud dependency for local operation, so the apps on the node keep collecting and keep their own local history while the link is down. What happens to readings headed upstream depends on the app. HotLoop Edge holds them in a disk queue and sends them in order when the link returns. In a lab test on EmberRTOS 0.1.6 with the uplink cut for more than eleven minutes at 100 readings a second, the local history had no gap and all 95,000 readings reached the upstream broker. The queue has a limit, 64 MiB by default, roughly forty minutes at that rate. Past the limit the oldest readings are dropped first, and the count is reported rather than hidden.
Can EmberNet forward OT data to a SIEM or historian?
Yes. Data collected at the edge can be forwarded outbound to your time-series historian, Splunk, Microsoft Sentinel, or any SIEM that accepts a webhook, syslog, or REST feed. The forward is outbound from the edge. No inbound port is required on the plant network.
Ready to collect from your plant floor?
Tell us what you are running and an engineer will walk you through how EmberNet connects to it.