typically you should set up your 'ingress' rules so you allow only what you absolutely need and drop everything else
good practice is to put those rules at the very top of your rulebase so an accidental 'any any' further down doesn't let in any bad things from the internet
a typical layout would be something like this:
-block embargo countries and known malicious IP addresses (from palo EDL for example), set the service to 'any'
-allow inbound server connection (smtp,https,...). make sure you define app-id and ports (app-default is fine, just don't put 'any' in the service)
-allow in/outbound IPSec
-allow inbound GlobalProtect
-drop (this is silent making it 'stealth') all other packets from source untrust (destination ANY so it accounts for NAT rules etc), set the service to 'any'
As @Tom mentioned, if you are hosting admin access on your untrust interface, migrate that access to GlobalProtect as soon as possible (#1 top priority) as this is extremely risky
... View more