EmberNet
EmberSecurity

See what is on your plant network, and what it is doing.

EmberSecurity watches every EmberNet edge box for the things that matter on a plant floor: a device that should not be there, a PLC write nobody planned, a shell where none belongs. What it sees comes to one place, the EmberSecurity area in EmberCORE.

On every box

Four containers, each with one job.

Each one reports on its own, so a sensor that goes quiet is shown as quiet and never mistaken for a calm network.

Network watch

The network

Watches 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

The protocols

Reads the industrial protocols on the wire: who talked to which PLC, what they asked it to do, and every device it has seen.

Runtime guard

The runtime

Watches the box itself for shells started inside containers and for unexpected outbound connections.

Integrity and posture

The files

Watches files and configuration on the box for changes.

The EmberSecurity area

A security center inside EmberCORE.

Your team reads alerts, PLC activity, and box health in the console they already use, signed in the way they already sign in.

A tenant sees only its own boxes and events. Fireball staff see every tenant. The server applies that filter on every request, so it does not depend on what the screen shows.

What your team gets

  • An alert queue: acknowledge, assign, and close with a note, each recorded in the audit trail
  • OT activity: every PLC write, marked inside or outside your maintenance window, and an inventory of every device on the PLC leg
  • A plant network map that places each device by Purdue level, and a threat map of outside addresses
  • One view per box, with all four containers and when each last reported
  • Blocked traffic: what Plasma refused, by destination and port
Over EmberFLUX

No new port, no new path.

Everything EmberSecurity reports leaves the box over EmberFLUX on port 443, the connection the box already uses. A plant that allows only outbound 443 needs no firewall change to get security reporting.

EmberSecurity watches and reports. It does not change a PLC and it does not sit in a control loop. The part that decides what traffic is allowed is Plasma, whose edge firewall gives the plant network one way in and out of a box, TCP 443, and counts every packet it refuses. Those counts show up in the EmberSecurity area.

See how the platform fits together

See EmberSecurity on your own network.

Tell us about your plant and its PLCs, and we will show you what EmberSecurity sees.

Request a demo