Chat now with support
Chat with Support

Safeguard Authentication Services 4.1.5 - Management Console for Unix Administration Guide

One Identity Privileged Access Suite for Unix Introducing One Identity Management Console for Unix Installing Management Console for Unix Preparing Unix Hosts Working with Host Systems Managing Local Groups Managing Local Users Active Directory Integration Authentication Services Integration Privilege Manager Integration Reporting Setting Preferences Security Troubleshooting Tips
Auto Profile Issues Active Directory Issues Auditing and Compliance Cannot Create a Service Connection Point Check Authentication Services Agent Status Commands Not Available CSV or PDF Reports Do Not Open Database Port Number Is Already in Use Elevation Is Not Working Hosts Do Not Display Import File Lists Fakepath Information Does Not Display in the Console Java Applet Failures License Info in Report is not Accurate Out of Memory Error Post Install Configuration Fails on Unix or Mac Privilege Manager Feature Issues Profile Task Never Completes questusr Account was Deleted Readiness Check Failed Recovering From a Failed Upgrade Reports Are Slow Reset the Supervisor Password Running on a Windows 2008 R2 Domain Controller Service Account Login Fails Setting Custom Configuration Settings Single Sign-on (SSO) Issues JVM Memory Tuning Suggestions Start/Stop/Restart Management Console for Unix Service Tool Bar Buttons Are Not Enabled UID or GID Conflicts
System Maintenance Command Line Utilities Web Services Database Maintenance

Event Logs and Keystroke Logging

Privilege Manager enables event logging. Each time a command is run, the policy server accepts or rejects the requested command according to the rules in the policy and creates an event (audit) log. The policy server records the keystroke input and terminal output for each accepted command, creating comprehensive "keystroke logs" files. With these logs, you can perform forensic-level auditing of any command executed.

Event logs are always captured and stored on the policy servers in /var/opt/quest/qpm4u/pmevents.db; keystroke logs are stored at var/opt/quest/qpm4u/iolog.

Note: You can use the iolog_dir and iolog_file policy options to reconfigure the iolog file location. For more information about the policy options, refer to the Privilege ManagerAdministration Guide.

You can view event logs or replay keystroke logs from the Policy tab of the mangement console if you are logged in either as the supervisor or an Active Directory account with rights to audit the policy file; that is, an account in the Audit Sudo Policy or Audit PM Policy role.

BEST PRACTICE: As a best practice, One Identity recommends that you set up a separate policy server for archiving and viewing logs.

Enable Keystroke Logging

To enable keystroke logging for sudo policy

  1. From the mangement console, navigate to Policy | Sudo Policy Editor.

  2. Open the Open menu and select Current version to open the latest saved version of the policy file that is currently in use by the mangement console. (See Open Policy Files for details.)

  3. Add the following line to the policy file to enable keystroke logs:

    Defaults log_output
  4. Add an entry for a local user in the form who where = (as_whom) what. For example:

    localuser     ALL=(ALL)     ALL

    where localuser is a local user account name.


    • This allows localuser to perform any command on any machine as any user.
    • To set up a local user, see Add Local User.
  5. Save and close the policy.

To enable keystroke logging for pmpolicy

  1. Using the GUI editor, open the role's General setting page and select the Enable keystroke logging option. (See Specify General Settings in the online Help for details.)

Record Keystrokes

Privilege Manager only generates a keystroke log when the policy server accepts a command and keystroke logging is enabled in the policy. When the policy server accepts a command, Privilege Manager records the keystrokes and stores them on the policy server. If the policy server rejects a command, Privilege Manager does not record keystrokes nor does it generate a log.

To generate a keystroke log

  1. Log into the host on which the Privilege Manager software is installed as a non-privileged user specified in the policy.

  2. At the command prompt, enter:

    sudo bash

    Enter your password.

    When you enter sudo bash, it opens a new shell.

  3. At the new shell's command prompt, enter the following lines:

    echo "This is fun."
    echo "My keystrokes are being recorded"

    Note: For a fun demonstration, type echo"This is a mistake" and then backspace over a mistake and enter fixed. When you replay the keystroke log you will see that it records every keystroke!

  4. Enter exit to close the bash shell.

    It records every keystroke after you enter sudo until you enter exit.

You are now ready to replay your keystroke log from the mangement console.

List Events and Replaying Keystroke Logs

Keystroke logs are related to events. When you run a command, such as sudo whoami, the policy server either accepts or rejects the command based on the rules in the policy. When the policy server accepts the command, it creates an event and a corresponding keystroke log. If it rejects the event, it does not create a keystroke log. In order to view a keystroke log, you must first list events.

Note: To record and replay keystroke logs, you must log in either as the supervisor or an Active Directory account with rights to audit the policy file; that is, an account in the Audit Sudo Policy or Audit PM Policy role.

To list events and replay keystroke logs

  1. From the mangement console, navigate to Policy | Event Logs.

    Note: You can also access Event Logs from these context menus:

    • From the host list on the All Hosts view, right-click a host name and choose Find event logs.
    • From the console All Local Users tab, right-click a user name and choose Find event logs.
    • From a host's properties Users tab, right-click a user name and choose Find event logs.
    • From the console Active Directory tab, right-click an AD object name and choose Find event logs.

  2. Select options in the search controls on the Find Event Logs pane, and click Find.

    For example, you can search for all events logged for a particular user, or all events logged on a particular host, or you can find events logged during a specific date and time.

    • In the Policy Group box, select a policy group name.
    • In the Where user is box, enter or select either a local user or Active Directory user.
    • In the Where Host is box, select or enter either a fully qualified host name format ( or a short name format (myhost), depending on how host names are resolved and the use of the short name setting in the pm.settings file.

      Note: Host names may appear in the event logs and keystroke log files in either format. To ensure you match a host name, when you specify host name search criteria, use the short host name format with an asterisk wild card (myhost*).

    • In the Log contains box, enter an optional keyword to search for in the contents of all logs.

      For example, you can find events that pertain to the usage of a specific command or content of the command output.

    • In the Log status box, choose to list all logs reporting Accepted events, Rejected events, or both types of events.
  3. Click the Replay keystroke log button next to a listed event to load the log for replay.

    A Replay Log tab displays.

  4. Click the Play button () to replay the log.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating