Cisco Cyber Vision New UI Administration Guide, Release 5.6.0

Remote asset session requests

Updated: September 8, 2026

Want to summarize with AI?

Describe how remote asset session requests are managed and approved within Cyber Vision Secure Remote Access (CV SRA), outlining their key attributes and responsible roles.

A remote asset session request is a workflow in CV SRA that enables authorized users to request access to specific assets, designates Access Managers as the primary approvers for session requests, and permits SRA System Admins or SRA Access Admins to approve requests if Access Managers are unavailable.

Enables authorized users to request access to specific assets.
Designates Access Managers as the primary approvers for session requests.
Permits SRA System Admins or SRA Access Admins to approve requests if Access Managers are unavailable.

User roles and permissions for remote asset session requests

The following table lists the user roles and their permissions for managing remote asset session requests in CV SRA.

Table 1. User roles and permissions for remote asset session requests
User role	Permissions
SRA System Admins	Manage all requests in the organization
SRA Access Admins	Manage all requests in the organization
SRA Access Managers	Manage requests only for groups where they are assigned as approvers

Possible causes for 512 errors by protocol

The following conditions can cause a 512 error when you connect to a remote session:


Access method	Possible causes
SSH	Internal server error. The asset host key could not be retrieved. An error occurred while checking the host key. The provided host key does not match a known host key.
RDP and Telnet	Internal server error.
VNC	Internal server error. Unsupported credential type.

Manage requests as an SRA access manager

Review, approve, or deny pending remote asset session requests submitted by users in groups you manage.

SRA Access Managers handle access requests for assigned groups. Requests appear in the dashboard only if you are set as an approver for the group.

Before you begin

Ensure you have the SRA Access Manager role and are assigned to the relevant group.

Procedure

Log in to the Cisco IoT Operations Dashboard as an SRA Access Manager.
Choose SRA > Access Management.
On the Access Management pane, select the Pending Requests tab.

The My pending requests tab appears.

All requests for which you are an approver are listed in this tab. These requests are submitted by users within your group.
In the Actions column, select Approve , Deny , or View .

The request is approved or denied.

What to do next

Users with SRA User role can connect to the remote session by logging in to the IoT Operations Dashboard.

Manage requests as a SRA system or access admin

Approve or deny any pending remote asset session requests organization-wide.

SRA System admins and access admins can manage all session requests, including those assigned to specific access managers.

Before you begin

Ensure you are logged in as either a System Admin or Access Admin.

Procedure

Log in to the Cisco IoT Operations Dashboard as a System or Access Admin.
Choose SRA > Access Management > Pending Requests > All pending requests.

All requests in your organization that need approval are listed here, including those assigned to the Access Managers.
In the Actions column, select Approve, Deny, or View.

Request outcomes

A request outcome is a remote access management state that determines what happens after a request is approved or denied in Cisco IoT Operations Dashboard.

Sends an email notification to the SRA user after a request is approved or denied.
Provides instructions to the user regarding next steps based on the request decision.
Allows access to the requested remote session upon approval or requires re-initiating the request if denied.

Additional reference information about request outcomes

When a request is approved, the user can access and connect to the remote session by clicking the View button in the notification email, which directs them to the Remote Sessions page of Cisco IoT Operations Dashboard. If a request is denied, the remote session status changes to Request Access, and the user must submit a new request to obtain access.

Request History details

The Request History tab displays access request entries that vary depending on your user role.

You can view the history of all access requests in the Request History tab. The entries displayed in the Request History tab vary depending on your user role.

Table 2. Request History tab entries by user role
User role	Request History tab entries
SRA System Admins	All approved, denied, expired, revoked, and withdrawn requests for all users across all groups in the organization
SRA Access Admins	All approved, denied, expired, revoked, and withdrawn requests for all users across all groups in the organization
SRA Access Managers	All approved, denied, expired, revoked, and withdrawn requests of all users in the group where they are assigned as approvers. They cannot refer to the entries of a group where they are not the approvers.

Revoke an approval request

Cancel an approved remote asset session request if it was authorized in error.

Revoking a request removes approval but does not affect any currently active sessions. Sessions continue until timeout, but new connections based on the revoked request are blocked. All revoked requests appear in the Request History tab. The request history can be sorted or downloaded for further review.

Before you begin

Ensure you have the necessary permissions (such as SRA Access Manager, Access Admin, or System Admin role).

Procedure

Go to the Request History tab.
Select the request you want to revoke.
Click Revoke in the Actions menu.
Alternatively, select View in the Actions menu and then click Revoke on the View Details page.

The request status changes to “revoked” in the Request History tab. The current session remains active until timeout, but users cannot initiate new connections with the revoked request.

What to do next

You may sort or filter the Request History by various criteria or download the list as a CSV file for auditing.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.