<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Setting up a secure WinSCP connection in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413090#M6555</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I suggest opening a case to get that resolved as you should be able to prevent users from seeing the PSM drives.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jun 2026 14:35:09 GMT</pubDate>
    <dc:creator>D.Demshock823557</dc:creator>
    <dc:date>2026-06-11T14:35:09Z</dc:date>
    <item>
      <title>Setting up a secure WinSCP connection</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413087#M6552</link>
      <description>&lt;P&gt;I am setting up access for remote users to use CyberArk WinSCP platform to access a file share on a target device. I  find that when the access is set up the user can also browse the files in C:\ drive on the PSM server in WinSCP. This is very insecure. How do I prevent this?&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2026 11:35:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413087#M6552</guid>
      <dc:creator>cyberpro006</dc:creator>
      <dc:date>2026-06-11T11:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up a secure WinSCP connection</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413088#M6553</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;For self-hosted the PSM comes with a PowerShell script to hide the PSM drives. Here is a reference - https://community.cyberark.com/s/article/How-to-hide-local-PSM-Drives&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2026 14:20:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413088#M6553</guid>
      <dc:creator>D.Demshock823557</dc:creator>
      <dc:date>2026-06-11T14:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up a secure WinSCP connection</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413089#M6554</link>
      <description>&lt;P&gt;I have ran that script 3 times now and deleted all the PSM shadow users and I am still having this issue. The user is able to browse the PSM server C drive by moving up the directory. &lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2026 14:32:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413089#M6554</guid>
      <dc:creator>cyberpro006</dc:creator>
      <dc:date>2026-06-11T14:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: Setting up a secure WinSCP connection</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413090#M6555</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I suggest opening a case to get that resolved as you should be able to prevent users from seeing the PSM drives.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2026 14:35:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/setting-up-a-secure-winscp-connection/m-p/1413090#M6555</guid>
      <dc:creator>D.Demshock823557</dc:creator>
      <dc:date>2026-06-11T14:35:09Z</dc:date>
    </item>
  </channel>
</rss>

