Chatta subito con l'assistenza
Chat con il supporto

One Identity Safeguard for Privileged Passwords 6.0.12 LTS - User Guide

Reviewing a completed password release request

The Security Policy Administrator can configure an access request policy to require a review of completed password release requests for accounts in the scope of the policy.

You can configure Safeguard for Privileged Passwords to notify you of a password release request that requires your review. For more information, see Configuring alerts.

(web client) To review a completed password release request

Select Reviews on the left of the page to manage reviews. On the Reviews page, you can:

  • View details: Select the request and the details display on the right of the page.
  • Mark one or more request as reviewed: Select the requests. Then, click Mark all the selected requests as reviewed. A comment may be required or, if not required, added.
  • Change the columns that display: Click Select columns to display then select the columns you want to see.
  • Search: For more information, see Search box.

(desktop client) To review a completed password release request

  1. From your  Home page, the Reviews widget has these controls:
    1. Click  (expand down) to open the list of pending reviews.
    2. Click  Popout to float the Reviews pane.

      You can then select and drag the pane to any location on the console and re-size the window.

    NOTE: You enable or disable the Home page widgets in the  Settings (desktop client) menu.

  2. Open the list of pending reviews and select an account name to see the details of the password release request.

  3. Take the following action on password release requests:

    • Select Workflow to review the transactions that took place in the selected request.
    • Select  Review to complete the review process.

      Optionally, enter a comment of up to 255 characters.

    Once the review is complete, it no longer appears on the Reviews pane.

TIP: If one requester checks in the request and another requester wants to use it, the second requester is unable to check out the password until the original request has been reviewed. However, the Security Policy Administrator can Close a request that has not yet been reviewed. This will bypass the reviewer in the workflow and allow the account to be accessed by another requester.

Session request workflow

Authorized users can authorize connections, view active connections, limit access to specific resources, be alerted if connections exceed pre-set time limits, and even terminate connections.

Typically a session request follows the workflow below:

  1. Request: Users that are designated as an authorized user of an entitlement can request a session for any asset in the scope of that entitlement's policies.
  2. Approve: Depending on how the Security Policy Administrator configured the policy, a session request will either require approval by one or more Safeguard for Privileged Passwords users, or be auto-approved.
  3. Review: The Security Policy Administrator can optionally configure an access request policy to require a review of completed requests for assets in the scope of the policy. In addition, if session recording is enabled in the policy, reviewers can audit the workflow transactions and launch the Desktop Player to replay the session as part of the review process.

The following topics explain the entire end-to-end session access process from request to approval to review (and play back if sessions recording is enabled).

About sessions and recordings

One Identity Safeguard for Privileged Passwords proxies all sessions to target resources. Users do not have direct access to resources, therefore, the enterprise is protected against viruses, malware or other dangerous items on the user's system. Safeguard can proxy and record Unix/Linux, Windows, network devices, firewalls, routers and more.

NOTE: PuTTY is used to launch the SSH client for SSH session requests and is included in the install. The desktop client looks for any user-installed PuTTY in the following locations:

  • Any reference to putty in the PATH environment variable
  • c:/Program Files/Putty
  • c:/Program Files(x86)/Putty
  • c:/Putty

If PuTTY is not found, the desktop client uses the version of PuTTY that it installed at:

<user-home-dir>/AppData/Local/Safeguard/putty.

If the user later installs PuTTY in any of the locations above, the desktop client uses that version which ensures the user has the latest version of PuTTY.

Important notes

  • Sessions requests are enabled by default. However, if authorized users cannot request sessions, check the Session Requests Enabled setting in the desktop client (Administrative Tools | Settings | Access Request | Enable or Disable Services).

    NOTE: You must have Appliance Administrator permissions to manage the service settings.

  • All session activity (every packet sent and action that takes place on the screen, including mouse movements, clicks, and keystrokes) is recorded and available for play back.
  • If Safeguard for Privileged Passwords detects no activity for 10 minutes during a privileged session, the session is terminated.

Requesting session access

If you are designated as an authorized user of an entitlement, you can request access for a specific period (or session) to any account or asset in the scope of the entitlement's policies.

You can configure One Identity Safeguard for Privileged Passwords to notify you of pending access request workflow events, such as when a session request is pending, denied, or revoked, and so on. For more information, see Configuring alerts.

