Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

IBM Privileged Session Recorder

 

The JSA DSM for IBM Privileged Session Recorder can collect event logs from your IBM Privileged Session Recorder device.

The following table lists the specifications for the IBM Privileged Session Recorder DSM.

Table 1: IBM Privileged Session Recorder Specifications

Specification

Value

Manufacturer

IBM

DSM name

Privileged Session Recorder

RPM filename

DSM-IBMPrivilegedSessionRecorder

Protocol

JDBC

JSA recorded event types

Command Execution Audit Events

Automatically discovered?

No

Includes identity?

No

More information

(https://support.juniper.net/support/downloads/)

To collect IBM Privileged Session Recorder events, use the following procedures:

  1. If automatic updates are not enabled, download and install the following RPMs on your JSA Console:

    • Protocol-JDBC RPM

    • IBM Privileged Session Recorder DSM RPM

  2. On the IBM Security Privileged Identity Manager dashboard, obtain the database information for the Privileged Session Recorder data store and configure your IBM Privileged Session Recorder DB2 database to allow incoming TCP connections.

  3. For each instance of IBM Privileged Session Recorder, create an IBM Privileged Session Recorder log source on the JSA Console. Use the following table to define the Imperva SecureSphere parameters:

    Table 2: IBM Privileged Session Recorder Log Source Parameters

    Parameter

    Description

    Log Source Type

    IBM Privileged Session Recorder

    Protocol Configuration

    JDBC

    Log Source Identifier

    DATABASE@HOSTNAME

    Database Type

    DB2

    Database Name

    The Session Recorder data store name that you configured on the IBM Privileged Identity Manager dashboard.

    IP or Hostname

    The Session Recorder database server address.

    Port

    The port that is specified on IBM Privileged Identity Manager dashboard.

    Username

    The DB2 database user name

    Password

    The DB2 database password

    Predefined Query

    IBM Privileged Session Recorder

    Use Prepared Statements

    This option must be selected.

    Start Date and Time

    The initial date and time for the JDBC retrieval.

Configuring IBM Privileged Session Recorder to Communicate with JSA

Before you can configure a log source in IBM Privileged Session Recorder for JSA, obtain the database information for the Privileged Session Recorder data store. You must also configure your IBM Privileged Session Recorder DB2 database to allow incoming TCP connections from JSA.

IBM Privileged Session Recorder is a component of IBM Security Privileged Identity Manager.

  1. Log in to the IBM Security Privileged Identity Manager web user interface.
  2. Select the Configure Privileged Identity Manager tab.
  3. Select Database Server Configuration in the Manage External Entities section.
  4. In the table, double-click the Session Recording data store row in the Database Server Configuration column.
  5. 5. Record the following parameters to use when you configure a log source in JSA:

    IBM Privileged Session Recorder Field

    JSA Log Source Field

    Hostname

    IP or Hostname

    Port

    Port

    Database name

    Database Name

    Database administrator ID

    Username

Configuring a Log Source for IBM Privileged Session Recorder

JSA does not automatically discover IBM Privileged Session Recorder events. To integrate IBM Privileged Session Recorder event data, you must create a log source for each instance from which you want to collect event logs.

  1. Log in to JSA.
  2. Click the Admin tab.
  3. In the navigation menu, click Data Sources.
  4. Click the Log Sources icon.
  5. Click Add.
  6. In the Log Source Name field, type a name for your log source.
  7. From the Log Source Type list, select IBM Privileged Session Recorder.
  8. From the Protocol Configuration list, select JDBC.
  9. Configure the parameters for the log sorce.
  10. Click Save.
  11. On the Admin tab, click Deploy Changes.

Related Documentation