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.
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 Console Settings menu.
Take the following action on password release requests:
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.
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:
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).
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.
Sessions requests are enabled by default. However, if authorized users cannot request sessions, check the Session Requests Enabled setting (Administrative Tools | Settings | Access Request | Enable or Disable Services).
NOTE: You must have Appliance Administrator permissions to manage the service settings.
Both SSH and RDP session recordings use the Timestamping Certificate Authority.
Recordings are signed and timestamped every 30 seconds so that partial recordings may be verified as authentic.
During an RDP session, Safeguard proxies the connection to the target asset.
When an RDP connection is established, the embedded sessions module will generate a certificate on the fly and sign it using the RDP Connection Signing Certificate. Therefore the RDP client trusts the RDP Connection Signing Certificate and the generated certificate that is signed by the RDP Connection Signing Certificate. This allows the client to verify that the connection is trusted.
During an SSH session, Safeguard proxies the connection to the target asset. Therefore, Safeguard for Privileged Passwords's SSH host key (Settings | Sessions | SSH Host Key) must be trusted by the client. This SSH host key is unique and produced during manufacturing. This key can be trusted by the client or replaced with a different key if desired.
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 forth. For more information, see Configuring alerts.
To request session access
From your Home page, click New Request to open the New Access Request dialog.
NOTE: You can also submit an access request from your Favorites pane, if you previously saved it as a favorite.
On the Asset Selection tab, select the assets to be included in the access request.
Limit: 50 assets
The assets available for selection are based on the scope defined in the entitlement's access request policies.
On the Account & Access Type tab, 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.
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 (Access Config tab) defined for the entitlement's access request policy. That is:
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 or RDP session.
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.
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 or SSH.
The access type options available depend on the type of asset selected on the Asset Selection tab. For example, RDP is only available for Windows sessions.
To remove an asset or account from the list, select the entry in the grid and click the Delete toolbar button.
Normal Access: (This option is only available 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.
Emergency Access: (This option is only available 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.
Request Immediately: Clear this option to enter a specific date and time for the request. Enter the time in the user’s local time.
Ticket Number: Enter a valid ticket number for this request.
Safeguard for Privileged Passwords does not display the Ticket Number option unless the Security Policy Administrator selected Require Ticket Number for this policy.
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.
Reason: Select an access request reason code for this request.
Select the Description down arrow to view the description defined for the selected reason.
Safeguard for Privileged Passwords does not display the Reason option unless the Security Policy Administrator selected reasons for this policy.
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.
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.
Limit: 255 characters
To save the access request as a favorite, click the Add to Favorites button.
The Add to Favorites dialog 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 Home page Favorites pane. Selecting it from the Favorites pane displays the New Access Request dialog allowing you to edit the request details or enter a required reason or comment before submitting the request.
After entering the required information, click Submit Request.
The Access Request Result dialog displays showing you the access requests submitted and whether a request was successful.