topic Re: Apps vs URL Profile - block application in General Topics

Apps vs URL Profile - block application

migration — Mon, 29 Aug 2011 09:23:27 GMT

Hi all,

I tested this strange (imho) behaviour with PAN 2020 4.0.3:

1. create a first security policy with ssl, http-proxy, dns but without web-browsing application (as you can see in 1.jpg) with action ALLOW

2. create a following security policy with facebook application and action DENY

3. create a final security policy for all other outbound traffic, with action ALLOW ALL for all applications but with a Custom URL Profile that blocks facebook (as you can see in 2.jpg) - all other Sec. Profiles are in alert mode.

(and obviously commit the configuration )

when I try to go to www.facebook.com from my client (the source address of the rules) I get blocked by URL Profile (4th rule) and not by application signature present in the 2nd rule - first match is not respected

If I add web-browsing application in the 1st rule (point 1) and retry to go to www.facebook.com, this time I get blocked by application signature present in 2nd rule - this time first match is respected

If I delete the URL Profile from rule 4 and I delete web-browsing application from 1st rule, I get blocked correctly by the 2nd rule

Why this behaviour?

Thanks in advance

Re: Apps vs URL Profile - block application

jleung — Tue, 30 Aug 2011 03:29:17 GMT

Hi Iceman,

It is expected.

In order to understand your observation, you need to understand our app-id design and app dependency.

Although we have app-id for facebook, but during the life of a facebook session, the initial packet of facebook is actually first recognized as web-browsing before we identify it as facebook. If you are running the facebook app through an explicit proxy, the traffic will be first identified as web-browsing, then http proxy followed by facebook.

So in order to allow facebook, you need to allow web-browsing, http proxy and facebook- and this is called app dependency.

For case1, web-browsing is blocked by your URL filtering so facebook cannot work.

For case2, web-browsing and http proxy are allowed but facebook itself is not and that's why facebook cannot work.

For case3, if you deleted the URL filtering, web-browsing will be allowed by the last policy, http proxy will be allowed by 1st policy, but finally facebook will be blocked by 2nd policy.

Re: Apps vs URL Profile - block application

migration — Tue, 30 Aug 2011 08:33:47 GMT

Thank you.

App dependency is always challanging!

Re: Apps vs URL Profile - block application

jleung — Tue, 30 Aug 2011 13:04:37 GMT

Yes sometimes.