AppGate for Operational Technology (OT) uses secure remote access (SRA) to give users controlled access to Level 2 and Level 3 assets. These assets, such as operator interfaces and manufacturing execution system (MES) software, are in the supervisory and site operations layers that connect physical control equipment to enterprise IT networks.
With AppGate for OT, users connect to remote desktop protocol (RDP) and secure shell (SSH) targets through brokered sessions. The Gateway hosts each session, and the user device only displays it. The Gateway can also sign the user in to the target with credentials stored as a secret, so users never see those credentials. Users start brokered sessions from the client.
Admins can record brokered sessions, view and terminate active sessions, and play back or download recordings as MP4 files. The Gateway stores the recordings.
AppGate for OT also includes the following:
Single-Site User licenses for users who need access to only one Site, such as contractors and third-party vendors
Protocol templates for OT protocols in Network entitlements
A Claroty CTD resolver that resolves hosts from a Claroty CTD asset inventory
Each feature requires a license. See Licensing for AppGate for OT.
NOTE
AppGate ZTNA v7.0 does not support brokered access for mobile clients that connect through the Portal. Support is planned for a future release.
Prerequisites
Licensing for AppGate for OT
The following licenses control AppGate for OT features:
License | Included features | How it is counted | Details |
|---|---|---|---|
Brokered Access | Brokered RDP and Brokered SSH entitlement types. | Per named user. Add-on to a Client User, Portal User, or Single-Site User license. | Does not require the Operational Technology license. Can be used for IT and OT use cases. Seats assigned on a first-come, first-served basis. When all seats are in use, AppGate ZTNA does not assign brokered entitlements to users without a seat, even if a policy grants them. Lease time defaults to 30 days. Can be configured when the license is generated. |
Session Governance | Session recording, live monitoring, the Active Brokered Sessions page, and the Recorded Brokered Sessions page. | Per named user. Add-on to a Client User, Portal User, or Single-Site User license. | Does not require the Operational Technology license. Can be used for IT and OT use cases. Seats assigned on a first-come, first-served basis. Lease time defaults to 30 days. Can be configured when the license is generated. |
Single-Site User | Entitlements from one Site only. | Per named user. | For users who need access to only one Site, such as contractors and third-party vendors. Does not require Operational Technology license. Can be used for IT and OT use cases. |
Operational Technology | Protocol templates and the Claroty CTD resolver. Brokered Access license. | Collective-wide. |
The Licensed Users page (Usage > Licensed Users) shows each user’s license type in the License Type column.
When you upload a Brokered Access or Session Governance license, the Licenses page (Settings > Licenses) shows a gauge for each under Effective License Summary.
Gateway requirements
Brokered RDP and SSH sessions run on the Gateway. The Gateway hosts the session, and the client or Portal renders it.
The Gateway processes sessions and stores recordings. Size your Gateways for the expected number of concurrent sessions and the recording storage you need. See Instance sizing for session counts and storage requirements by hardware profile.
NOTE
Brokered sessions do not use the Connection Broker.