Configure the GSW Telnet Server and SSH Server Accessiblity Filters

The GSW Universal Terminal Server (Telnet Server and SSH Server for Windows) provides the flexibility to control who is allowed access to your server.

Only if a connection attempt meets your configured access criteria is it allowed. Georgia SoftWorks connection restriction configuration has thorough filtering capabilities straining out connection attempts that do not meet your specifications.

Configurable Filters and Restriction Options:

SSH2 Administrators can restrict users to SSH Clients (both 3rd party clients and GSW clients), or only allow connections from GSW SSH clients (both FIPS 140-2 compliant and non-FIPS 140-2 compliant).

FIPS 140-2 – This feature allows connections only from the Georgia SoftWorks FIPS 140-2 SSH Clients. This is a high level of security that the system administrator can configure. Many times the system administrator will insist that End-to-End FIPS 140-2 compliance is the only allowable option.

IP Address – Remote access may be limited only to specific IP addresses. The system administrator may optionally restrict connections via telnet based on the Host IP address.

User Name – Restriction based on the user ID is useful when there are a defined set of users that are allowed access to the Windows Server via SSH/Telnet.

3rd Party Client – This feature allows connections only from the Georgia SoftWorks SSH/Telnet Client. This is another level of security that the system administrator can configure. Many times the system administrator will not want users using any generic client to connect to his or her system.

Encryption – This feature allows connections only from the encrypted Georgia SoftWorks Telnet Client. This is another level of security that the the system administrator can configure. Many times the system administrator wants to ensure that ALL connections to the Georgia SoftWorks UTS are encrypted.

Time of the Day – This option can restrict access based on the time of the day.

Connection count – This feature specifies the number of connections allowed. Many times administrators want to limit the total number of connections to be a smaller value than thenumber of connections purchased.

Connection Count by : USERNAME – System administrators may want to limit the number of simultaneous logons for specific User Ids. This is especially useful for ASP environments where an entire company, department or group is assigned a single User Id that everyone shares. Reasons for limiting the number range from server resource allocation to purchased access.

Connection Count by : IP ADDRESS – The system administrator may want to limit the number of simultaneous logons from specific IP Addresses. This is especially useful for ASP environments where many users access the GSW UTS from locations that can be identified by a specific IP Address. The system administrator may want to limit the number of simultaneous connections for a variety of reasons that range from server resource allocation to purchased access.

 

 

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s