News

EmberNet Builds a Security Operations Center Into the Console Plants Already Use

MACEDONIA, Ohio, November 19, 2026: Fireball Industries today announced EmberSecurity, the security monitoring layer of its EmberNet industrial edge platform, and the EmberSecurity area in EmberCORE, a security operations center built into the console plant teams already sign in to. EmberSecurity answers the questions a plant leader asks after something odd happens on the floor: what is on my network, who told that PLC to do that, and are my sensors still alive. It does it without scanning the plant, without a new port, and without a second console to learn and secure.

The problem

A plant network is a quiet place until it is not. A device appears on a PLC leg that nobody installed. A PLC takes a write at an hour nobody planned. A shell opens inside a container where none belongs. Each one is a small event, and each one is the kind of thing an IT/OT team needs to see the day it happens, not the day the line stops. The plant floor is where those questions are hardest to answer.

What EmberSecurity does

Four containers run on each EmberNet edge box, and each one has one job.

  • Network watch reads the PLC leg and the plant network for traffic that matches a known attack, and for traffic that should not exist on that leg.
  • OT protocol sensor reads the industrial protocols on the wire: who talked to which PLC, what they asked it to do, every write, and every device it has seen. It learns from traffic and scans nothing.
  • Runtime guard watches the box itself for shells started inside containers and for unexpected outbound connections.
  • Integrity and posture watches files and configuration on the box for changes.

Everything they see lands in the EmberSecurity area of EmberCORE, where your team already works:

  • An alert queue to acknowledge, assign, and close each alert. Closing takes a note, and every action is recorded in the audit trail with who did it and when.
  • OT activity with every PLC write marked as inside or outside your maintenance window, plus an inventory of every device seen on the PLC leg, each marked New or Known.
  • A plant network map that places each device by Purdue level, and a threat map of the outside addresses that tripped the network watch.
  • Blocked traffic, showing what Plasma refused, by destination and port, when Plasma's edge firewall is switched on.
  • One view per box, with all four containers and when each one last reported.

Why it is different

It is already where your team works. EmberSecurity is not a separate product with its own login. Engineers, admins, and auditors read it in EmberCORE, signed in the way they already sign in, and an Admin can acknowledge, assign, and close alerts.

It adds no new door to the plant. Everything EmberSecurity reports leaves the box over Flux on TLS port 443, the same outbound connection the box already uses. A plant that allows only outbound 443 needs no firewall change to get security reporting, and the detection rules ship inside each release, so the box needs no extra internet access to stay current.

A quiet sensor never looks like a calm network. The network watch, the OT protocol sensor, and the runtime guard each send a heartbeat every 30 seconds. A container that stops is shown as stopped, so an empty alert queue means good news only when the boxes are reporting.

It keeps tenants apart on the server. Every box reports under its own tenant and box identity. EmberCORE applies a tenant's filter on the server before it asks for anything, so a tenant sees only its own boxes and events, Fireball staff see every tenant, and a request for another tenant's alert is refused.

It watches and reports. EmberSecurity does not change a PLC and does not sit in a control loop. Plasma decides what traffic is allowed, and EmberSecurity shows you what Plasma refused.

"Plant leaders do not need another console that only a security specialist can read," said Patrick Ryan, CTO of Fireball Industries. "They need to open the one they already use and see what is on the network, what touched a PLC, and whether the sensors are alive. We built it to watch and report only: it never reaches into a PLC, and it sends everything out over the connection the box already has."

What it means for your plant

For a plant manager, an unplanned PLC write or a new device on the floor shows up with a time and a box, and the alert can be assigned to the person who follows up. For an IT/OT lead, one console and one sign-in cover all of your boxes, with every alert action on the record for the next audit. For the security reviewer, EmberSecurity opens no other port on the box and needs no other path off the site, and tenant separation holds on the server.

Learn more

To see EmberSecurity on your own network, request a demo at embernet.ai/embersecurity.html. Documentation is at docs.embernet.ai/docs/security/overview.

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