Who Told That PLC to Do That? Check Every Write Against Your Maintenance Window
The call usually comes in the same way. A setpoint is not where it was yesterday, or a line stopped and nobody on the shift touched anything. Before anyone asks what happened, a better question comes first: who told that PLC to do that, and were they supposed to?
Most plants cannot answer it quickly. The honest answer is a mix of memory, a shared logbook, and a laptop somebody remembers plugging in. I think a plant should be able to answer it in a minute, from one screen, with a name and a time.
A write is the event that matters
A PLC that is being read from is doing its job. A PLC that is being written to is being told to change what it does. That is the event you want on a record, every time, whether the source is an engineer on a planned change or a device that has no business on the network.
On every EmberNet edge box, the OT protocol sensor reads the industrial protocols on the wire. It records who talked to which PLC, what they asked it to do, every write, and every device it has seen. It learns all of this from the traffic itself and scans nothing, so it adds no probing to a network that already has enough going on.
One screen for what your PLCs are being told
The EmberSecurity area in EmberCORE has a view called OT activity. It shows who talks to which PLC, a log of every PLC write, and an inventory of the devices EmberSecurity has seen. Each device is marked New or Known, and each write is marked as inside or outside a maintenance window.
That last mark is the useful one. A write on a Tuesday afternoon is not interesting by itself. A write that lands outside the hours when your team expects changes is the one worth a phone call.
Tell it when changes are expected
A maintenance window in EmberSecurity is a weekly time when PLC writes are expected. A tenant Admin sets them, and they apply to the whole tenant. For example, you might say that changes happen on Sunday from 06:00 to 10:00, and anything outside that is a question.
One detail matters here. With no windows set, every write counts as outside a window. That is the right default, because the system should not assume a change was planned. It also means you should set your windows first, or the OT activity view will mark everything and tell you very little.
What Monday morning looks like
Say you open EmberSecurity and the OT activity view shows a write outside the window. Here is how that goes.
- Open the alert and read the title, the severity, then the box and the source.
- Decide what it is. A write outside the maintenance window is worth a call to the plant. An unfamiliar device on a PLC leg is a question for whoever installed equipment this week.
- Acknowledge it, so the team knows someone has seen it.
- Assign it by email to the person who will follow up.
- Close it with a note. The note is required, and it should say what it was and what was done, because the note is what the next person reads.
Acknowledging, assigning, and closing are recorded with who did them and when, and they appear in the audit trail. When an auditor asks how your team handled a PLC change, the answer is already written down.
The plant network map helps here too. It draws one box's devices by Purdue level, from what EmberSecurity heard on that box in the last 24 hours. Devices first seen in that time are marked, and a write outside the maintenance window draws a red line you can follow to the alert.
What it does not do
I want to be plain about the boundary. EmberSecurity watches and reports. It does not change a PLC, and it does not sit in the path of a control loop. A monitoring tool that can touch your control path is a second thing to worry about, so this one stays out of it.
Deciding what traffic is allowed is the job of Plasma, EmberNet's network controller, which runs an edge firewall on each box. EmberSecurity shows you what Plasma refused, by destination and port, in the Blocked traffic view, when Plasma's edge firewall is switched on.
Your team reads all of this in EmberCORE, with the sign-in it already has. Engineers and above, and Auditors, can read every view. Admins can also acknowledge, assign, and close alerts and set maintenance windows.
What to do next
Start with the part that costs nothing: write down the hours when changes to your PLCs are really expected, and who is allowed to make them. That list is your maintenance window, and it is useful whether or not you ever buy anything from us.
Then read how the EmberSecurity area works in the console documentation, or see the EmberSecurity overview for the four sensors on every box. If you want to see it on your own PLCs, tell us about your plant and an engineer will show you what it sees.