To request session access

  1. Go to the new access request page:

    • From the web client, click Home or My Requests, then click New Request.
    • From the desktop client, go to the Home page, then click New Request.

    NOTE: You can also submit an access request from your Favorites pane, if you previously saved it as a favorite.

  2. On Asset Selection, select the assets to be included in the access request. The assets available for selection are based on the scope defined in the entitlement's access request policies. The limit is 50 assets.
    If an SPS_Initiated connection policy is selected when creating an access request, the assets associated by that request will not display. The session-related access policy assigned to SPS_Initiated is filtered out. A connection policy other that SPS_Initiated must be selected to create an Access Request for the asset.

  3. On Account & Access Type Selection, select the accounts to be included in the access request and the type of access being requested for each selected account. The accounts include linked accounts, if any.

    • Asset: The display name of the managed system.
    • Network Address: The network host name or IP address of the managed system.

    • Account: The accounts available appear in the Account column. When an asset has multiple accounts available, either Select Account(s) or the account name appears as a hyperlink in the Account column. Click the hyperlink in the Account column to display a list of accounts available and select the accounts to be included in the access request.

      The accounts available for selection are based on the Asset-Based Session Access setting. For more information, see Access Config tab in the Safeguard for Privileged Passwords Administration Guide. Or, the accounts available for selection may have been added in the Scope tab when editing the entitlement access policy. For more information, see Scope tab in the Safeguard for Privileged Passwords Administration Guide.

      The settings are:

      • If None is selected in the access request policy, the accounts Safeguard for Privileged Passwords retrieved from the vault will be available for selection. The selected account will then be used when the session is requested.

      • If User Supplied is selected in the access request policy, you will be required to enter the user credentials as part of the request workflow, prior to launching the SSH, RDP, or telnet session.

      • If Linked Account is selected in the access request policy, linked directory accounts will be available for selection. The selected account will then be used when the session is requested.

      • If Directory Account is selected in the access request policy, only the specified directory accounts will be available for selection. The selected directory account will then be used when the session is requested.

    • Domain: The name of the domain for the request.

    • Access Type: The type of access request appears in the Access Type column. When multiple access request types are available, this value appears as a hyperlink, which when selected displays an additional dialog allowing you to select the access type. Select one of the following for a session request: RDP, SSH, or Telnet.

      The access type options available depend on the type of asset selected on Asset Selection. For example, RDP is only available for Windows sessions.

    You can remove an asset or account from the list, select the entry and click Delete.

  4. On the Request Details tab, configure the following settings, which will apply to all of the selected assets and accounts:

    1. Normal Access: If the policy has emergency access enabled, select this option to gain normal access to this password. Normal access ensures the access request goes through the entire end-to-end access release process from request to approval to review as defined in the policy by the Security Policy Administrator.

    2. Emergency Access: If the policy has emergency access enabled, select this option to gain immediate emergency access to this password. When you use Emergency Access, the request requires no approval.

    3. Request Immediately: Clear this option to enter a specific date and time for the request. Enter the time in the user’s local time.

    4. Checkout Duration: This either displays the Checkout Duration; or, if the Allow Requester to Change Duration option is enabled in the policy, it allows you to set the days, hours, and minutes that you want the password and overrides the Checkout Duration set in the access request policy.

    5. Ticket Number: If the policy requires a ticket number, enter a valid ticket number for this request. When multiple accounts are specified in the request, if any of the selected accounts require a ticket number, you must specify a valid ticket number. The specified ticket number will be applied to all of the requests associated with this access request. This feature is set up through the desktop client.

    6. Reason: If the policy requires reason, select an access request reason code for this request. Select the Description down arrow to view the description defined for the selected reason. When multiple accounts are specified in the request, if any of the selected accounts require a reason, you must specify a reason. The specified reason will be applied to all of the requests associated with this access request.

    7. Comment: Enter information about this request. When multiple accounts are specified in the request, if any of the selected accounts require a comment, you must enter a comment. The comment will be applied to all of the requests associated with this access request. The limit is 255 characters.

  5. To save the access request as a favorite, click the Add to Favorites button.

    Add to Favorites displays, allowing you to specify a name and description for the access request. It also allows you to assign a color to the request's icon.

    This access request is then added to your Favorites. How you manage favorites depends on your interface:

  6. After entering the required information, click Submit Request. Access Request Result displays showing you the access requests submitted and whether a request was successful.

  7. To copy or view information, click the  (expand down) arrow on the left of an active request.

    • If the access request is for sessions:
      • Click  Copy to copy the connection string to the clipboard. Paste the string into a client application to launch the session.
      • Click Show to view the connection string.
      • Click Help to copy the value into the appropriate field of the configuration dialog.
    • If the access request is for passwords:
      • Click  Copy to copy credential to the clipboard. The credential can then be pasted into the dialog that needs the credential to grant access.
      • Click Show to view the credential.
      • Click Help to copy the value into the appropriate field of the configuration dialog.

If the session does not launch

In a rare event that the access request does not result in a launchable session request, the following notifications display:

  • Please try again. The linked sessions module state is currently down or may be in a locked state. This message may mean one of the following:
    • SPP could not contact SPS. Try again so the request can be redirected to another managed host in the SPS cluster.

    • The SPS configuration is locked. Try again because this condition is typically because the SPS administrator is making configuration changes to the SPS appliance at the same time that a new access request is being created or a session is being launched.

  • Missing the session connection policy. or
    The selected Access Request Policy cannot be used to initiate a session from SPP. The highest priority policy must be associated with a valid SPS connection policy.
    Check the connection policy configuration. In the desktop client, go to Entitlements | Access Request Policy | Sessions Settings to add a valid connection policy. Save the policy and recreate the access request. For more information, see Session Settings tab in the Safeguard for Privileged Passwords Administration Guide.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione