topic Re: security policy for GlobalProtect in General Topics

security policy for GlobalProtect

ecirclegmbh — Wed, 11 Apr 2012 13:28:07 GMT

which applications/services do i have to enable for GlobalProtect (standard license). I can't find any documentation on this.

actual SW: 4.1.5

Thank you

Re: security policy for GlobalProtect

rmonvon — Wed, 11 Apr 2012 13:45:20 GMT

Hi...Once you complete the configuration for Global Protect, the VPN feature will be active and ready to accept client connections. You define the security rules to allow specific apps/services through for the VPN clients only and not the the VPN feature itself. Let's say you want to permit only ssh traffic for the VPN clients, you would define the security rule to permit app=ssh.

Thanks.

Re: security policy for GlobalProtect

ecirclegmbh — Thu, 12 Apr 2012 07:10:43 GMT

Thank you for your reply.

Ok, no special policy for GlobalProtect.

But the portal doesn't show on https://external-ip

Tried with different authentication profiles.

Any hints?

Cheers

Re: security policy for GlobalProtect

sjamaluddin — Mon, 16 Apr 2012 18:33:03 GMT

Please could you check the configuration and ensure that you have the server certificate configured correctly. You may have to open a support case to ensure the configs are correct. Can you telnet to port 443 on that external interface, that way we can ensure that at least port 443 traffic it making it to the PAN Firewall external interface.

Re: security policy for GlobalProtect

Retired Member — Thu, 26 Apr 2012 13:31:42 GMT

Check your NAT policy,

you shouldnt have any-untrust rule in your nat. You need to be specific in creating NAT rule.

Re: security policy for GlobalProtect

CRT-Capital — Sun, 10 Feb 2013 19:18:44 GMT

I'm running 4.1.10. In order for the PAN to accept client connections (I'm binding the portal to the "outside" interface) I had to create a security rule - "outside zone to outside zone, destination the external interface of the PAN, apps - SSL, web browsing, and panos-global-protect, services http (80) and https (433)." Without this rule clients were not able to connect. BUT this has to do with the fact that I have an explicit deny rule at the bottom of my policy for logging purposes. So, in my case I need to create explicit zone to zone rules (I didn't recreate the hidden same zone to same zone allow rule - this is by design).