- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-21-2026 05:53 AM
Hi Team,
We are currently using the out-of-the-box WinSCP connection component in Idira Privilege Cloud.
The WinSCP connection is working successfully, and users are able to launch WinSCP and connect to the target server as expected.
However, we have a security requirement where the end user should only be able to access their local/client drives through the WinSCP session. They should not be able to browse or access the drives of the PSM Component Server.
Currently, when the user launches the WinSCP session, they are able to see/access the drives of the PSM Component Server in addition to their local drives.
We followed the steps mentioned in the following Idira article to restrict access to the PSM Component Server drives:
Reference article:
https://community.cyberark.com/s/article/00003645
However, even after following the steps in the article, the end user is still able to access/browse the PSM Component Server drives.
Our requirement is:
Could someone please advise on the recommended Idira-supported approach for WinSCP in Privilege Cloud to achieve this?
We would also like to understand whether this should be handled through:
We have already tried the approach mentioned in the above article, but the PSM Component Server drives are still accessible to the end user.
Any guidance on the correct configuration or recommended approach would be greatly appreciated.
Thank you.
08-21-2026 10:01 AM
Hey @Jagadeshwar Reddy Sudha This is related to WinSCP version 6.3.3, it has it's own file explorer which doesn't adhere to the OS policies for navigating directories. Make sure you're on the latest version of PCLOUD PSM 15.0 which fixes this. It comes with *\PSM\Components\PSMWinSCPDispatcher.exe v15.0.0.x and WinSCP.exe v6.5.5.x
If you haven't yet upgraded to 15.0, you can manually upgrade just the WinSCP component via:
https://community.cyberark.com/marketplace/s/#a3550000000EiD1AAK-a3950000000jjW9AAI
08-21-2026 06:15 AM
Hello,
I wouldn't use the script in that article and would use the one that came with the PSM server installation package.
This reference shows a command to test drive availability which could be helpful - https://community.cyberark.com/s/article/How-to-hide-local-PSM-Drives.
08-21-2026 06:46 AM
hi @Donovan Demshock
Thank you for the solution.
We have applied the recommended HideLocalDrives.ps1 solution. It successfully hides the C: drive for other PSM sessions.
However, when launching the WinSCP PSM connection, we are still able to see and access the PSM Component Server drives.
Could you please advise if there is any additional configuration required specifically for the WinSCP PSM connection to restrict access to the PSM Component Server drives while still allowing users to access their local drives?
Thank you.
08-21-2026 10:01 AM
Hey @Jagadeshwar Reddy Sudha This is related to WinSCP version 6.3.3, it has it's own file explorer which doesn't adhere to the OS policies for navigating directories. Make sure you're on the latest version of PCLOUD PSM 15.0 which fixes this. It comes with *\PSM\Components\PSMWinSCPDispatcher.exe v15.0.0.x and WinSCP.exe v6.5.5.x
If you haven't yet upgraded to 15.0, you can manually upgrade just the WinSCP component via:
https://community.cyberark.com/marketplace/s/#a3550000000EiD1AAK-a3950000000jjW9AAI
09-07-2026 01:43 AM
Thank you for the detailed information and guidance!
We upgraded the WinSCP version as suggested, and the issue has been resolved. We really appreciate your help in identifying the root cause and providing the solution.
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!

