How to block malicious IP to connect GlobalProtec (Prisma Access)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

How to block malicious IP to connect GlobalProtec (Prisma Access)

L1 Bithead

How do I block malicious IP of connecting to GlobalProtec (Prisma Access), in logs I see many attempts at login on VPN:

 

1.jpg

 

I created a Security Police but I was unsuccessful

 

2.jpg

I opened the ticket with Palo Alto but I believe you don't have much knowledge in Prisma Access to solve the problem.

 

1 accepted solution

Accepted Solutions

L6 Presenter

You can block the "panos-global-protect " application in the security policy but keep in mind that it depends on ssl. You can check the apps at https://applipedia.paloaltonetworks.com/ . Also from your logs I see  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.

 

Also do a policy test from the panorama to see if you are matching the correct rule https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/test-policy-match-and...

 

 

 

It is interesting if you are using globalprotect agent or clientless vpn or Prisma Access in proxy mode where you see this issue.

 

 

Still just in case check for commit issues to the Prisma Access from the panorama https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMb2CAG 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.

 

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.

 

View solution in original post

1 REPLY 1

L6 Presenter

You can block the "panos-global-protect " application in the security policy but keep in mind that it depends on ssl. You can check the apps at https://applipedia.paloaltonetworks.com/ . Also from your logs I see  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.

 

Also do a policy test from the panorama to see if you are matching the correct rule https://docs.paloaltonetworks.com/panorama/10-1/panorama-admin/troubleshooting/test-policy-match-and...

 

 

 

It is interesting if you are using globalprotect agent or clientless vpn or Prisma Access in proxy mode where you see this issue.

 

 

Still just in case check for commit issues to the Prisma Access from the panorama https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMb2CAG 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.

 

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.

 

  • 1 accepted solution
  • 1875 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!