<?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: How to block malicious IP to connect GlobalProtec (Prisma Access) in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/how-to-block-malicious-ip-to-connect-globalprotec-prisma-access/m-p/529361#M455</link>
    <description>&lt;P&gt;You can block the "&lt;A id="DetailLink" href="https://applipedia.paloaltonetworks.com/#" target="_blank" rel="noopener"&gt;panos-global-protect &lt;/A&gt;" application in the security policy but keep in mind that it depends on ssl. You can check the apps at &lt;A href="https://applipedia.paloaltonetworks.com/" target="_blank" rel="noopener"&gt;https://applipedia.paloaltonetworks.com/&lt;/A&gt; . Also from your logs I see&amp;nbsp; that probably your Palo alto is intergrated with SAML with Azure AD and you can try to block the IP address also on the Azure AD using conditional Access.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also do a policy test from the panorama to see if you are matching the correct rule &lt;A href="https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/test-policy-match-and-connectivity-for-managed-devices/troubleshoot-policy-rule-traffic-matches" target="_blank" rel="noopener"&gt;https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/test-policy-match-and-connectivity-for-managed-devices/troubleshoot-policy-rule-traffic-matches&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is interesting if you are using globalprotect agent or clientless vpn or Prisma Access in proxy mode where you see this issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Still just in case check for commit issues to the Prisma Access from the panorama &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMb2CAG" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMb2CAG&lt;/A&gt; as maybe Pre rule is not commited the Virtual Firewalls that make up Prisma Access but still for some checks the support can actually connect to the firewalls in the cloud so push them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also there could be a proxy so Prisma Acess may not see the real ip and then you may enable "Trust XFF" if you are doing SSL decryption.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 31 Jan 2023 21:03:19 GMT</pubDate>
    <dc:creator>nikoolayy1</dc:creator>
    <dc:date>2023-01-31T21:03:19Z</dc:date>
    <item>
      <title>How to block malicious IP to connect GlobalProtec (Prisma Access)</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/how-to-block-malicious-ip-to-connect-globalprotec-prisma-access/m-p/528582#M454</link>
      <description>&lt;P&gt;How do I block malicious IP of connecting to GlobalProtec (Prisma Access), in logs I see many attempts at login on VPN:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.jpg" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/47404iE90B6FF8DC39C7E0/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="1.jpg" alt="1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I created a Security Police but I was unsuccessful&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2.jpg" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/47406i64BA6EA642B4D6AE/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="2.jpg" alt="2.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;I opened the ticket with Palo Alto but I believe you don't have much knowledge in Prisma Access to solve the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 16:32:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/how-to-block-malicious-ip-to-connect-globalprotec-prisma-access/m-p/528582#M454</guid>
      <dc:creator>ThacitoPereira</dc:creator>
      <dc:date>2023-01-25T16:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to block malicious IP to connect GlobalProtec (Prisma Access)</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/how-to-block-malicious-ip-to-connect-globalprotec-prisma-access/m-p/529361#M455</link>
      <description>&lt;P&gt;You can block the "&lt;A id="DetailLink" href="https://applipedia.paloaltonetworks.com/#" target="_blank" rel="noopener"&gt;panos-global-protect &lt;/A&gt;" application in the security policy but keep in mind that it depends on ssl. You can check the apps at &lt;A href="https://applipedia.paloaltonetworks.com/" target="_blank" rel="noopener"&gt;https://applipedia.paloaltonetworks.com/&lt;/A&gt; . Also from your logs I see&amp;nbsp; that probably your Palo alto is intergrated with SAML with Azure AD and you can try to block the IP address also on the Azure AD using conditional Access.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also do a policy test from the panorama to see if you are matching the correct rule &lt;A href="https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/test-policy-match-and-connectivity-for-managed-devices/troubleshoot-policy-rule-traffic-matches" target="_blank" rel="noopener"&gt;https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/test-policy-match-and-connectivity-for-managed-devices/troubleshoot-policy-rule-traffic-matches&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is interesting if you are using globalprotect agent or clientless vpn or Prisma Access in proxy mode where you see this issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Still just in case check for commit issues to the Prisma Access from the panorama &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMb2CAG" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMb2CAG&lt;/A&gt; as maybe Pre rule is not commited the Virtual Firewalls that make up Prisma Access but still for some checks the support can actually connect to the firewalls in the cloud so push them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also there could be a proxy so Prisma Acess may not see the real ip and then you may enable "Trust XFF" if you are doing SSL decryption.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jan 2023 21:03:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/how-to-block-malicious-ip-to-connect-globalprotec-prisma-access/m-p/529361#M455</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2023-01-31T21:03:19Z</dc:date>
    </item>
  </channel>
</rss>

