topic Re: application override in Automation/API Discussions

application override

lisiecki — Fri, 09 Nov 2012 23:38:12 GMT

Do I require a security rule if I create an application override rule?

Re: application override

SRA — Sat, 10 Nov 2012 00:25:23 GMT

yes, you will need a security policy rule to allow/block the custom app from your app override rule.

Re: application override

mgp — Tue, 25 Jun 2013 03:14:14 GMT

Hi lisiecki,

If we see in https://live.paloaltonetworks.com/docs/DOC-2344, there will be no scanning performed on the session in Application Override.

Re: application override

sraghunandan — Tue, 25 Jun 2013 03:29:53 GMT

Also refer https://live.paloaltonetworks.com/docs/DOC-1071

Re: application override

santonic — Wed, 23 Jul 2014 08:42:16 GMT

I have a related question about application override.

Let's say we created custom app my-telnet.

Then we created an application override rule which identifies traffic let's say from network 10.10.10.0/24 to host 172.24.24.24 on port 24 as my-telnet

In security rules we have a more general rule allowing traffic from 10.0.0.0/8 to 172.24.0.0/16 for all applications on all ports. (so basically custom application my-telnet is not used anywhere in security policy)

Will session from 10.10.10.0/24 to host 172.24.24.24 on port 24 be recognised as my-telnet?

Re: application override

pulukas — Wed, 23 Jul 2014 09:50:17 GMT

you will need to have the specific rule before the general rule for it to be recognized. Firewall rules are processed from top down and stop processing on the first match.

Re: application override

santonic — Wed, 23 Jul 2014 10:38:20 GMT

Thanx for the answer but I think you're wrong.

I've decided to test it; I've created 'myapp' with no protocol/port.. definition.

I've created application override rule saying anything from certain IP address to destination port 222 is 'myapp'

I've created security policy with one rule which allows all traffic for all apps on any port.

Session from the IP address defined in application override rule to port 222 was recognised as 'myapp'