Question on deploying PSM+SIA for Internal Users & Vendors

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Question on deploying PSM+SIA for Internal Users & Vendors

L4 Transporter

Hi Team,

I'm seeking clarification regarding the purpose of the two configurations listed below.

  • Are these configurations mutually exclusive?
  • From my understanding, is the main difference that the first option is typically recommended for ISPSS customers or those with a strong internal support team, while the second option is better suited for non-ISPSS customers or those without a robust PAM team?

 

  1. Configure remote for employees using the HTML5 Gateway service
  2. Configure remote access for employees
1 accepted solution

Accepted Solutions

No, the two configurations are not mutually exclusive but serve different purposes.

 

CyberArk Remote Access is a SaaS-based solution that provides secure, passwordless, and just-in-time privileged access for remote vendors and users without requiring VPNs or agents. https://docs.cyberark.com/remote-access-standard/latest/en/content/intro/getstarted.htm

HTML5 Gateway provides a browser-based, clientless connection method, improving security and simplifying vendor and remote-user access.

 

HTML5 Gateway is recommended for ISPSS customers, external vendors, and remote users needing browser-based secure access, while Native Remote Access suits on-prem customers and internal users using native RDP/SSH clients.

 

They can also be combined, where Remote Access manages user authentication and just-in-time provisioning, while the HTML5 Gateway provides a secure, isolated session to access target systems.

View solution in original post

3 REPLIES 3

No, the two configurations are not mutually exclusive but serve different purposes.

 

CyberArk Remote Access is a SaaS-based solution that provides secure, passwordless, and just-in-time privileged access for remote vendors and users without requiring VPNs or agents. https://docs.cyberark.com/remote-access-standard/latest/en/content/intro/getstarted.htm

HTML5 Gateway provides a browser-based, clientless connection method, improving security and simplifying vendor and remote-user access.

 

HTML5 Gateway is recommended for ISPSS customers, external vendors, and remote users needing browser-based secure access, while Native Remote Access suits on-prem customers and internal users using native RDP/SSH clients.

 

They can also be combined, where Remote Access manages user authentication and just-in-time provisioning, while the HTML5 Gateway provides a secure, isolated session to access target systems.

L4 Transporter

Thanks @Vamshi Nivas Dubbasi Sudarshan​.

  • Given that SIA is limited to supporting only four types of targets, for a ISPSS Customer, and considering use case - which requires providing access for both internal users and external vendors to Windows, Linux, network devices, and hypervisors would it be sufficient to proceed with just the first option ?
  • Is HTML5 not used in both the cases in the backend ? I see the same line in both links. (Privilege Cloud uses CyberArk Remote Access and HTML5 to enable secure remote access sessions through PSM from any web browser and any end user platform. This functionality eliminates the need for VPN clients while still enabling privileged users to connect and perform critical work)

First option (HTML5 Gateway Service) is sufficient to provide secure access for both internal users and external vendors and yes, HTML5 Gateway is used in the backend for both options

https://docs.cyberark.com/ispss-deployment/latest/en/content/privilege%20cloud/privcloud-config-remo...

The main difference lies in management and deployment, not in how the sessions are delivered.

Hope this helps!

 

  • 1 accepted solution
  • 120 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!