"-base" applications and how they relate to non-base applications

[joshuahill9]

The term "base" makes this impossible to search for because "application-based" and "port-based" shwo up everywhere. I am not finding an answer in any documentation yet. So, please help me clarify. If I specify the application to be one with the suffix "-base" does that mean it includes all the specializations, or does it mean it is only including the first-ever defined application signature in that category, such as the very first SMB version signature? Maybe it's a third option. 

Yes, in the real world I try to make the rule very relaxed and then see what actually hits the rule, but I have a coworker asking now so we require a better answer - so thank you in advance! 

[TomYoung · Accepted solution]

Hi @joshuahill9 ,

I agree.  There is little documentation on it.  From my understanding, the -base app is like the generic app before more specific apps can be identified.  In the examples below (Objects > Applications ) you see 2 -base apps.  The -base apps do not include other apps.  The "container app" at the top of each example does include all the specific apps listed under it.

PANW also has an online reference.  https://applipedia.paloaltonetworks.com/

Thanks,

Tom

[joshuahill9]

Your response might be the best solution I get, thank you. I will leave it open over the weekend just in case another person responds. Applipedia is definitely a good resource. 

If the -base is the most simple/basic app signature that all specializations will match I guess it could be used as a catch-all after more specific rules. Example - allow smbv3 but then later in the policy list log and drop smb-base in order to identify hosts using out of date protocols - or later in the policy list log and allow smb-base with a stricter antivirus/file/whatnot rules.    If I do get a different solution I will try to delete this reply so I don't confuse others. 

Thanks!