<?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: Broker bypass controls as a preventative control in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320635#M20109</link>
    <description>&lt;P&gt;Hi Jon, I believe you can achieve this through &lt;/P&gt;&lt;P&gt;Configure Windows Firewall Rules on the target servers to allow RDP access only from the PSM server.&lt;/P&gt;&lt;P&gt;Use Local Security Policy (secpol.msc) or Group Policy (GPO) to enforce "Deny Logon Locally" and "Deny Logon Through RDP" for all admin accounts except the PSM service account.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Feb 2025 15:11:29 GMT</pubDate>
    <dc:creator>S.Vishwakarma290899</dc:creator>
    <dc:date>2025-02-26T15:11:29Z</dc:date>
    <item>
      <title>Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320633#M20107</link>
      <description>&lt;P&gt;I am curious about methods used to block logins that bypass the PSM. Let's assume we are talking about Windows target servers, which are onboarded to CyberArk and admins are expected to use PSM to access them. Further, lets assume a bad actor has a username and password with admin privileges on the target server (eg a backdoor account created by a server admin)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Clearly PTA can help detect a login that bypasses PSM, but that's a detective control not preventative.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;IP based firewalls could help with this, blocking access to the target server except from the PSM. But in a complex network it can be very hard to reliably configure the firewalls.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What other controls can be used to prevent someone logging in to a target Windows server and bypassing PSM? For instance is there something that can be done with mutual certificate validation? &lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 14:57:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320633#M20107</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-02-26T14:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320634#M20108</link>
      <description>&lt;P&gt;Hi Jon, I believe you can achieve this through &lt;/P&gt;&lt;P&gt;Configure Windows Firewall Rules on the target servers to allow RDP access only from the PSM server.&lt;/P&gt;&lt;P&gt;Use Local Security Policy (secpol.msc) or Group Policy (GPO) to enforce "Deny Logon Locally" and "Deny Logon Through RDP" for all admin accounts except the PSM service account.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 15:11:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320634#M20108</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-02-26T15:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320635#M20109</link>
      <description>&lt;P&gt;Hi Jon, I believe you can achieve this through &lt;/P&gt;&lt;P&gt;Configure Windows Firewall Rules on the target servers to allow RDP access only from the PSM server.&lt;/P&gt;&lt;P&gt;Use Local Security Policy (secpol.msc) or Group Policy (GPO) to enforce "Deny Logon Locally" and "Deny Logon Through RDP" for all admin accounts except the PSM service account.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 15:11:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320635#M20109</guid>
      <dc:creator>S.Vishwakarma290899</dc:creator>
      <dc:date>2025-02-26T15:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320636#M20110</link>
      <description>&lt;P&gt;Hi Jon, I believe you can achieve this through &lt;/P&gt;&lt;P&gt;Configure Windows Firewall Rules on the target servers to allow RDP access only from the PSM server.&lt;/P&gt;&lt;P&gt;Use Local Security Policy (secpol.msc) or Group Policy (GPO) to enforce "Deny Logon Locally" and "Deny Logon Through RDP" for all admin accounts except the PSM service account.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 15:11:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320636#M20110</guid>
      <dc:creator>S.Vishwakarma290899</dc:creator>
      <dc:date>2025-02-26T15:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320637#M20111</link>
      <description>&lt;P&gt;thanks for your answer @Suresh Vishwakarma​&amp;nbsp; I am not relying on firewalls as a control in this scenario, as I mention in the question.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Deny Logon settings will block that particular user from logging in to be sure, but it doesn't discriminate whether the login attempt was via PSM or not, so this doesn't fully answer me. A partial solution is indeed to block logon for any account that isn't managed by CyberArk, however there is no way for the OS to validate whether or not an account is managed by CyberArk. Disabling the account has a similar effect.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 16:16:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320637#M20111</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-02-26T16:16:34Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320638#M20112</link>
      <description>&lt;P&gt;you're right, Windows Deny Logon policies don’t differentiate between logins through CyberArk PSM and direct logins, and the OS itself isn’t aware of whether access is coming from PSM.&lt;/P&gt;&lt;P&gt;I think better approach is to use controls that enforce PSM-only access by integrating CyberArk with Windows security mechanisms.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's how it can be done:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Restrict Logins to CyberArk-Managed Accounts – Configure Windows policies so that only accounts managed by CyberArk can log in.&lt;/LI&gt;&lt;LI&gt;Enforce Kerberos Authentication – Block NTLM and ensure that privileged access happens only through PSM via Kerberos.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 26 Feb 2025 17:27:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320638#M20112</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-02-26T17:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320639#M20113</link>
      <description>&lt;P&gt;you're right, Windows Deny Logon policies don’t differentiate between logins through CyberArk PSM and direct logins, and the OS itself isn’t aware of whether access is coming from PSM.&lt;/P&gt;&lt;P&gt;I think better approach is to use controls that enforce PSM-only access by integrating CyberArk with Windows security mechanisms.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's how it can be done:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Restrict Logins to CyberArk-Managed Accounts – Configure Windows policies so that only accounts managed by CyberArk can log in.&lt;/LI&gt;&lt;LI&gt;Enforce Kerberos Authentication – Block NTLM and ensure that privileged access happens only through PSM via Kerberos.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 26 Feb 2025 17:27:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320639#M20113</guid>
      <dc:creator>S.Vishwakarma290899</dc:creator>
      <dc:date>2025-02-26T17:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320640#M20114</link>
      <description>&lt;P&gt;you're right, Windows Deny Logon policies don’t differentiate between logins through CyberArk PSM and direct logins, and the OS itself isn’t aware of whether access is coming from PSM.&lt;/P&gt;&lt;P&gt;I think better approach is to use controls that enforce PSM-only access by integrating CyberArk with Windows security mechanisms.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's how it can be done:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Restrict Logins to CyberArk-Managed Accounts – Configure Windows policies so that only accounts managed by CyberArk can log in.&lt;/LI&gt;&lt;LI&gt;Enforce Kerberos Authentication – Block NTLM and ensure that privileged access happens only through PSM via Kerberos.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 26 Feb 2025 17:27:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320640#M20114</guid>
      <dc:creator>S.Vishwakarma290899</dc:creator>
      <dc:date>2025-02-26T17:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320641#M20115</link>
      <description>&lt;P&gt;Hi @Jon Musker​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that @Suresh Vishwakarma​&amp;nbsp;provided an answer to your question. Could you kindly let us know if this solution helped?&lt;/P&gt;&lt;P&gt;If so, please mark the answer as 'Select as Best' to assist other community members.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you, Liad&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 11:40:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320641#M20115</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-03-10T11:40:21Z</dc:date>
    </item>
    <item>
      <title>Re: Broker bypass controls as a preventative control</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320642#M20116</link>
      <description>&lt;P&gt;hm, I appreciate the responses @Suresh Vishwakarma​&amp;nbsp;. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Restricting the login accounts is useful, but it doesn't lock me to access from PSM. A malicious user who gained knowledge of a CyberArk-managed account password could login from any machine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards your second suggestion, I haven't figured out how I would use Kerberos to restict RDP access to only come from PSM servers.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 09:34:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/broker-bypass-controls-as-a-preventative-control/m-p/1320642#M20116</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-03-13T09:34:39Z</dc:date>
    </item>
  </channel>
</rss>

