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.
CAUTION:The embedded sessions module in Safeguard for Privileged Passwords version 2.7 (and later) will be removed in a future release (to be determined). For uninterrupted service, organizations are advised to join to the more robust Safeguard for Privileged Sessions Appliance for sessions recording and playback.
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. The assets available for selection are based on the scope defined in the entitlement's access request policies. The limit is 50 assets.
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, RDP
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, 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: 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: 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: 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.
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.
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.
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.
In a rare event that the access request does not result in a launchable session request, the following notifications display:
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.
The actions a user authorized to request access to a privileged session can take depends on the state of the request.
Note: You enable or disable the Home page widgets in the Settings menu.
Open the list of requests and select one of these view filters. The number indicates how many requests are in that state.
The approver can revoke a request between the time the requester launches the session and checks it back in.
When a user with Security Policy Administrator permissions revokes a "live" session, the active session is terminated.
You can take the following actions on session requests, depending on the state.
In addition, you can use the following buttons to view or copy information into the dialog that contains the credentials needed to launch the session.
Approved: Select Cancel to remove the request. A session request changes from "Approved" to "Available" when the requested time is reached. It stays available until you either cancel the request or it reaches the end of the duration period.