<?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>article PSM - Lock down PSM RDP access for users using PSM's RDP proxy function in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/psm-lock-down-psm-rdp-access-for-users-using-psm-s-rdp-proxy/ta-p/1430072</link>
    <description>For environments where PSM's RDP proxy is used (using an RDP client to connect through the PSM), the connecting accounts will normally need RDP access to the PSM server.&amp;nbsp; This leaves the PSM open and allows users the ability to bypass PSM session monitoring by opening another RDP window from the PSM server.&amp;nbsp; To help lock down the PSM to users but leave PSM connections open through RDP proxy, AppLocker may be used.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;OL&gt;&lt;LI&gt;On the PSM server, open gpedit.msc and go to "Computer Configuration &amp;gt; Windows Settings &amp;gt; Security Settings &amp;gt; Application Control Policies &amp;gt; AppLocker &amp;gt; Executable Rules".&lt;/LI&gt;&lt;LI&gt;Right-click on "Executable Rules" and select "Create New Rule".&lt;/LI&gt;&lt;LI&gt;Select Deny as the action.&amp;nbsp; Under "User or Group" select the target user or group that will be restricted.&lt;/LI&gt;&lt;LI&gt;For the type of condition, select Path.&lt;/LI&gt;&lt;LI&gt;Set the path to "*".&lt;/LI&gt;&lt;LI&gt;Under Exceptions, add a new exception for PSMInitSession.exe (by default, under "C:\Program Files (x86)\CyberArk\PSM\Components").&amp;nbsp; Set the rule scope to any level needed (note: if file version is selected, this must be updated every time the PSM is upgraded).&lt;/LI&gt;&lt;LI&gt;Lastly, set the name of the rule and click Create.&amp;nbsp; The user will now be able to connect through the PSM for monitored sessions, but will be presented with a blank screen if they attempt to access the PSM server directly.&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Tue, 04 Aug 2020 16:57:07 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2020-08-04T16:57:07Z</dc:date>
    <item>
      <title>PSM - Lock down PSM RDP access for users using PSM's RDP proxy function</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/psm-lock-down-psm-rdp-access-for-users-using-psm-s-rdp-proxy/ta-p/1430072</link>
      <description>For environments where PSM's RDP proxy is used (using an RDP client to connect through the PSM), the connecting accounts will normally need RDP access to the PSM server.&amp;nbsp; This leaves the PSM open and allows users the ability to bypass PSM session monitoring by opening another RDP window from the PSM server.&amp;nbsp; To help lock down the PSM to users but leave PSM connections open through RDP proxy, AppLocker may be used.

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;OL&gt;&lt;LI&gt;On the PSM server, open gpedit.msc and go to "Computer Configuration &amp;gt; Windows Settings &amp;gt; Security Settings &amp;gt; Application Control Policies &amp;gt; AppLocker &amp;gt; Executable Rules".&lt;/LI&gt;&lt;LI&gt;Right-click on "Executable Rules" and select "Create New Rule".&lt;/LI&gt;&lt;LI&gt;Select Deny as the action.&amp;nbsp; Under "User or Group" select the target user or group that will be restricted.&lt;/LI&gt;&lt;LI&gt;For the type of condition, select Path.&lt;/LI&gt;&lt;LI&gt;Set the path to "*".&lt;/LI&gt;&lt;LI&gt;Under Exceptions, add a new exception for PSMInitSession.exe (by default, under "C:\Program Files (x86)\CyberArk\PSM\Components").&amp;nbsp; Set the rule scope to any level needed (note: if file version is selected, this must be updated every time the PSM is upgraded).&lt;/LI&gt;&lt;LI&gt;Lastly, set the name of the rule and click Create.&amp;nbsp; The user will now be able to connect through the PSM for monitored sessions, but will be presented with a blank screen if they attempt to access the PSM server directly.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Tue, 04 Aug 2020 16:57:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/psm-lock-down-psm-rdp-access-for-users-using-psm-s-rdp-proxy/ta-p/1430072</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2020-08-04T16:57:07Z</dc:date>
    </item>
  </channel>
</rss>

