Skip to content

Executable Restrictions ​

WARNING

Executable Restrictions are not available for STLinks operating in Gateway or Reverse-Gateway mode.

Routes can be configured to block access to all processes on the client or server machine except for processes authorized in the Commander.

Executable restrictions allow you to define the SHA-512 hash of a binary executable and assign that SHA-512 as an authorized process to communicate with either end of the SealedTunnel.

A Binding Route can be configured to only allow incoming connections from authorized binary executables. When a process attempts to connect to the binding address, the STLink will get the full file path of the attempting process, SHA-512 the binary of the process at that path, and check it against the authorized SHA-512 list. If the attempting process is not in the authorized list, the connection will be rejected by the STLink.

A Mapping Route can be configured to only send traffic to an authorized destination service or process. Before the STLink establishes the connection with the listening service, the STLink will first get the full path of the executable listening on that IP address/port, SHA-512 the binary of the executable at that path, and check it against the authorized SHA-512 list. If the service's binary SHA-512 does not match any authorized executable, the connection will not be delivered and the packets will be dropped.

Allowable Executable Rules ​

The Rules table in the Executable Restrictions tab lists the global authorized SHA-512 executables. This list does not enforce any process restrictions on any SealedTunnels. The global list tracks all authorized SHA-512 executables in the system. Individual Allowable Executable Rules can be assigned to a Binding Route or a Mapping Route.

You can create a new Allowable Executable Rule by clicking the orange + Allowable Rule button above the table.

All Allowable Executable Rules require three pieces of information:

FieldDescription
SHA-512The SHA-512 hash of the binary executable
NameThe name of the Allowable Executable Rule
DescriptionA description of the executable

There is also a switch that you can turn on that will disable an Allowable Executable Rule, which will disallow the rule globally from all Routes.

You can select an Allowable Executable Rule from the table and edit its information or delete the rule, which will also remove it from all associated Routes.

Allowable Executable Rules can be assigned to individual Routes through the Route Processes Tab

Blocked Executable Notifications ​

INFO

Blocked Executable Notifications are de-duplicated automatically.

The Notifications table in the Executable Restrictions tab shows the blocked processes that have attempted to communicate with either end of a SealedTunnel.

Each entry in the notifications table includes the SHA-512, the originating STLink, the process description pulled from the operating system, the full path of the blocked executable, and the owning customer account.

You can click on any notification from the table to view the full information on the blocked executable. You can also convert the notification into an Allowable Executable Rule by clicking the green Add Allowable Executable button or delete the notification.

The Notifications tab will have a red (!) exclamation point inside a circle displayed when there are new notifications available.

SMTP support for blocked executable notifications will be introduced in a future release.