<?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: PSM - Worst Case Scenario. in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350881#M42712</link>
    <description>&lt;P&gt;Sorry, for a formal CyberArk response, I think, you should contact official support, but sometimes official CyberArk representatives also reply here.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Oct 2019 07:59:19 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2019-10-08T07:59:19Z</dc:date>
    <item>
      <title>PSM - Worst Case Scenario.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350878#M42709</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently reviewing a number of items for PCI compliance and Network Level Authentication being disabled on the PSM servers has come up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With CVE 2019-0708 out let’s assume that someone has managed to gain access to a PSM server since NLA was disabled.&lt;/P&gt;&lt;P&gt;What, potentially, could an attacker do from this position?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Could an attacker see what RDP sessions are open?&lt;/LI&gt;&lt;LI&gt;Could an attacker hijack an existing RDP session?&lt;/LI&gt;&lt;LI&gt;Could an attacker capture credentials, either from the user to the PSM or from the PSM to the target server?&lt;/LI&gt;&lt;LI&gt;Other than killing the PSM service and causing a DoS situation, is there anything else related to the PSM that they could accomplish?&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Fri, 04 Oct 2019 21:14:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350878#M42709</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-10-04T21:14:01Z</dc:date>
    </item>
    <item>
      <title>Re: PSM - Worst Case Scenario.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350879#M42710</link>
      <description>&lt;P&gt;1-3 reply is Yes, I would not put here how this can be done, to avoid posting sensitive information.&lt;/P&gt;&lt;P&gt;If you are also using PSM for domain admins and or CyberArk Admins or other tier 0 accounts, then they potentially can do everything within your environment.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Oct 2019 11:24:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350879#M42710</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-10-05T11:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: PSM - Worst Case Scenario.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350880#M42711</link>
      <description>&lt;P&gt;Thanks. I was hoping for a formal CyberArk response. One would hope that CyberArk has added some "secret sauce" around how they handle RDP sessions and the credentials being passed back and forth.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Oct 2019 15:17:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350880#M42711</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-10-07T15:17:10Z</dc:date>
    </item>
    <item>
      <title>Re: PSM - Worst Case Scenario.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350881#M42712</link>
      <description>&lt;P&gt;Sorry, for a formal CyberArk response, I think, you should contact official support, but sometimes official CyberArk representatives also reply here.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2019 07:59:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350881#M42712</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-10-08T07:59:19Z</dc:date>
    </item>
    <item>
      <title>Re: PSM - Worst Case Scenario.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350882#M42713</link>
      <description>&lt;P&gt;Hey @Christopher McNeil​&amp;nbsp;&lt;/P&gt;&lt;P&gt;Officially we recommend installing the patch as recommended by the vendor to resolve the vulnerability. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;-Matt&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2019 11:48:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350882#M42713</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-10-10T11:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: PSM - Worst Case Scenario.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350883#M42714</link>
      <description>&lt;P&gt;Thank Matt. We have applied the patch.&lt;/P&gt;&lt;P&gt;The concern was more around the class of attack (pre-authentication) and disabling NLA (which was a work around for 2019-0708) on the PSM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think we have a good understanding of the issue at this point and are working with our GRC team to get the appropriate signoffs&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2019 15:15:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-worst-case-scenario/m-p/1350883#M42714</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-10-10T15:15:14Z</dc:date>
    </item>
  </channel>
</rss>

