Modbus security has to come from around the protocol, because Modbus itself carries no authentication and no encryption: a meter answers any valid request, whoever sent it. Energy sites protect meters and inverters by keeping Modbus off untrusted networks, limiting who can write, and sending data out through a gateway that dials out.
Energy meters and inverters raise the stakes, because their readings feed sub-billing, export limits and EV charging. A forged reading there changes what a controller does next.
Does Modbus have authentication or encryption?
Not in its classic serial and TCP forms. The Modbus Application Protocol specification defines a frame of a function code and data, and the serial and TCP versions add only an address, an error check or a header; none of them carries a user, a key or a signature. The serial line specification even describes its security as parity and frame checking with a CRC or LRC, an error check whose algorithm is printed in the specification itself.
NIST SP 800-82r3 notes that many OT protocols have no authentication at any level, which opens the door to replaying, modifying or spoofing data. The Modbus Organization’s Modbus/TCP Security specification wraps Modbus/TCP in TLS on port 802, with X.509 certificates on both client and server and role-based authorization, while plain Modbus/TCP stays on port 502. It helps only where both ends support it.
Can Modbus messages be spoofed on RS-485?
Yes. Anything wired to the pair can read every frame and send its own, and the meters cannot tell it from their master. The serial line is a master-slave bus: one master at a time, up to 247 slaves with addresses 1 to 247, and slaves that only ever answer the master.
Address 0 is the broadcast address. Every slave must accept a broadcast write and none replies, so a forged broadcast leaves no answer on the wire. If an inverter’s export limit or an EV charger’s current depends on a meter reading carried over Modbus, a device spliced into that line can change what the inverter or charger does. Finding the right register takes only the device’s documentation and the rules in Modbus register addressing.
How do you secure Modbus TCP devices?
Treat every Modbus device as trusting its whole network, and shrink that network. These are the measures roughly in the order I would apply them.
- Never expose port 502 to the internet; port forwarding to a meter or inverter publishes it to anyone who scans.
- Put meters and inverters in their own zone, behind a firewall that lets only the gateway or master reach them, as in IoT network segmentation for plants.
- Where writes are not needed, block them. NIST SP 800-82r3 describes OT firewalls with built-in Modbus parsers for deep packet inspection; with one, reads (function codes 03 and 04) can pass while write codes such as 06 and 16 are stopped.
- Turn off remote writes in the device’s own settings where it offers that option.
- Lock the cabinet. NIST lists restricting physical access, with locks, card readers or guards, among the main OT security objectives.
- Use Modbus/TCP Security where both ends support it.
Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Hermetry Edge runs on a licensed gateway at the site and reads Modbus RTU over RS-485 and Modbus TCP devices, depending on the gateway model. The gateway dials out over TLS with its own device certificate, so nothing on site needs to accept connections from the internet, and commands never travel over an unencrypted session.
The serial line between any gateway and its meters is still plain Modbus, so the cabinet lock and the zone still matter. For a multi-site setup on energy sites, see automatic energy meter reading across many sites.
Frequently asked questions
Can a VPN make Modbus TCP secure?
A VPN encrypts the path it covers and decides who may join it, but every Modbus device inside it still answers any valid request from any VPN user or compromised machine on the same network. Combine it with a zone that lets only the master or gateway reach the meters, and keep writes blocked where they are not needed.
Does Modbus RTU’s CRC stop tampering?
No. The CRC detects transmission errors; it does not prove who sent a frame. The algorithm is published in the Modbus serial line specification, so anyone who changes a frame can compute a valid CRC for the new contents. Integrity against tampering has to come from somewhere else, such as a secured transport or physical protection of the line.
How would you notice a forged Modbus write?
Watch for writes you did not expect. NIST SP 800-82r3 notes that some intrusion detection and prevention products include signatures for OT protocols such as Modbus. On Modbus TCP, I would alert on any write function code from an IP address other than the master’s, and regularly compare the limits read back from each inverter with the values you configured.

