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

Least privilege in OT: who may watch, who may operate, who may change

Least privilege in a plant sorts into three tiers: who may watch, who may operate and who may change. Here is how each tier holds up on Modbus, MQTT and shared control room logins.

Least privilege in OT means every person, program and device gets only the access its job needs. In a plant that sorts into three tiers: watching (read-only), operating (alarms and the commands the procedure allows) and changing (configuration, logic and credentials). Keep each tier on its own accounts, so a read-only screen never becomes a write path.

What does least privilege look like in a plant?

It looks like three groups of people with three kinds of access. The split below is my own.

TierTypical peopleAllowed
WatchManagers, auditors, customers, remote supportScreens, trends, alarm lists, reports
OperateShift operators, field techniciansAcknowledge alarms, start and stop within procedure, change setpoints inside limits
ChangeControl engineers, integratorsConfiguration, logic, alarm rules, device credentials

The 2013 edition of IEC 62443-3-3 lists least privilege among the common constraints for control system security and covers authorization under foundational requirement 2, use control (the series is covered in IEC 62443 explained for asset owners, integrators and device makers). No access tier replaces the safety system: trips and interlocks have to hold whoever is logged in.

How do you restrict write access to PLC registers?

Mostly in front of the PLC, because plain Modbus/TCP cannot tell who is asking. A request carries a transaction identifier, a protocol identifier, a length, a unit identifier, a function code and data, and no field for a user.

The Modbus TCP implementation guide’s access control is a list of allowed IP addresses, so any program on an allowed machine can write. I put the watch tier on a path that only reads, such as a gateway that polls the PLC and publishes values upward, and keep write access to the few hosts that need it. IoT network segmentation for plants covers which zone each device belongs in.

The Modbus/TCP Security specification closes part of the gap. It runs Modbus over TLS on port 802, and the client’s role travels in an extension of its X.509v3 certificate. The server checks that role against its own roles-to-rights rules, and a request the role may not make gets exception code 01, Illegal function. How roles map to rights is left to each vendor, so check what a device enforces before relying on it (client certificates are covered in X.509 client certificate authentication for devices).

Where do read-only users break down in industrial systems?

Read-only access breaks where a viewer needs one small write, such as an on-call engineer who wants to acknowledge an alarm from a phone at night.

I would rather move that person into the operate tier with a named account than add exceptions to a viewer role. The other weak spot is the shared control room login: everyone on shift uses it, it ends up with operate rights or more, and the audit trail shows the account rather than the person.

Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Its groups add permissions on top of the built-in Owner, Admin and User roles and never take one away. The IoT viewer group template sees every IoT page and list and is given no right to change anything; the IoT operator template watches and edits devices and writes their attributes, with no device credentials and no creating or deleting devices. By default, users send basic device commands and administrators send privileged and critical ones, as the page on groups and permissions lists.

How do you limit what an MQTT client can subscribe to?

On the broker, with a topic access list per client identity. The MQTT 5.0 specification says a server implementation should restrict which topics a client may publish to and which topic filters it may subscribe with, and should consider limiting broad filters such as #.

I give each device its own credentials and a topic pattern that contains its own identifier, so it publishes its telemetry, receives its own commands and nothing else. No field device should be able to subscribe to #, or one leaked device password reads the whole site.

Frequently asked questions

Should operators share one control room login?

No. A shared login hides who acknowledged an alarm or changed a setpoint, and removing one person means changing the password for everyone. Give each operator a named account in the operate tier, with a sign-in method fast enough for shift changes.

Does least privilege apply to devices and integrations?

Yes. A gateway that only publishes telemetry has no reason to read other devices’ topics, and a reporting integration that only reads data should use a read-only key. Programs can keep their access for years without anyone watching them sign in.

How should vendor remote access fit the three tiers?

Give the vendor a named account of their own, in the watch tier by default, and raise it to operate or change only for the session that needs it. Switch the access off when the work ends.

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.