NOTE: This topic assumes you have already performed the initial appliance installation and configuration steps in the One Identity Safeguard for Privileged Passwords Appliance Setup Guide provided in the box with your hardware equipment.
(web client) To modify the appliance configuration settings
- Log in to the SPP web client using the Appliance Administrator account.
- Click Appliance Management > Appliance page.
- Click Networking
to configure the appliance. For more information, see Networking..
-
On the Appliance Configuration page, configure the following:
- Network (X0): Enter the DNS Server address information for your primary interface.
- Click Save.
- Click Time to enable and view information about the Network Time Protocol (NTP):
- Select Enable NTP.
- Set the primary and secondary NTP servers, if desired.
- The Last Sync Time is displayed. To view or hide details, click Show Last Sync Details or Hide Last Sync Details. For more information, see Time..
- Click Save.
When making an RDP connection, you may encounter two different certificate messages.
-
Unsigned RDP file message
This message occurs when Remote Desktop Connection opens the RDP file that is downloaded when you click 
Play in the SPP user interface.
We are currently working on a solution that will allow SPP to sign this RDP file to avoid this message.
-
Untrusted server certification message
This message occurs when the workstation has not trusted the SPP RDP Connection Signing Certificate.
NOTE: The IP address of the connecting server is that of the Safeguard appliance.
To avoid this message, you must trust the RDP Connection Signing Certificate and certificates in its chain of trust or replace the current certificate with an enterprise certificate and chain of trust that is trusted.
One Identity recommends that you replace the entire configuration with your own trusted enterprise PKI. This would result in a structure such as:
- Your Root CA
- Your Issuing CA
- Your RDP Signing Certificate (from Safeguard CSR)
- <Sessions module generated certificate>
The Root CA, Issuing CA, and RDP Signing Certificates can be distributed via Group Policy, Active Directory, or other distribution means.
One Identity Safeguard for Privileged Passwords supports session access requests with mainframes using software terminal emulation including telnet and TN3270/TN5250 over telnet. Safeguard for Privileged Sessions version 6.1 or higher is used for session recording.
Actions
- Security officers can record activities of administrators who maintain critical systems running on IBM iSeries and mainframe computers.
- Asset Administrators can:
- Customize the TN3270/TN5250 login screen field detection to work for the Safeguard custom login setup.
- Mark an asset as supporting telnet sessions and specify if the asset is available.
- Security Policy Administrators can create an entitlement with an access policy that includes session access using telnet and TN3270/TN5250 sessions over telnet.
- Requesters' log in experience follows the regular client telnet or TN3270/TN5250 interface even when the session is being recorded. Sessions are not launched from SPP and all required log in information is available through SPP.
Steps for sessions access requests using telnet and TN3270/TN5250 over telnet
IMPORTANT: Assistance with One Identity Professional Services is required for help with configurations and installation including available plug-ins, policy creation, pattern files, shortcuts, and best practices.
Safeguard for Privileged Sessions set up steps
Complete the following set up steps in Safeguard for Privileged Sessions (SPS). For operation details, see the One Identity Safeguard for Privileged Sessions Administration Guide: One Identity Safeguard for Privileged Sessions Administration Guide.
- Import the necessary plug-in to supply authentication and authorization (AA) and credential store (credstore) information to authenticate with and pull the credentials from SPP. The plug-in file and instructions are available at the Safeguard Custom Platform Home wiki on GitHub.
- Create and assign Pattern Sets that use pattern files specific to the log in experience for each connection. A pattern file describes the log in experience for a specific system. The pattern file may include the on-screen location of the user name, password or SSH key field location, login result, descriptions, states, and other required detail. Because log in experiences vary from mainframe to mainframe, custom pattern files must be created, uploaded, and referenced by the system-related connection policy. Template pattern files and instructions are available at the Safeguard Custom Platform Home wiki on GitHub.
|
|
CAUTION: Template pattern files are provided for information only. Customized telnet and TN3270/TN5250 pattern files need to be created. Updates, error checking, and testing are required before using them in production. |
- Specify each Authentication Policy and list the authentication methods that can be used in a connection.
-
Create and configure each Connection Policy. Multiple connection policies are typically required because of the uniqueness of each system log on experience and related pattern file as well as the fact that inband destinations are not used for TN3270/TN5250 over telnet.
For example, telnet can be used for inband destinations. However, inband destinations are not used for TN3270/TN5250 over telnet. Instead, a fixed address including the port and server can be identified which results in the need for a different connection policy for each mainframe. A fixed address in Safeguard for Privileged Sessions includes the port used; the SPP asset port is not used in the connection but is usually the same.
- Export a configuration file, if desired.
- Configure basic settings for the SSH server, cluster interface, and cluster management.
SPP set up steps
Complete the following set up steps in SPP.
- The Asset Administrator adds the mainframe asset including the Telnet Session Port that is identified on the Asset Management > Asset > Management tab. For more information, see Adding an asset.
- The Security Policy Administrator sets the Access Type (Telnet) on the Security Policy Management > Entitlements > Access Request Policies tab.
SPP requester steps
In SPP after all configuration is complete, the requester proceeds based on the terminal service application in use.
- For a terminal service application that uses an inband connection string (like telnet), click
Copy to copy the Hostname Connection String and check out the password or SSH key. Then, paste the information in the log in screen.
- If the terminal service application requires more information for log in (for example, TN3270/TN5250 over telnet):
- Click
Show to display values that may include Vault Address (the SPP address), a one-time Token, Username, Asset, and Sessions Module (the Safeguard for Privileged Sessions address).
- Click Copy by any of the values to copy a single value. Or, you can click Copy at the right of all values to copy the entire the connection string, if that is required by your terminal service application.
- Paste the necessary information into your terminal service application.
- Click
Check-In Request to complete the password or SSH key check out process. This makes the session request available to reviewers.
- Click
Hide to conceal the information from view.
NOTE: The user would copy an entire connection string if, for example, you have a launcher to take the connection string and launch the profile of the terminal service application.
Some database servers use Secure Socket Layer (SSL) when communicating with SPP. Depending on the platform type, version, and configuration, the database server can either use SSL for only encrypting the session or it can use SSL for encrypting and verifying the authenticity of the database server.
ODBC Transport
The following platforms use the ODBC transport. SPP installs the appropriate software driver on the appliance to communicate with the platform. The configuration data that SPP uses to initialize a connection with the server is in the form of a connection string consisting of a colon-separated list of driver-specific options.
By default, the database servers encrypt the login data, but not the subsequent data passed on the connection. You must configure SSL and enable it on the database server to enable encryption for the session data.
Microsoft SQL Server
MicrosoftSQL Serveris always capable of encrypting the connection with SSL. It listens on a single port for both SSL and non-SSL connections.
If you have set the Force Encryption option to yes on the SQL server, then it uses SSL to encrypt the data, regardless of whether the SPP client requests it or not.
You can set the Force Encryption option to yes on the SQL server without configuring a server certificate. In this case, the SQL server transparently generates a self-signed certificate to use when a SPP client requests encryption. This makes it possible for the SQL server to use SSL only to provide encryption for the session without verifying the server certificate.
NOTE: It is not possible from within a running session to detect whether the SQL server is using SSL for encryption.
Table 230: Microsoft SQL Server SSL support
| SPP Client Options |
Microsoft SQL Server Configuration |
Result |
| Use SSL Encryption |
Verify SSL Cert |
Force Encryption |
Server Cert Configured |
| No |
n/a |
No |
n/a |
The SQL Server does not encrypt the session. |
| Yes |
No |
n/a |
No |
SPP requests that the SQL server encrypt the session using a generated self-signed certificate. |
| Yes |
No |
n/a |
Yes |
SPP requests that the SQL server encrypt the session using the server certificate. |
| Yes |
Yes |
n/a |
No |
The SQL server rejects the connection as there is no certificate to verify against. |
| Yes |
Yes |
n/a |
Yes |
SPP requests that the SQL server encrypt the session and verify the server certificate against the trusted CA certificates in SPP. |
MySQL Server
To support SSL you must compile the MySQL server software with SSL support and correctly configure it with a CA certificate and server certificate. If there is any problem with the certificate, the MySQL server may log an error and start up without SSL support. In this case the MySQL server rejects the request to enable SSL for a session as there is no certificate to verify against and does not encrypt the session. The MySQL server listens on a single port for both types of connections.
The behavior of the MySQL server depends on the server version and configuration. In some versions of MySQL, the server enables SSL by default on all SPP client sessions once it is configured.
If the MySQL server defaults to using SSL, or requires SSL for a user, the MySQL server encrypts the session even if the SPP client does not request it. However, the SPP client cannot request to use SSL just for encryption; it can only request SSL if you have imported the correct CA certificate to SPP.
NOTE: It is possible to detect that SSL is in use from within a session by examining the session variables. That is, the SPP client can detect if a request to use SSL has not been honored and displays an error.
Table 231: MySQL Server SSL support
| No |
No |
Unencrypted session. |
| No |
Yes |
Determined by the MySQL server. The server encrypts the session if it defaults to using SSL or requires it for this user. |
| Yes |
No |
SPP client detects this and reports a failure. |
| Yes |
Yes |
SPP requests that the MySQL server encrypt the session and verity the server certificate against the trusted CA certificate in SPP |
For more information, see Preparing MySQL servers..
Sybase ASE Server
To support SSL you must correctly configure the Sybase server with a CA certificate and server certificate. The Sybase server listens on different ports for SSL and non-SSL connections, and rejects a mismatched request from a SPP client to a particular port.
The SPP client cannot request to use SSL just for encryption; it can only request SSL if you have imported the correct CA certificate to SPP.
Table 232: Sybase ASE Server SSL support
| No |
No |
Unencrypted session. |
| No |
Yes |
The Sybase server rejects the connection attempt.
NOTE: The ODBC driver cannot detect that this is an SSL error and displays a client cannot connect error. |
| Yes |
No |
The Sybase server rejects the session with an SSL error. |
| Yes |
Yes |
SPP requests that the Sybase server encrypt the session and verify the server certificate against the trusted CA certificates in SPP. |
For more information, see Preparing Sybase (Adaptive Server Enterprise) servers..
