The Gap in Factory Security Is Vendor Remote Access
Most plants put up firewalls and separate the office network from the production network. Yet the remote paths equipment vendors use often fall outside that perimeter. To respond quickly to breakdowns, vendors routinely install remote control software on HMI PCs or mount an LTE modem inside the control cabinet and leave it connected around the clock.
The problem is that these paths leave almost no trail. The plant cannot tell who logged in, when, to which machine, or whether they changed the PLC logic. However well the networks are segmented, a single LTE modem becomes a separate internet doorway that never passes through the firewall. If the vendor's laptop is compromised, that doorway becomes an attack path.
Start With a Full Inventory of Remote Access Paths
You cannot control what you have not found.
On a line of around 50 machines, it is not unusual for this inventory alone to turn up several paths the plant did not know about. Modems inside cabinets are often missing from drawings, so a physical walkdown is needed.
Move to a Request–Approve–Connect–Close Flow
The core idea is to turn an always-open door into one that opens only on request.
Consolidate all paths through a single remote access gateway (jump server). Vendors reach the gateway and nothing else; from there they connect only to approved machines. This fits the zone-and-conduit model described in IEC 62443. Issue individual accounts per vendor technician, enforce multi-factor authentication, and restrict each account to a defined set of machines.
What to Capture During a Session
Write operations on running equipment need separate handling. Allow read-only monitoring remotely, but tie logic downloads and parameter changes to on-site supervision or a stopped production state. Remote access history should feed into your existing PLC change management and backup system, so "who logged in and what changed" lives in one place.
Rolling It Out in Stages
Changing everything at once invites pushback from the floor. A three-stage rollout works better.
Write remote access conditions, mandatory gateway use, and log delivery obligations into vendor contracts. Answer the operators' fear that "the line will sit idle while we wait for approval" with an emergency procedure: the night-shift lead approves immediately after a phone check, and the work is reviewed afterward. Emergency sessions are recorded and logged just like any other.
How POLYGLOTSOFT Helps
POLYGLOTSOFT builds remote access request and approval workflows linked to the equipment master in your MES. Approvers are assigned automatically based on machine ownership and production status, and a dashboard ties access history to PLC change history. If you want to bring vendor remote access under control without slowing down breakdown response, talk to POLYGLOTSOFT.
