Industry

Seven Questions to Ask Before You Put Security Monitoring on Your PLC Network

Security monitoring on a plant network is not the same purchase as security monitoring in an office. The network carries machines that make product, and the people who run it have good reasons to be careful about anything new that touches it.

So here are seven questions I would ask any vendor before I let a monitoring tool near a PLC network. I will answer each one for EmberSecurity, using what our public documentation says, so you can check me.

1. Does it scan my plant?

Some tools find devices by probing the network. EmberSecurity does not. Its inventory is learned from traffic, and nothing is scanned. The OT protocol sensor reads the industrial protocols on the wire and records who talked to which PLC, what they asked, every write, and every device it has seen. Each device is marked New or Known.

2. Does it need a new port or a new path off the site?

No. Everything EmberSecurity reports leaves the box over Flux on TLS port 443, the same outbound connection the box already uses. EmberSecurity opens no other port on the box and needs no other path off the site. A plant that allows only outbound 443 needs no firewall change to get security reporting.

3. Does it need internet access to stay current?

The sensors' rules are built into each release. A new rule set arrives as a normal update, and the box needs no extra internet access to get it. That matters for sites where every new outbound path is a change request.

4. Does it sit in my control loop?

It should not, and ours does not. EmberSecurity watches and reports. It does not change a PLC, and it is not in the path of a control loop. The part that decides what traffic is allowed is Plasma, EmberNet's network controller. EmberSecurity reports what Plasma refused, by destination and port, when Plasma's edge firewall is switched on.

I like that split. The thing that watches should not be the thing that can stop a machine.

5. What does it show when a sensor dies?

An empty alert queue is only good news while the sensors are reporting. The network watch, the OT protocol sensor, and the runtime guard each send a heartbeat, so a container that has stopped is shown as stopped. In EmberCORE, the Command view counts how many boxes are reporting and how many have been silent for more than 15 minutes, and a heat strip gives every box its own cell. A silent sensor is never mistaken for a quiet network.

6. Who can see my data?

Every box reports under its tenant and its own box identity. EmberCORE applies your tenant's filter on the server for every request, before it asks the central store anything. A tenant user sees only their own tenant's boxes and events, and a request for another tenant's alert or box is refused. Fireball's support staff can see every tenant to help. The rule is enforced on our servers, not just hidden on the screen.

Inside your company, roles decide what people can do. Engineers and above, and Auditors, can read every view. Admins also acknowledge, assign, and close alerts and set maintenance windows.

7. Does it leave a record of what my team did?

Every alert can be acknowledged, assigned, and closed, and closing takes a note. Those actions are recorded with who did them and when, and they appear in the audit trail. When someone asks how your team handled an event six months ago, you read the note.

What the answers add up to

Put the seven together and you get a monitoring layer that learns from traffic instead of probing, leaves through the one connection your site already allows, brings its own rules, stays out of the control path, tells you when it goes quiet, keeps each tenant apart, and writes down what your people did. It lives in the EmberCORE console your team already signs in to, so there is no second tool to learn.

It also sits inside a bigger design. If you are still deciding how far to trust a network perimeter, read our whitepaper, The Purdue Model Is Dead, and The Literal Cost of Seconds for what a stopped line costs. Both are on the Fireball resources page.

What to do next

Take the seven questions to your current vendor, or to the next one you evaluate. Where an answer is vague, ask for it in writing.

For ours, the EmberSecurity overview has the full detail on the four containers and how reporting travels. When you are ready to see it on your own network, tell us about your plant and its PLCs and we will show you what EmberSecurity sees.