TroutTrout
Control who reaches what · Named logins

Give everyone their own login. No more shared passwords.

OT identity means each person signs in as themselves before reaching a machine. Access Gate puts that login in front of PLCs and HMIs. Nothing is installed on them.

Last updated:

All DirectoriesAll Groups
Users & Groups
UserDirectoryGroupAccessAuth
Florian DoumencEntra IDEngineeringssh:22
https:443
MFA
Jane MartinTailscaleOperatorshttps:443MFA
Moxa (vendor)Access GateBella Enclavemodbus:502Time-bound
Sam ChenActive Dir.Maintenancessh:22
http:80
MFA
CNC machining centers along a shop-floor aisle

Shared accounts and missing MFA on OT

Operators often use one shared HMI account per shift, and vendors often share a password too. Older PLCs and HMIs do not support multi-factor authentication. Access Gate solves this with simple splash pages for users to authenticate.

Where identities come from

Three sources of named logins.

Access Gate uses the directories you already run. No new user database is needed on the plant floor.

01 · Staff

Your existing directory.

Staff sign in with the account they already have, from Entra, Okta, Active Directory or LDAP. Accounts are created and removed through your usual process.

02 · Plant

A separate OT directory.

Best practice is a distinct OT identity store, federated beside the IT one. If you have none, Access Gate can host one. Each directory keeps its own lifecycle, so an IT issue does not carry over to OT.

03 · Vendors

Access that ends with the job.

Vendors get scoped, time-bound access at the gate. They are never added to your directory and never hold standing credentials.

What every login carries

Every session is tied to one person.

Each login defines which machines a person can reach, and for how long. Each session is recorded for the audit.

Who.

The person, read from the directory.

  • Named person
  • Group from the directory
  • Staff or vendor
  • Second factor checked at the gate

What.

What they may reach, and for how long.

  • Machines assigned to them
  • Protocol: RDP, SSH, VNC or HTTPS
  • Window: 15 min, 1 h or 8 h
  • Access closes when the window ends

Record.

What happened, kept as evidence.

  • Session recorded
  • Name, machine and time logged
  • Sent to your SIEM over syslog
  • Revocations in the access history
One login, three uses

One login for floor and remote access.

Each person signs in with their own directory account. The same login is used for access on the floor and for remote sessions, and it is written to every audit record.

Diagram: one named user, synced from Active Directory and signed in through an Access Gate access screen, drives three uses: access to their own machines on the floor, recorded remote sessions, and an audit trail of who reached which machine and when.
01

On the floor.

Each person reaches only the machines assigned to them. Access is revoked automatically when the time window ends.

Zero Trust access control
02

Remote sessions.

The same login opens RDP, SSH or VNC in the browser, for staff and vendors. Each session is recorded.

Secure remote access
03

Audit trail.

Every login is logged with the name, the machine and the time. Send it to your SIEM over syslog.

OT compliance
Ways to give named logins on OT

Five ways to give named logins, compared.

The table compares who each login identifies, where MFA is checked, and what changes in the plant. More detail is in MFA for OT.

MethodWho the login namesMFA on machines that can'tWhat changes on the plant
Shared accountsNobodyA role or a whole shift. The individual user is not recorded.NoNo. The password is the only check.NoneNo change.
Local accounts on each machinePartialA person, on machines that have accounts. A PLC has none.NoNo. PLCs and older HMIs do not support MFA.HighAn account to create and remove on every machine.
Active Directory on the HMIPartialA person, on HMIs that can join the domain.NoNot on panels running Windows XP or 7, and not on PLCs.MediumThe HMI joins the IT domain, which makes the plant depend on IT.
PAM bastion or jump serverPartialThe person at the jump server. The machine receives a shared local account.At the hostYes, at the host. The connection from the host to the machine has no MFA.MediumA bastion to deploy and accounts to onboard.
Access GateUsed by Access GateThe personThe named person, at the machine.YesYes, at the gate before the machine. TOTP works offline.One routeNothing on the machines. One route on the existing router.
Prove every audit

What the frameworks ask about identity.

Each framework asks you to identify the person and check a second factor. Here is the requirement and what Access Gate gives you.

FrameworkRequirementWhat Access Gate gives you
CMMC Level 2 / NIST SP 800-171 3.5.1, 3.5.3Identify each user, and use MFA for network access and for privileged accounts.Named accounts from your directory, and MFA at the gate in front of machines that cannot do it.
NERC CIP-004Access management for personnel.Per-user, per-machine access rules, with access history and revocations in the logs.
NERC CIP-005-7 R2MFA on Interactive Remote Access, through an Intermediate System.MFA on every remote session at the gate, with each session recorded.
IEC 62443 FR 1 (SR 1.1, SR 1.2)Identify and authenticate human users, software processes and devices.The zone boundary authenticates each person, as the standard allows when the component cannot.
NIST SP 800-82Strong authentication and monitoring on remote access into an ICS.MFA and a recorded session on the same path.
A method you can follow

How to replace shared OT accounts with named logins.

Five steps to move a plant from shared accounts to named logins.

  1. 01

    List the shared accounts and the paths.

    Note every shared HMI login, vendor password and service account, and every way in that uses one: the VPN, the jump server, the modem in the cabinet.

  2. 02

    Choose where each identity comes from.

    Use your IT directory for staff. For plant accounts, add a separate OT directory, or let Access Gate host one. Give vendors time-bound accounts outside both directories.

  3. 03

    Put Access Gate in front of the machines.

    One appliance per site, connected beside the network. One route on the existing router sends machine traffic through it. Nothing is installed on the machines.

  4. 04

    Give each person their machines and a window.

    Assign machines per person or group, with a window of 15 min, 1 h or 8 h. Access Gate checks the second factor at sign-in. TOTP works offline, including on isolated sites.

  5. 05

    Retire the shared accounts and old routes.

    Close the access paths that Access Gate replaces. Keep one named break-glass account with an offline second factor and heightened logging, and test it.

Up in a day

Access Gate is up in a day per site, and took 4 hours per site at Thales. Removing the route undoes it.

FAQ

Questions about OT identity.

1

Route added on your existing router. Nothing is installed on the PLCs, HMIs or SCADA.

OT identity is knowing which named person opened each session to a machine. Shared HMI logins and vendor passwords do not record this. Access Gate checks each person against your directory before the session opens, and logs the session under that name.

Best practice is a distinct OT identity store, kept beside corporate Active Directory. Access Gate federates IT and OT directories side by side (Entra, Okta, AD, LDAP). If you have no OT directory, it can host one.

The factor sits in the network path, in front of the PLC. The PLC is untouched. No one reaches it without passing MFA at the gate. Under CMMC, a machine that cannot do MFA is a documented exception with a compensating control. Access Gate is that control.

Vendors get scoped, time-bound access at the gate. They are never added to your directory. They never hold standing credentials, so access ends with the job or the window.

Yes, once the HMI is behind Access Gate. Each person signs in with a named login before reaching it, and the session is recorded under that name.

Plan a named break-glass account with an offline second factor and heightened logging. If Access Gate is offline, the network keeps running and operators keep control at their local panels. A directory hosted on site only needs the local network.

No. Identity is checked in the network path. There is no agent to install and no change to the HMIs, PLCs or SCADA. Operators sign in from a browser.

Start with one shared login

See named logins on one of your lines.

Pick one line with a shared HMI login. We show you Access Gate in front of it, with each person signing in as themselves.