EmberNet's Plasma Gives Every Edge Box One Door and Puts a Firewall in Front of the PLCs
MACEDONIA, Ohio, November 21, 2026: Fireball Industries today announced Plasma, the network controller of its EmberNet industrial edge platform. Plasma does two jobs a plant has always had to buy, install, and secure separately. It manages the routers, access points, and gateways across every site from EmberCORE, the console plant teams already sign in to. And on each EmberNet edge box it runs an edge firewall that gives the box one way in and out of the plant network and stands between the plant network and the PLCs, so a device that should not reach a controller cannot.
The problem
Most plant networks were never designed. They grew. A switch went in for a new line, a gateway went in for a vendor, and a laptop got plugged into the PLC network because that was the fastest way to fix something on a Friday. Every one of those connections is a path to a controller that runs the process, and very few plants can say with confidence which ones are still open.
The usual answer is another firewall, another management tool, and another specialist to run them. Plasma puts both jobs inside the platform the plant already runs.
What Plasma does
One door per box. With Plasma's edge firewall switched on, an EmberNet edge box takes nothing new from the plant network. No service listens there. Out to the plant network, the box uses TCP 443 plus DNS, DHCP, NTP, and ping, and everything else is dropped and counted. Port 443 is the one path off the site, the same path Flux already uses, so the box adds no new opening to the plant's own firewall.
A firewall in front of every PLC. When a box has a PLC leg, Plasma sits in line between the box and the plant switch and between the box and the PLC switch. Each PLC gets its own entry in the policy: its name, its address, and the protocols it speaks, such as Modbus, EtherNet/IP, Profinet, OPC UA, or CODESYS.
- Plasma matches each PLC by its IP address and its hardware address together, so a device plugged into the PLC leg cannot reach a controller by copying an IP address.
- A device or protocol that is not listed is dropped and counted.
- The plant network and the PLC leg are never connected to each other through the box.
- Nothing on a PLC needs reconfiguring, and industrial protocols that depend on broadcast keep working.
- A box whose single port carries the PLC networks as VLANs is guarded one VLAN at a time, even where several VLANs reuse the same addresses.
Built for a plant that cannot stop.
- A new policy is checked before it is applied, applied in one step, and the last good policy is kept. A policy that does not validate never reaches the wire.
- A planned Plasma restart, such as an automatic update, keeps the box's path to the plant and its network address, so traffic keeps flowing and a historian sees no gap.
- If Plasma stops, the box fails in the safe direction. Management and Flux traffic, and the cyclic traffic between the box and its PLCs, keep flowing under a fallback policy that allows the same traffic and nothing more, while anything that would cross between the plant network and the PLC leg stays closed. The box restores its normal path on its own, without a person.
- Losing the link to Plasma's controller changes nothing on the wire. The box keeps enforcing the policy it has.
Each tenant's own rules. A tenant that needs its boxes to reach something beyond the defaults, such as a site historian, adds it to the tenant's allowlist in Plasma by address or name and port. The allowlist applies to every box in that tenant and never affects another tenant.
Every refusal on the record. Every drop is counted. The counts reach EmberCORE through EmberSecurity every 30 seconds and appear in the Blocked traffic and Threat map views, so a count that suddenly rises points straight at a device that is new, misconfigured, or not supposed to be there.
The whole network in one console. In EmberCORE, under Network and then Network devices, Plasma keeps a live inventory of the routers, access points, and gateways at every site, with a topology graph, monitoring history from one day to a year, priority-sorted alerts, and a map of where each device sits. Devices are configured from templates, and each one carries a config status apart from its health, so a device that someone changed by hand shows up as drifted from its template before the next push quietly wipes the change out.
"Every plant we walk into has a path to a PLC that nobody remembers opening," said Patrick Ryan, CTO of Fireball Industries. "Plasma closes those paths at the box, names every controller and the protocols it is allowed to speak, and fails safe when something goes wrong, because a firewall that stops a machine is not one a plant will keep. And it lives in the same console your team already uses, not in another product someone has to learn."
What it means for your plant
For a plant manager, the PLCs that run the line can be reached only by the devices and protocols your team has named, and a firewall update or restart does not cost a minute of production. For an IT/OT lead, the network equipment at every site is managed from one console, with configuration drift caught before it disappears. For the security reviewer, each box exposes no service to the plant network, opens no new path off the site, and keeps a count of everything it refused.
Availability
Plasma's network management is in EmberCORE today for tenants with a Plasma organization, for tenant Admins and Engineers. The edge firewall runs as a container on each EmberNet edge box, updates itself from the stable channel like the rest of the box, and is switched on from the box's setup app once the plant-side port is chosen.
Learn more
Documentation is at docs.embernet.ai/docs/networking/plasma-edge-lockdown and docs.embernet.ai/docs/dashboard/network-devices. To see Plasma on your own network, contact Fireball Industries at fireballz.ai/get-a-quote.
About EmberNet
EmberNet is the industrial edge platform built by Fireball Industries. It brings together the EmberRTOS real-time operating system, Flux zero-trust networking, the EmberCORE console, and the apps a plant runs, working as one, with no cloud dependency and no vendor lock-in. Learn more at embernet.ai.
About Fireball Industries
Fireball Industries has been building, deploying, and maintaining industrial automation systems since 2022. It is headquartered in Macedonia, Ohio, with an engineering office in Yuma, Arizona, and operations in Zacatecas, Mexico. Fireball does turnkey automation, UL 508A control panels, and TÜV machine safety assessments, and it is EmberNet's master systems integrator. Learn more at fireballz.ai.
Media contact
Nidia Verdugo, nidia@fireballz.ai