SPS 7.5 SafeguardDesktopPlayerUserGuide
SPS 7.5 SafeguardDesktopPlayerUserGuide
Sessions 7.5
Summary of changes 5
First steps 19
Thank you for installing the Safeguard Desktop Player 19
Getting started with the Safeguard Desktop Player 20
The Search window of Safeguard Desktop Player 22
Preferences for the Safeguard Desktop Player 24
Keyboard shortcuts 71
About us 72
Contacting us 72
Technical support resources 72
Summary of changes
Changes in product:
l For RDP and ICA trails, you can select a keyboard layout depending on the language
used in the trail and recreate the subtitle of the trail.
For more information, see Replaying audit trails.
l The installation of the Safeguard Desktop Player on Windows has been improved. You
no longer need elevated privileges to install the Safeguard Desktop Player, and for
future versions, you can install the new version without first having to uninstall the
previous version.
If you already have an earlier version of the Safeguard Desktop Player application
installed on the host (version 1.8 or earlier), uninstall the previous installation. For
future versions of the Safeguard Desktop Player, you do not need to uninstall the
previous version before you can install the new version as this will be done
automatically.
For more information, see Installing Safeguard Desktop Player on Windows.
Changes in product:
Changes in product:
l It is now possible to search in the contents of the audit trails for trails of graphical
sessions created and indexed with SPS 6.0.
For more information, see Searching in the content of the current audit file.
Changes in product:
Changes in product:
Changes in product:
Changes in product:
l It is now possible to replay the audit trails of X11 sessions. For more information, see
Replaying X11 sessions.
Changes in product:
NOTE: You can replay audit trails in your browser, or using the Safeguard Desktop Player
application. Note that there are differences between these solutions.
For details on the Safeguard Desktop Player application, see Safeguard Desktop Player
User Guide.
The following table details the differences between the solutions provided by the browser
and the Safeguard Desktop Player application when replaying audit trails.
Exports to PCAP - ✔
This section provides information on how to install the Safeguard Desktop Player
application in different operating systems.
l Microsoft Windows:
l 64-bit version of Windows 10 (from version 1607)
l 64-bit version of Windows 11
l Windows Server 2016 (from version 1607)
l Windows Server 2019
l Windows Server 2022
Install the appropriate driver for your graphic card.
l Linux:
RHEL 7, CentOS 7, or newer. The Safeguard Desktop Player application will probably
run on other distributions as well that have at least libc6 version 2.17 installed.
Depending on the distribution, you will need to install the following packages:
l On Debian-based GNU/Linux:
l libxcb-render-util0
l libxcb-keysyms1
l libxcb-image0
l libxcb-randr0
l libxcb-xkb1
To install the Safeguard Desktop Player application, you need about 200MB disk space, and
a temporarily used disk space to store the audit trails that are replayed. The size of the
temporary files depends on the size of the replayed audit trails.
You can install the Safeguard Desktop Player application with user privileges.
Prerequisites
l You must have a valid support portal account with access to SPS downloads.
l Microsoft Windows:
l 64-bit version of Windows 10 (from version 1607)
l 64-bit version of Windows 11
l Windows Server 2016 (from version 1607)
l Windows Server 2019
l Windows Server 2022
Install the appropriate driver for your graphic card.
For details, see Safeguard Desktop Player system requirements.
l If you already have an earlier version of the Safeguard Desktop Player application
installed on the host (version 1.8 or earlier), uninstall the previous installation. For
future versions of the Safeguard Desktop Player, you do not need to uninstall the
previous version before you can install the new version as this will be done
automatically.
1. Download the Safeguard Desktop Player application for Windows from the
Downloads page.
2. Install the Safeguard Desktop Player application using one of the following options:
l Navigate to the Downloads directory and start the installation.
l Silent install if using terminal: Alternatively, from the terminal, use the msiexec
/quiet silent install option to install the Safeguard Desktop Player.
For example: msiexec /i <player.msi>
INSTALLFOLDER="C:\Users\<yourusername>\AppData\Local\Safeguard\" /quiet
The installation wizard opens.
3. On the Setup Preferences page, select the required options. After that, click Next
to create the start menu icon, and register the audit trail file extensions.
4. Select where you want to save the Safeguard Desktop Player application installer,
and after that, click Next. The default installation folder is
C:\Users\<yourusername>\AppData\Local\Safeguard.
5. Read the Software Transaction, License and End User License Agreements of
Safeguard Desktop Player, select I accept the license, then click Next.
6. To install the Safeguard Desktop Player application, click Install, and after that,
when the installation is complete, click Finish.
Prerequisites
l You must have a valid support portal account with access to SPS downloads.
l Microsoft Windows:
l 64-bit version of Windows 10 (from version 1607)
l 64-bit version of Windows 11
l Windows Server 2016 (from version 1607)
l Windows Server 2019
l Windows Server 2022
Install the appropriate driver for your graphic card.
For details, see Safeguard Desktop Player system requirements.
l If you already have an earlier version of the Safeguard Desktop Player application
installed on the host (version 1.8 or earlier), uninstall the previous installation.
To install the Safeguard Desktop Player application on Windows to use with the
SPP desktop client application
1. Download the Safeguard Desktop Player application for Windows from the
Downloads page.
2. Open a terminal with elevated privileges.
3. Enter msiexec /i <player.msi> INSTALLFOLDER="C:\ProgramFiles\Safeguard"
/quiet
The Safeguard Desktop Player is installed at C:\Program Files\Safeguard Desktop
Player and you can use it with the SPP desktop client application.
Prerequisites
l You must have a valid support portal account with access to SPS downloads.
l Linux:
1. Download the Safeguard Desktop Player application for Linux from the
Downloads page.
2. Open a terminal, and navigate to the Downloads directory.
3. To install the Safeguard Desktop Player application, start the downloaded file.
l Installing for every user (system-wide installation): System-wide installation
requires root privileges. To install Safeguard Desktop Player for every user on
the host, issue the following commands:
l Installing for the current user: You can install the Safeguard Desktop Player
application with user privileges. To install Safeguard Desktop Player for the
current user on the host, issue the following commands:
5. Read the Software Transaction, License and End User License Agreements of
Safeguard Desktop Player, select I accept the license, then click Next.
6. To install the Safeguard Desktop Player application, click Install, then click Finish
when the installation is complete.
Prerequisites
l You must have a valid support portal account with access to SPS downloads.
l MacOS High Sierra 10.13, or newer.
For details, see Safeguard Desktop Player system requirements.
1. Download the Safeguard Desktop Player application for Mac from the
Downloads page.
2. Double-click the desktop_player_installer.version.release.dmg to open the
installer, then drag the Safeguard Desktop Player application to the
Applications folder.
3. If your Mac is set to allow applications only from the App Store, you get a warning
that you cannot install the application. You can temporarily override your Mac
security settings and open the application as follows:
First steps
Figure 9: Warnings
10. Settings
You have the following settings options:
l Import the required certificate to replay an encrypted audit trail. For more
information, see Replaying encrypted audit trails.
l Open Preferences, which you can use to set the application language, select a
keyboard layout, select how you want to display the window title events on the
seeker and in subtitles, and so on. For more information, see Preferences for
the Safeguard Desktop Player.
l Open the documentation in your browser.
11. Search
1. Play/pause, replay
Start or pause replaying the audit trail. You can also click the video to start or
pause replaying.
2. Jump to previous event
layout, and so on, for Safeguard Desktop Player, navigate to (Settings) >
Preferences.
Language
l Safeguard Desktop Player application language: Set the preferred language for
the menus, buttons, and other controls of your Safeguard Desktop Player.
For the changes to take effect, close and restart the Safeguard Desktop Player
application.
l Keyboard layout: In some cases, RDP and ICA audit trails do not contain their
specific keyboard layouts. To avoid misspellings in the subtitles, you can set your
specific layout for all your audit trails.
For each individual audit trail, you can still override these global settings from
your Details page of your Safeguard Desktop Player as shown in the example
figure below:
Figure 11: Safeguard Desktop Player > Details page > Changing the
keyboard layout for individual RDP or ICA audit trails
l Window title: Select how you want to display the window title events on the seeker
and in subtitles.
l If your audit trails are indexed, select Only indexed trails (faster). Indexed
audit trails already contain the window titles, and the process of displaying the
window titles is faster.
l If you are unsure whether your audit trails are indexed, select Always.
Safeguard Desktop Player detects if your audit trails are indexed. If no indexed
audit trail is available, Safeguard Desktop Player will start indexing the audit
trails automatically.
l If your audit trails are not indexed, select Forced detection (slower). The
audit trail will be re-indexed, regardless if it had been indexed before or not,
and as a result, the process of displaying the window titles is slower.
l If you do not want to display window titles, select Never.
Figure 12: Safeguard Desktop Player > Details page > Changing the
encoding for individual audit trails
l Telnet codec: To deal with special characters, you can set the default codec to
display text. The SPS default settings for the Telnet codec is 500 and for the Telnet
alternate codec is 310.
When you open an audit trail, the Safeguard Desktop Player application automatically
validates it. You can see the results of this validation above the session details.
This section describes how to replay an audit trail that is not encrypted.
To replay an encrypted audit trail, see Replaying encrypted audit trails.
You can use the SPS Search page to download an audit trail. For more information, see
Using the Search interface in the Administration Guide.
Prerequisites
l The audit trail is available on the computer that runs the Safeguard Desktop Player.
l Using a web browser, you open the audit trail on the SPS search interface and you
open the Safeguard Desktop Player application on the same computer.
1. Open an audit trail that you want to replay. Use one of the following methods:
l Start the Safeguard Desktop Player application from the menu or the command
line, then click OPEN. Select the audit trail you want to replay.
l Navigate to the audit trail file and open it.
The Safeguard Desktop Player application displays the details of the sessions
stored in the audit trail file. It automatically starts to prepare (render) the audit
trail for replaying. You can start replaying the audit trail while rendering is in
2. To start playing the audit trail, click the play button. If the audit trail contains more
than one channels that can be replayed, you can select the channel to replay.
Alternatively, click the icon next to the channel that you want to replay.
The replay window opens.
Prerequisites
l To replay encrypted audit trails, the private key of the certificate used to encrypt the
audit trail must be available on the host running the Safeguard Desktop Player. On
Microsoft Windows, the Safeguard Desktop Player can retrieve this certificate from
Windows Certificate Store > Current User > Personal Certificate Store.
l To validate digitally-signed audit trails, the respective CA certificates that issued the
certificates used to sign the audit trail must be available on the host running the
Safeguard Desktop Player. (This is the CA of the certificates set at Policies > Audit
policies > Enable signing on the SPS interface.) On Microsoft Windows, the
Safeguard Desktop Player can retrieve this certificate from Windows Certificate
Store > Local Computer > Trusted Root Certification Authorities.
l To validate timestamped audit trails, the CA certificate of SPS must be available on
the host running the Safeguard Desktop Player. (This is the CA certificate of SPS set
at Basic Settings > Management > SSL Certificates > CA X.509 Certificate.)
On Microsoft Windows, the Safeguard Desktop Player can retrieve this certificate
from Windows Certificate Store > Local Computer > Trusted Root
Certification Authorities.
The certificates and the private keys must be available in PEM format, other formats are
not supported.
NOTE: On Microsoft Windows, you cannot import CA certificates from a shared drive. In
this case, copy the certificate to a local folder and import it from there.
NOTE: Certificates are used as a container and delivery mechanism. For encryption and
decryption, only the keys are used.
TIP: One Identity recommends using 2048-bit RSA keys (or stronger).
>
1. Open the encrypted audit trail. Safeguard Desktop Player tries to decrypt and
validate it. If the decryption or validation fails, the Safeguard Desktop Player notifies
you on the screen. Click Warnings to see the fingerprint of the required certificate.
4. Click Load. The Safeguard Desktop Player displays the details of the certificate.
5. Select how you want to store the certificate, then click Import. On Microsoft
Windows, you can import the certificates to the Windows Certificate Store and reuse
them later. On other platforms, Safeguard Desktop Player stores the certificates only
temporarily, and automatically deletes them when you close the application.
l If you want Safeguard Desktop Player to delete the certificate after you close
the application, select Store temporarily only.
l If you are importing a private key to decrypt an audit trail, select Store as
personal certificate.
l If you are importing a CA certificate to validate the timestamp or signature of
the audit trails, select Store as trusted root certificate.
6. Repeat the previous steps to import other certificates if needed.
7. Click , then to start replaying the audit trail.
This section describes how to replay an encrypted audit trail using the command line. Use
this method if you want to import the private key only temporarily, or if you want to
automate the process. To import the required certificates using the graphical interface of
Safeguard Desktop Player, see Replaying encrypted audit trails.
Prerequisites
l To replay encrypted audit trails, the private key of the certificate used to encrypt the
audit trail must be available on the host running the Safeguard Desktop Player. On
Microsoft Windows, the Safeguard Desktop Player can retrieve this certificate from
Windows Certificate Store > Current User > Personal Certificate Store.
l To validate digitally-signed audit trails, the respective certificates that issued the
certificates used to sign the audit trail must be available and valid on the host running
the Safeguard Desktop Player. (This is the certificate set at Policies > Audit
policies > Enable signing on the SPS interface.) On Microsoft Windows, the
Safeguard Desktop Player can validate this certificate from Windows Certificate
Store > Local Computer > Trusted Root Certification Authorities.
NOTE: In case of certificate chains, the whole chain must be imported in this Certi-
ficate Store.
l To validate timestamped audit trails, the CA certificate of SPS must be available on
the host running the Safeguard Desktop Player. (This is the CA certificate of SPS set
at Basic Settings > Management > SSL Certificates > CA X.509 Certificate.)
On Microsoft Windows, the Safeguard Desktop Player can retrieve this certificate
from Windows Certificate Store > Local Computer > Trusted Root
Certification Authorities.
The certificates and the private keys must be available in PEM format, other formats are
not supported.
NOTE: On Microsoft Windows, you cannot import CA certificates from a shared drive. In
this case, copy the certificate to a local folder and import it from there.
NOTE: Certificates are used as a container and delivery mechanism. For encryption and
decryption, only the keys are used.
For example, if the private key file is C:\temp\my-key.pem and its password is secret,
the command is player --key C:\temp\my-key.pem:secret
Otherwise, use the following command:
2. (Optional) If the audit trail is timestamped or signed, you must have the proper
certificate to validate the audit trail. Include the path to the certificate in the
command line when starting the Safeguard Desktop Player:
3. Open the encrypted audit trail. Safeguard Desktop Player tries to decrypt it with
the private key you provided. If decryption is successful, you can replay the audit
trail. Alternatively, you can specify the audit trail to open from the command line,
for example:
Prerequisites
To follow active connections, you must be allowed to authorize the sessions of the relevant
connection policy. For more information on how you can configure that, see Configuring
four-eyes authorization in the Administration Guide.
Every time you open an .srs file in Safeguard Desktop Player, you must authenticate
yourself to SPS through Safeguard Desktop Player. To access SPS and follow active
sessions, you must have:
On Microsoft Windows, Safeguard Desktop Player retrieves the SSL certificate from
Windows Certificate Store > Local Computer > Trusted Root Certification
Authorities.
On Linux or MacOS, import the SSL certificate to Safeguard Desktop Player as follows:
1. On the SPS web interface, navigate to Sessions , select Active in Connections, and
click next to the connection you want to monitor in semi-real time.
2. In Safeguard Desktop Player, click OPEN, and select the audit trail to replay.
NOTE: If you open a closed session from an srs file, you can start to replay its
content and follow the session even if the file has not been fully downloaded
and rendered.
Safeguard Desktop Player displays the sessions stored in the audit trail file.
4.
a. Terminate
Terminate the session that you are monitoring if you notice a user action that
poses a security risk.
b. LIVE status indicator
The indicator shows two different states:
l When the Safeguard logo is animated, it indicates that the connection is
active and there is some user interaction on the client-side.
l When the Safeguard logo is static, it indicates that the connection is
active but there is no user interaction on the client-side.
The color of the LIVE label indicates if the displayed frame is live (blue) or an earlier
frame (gray). If you stopped the playback or rewound it, to return to the live
streaming, click LIVE.
TIP: If you are replaying terminal-based audit trails, for example, SSH or TELNET,
you can change the font size of the displayed text by holding down the Ctrl key and
scrolling your mouse wheel.
When the session ends, a button is displayed. If you click this button, the player
reverts to normal replay mode, and you can change the replay speed, and the seeker
becomes available again.
Safeguard Desktop Player allows you to search in the contents of the recorded audit trails,
for example, in commands that the user executed in the session, or to find a specific text
that was displayed on the screen.
You can also search in the contents of the audit trails for trails of graphical sessions created
and indexed with SPS 6.0.
Prerequisites
1. In the Safeguard Desktop Player application, click OPEN, and select the audit trail to
replay. If the audit trail is encrypted, see Replaying encrypted audit trails.
Safeguard Desktop Player displays the sessions stored in the audit trail file.
l For examples of exact matches, see Searching for exact matches on page 45.
l For examples of using boolean operators to combine search keywords, see
Combining search keywords on page 46.
l For examples of wildcard searches, see Using wildcard searches on page 47.
l For examples of searching with special characters, see Searching for special
characters on page 49.
l For examples of fuzzy search that finds words with similar spelling, see Searching for
fuzzy matches on page 51.
l For examples of proximity search to find words that appear within a special distance,
see Proximity search on page 51.
l For examples of adjusting the relevance of a search term, see Adjusting the
relevance of search terms on page 51.
For details on how to use more complex keyphrases that are not covered in this guide, see
the Apache Lucene documentation.
By default, One Identity Safeguard for Privileged Sessions (SPS) searches for keywords as
whole words and returns only exact matches. Note that if your search keywords include
special characters, you must escape them with a backslash (\) character. For details on
special characters, see Searching for special characters on page 49. The following
characters are special characters: + - & | ! ( ) { } [ ] ^ " ~ * ? : \ /
Matches example
To search for a string that includes a backslash characters, for example, a Windows
path, use two backslashes (\\).
Matches C:\Windows
You can use boolean operators – AND, OR, NOT, and + (required), – to combine search
keywords. More complex search expressions can also be constructed with parentheses. If
you enter multiple keywords,
Matches (returns hits that contain the first phrase, but not the second)
To search for expressions that can be interpreted as boolean operators (for example:
AND), use the following format: "AND".
The ? (question mark) wildcard means exactly one arbitrary character. Note that it
does not work for finding non-UTF-8 or multibyte characters. If you want to
search for these characters, the expression ?? might work, or you can use the *
wildcard instead.
You cannot use a * or ? symbol as the first character of a search.
Matches example1
examples
example?
Matches example12
Matches example
examples
example.com
Matches example1
examples
example.com
exemple.com
To search for the special characters, for example, question mark (?), asterisk (*),
backslash (\) or whitespace ( ) characters, you must prefix these characters with a
backslash (\). Any character after a backslash is handled as character to be searched for.
The following characters are special characters: + - & | ! ( ) { } [ ] ^ " ~ * ? : \ /
Matches example?
To search for a string that includes a backslash characters, for example, a Windows
path, use two backslashes (\\).
Matches C:\Windows
To search for a string that includes a slash character, for example, a UNIX path, you
must escape the every slash with a backslash (\/).
Matches /var/log/messages
Matches (1+1):2
For terminal connections, use the command: prefix to search only in the commands
(excluding screen content). For graphical connections, use the title: prefix to search only
in the window titles (excluding screen content). To exclude search results that are
commands or window titles, use the following format: keyword AND NOT title:[* TO *].
You can also combine these search queries with other expressions and wildcards, for
example, title:properties AND gateway.
To find an expression in the screen content and exclude search results from the
commands or window titles, see the following example.
You can also combine these search filters with other expressions and wildcards.
Matches A screen where properties appears in the window title, and gateway
in the screen content (or as part of the window title).
Does not Screens where both properties and gateway appear, but properties
match is not in the window title.
Fuzzy search uses the tilde ~ symbol at the end of a single keyword to find hits that contain
words with similar spelling to the keyword.
Matches roams
foam
Proximity search
Proximity search uses the tilde ~ symbol at the end of a phrase to find keywords from the
phrase that are within the specified distance from each other.
Matches (returns hits that contain keyword1 and keyword2 within 10 words
from each other)
By default, every keyword or phrase of a search expression is treated as equal. Use the
caret ^ symbol to make a keyword or expression more important than the others.
Matches (returns hits that contain keyword1 and keyword2, but keyword1 is
4-times more relevant)
Matches (returns hits that contain keyword1 and keyword2, but keyword1 is
5-times more relevant)
This section describes how to export an audit trail as a video file (optionally, including the
accompanying subtitles).
NOTE: To export an audit trail, you must open it.
The exported files use the WEBM format with the VP8 codec. You can replay WebM videos in
most modern browsers, and several media player applications. For details, see the Playing
WebM Video page.
Prerequisites
5. Click , and select the directory where you want to save the video file.
6. Click EXPORT.
You can enable auditing the sound that is transferred between an RDP client and the server.
Using the Export audio option of Safeguard Desktop Player, you can export the input
sound (the one that comes from the audited user) and the output sound (the one that is
received by the audited user) into .wav files.
Prerequisites
In SPS, using the Channel Policies settings of the Traffic Controls > RDP option, select
the Record audit trail checkbox for the Sound and the Dynamic virtual channel in the
policy that you want to use for sound auditing.
For more information, see Configuring SPS to enable exporting sound from audit trails in
the SPS Administration Guide.
The displayed dialog shows the exported files with their paths. On clicking the paths, the
destination folders open. The dialog also lists the errors that occurred during the export.
The sound files are saved in the following format:
l <timestamp>_input.wav
l <timestamp>_output.wav
Using the Export zat/zatx... option of Safeguard Desktop Player, you can save the trail
currently opened to a selected location.
After opening an srs file, you can export its content to a zat or zatx file if all the following
criteria are met:
The displayed dialog shows the exported file with the trail.zat or trail.zatx file name.
This section describes how to share an encrypted audit trail with a third party.
NOTE: To export an audit trail, you must open it.
Prerequisites
This procedure involves encrypting the audit trail with an encryption key that you can share
with the third party. Encrypting audit trails requires an X.509 certificate in PEM format that
uses an RSA key.
You will also need the audit trail file that you want to share, and the encryption key(s)
required to replay it. You cannot use this procedure to encrypt an audit trail that is not
already encrypted.
NOTE: Certificates are used as a container and delivery mechanism. For encryption and
decryption, only the keys are used.
TIP: One Identity recommends using 2048-bit RSA keys (or stronger).
1. Specify the audit trail to process its decryption key, the new audit trail file, and the
new encryption key.
2. Open the output file in the Safeguard Desktop Player and import the private key of
the certificate you used to re-encrypt the audit trail. Verify that you can replay the
audit trail. If it is working as expected, you can share the re-encrypted audit trail file
and the private key with third parties, they will be able to replay the audit trail using
the SPS application.
With the Safeguard Desktop Player application, you can replay audit trails that contain
graphical X11 sessions (the contents of the X11 Forward channel of the SSH protocol).
You can replay X11 sessions similarly to other audit trails, but consider the following points:
l X11 sessions can contain several different X11 channels. For example, some
applications open a separate channel for every window they display. The Safeguard
Desktop Player application automatically merges these channels into a single
channel, to make reviewing the sessions easier. Since these audit trails can contain
SSH terminal channels as well, you can choose between replaying the SSH sessions
and the X11 session in the CHANNELS > X11 section of the audit trail data.
l If you need the list of X11 channels that the audit trail contains, they are listed in
CHANNELS > X11 > channel_ids section of the audit trail data.
You can export the files that the user transferred in SCP, SFTP, and HTTP sessions as well
as through the RDP clipboard. You can export such files from the audit trails using the
command line or the Safeguard Desktop Player GUI.
NOTE: Exporting transferred files through the RDP clipboard is a feature that has been
tested with Microsoft-supported clients.
Configure SPS to allow exporting files from an audit trail. For more information, see
Configuring SPS to enable exporting files from audit trails after RDP file transfer in the
Administration Guide.
NOTE: By default, the Safeguard Desktop Player application only exports complete files.
To export partially transferred files, see Exporting transferred files from SCP, SFTP, HTTP
and RDP audit trail using the command line.
To export files from an audit trail after RDP file transfer through clipboard or
disk redirection
1. Navigate to Main Menu > Sessions in SPS, select the session during which the
files were copy-pasted through the clipboard or transferred through disk redirection,
and click .
Exporting transferred files from SCP, SFTP, HTTP, and RDP audit 61
trails
2. Click , save the .zat file, and open the Safeguard Desktop Player
application.
3. Open the .zat file and click in the Safeguard Desktop Player interface
window.
4. Navigate to EXPORT > Export transferred files... and select Choose in the
Select folder – Safeguard Desktop Player window. Safeguard Desktop Player
automatically displays the files in a new window under EXPORTED FILES
(<number of files>), with information about the files' original path.
5. (Optional) Open the files to see if the export was successful.
l SCP
l SFTP
l HTTP
l RDP
To export the files that you transferred in an SCP, SFTP, HTTP, or RDP session
using the command line
Start a command prompt and navigate to the installation directory of Safeguard
Desktop Player.
By default, the installation directories on the different operating systems are the following:
NOTE: By default, the Desktop Player only exports complete files. If you want to export
partially transferred files as well, use the adp --export-files command.
Exporting transferred files from SCP, SFTP, HTTP, and RDP audit 62
trails
1. List the channels in the audit trail, and find the one you want to extract files from.
Note down the ID number of this channel as it will be required later on (it is 3 in the
following example).
l Windows: adp.exe --task channel-info --file <path/to/audit-trail.zat>
l Linux or MacOS: ./adp --task channel-info --file <path/to/audit-
trail.zat>
If the audit trail is encrypted, use the --key <keyfile.pem:passphrase> option.
Repeat the option if the audit trail is encrypted with multiple keys. Include the colon
(:) character even if the key is not password-protected. Example output:
2. Export the files from the audit trail. Use the ID number of the channel from the
previous step.
Windows: adp --task indexer --channel 3 --file <path/to/audit-trail.zat> --
export-files <folder/to/save/files/>
Linux or MacOS: adp --task indexer --channel 3 --file <path/to/audit-
trail.zat> --export-files <folder/to/save/files/>
If the audit trail is encrypted, use the --key <keyfile.pem:passphrase> option.
Repeat the option if the audit trail is encrypted with multiple keys. Include the colon
(:) character even if the key is not password-protected.
3. Check the output directory for the exported files.
Exporting transferred files from SCP, SFTP, HTTP, and RDP audit 63
trails
16
You can choose to convert audit trails to packet capture (PCAP) format, which is a common
file format for storing network traffic.
To export raw network traffic in PCAP format using the command line
Start a command prompt and navigate to the installation directory of Safeguard
Desktop Player.
By default, the installation directories on the different operating systems are the following:
1. List the channels in the audit trail, and find the ones that you want to export. Note
down the ID number of the channels as it will be required later on (it is 3 in the
following example).
l Windows: adp.exe --task channel-info --file <path/to/audit-trail.zat>
l Linux or MacOS: ./adp --task channel-info --file <path/to/audit-
trail.zat>
2. Export the channels from the audit trail. Use the ID numbers of the channels from the
previous step.
l Windows: adp.exe -f <path/to/audit-trail.zat> -c <channel id> -t
indexer --export-pcap output.pcap
l Linux or MacOS: adp -f <path/to/audit-trail.zat> -c <channel id> -t
indexer --export-pcap output.pcap
If the audit trail is encrypted, use the --key <keyfile.pem:passphrase> option.
Repeat the option if the audit trail is encrypted with multiple keys. Include the colon
(:) character even if the key is not password-protected.
3. Check the output directory for the exported files.
To export the channels stored in the audit trail using the GUI
This section describes how to export screen content text from text-based protocols
(terminal-based protocols and HTTP) in TXT format. Screen content text is saved into files
as UTF-8 encoded text with UNIX timestamps.
l Start the Safeguard Desktop Player application, and on the opening screen, click >
About. This displays the version number of Safeguard Desktop Player and also the
underlying adp application.
l Execute the following commands from the command line in the directory where
Safeguard Desktop Player is installed:
l Windows: adp.exe --version & player.exe --version
l Linux: ./adp --version; ./player --version
To export the files that the user transferred in an SCP, SFTP, or HTTP session
using the GUI
Problems in VirtualBox
If the fonts are not displayed correctly, or the Safeguard Desktop Player application crashes
when started in VirtualBox, enable 3D acceleration (Machine > Settings > Display >
Screen > Enable 3D Acceleration), and install VirtualBox Guest Additions.
If these do not solve the problem, see Force rendering software.
Logging
The Safeguard Desktop Player application displays important log messages on the
Warnings tab. If you increase the log level of the application above the default, additional
log messages are also displayed.
To specify the log level of the Safeguard Desktop Player application, use the following
command-line parameters.
l -l or --log-level <number>
l Set the log level of Safeguard Desktop Player:
l 3 - Default log level.
l 0 - Completely disables logging.
l 7 - The is most verbose level, used for debugging.
For example:
Keyboard shortcuts
You can use the following keyboard shortcuts to control the replay.
l Play/Pause: SPACE
l Jump to previous event: p
l Jump to next event: n
l Enable video scaling (Scale video): Ctrl + Z
l Toggle fullscreen replay: f
l Decrease replay speed: [
l Increase replay speed: ]
l Reset replay speed :=
l Jump backward, short, medium, long: Shift + Left Arrow, Alt + Left Arrow, Ctrl
+ Left Arrow
l Jump forward, short, medium, long: Shift + Right Arrow, Alt + Right Arrow, Ctrl
+ Right Arrow
l Search in trail content: Ctrl + F
About us
One Identity solutions eliminate the complexities and time-consuming processes often
required to govern identities, manage privileged accounts and control access. Our solutions
enhance business agility while addressing your IAM challenges with on-premises, cloud and
hybrid environments.
Contacting us
For sales and other inquiries, such as licensing, support, and renewals, visit
https://www.oneidentity.com/company/contact-us.aspx.