- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
08-24-2025 11:30 PM
Hi Team,
I'm seeking clarification regarding the purpose of the two configurations listed below.
08-25-2025 12:07 AM
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.
08-25-2025 12:07 AM
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.
08-25-2025 12:46 AM
Thanks @Vamshi Nivas Dubbasi Sudarshan.
08-25-2025 01:02 AM
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
The main difference lies in management and deployment, not in how the sessions are delivered.
Hope this helps!
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!

