
MFG · Manufacturing
Field note · Manufacturing · Plastics & Packaging
The vendor’s remote-access box nobody inventoried
Open the door of a moulding machine's cabinet and look up. Taped to the inside of the door, there is often a small antenna, and a cable running down to a box the size of a paperback.
Every machine arrives on a plant floor with a way for its builder to reach it. A press, a moulder, a printer, a palletiser: each is a complete product, and its maker expects to support it from a distance. So a cellular modem goes into the cabinet, or a VPN appliance clips onto the DIN rail, or an agent on the HMI quietly calls out to the builder's cloud. It earns its keep in the first weeks of commissioning, when faults are frequent and the builder's engineer is a remote session away.
Then the project closes. The engineer flies home, the punch list is signed, and the box stays, because nobody asked for it to go and removing it means losing support. Years later it is usually still live, still reachable from outside, and still missing from every list the plant keeps.
The plant bought a press
The network drawing, where there is one, shows the plant's own equipment: switches, servers, the controllers the plant specified. The builder's remote link belongs to the machine. It came inside the machine's cabinet, runs off the machine's power supply, and is documented, if anywhere, in the machine's manual.
The contract agrees. Remote support is written into the service agreement as something the builder provides, not a device the plant hosts. The procurement file says "remote diagnostics included". It doesn't say that a device with its own address, its own credentials and its own route to the internet now lives on the plant network. Nobody on the plant side got anything wrong. The line between the builder's product and the plant's network was simply never drawn.
The modem came free with the press. That's exactly why nobody wrote it down.
And they multiply. Each builder brings its own box, and on a flat network each box can reach every machine, not just its own. In plastics and packaging, where the floor is a federation of vendor networks, one link per builder is normal. In general manufacturing it happens line by line, with the integrator's link sitting alongside.

Finding it without stopping anything
You can't find the box by asking the network to identify itself. An active scan sends packets everywhere and waits for replies, and some controllers answer an unexpected packet by stopping. On a running line that risk isn't worth taking. A scan also only reaches what the scanner can route to, and a cellular modem has a route out that the plant network can't see from inside.
Three things work together, and none of them changes anything.
Listen. A remote-access appliance has to talk to be useful: it holds a tunnel open, checks in on a schedule, carries sessions when an engineer connects. That traffic has a shape. An address on the machine network holding a long-lived encrypted connection to somewhere outside, or looking up a hostname that belongs to a machine builder, is a strong signal even when the device has no label.
Walk. Open the cabinets with a torch. A modem has an antenna. A VPN appliance has a logo and a status light. A cloud agent shows up in the HMI's installed software, or as a tray icon the operators learned to ignore long ago. On a mid-sized floor it takes an afternoon, and it finds the boxes that happened to stay silent during the capture.
Read. Service contracts and commissioning handover packs say what remote support was agreed, and sometimes name the device. Read beside the capture and the walk-down, they close the gap both ways. A contract with no device found is a question for the builder; a device with no contract is a question for the plant.
Together they give a list the plant can hold: each link, its machine, its builder, its path out, and whether it was talking during the capture.
Sample · illustrative, not a client site
| Machine | Link | Seen in capture | Contract | Owner on site |
|---|---|---|---|---|
| Moulder 3 | Cellular modem in cabinet | Yes, daily check-in | Service agreement, remote diagnostics | Not named |
| Palletiser | VPN appliance on DIN rail | Yes, idle tunnel | Expired | Not named |
| Press line B | Cloud agent on HMI | No | Not found | Maintenance lead |
Keep the support, change its shape
Ripping the link out is rarely the answer. Remote support is worth having, and a plant that cuts it off finds the builder's engineer on a plane instead of on a session, at the plant's expense. Keep the support and change three things about it.
Brokered. The builder connects to a point the plant controls, never straight to the machine. That point sits in the industrial DMZ, Level 3.5 in the Purdue model, and a session opens inward from there to the one machine that needs it. The modem in the cabinet goes, or is disabled, because the route out now belongs to the plant. ISA/IEC 62443-3-2 treats this as a conduit between zones, placed on purpose rather than wherever the box happened to land.
Time-boxed. A session exists when someone on site opens it, for as long as the work takes. A standing tunnel, live at three in the morning just in case, is what made the box a way in. A request, an approval and an end time replace it, and the maintenance team becomes the people who say yes.
Logged. For any day, the plant can say which builder connected to which machine, when, and for how long. For a plant manager this matters most, because the remote link stops being something that happens to the plant and becomes something the plant did. NIST SP 800-82 Rev. 3 takes the same view: one controlled path, a decision for each use, and a record.

None of this needs new software between the builder and the machine, and none of it happens in week one. In the Range method the capture, walk-down and contract review come first, the list goes to the plant in writing, and nothing in a cabinet changes until the plant authorises it with a named person beside the work. You can't broker a link you don't know you have.
Sources
New to the vocabulary? Learn OT covers it from zero, free.
From the lab

