Detailed Use Cases
9 pages in this section.
Pages
Protocol Configuration Use Cases
How to configure Access Gate controls for key protocols (HTTP/HTTPS, SSH, RDP, SMB, Modbus, FTP).
Configure HTTP/HTTPS flows
Put identity and encryption in front of web HMIs and device admin pages: choose a TLS-termination mode, decide whether a login screen sits in front, and handle the quirks of embedded HMIs, without touching the device.
Configure SSH flows
Broker SSH through Access Gate two ways: a network-path grant where the operator holds their own key, or a Remote Access proxy where the gate holds the credential and serves a browser session.
Configure RDP flows
Broker RDP through Access Gate: reach an HMI workstation with no inbound RDP exposed, gate the desktop behind identity with an access screen, and scope who sees it by enclave.
Configure SMB flows
Secure SMB file shares in layers: control who reaches port 445 with an Access Gate enclave and access screen, lean on SMB3 signing and encryption on the wire, and keep server-side permissions as the last gate.
Configure Modbus flows
Control Modbus/TCP access to PLCs and RTUs, default-deny on port 502, identity-scoped grants, and TLS for a protocol with no encryption of its own.
Configure FTP flows
Broker FTP through Access Gate: grant access by enclave, pin passive-mode data ports, and gate the server behind identity with an access screen.
Configure OPC UA flows
Protect an unsecured OPC UA server with Access Gate: bring it inside an enclave, then secure the channel with TLS, OPC UA message security, or a gated tunnel, without touching the legacy server or client.
Configure MQTT flows
Secure MQTT on an OT network with Access Gate, default-deny on port 1883, identity-scoped enclaves, topic-level control, and TLS for a broker that ships with no auth or encryption.