New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Field network security at remote sites: switches, serial links and physical access

What protects the network inside an unmanned site: switch ports, SNMPv3, RS-485 pairs anyone can tap, cabinet locks and inventories that do not upset the process.

Field network security at a remote site protects the network inside the fence: the switch, the serial lines and the cabinet that holds them. Disable unused switch ports, manage the switch over SNMPv3 rather than community strings, treat every RS-485 pair as open to anyone who can touch it, and lock the cabinet.

I work on field connectivity for unmanned sites. Remote access is a separate topic; this post covers what someone can do once they stand next to the equipment.

How do you secure industrial Ethernet switches at a remote site?

Switch off every port that nothing uses, change the default password, and manage the switch only over an authenticated protocol. NIST SP 800-82 Rev. 3, NIST’s guide to operational technology (OT) security, lists disabling unused ports and services, after testing that this will not affect operation, and changing all default passwords.

  • Disable spare ports in the configuration, not only by leaving them empty. A live spare port invites a laptop.
  • RFC 3410 calls SNMPv1 and SNMPv2c fundamentally insecure, because they rely on plain-text community strings, and both were declared Historic. SNMPv3 adds authentication and privacy through its User-based Security Model.
  • The standard IF-MIB gives every port an operational status, and the switch can send a linkUp notification when a port leaves the down state. I poll that status like the SNMP at remote sites UPS values and alarm on a port that comes up while nobody is booked on site.

Zones and VLANs belong to the IoT network segmentation plan, and default passwords at pump stations have their own checklist.

Is an RS-485 network secure?

No. An RS-485 Modbus line carries no authentication, so anyone who clips onto the pair can read every frame and send their own. The Modbus serial line specification connects all devices in parallel on one trunk, and its frame holds only the device address, a function code, data and a CRC, which detects transmission errors but proves nothing about the sender.

NIST SP 800-82 says many OT protocols have no authentication at any level, which leaves room to replay, modify or spoof data. Modbus/TCP Security, on port 802, wraps Modbus in TLS, and it is defined for TCP. On a serial pair the protection is physical: keep the trunk in locked cabinets and closed conduit, leave no spare terminals on the bus, and make the gateway the only master.

Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Hermetry Edge runs on licensed gateways and routers and reads field devices such as Modbus RTU over RS485 and Modbus TCP, depending on the model. The gateway dials out over TLS with its own device certificate, so nothing on site needs to accept connections from the internet, and revoking that certificate ends the gateway’s live session at once.

What does physical security at a remote site need to cover?

Locks on the cabinet, a record of who opened it, and controllers kept in run mode. NIST SP 800-82 says equipment cabinets should be locked when not required for operation or safety, and PLC keys left in the Run position unless someone is programming.

The same guide warns that a remote location secured by little more than a padlock can give whoever gets past it access to an OT network segment. A door contact on the cabinet, wired to an input and alarmed, gives you the record a padlock cannot.

Is it safe to scan an OT network at a remote site?

Only with care, and preferably during a planned outage. NIST SP 800-82 warns that active scans may cause device instability or interfere with the process, and calls passive scanning, which only watches existing traffic, ideal for sensitive devices, although it cannot see a device that is not communicating.

By the same guide, automated network scanning does not apply to serial networks at all. At a small site I take the inventory with the cabinet open: every switch port, what is plugged into it, and every device on each RS-485 trunk.

Frequently asked questions

Does a VLAN on the site switch protect the serial devices behind a gateway?

No. A VLAN separates Ethernet traffic between switch ports, while the serial devices sit on an RS-485 pair behind the gateway. Someone with access to that pair reaches them directly, so the trunk needs a locked cabinet, closed conduit and no exposed spare terminals.

Is SNMPv2c acceptable on a closed site network?

RFC 3410 calls SNMPv1 and SNMPv2c fundamentally insecure because the community string travels in plain text, so anyone who can capture the traffic can read it. Where the switch and the poller support SNMPv3, I use it with authentication and privacy.

Should a remote cabinet have a door alarm?

I fit one wherever the cabinet holds network equipment. NIST SP 800-82 describes access monitoring as recording presence rather than preventing entry, and such systems can alert on unauthorised access. A door contact on a spare input does that cheaply.

Share

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.