Extentrix Tutis is a client-server solution that controls connections to terminal servers; Microsoft Windows servers running terminal services or Citrix Presentation Server based on security policies dictated by administrators.

In the server part there are mainly three components:

Extentrix Core Service: works on windows server 2003. It is a windows service that runs continuously and checks new sessions connected to the server.

Tutis Management Console (administrators’ tool): works on windows server 2003. Simple user interface enables the administrators to create, edit, and delete policies that control user’s access level.

“ExtentrixTutis” back-end Database: works on any servers running SQL 2k Server. It stores the policies and its associated details.

In the client’s part there is the Extentrix Agents. Since Extentrix Tutis supports two types of protocols: RDP and ICA, there are two types of Agents according to the protocols used by the clients, one for the RDP clients and the other for the ICA clients. The Agent is the middleman worker between clients and servers which gets clients environment information and sends it to the server.

By using Tutis Management Console, administrators can create policies that control user’s access level, associate policies with filters (e.g. client with specific name or IP, or clients connected for specific server name), define the security conditions such as specific registry keys values, running processes or files and define the response action for that conditions when it is met in any client environment.

The Tutis Management console saves the created policies in the “ExtentrixTutis” back-end database.

Extentrix Core Service runs continuously and checks new sessions connected to the server, when there is a new connected client, the core service gets the applied policies for that client from the “SecureAccess” database (which is filled using the Tutis Management Console) and establishes a connection between the server and the virtual driver that resides in the client’s machine.

The Core Service sends the Agent the policies requirements, in its turn the Agent scans the client environment for the requested information, such as some registry keys values or if some process is running, etc ….then it gets the information back to the server.

The information gotten from the Agent is checked whether it meets the policies conditions, then the corresponding Response Action will be performed on that client.

While the session (connected client) is active, the core service will check for any update on that session- by contacting the Agent- every 10 seconds and check for the applied policies.