- 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-17-2018 01:49 AM
PAS V9.6
I am currently arranging the connectivity for a PSM implementation.
Currently our PSM servers are only assessable for management purposes via Citrix.
To enable end users browsers to Connect to the PSM servers I need to enable connectivity direct from all users LANS for RDP.
The question is how does the PSM server differentiate between:
TCP/3389 used for the above scenario (managing remote servers)
TCP/3389 used to manage the PSM server itself (it’s a Windows server)
e.g. currently I can RDP to the server itself via Citrix. If the requested connectivity is provided, then the PSM server will be exposed to all user LANs.
Are there any recommendations to how this can be mitigated?
Kevin
08-17-2018 09:59 AM
PSM differentiates based on the Windows user that logs in. PSMConnect and PSMAdminConnect dont get an interactive logon and can only launch the „PSMInitSession.exe“ (iirc) application. All other users are treated normally by Remote Desktop Services.
Maybe there is a Group Policy that you can use to restrict where a user can log on from (PSMConnect from everywhere, Windows admin only from Citrix IP ranges).
Btw: PSM Connection Components that have RemoteApp enabled wont work via Citrix. Some limitation on Citrix side, I can dig up the knowledge base article if you are interested.
08-20-2018 06:14 AM
For users allow the RDP (TCP/3389) to VIP (Load Balanced IP) from their desktops.
For management allow RDP (TCP/3389) to PSM servers from a specific VLAN.
08-20-2018 08:11 AM
Did you have a chance to check out the network area feature so you might even restrict these users to the subnets they can authenticate into PVWA from?
08-20-2018 08:54 AM
08-20-2018 09:00 AM
In this case, I supposed his question is more of protecting the RDP service of the PSM server rather than tackling where users can do a PSM connect from..
08-20-2018 09:03 AM
I wonder if putting a HTML5 gateway in front of the PSM server can help the situation.
08-20-2018 09:13 AM
10-03-2018 07:34 AM
Hey Kevin,
just wondering, any progress on this ?
Cheers
Nirmal
10-18-2018 04:54 AM
Hi Nirmal,
There are a few options that I am ware of which will help mitigate this.
From 10.1 version there is the introduction of HTML5 Browser-based PSM Remote Access, this seems the best option but requires an upgrade to my environment which isn't an option available to me currently.
From a Windows perspective rather than from CyberArk you could try this https://blogs.technet.microsoft.com/leesteve/2017/06/26/allowing-rdp-access-to-only-certain-ips/
or another method would be implementing an RD Gateway
Regards,
Kevin
12-06-2018 03:38 AM
Kevin, we are confronted with the same issue. How did you get on?
kr,
Chris
12-07-2018 02:29 AM
Hi Chris,
With our V9.6 implementation and the limitations placed with this, I have had to enable connectivity over RDP to the PSM's from our LAN to enable users to use PSM.
We have also followed the recommendations with the hardening and also reviewed and restricted any Administrator access to the server.
Depending on your version of the PAS software and the limitations placed with this will very much determine what you can do.
I would recommend the additional security of using W2016 servers if this is an option for you and also the HTML5 Browser-based PSM Remote Access. These are things I am looking at introducing next year when we upgrade to a version 10.X build.
Regards,
Kevin
12-07-2018 02:40 AM
Thanks Kev, actually downloaded the HTML5-GW yesterday. Curious to see how it can help us. Have a great weekend!
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!

