18.3.2. Procedure – Performing four-eyes authorization on PSM

Steps: 

  1. When a user initiates a connection from a client and four-eyes authorization is required for the connection, PSM will pause the connection.

    Note

    Four-eyes authorization can be set separately for every channel. However, if a new channel that requires four-eyes authorization is opened in an existing connection, the channels already opened are also paused until the four-eyes authorization is successfully completed.

  2. Login to PSM, and select Four-Eyes from the main menu. The list of connections waiting for authorization will be displayed.

    Figure 18.7. Four-Eyes — Performing four-eyes authorization

    Four-Eyes — Performing four-eyes authorization
    Note

    Only those connections will be listed, where your usergroup has the Authorize or the Audit&Authorize permissions. No other PSM privilege is required to access this page.

  3. Select the connection and click Accept to enable the connection, Reject to deny the connection, or Accept&Follow to enable it and monitor in real-time.

    Note

    Following a session requires the following:

    • The Audit option must be enabled for the specific channel in the Channel policy of the connection.

    • The Audit Player application must be installed on the computer of the auditor.

    • If the Audit policy of the connection uses encryption, the appropriate decryption keys must be available on the computer of the auditor.

    Starting with Audit Player version 2012.1, AP replays the live streams in live mode, increasing the replay speed, skipping idle periods, and reverting to real-time replay when reaching the end of the current stream.

    Starting with Balabit Desktop Player version 1.1, Balabit Desktop Player replays the live streams in live mode. For details on how to monitor a connection in real-time using the Balabit Desktop Player, see Procedure 9, Replay audit files in follow mode in Balabit Desktop Player User Guide.

  4. Enter a note why the connection was accepted/rejected into the appearing dialog box. This description will be stored in the connection database together with other metadata about the connection.

    Figure 18.8. Describing why a connection was accepted/rejected

    Describing why a connection was accepted/rejected
  5. If you have to terminate an ongoing connection for some reason, select Active Connections from the main menu. The list of ongoing connections will be displayed.

    Figure 18.9. Active Connections — Displaying active connections

    Active Connections — Displaying active connections
  6. Select the connection to stop, and click Terminate.

    Note

    When following a connection in the Audit Player application, the auditor can also terminate the connection from the Audit Player by clicking Terminate.

    Figure 18.10. Terminating a connection in AP

    Terminating a connection in AP