VNC settings determine the parameters of the connection on the protocol level, including timeout value, and so on.
|
|
Caution:
Modifying the VNC settings is recommended only to advanced users. Do not modify these settings unless you exactly know what you are doing. |
To create a new VNC settings profile or edit an existing one
-
Navigate to VNC Control > Settings and click 
to create a VNC setting profile. Enter a name for the profile (for example vnc_special).
-
Click 
to display the parameters of the connection.
-
Modify the parameters as needed. The following parameters are available:
-
Network idle timeout: Connection timeout value in seconds. To avoid early timeout, set it to a larger value, for example a week (604800 seconds).
Even if the user is not active, the session can contain activity that must be audited (for example, the output of a script). The idle timeout period will start only after this activity has stopped.
|
|
Caution:
Determining if a connection is idle is based on the network traffic generated by the connection, not the activity of the user. For example, if an application or the taskbar of a graphical desktop displays the time which is updated every minute, it generates network traffic every minute, negating the effects of timeout values greater than one minute and preventing One Identity Safeguard for Privileged Sessions (SPS) from closing the connection. |
-
User idle timeout: If no user activity is detected, terminate the session after the configured time has passed since the last user activity.
This can be useful if only user-generated network traffic is important in a session. By using this option, situations described in the caution of Network idle timeout (such as a taskbar clock keeping the network traffic open indefinitely) can be avoided. To enable user idle timeout, select Enable user idle timeout and enter a value that is greater than or equal to the value of Network idle timeout.
-
Enable pre channel check: Select this option to evaluate the connection and channel policies before establishing the server-side connection. That way if the connection is not permitted at all, SPS does not establish the server-side connection.
-
To configure TLS security settings on both the Client side and the Server side, proceed to TLS security settings.
Figure 261: <Protocol> Control > Settings > TLS security settings - configuring TLS security settings
-
Cipher strength specifies the cipher string OpenSSL will use. The following options are possible:
-
Recommended: this setting only uses ciphers with adequate security level.
-
Custom: this setting allows you to specify the list of ciphers you want to permit SPS to use in the connection. This setting is only recommended to ensure compatibility with older systems. For more details on customizing this list, check the 'openssl-ciphers' manual page on your SPS appliance.
For example: ALL:!aNULL:@STRENGTH
-
Minimum TLS version specifies the minimal TLS version SPS will offer during negotiation. The following options are possible:
-
TLS 1.2: this setting only offers TLS version 1.2 during the negotiation. This is the recommended setting.
-
TLS 1.1: this setting offers TLS version 1.1 and later versions during the negotiation.
-
TLS 1.0: this setting offers TLS version 1.0 and later versions during the negotiation.
NOTE: Note that SPS only permits TLS-encrypted connections. SSLv3 is not supported.
-
Click 
.
-
Select this settings profile in the VNC settings field of your connections.
One Identity Safeguard for Privileged Sessions (SPS) can index the contents of audit trails using its own indexer service or external indexers. Indexing extracts the text from the audit trails and segments it to tokens. A token is a segment of the text that does not contain whitespace: for example words, dates (2009-03-14), MAC or IP addresses, and so on. The indexer returns the extracted tokens to SPS, which builds a comprehensive index from the tokens of the processed audit trails.
Once indexed, the contents of the audit trails can be searched from the web interface. SPS can extract the commands typed and the texts seen by the user in terminal sessions, and text from graphical protocols like RDP, Citrix ICA, and VNC. Window titles are also detected.
SPS has an internal indexer, which runs on the SPS appliance. In addition to the internal indexer, external indexers can run on Linux hosts.
Processing and indexing audit trails requires significant computing resources. If you have to audit lots of connections, or have a large number of custom reports configured, consider using an external indexer to decrease the load on SPS. For sizing recommendations, ask your One Identity partner or contact our Support Team.
-
The internal indexer service runs on the SPS appliance. It supports languages based on the Latin-, Greek- and Cyrillic alphabets, as well as Chinese, Japanese and Korean languages, allowing it to recognize texts from graphical audit trails in 100+ languages. It can also generate screenshots for content search results.
-
The external indexer runs on Linux hosts and instances. It uses the same engine as the indexer service of SPS, and has the same capabilities and limitations.
SPS can work with multiple external indexers to process audit trails.
NOTE: The version of the external indexer must be equal to or greater than the version of One Identity Safeguard for Privileged Sessions (SPS). To make sure you meet this criterion, One Identity recommends that you always upgrade your external indexer when you upgrade SPS. You can check that SPS has established a connection to the external indexer on the Indexer > Worker status page of the SPS web interface.
NOTE: If a text is displayed for less than 1 second, it is not indexed.
If you have indexed trails, the index is archived every 30 days.
|
|
Caution:
Hazard of data loss! Make sure you also back up your data besides archiving it.
For more information, see Data and configuration backups.
If a system crash occurs, you can lose up to 30 days of index, since the index is only archived every 30 days. |
Reindex audit trails
In certain cases, reindexing already indexed audit trails might be necessary, for example, if the audit trails were indexed without full screen content but you still need to search in the screen content. In this case, the audit trails can be reindexed with a different indexer configuration to perform screen content extraction. For more information, contact our Support Team.
Reindexing lucene indices enables you to use reindexed indices with Elasticsearch.
NOTE: Reindexing can be very time consuming. To avoid unwanted reindexing, see the following examples below for setting time and initiating dry start.
To reindex lucene indices
-
Create and run the following Python script from the core shell.
#!/usr/bin/env python |
from datetime import datetime |
import os.path |
content_store_changed_filename="/opt/scb/var/upgrade/content-store-changed-time/content_store_changed_timestamp" |
if not os.path.isfile(content_store_changed_filename): |
print("The "+content_store_changed_filename+" file does not exist. This file contains the information when lucene storage was updated to elastic search.") |
exit() |
f=open(content_store_changed_filename) |
s=float(f.read()) |
f.close() |
my_date = datetime.fromtimestamp(s) |
print("Run this command to reindex everything before lucene->elasticsearch update:") |
print("indexerctl reindex query \"*\" --end "+my_date.isoformat()) |
You will receive a result similar to this:
Example
indexerctl reindex query "*" --end 2021-05-22T20:21:05.604341 |
The example shows that all items will be reindexed until 2021-05-22 20:21:05.
-
You can set the start time parameter and check the list of items scheduled for reindexing:
Example
indexerctl reindex query "*" --end 2021-05-22T20:21:05.604341 --dry --start 2021-05-22T18:21:05.604341 |
The example shows that all indices will be reindexed between 2021-05-22 18:21:05 and 2021-05-22 20:21:05.
-
If you are satisfied with the results, start reindexing:
Example
indexerctl reindex query "*" --end 2021-05-22T20:21:05.604341 --start 2021-05-22T18:21:05.604341 |
This section describes how to configure One Identity Safeguard for Privileged Sessions (SPS) to index the audit trails.
Indexing is a resource intensive (CPU and hard disk) operation, and depending on the number of processed audit trails and parallel connections passing SPS, may affect the performance of SPS. Test it thoroughly before enabling it in a production environment that is under heavy load. If your SPS appliance cannot handle the connections and the indexing, consider using external indexers (see "Configuring external indexers" in the Administration Guide) to decrease the load on SPS. For sizing recommendations, ask your One Identity partner or contact our Support Team.
Note that the minimum value of Backup & Archive > Archive policies > Delete data from SPS after is 30 days when using the indexer service. If you previously had a setting lower than this, it will still archive the index after 30 days when the indexer service is used.
NOTE: Only those audit trails will be processed that were created after full-text indexing had been configured for the connection policy. It is not possible to process already existing audit trails.
NOTE: Using content policies significantly slows down connections (approximately 5 times slower), and can also cause performance problems when using the indexer service.
NOTE: The version of the external indexer must be equal to or greater than the version of One Identity Safeguard for Privileged Sessions (SPS). To make sure you meet this criterion, One Identity recommends that you always upgrade your external indexer when you upgrade SPS. You can check that SPS has established a connection to the external indexer on the Indexer > Worker status page of the SPS web interface.
To configure SPS to index the audit trails
-
Navigate to Basic Settings > Local Services > Indexer service.
Figure 262: Basic Settings > Local Services > Indexer service > Configure the Indexer service of SPS
-
Define the Maximum number of parallel audit trails to index on box.
This option determines the maximum number of parallel indexing tasks that the SPS appliance performs. The default value is set to the number of detected CPU cores. Note that indexing audit trails requires about 50-100 Mbytes of memory for terminal sessions (SSH, Telnet, TN3270), and 150-300 Mbytes for graphical sessions (RDP, ICA, VNC, X11). Consider the memory usage of your SPS host before modifying this value.
-
Define the Maximum number of parallel audit trails to index near real-time on box.
This option determines the maximum number of parallel indexing tasks that the SPS appliance performs near real-time, meaning that indexing starts when sessions are still ongoing. The default value is set to 0.
NOTE: A connection policy configured with near real-time priority (Connection policy > Enable indexing > Priority) requires that you set Maximum number of parallel audit trails to index near real-time on box to a value other than 0.
-
(Optional) If you have encrypted audit trails and you want to index them, upload the necessary RSA private keys.
Click , and then click the 
icon to upload a private key. A pop-up window is displayed.
Select Browse, select the file containing the private key, provide the Password if the key is password-protected, and click Upload. Alternatively, you can also copy-paste the private key into the Key field, provide the Password there, and click Set.
TIP: If you want to search in the trail content on the web interface: to view screenshots generated from encrypted audit trails, you also have to upload the necessary private encryption keys to your audit keystore. For more information, see Audit keystore.
-
Click .
-
Navigate to Policies > Indexer Policies.
-
Two Indexer Policies are available by default, both with automatic language detection:
-
full_indexing: Slower, indexes the complete content of the screen, including all events.
-
lightweight_indexing: Significantly faster, but it extracts only the executed commands (Command event) and the window titles (Window title event) that appear on the screen. It does not index any other screen content (for example, text that is displayed in a terminal or that appears in an RDP window).
For example, in the case of an SSH protocol, lightweight_indexing will index a command with parameters, such as cat --help, but will not index terminal printouts such as the help content itself.
When you add a new Connection Policy, the lightweight_indexing Indexer Policy is assigned to it by default.
NOTE: In the case of graphical protocols, the default Optical Character Recognition (OCR) configuration is automatic language detection. This means that the OCR engine will attempt to detect the languages of the indexed audit trails automatically. However, if you know in advance what language(s) will be used, create a new Indexer Policy.
To create a new Indexer Policy, click .
Figure 263: Policies > Indexer Policies > Indexing options and manual language selection
-
Select from the indexing options as follows:
-
Commands: Allows you to browse, search, and analyze the commands issued in SSH and Telnet sessions.
|
|
Caution:
Do not disable unless you have a reason to do so. |
-
Window titles: Text appearing as window titles that can be detected on the screen in RDP, Citrix ICA, and VNC connections. Window title detection involves Optical Character Recognition (OCR) on parts of the screen, and can be slightly resource-intensive. SPS versions up till 6.2 only detected only the active window in the screen. From SPS version 6.3, multiple windows can be detected.
Limitations
-
Default Windows themes are supported.
-
Windows that do not have an X (close window) button in the top-right corner (or it is not visible) are not detected.
-
Use window title detection for sessions that use a single monitor. The feature works in multi-monitor environments as well, but becomes very slow, therefore it is not recommended.
-
Window title detection is case-insensitive.
|
|
Caution:
Do not disable unless you have a reason to do so. |
-
Full screen contents: Select this option if you want to search in the full screen content of the audited sessions.
Extract every text that appears on the screen in Telnet, SSH, RDP, Citrix ICA or VNC connections. For graphical protocols, extracting screen content involves Optical Character Recognition (OCR) that requires lots of CPU and disk (consider installing external indexers).
-
Pointing device biometrics: Select this option only if you are using One Identity Safeguard for Privileged Analytics (SPA)).
Extract biometric data to authenticate the users based on their pointing device (for example, mouse) usage patterns. SPA can analyze mouse movement patterns of your users as a biometric identity verification method to protect against account theft.
-
Typing biometrics: Select this option only if you are using One Identity Safeguard for Privileged Analytics (SPA)).
Extract biometric data to authenticate the users based on their typing dynamics. SPA can analyze the typing patterns of your users as a biometric identity verification method to protect against account theft.
-
To configure what languages to detect, select Select languages manually for character recognition. Select the language(s) to detect. Note the following:
-
Specifying only one language provides the best results in terms of performance and precision.
-
The English language is always detected along with the non-English languages that you have configured. However, if you want the OCR to only recognize the English language, you have to select it from the list of languages.
-
There are certain limitations in the OCR engine when recognizing languages with very different character sets. For this reason, consider the following:
-
When selecting Asian languages (Simplified Chinese, Traditional Chinese, Korean), avoid adding languages that use the Latin alphabet.
-
When selecting the Arabic language, avoid selecting any other languages.
-
The Thai language is currently not supported. If you are interested in using SPS to index Thai texts, contact our Sales Team.
-
Specify an accuracy level for Optical Character Recognition (OCR). Each accuracy level brings a different degree of speed and accuracy:
-
Fast: The fastest option with potentially less accurate results. Select this option if speed is more important to you than getting the most accurate results possible.
-
Balanced (default setting): Fairly accurate option with less than optimum speed. Select this option if you want results to be fairly accurate but you have more than a few sessions to process and processing time is less of a concern.
-
Accurate: The most accurate option with less optimal speed. Select this option if you must have the most accurate results possible and speed is less important or you only have a few sessions to process.
-
Configure the Indexing policy for the Connection policy that you want to index:
By default, the lightweight_indexing Indexing policy is enabled for every Connection policy with normal priority. If this is ideal for you, skip this step and continue with the next step. If you want to use a different policy, for example because you want to OCR the complete screen content, or because you have created a language-specific indexer policy, complete the following substeps.
-
Navigate to the Control > Connections page of the traffic type (for example SSH Control), and select the connection policy to index.
-
Figure 264: <Protocol name> Control > Connections > Enable indexing — Select Indexing Policy
Select the Indexing Policy to be used. Both built-in Indexer Policies feature automatic language detection. To specify a particular language detection configuration, select the Indexing Policy you have created before (in Step 6).
-
To determine the priority level of indexing this connection, select the appropriate Priority level. Selecting a high priority level means that the trails of this connection will be indexed first. Selecting a low priority level means that the trails of this connection will be indexed also, but there might be a delay in indexing if there are a lot of high-priority connections waiting to be indexed. Selecting near real-time means that the indexing of sessions starts when sessions are still ongoing.
-
Click .
-
Check which channel policy is used in the connection, and navigate to the <Protocol name> Control > Connections page. Select the channel policy used in the connection to index.
-
On the <Protocol name> Control > Channel Policies page, verify that the Record audit trail option is selected for the channels you want to index (for example, the Session shell channel in SSH, or the Drawing channel in RDP).
-
Click .
TIP: To verify that indexing works as configured, start a session that uses this connection policy (connect from a client to a server).
When the session is finished, navigate to the Indexer > Indexer status page to verify that the indexer service is processing the audit trail.
If the audit trails are encrypted, ensure that the required decryption keys have been uploaded to Basic Settings > Local Services > Indexer service > Indexer keys.
