topic Re: PA-500 6.1.4 Policy and URL filtering in General Topics

PA-500 6.1.4 Policy and URL filtering

ITBT — Fri, 16 Oct 2015 06:51:12 GMT

Hi,

I have very big problem with my firewall. I have a few URL filtering rules which I block some of sites.

Example:

1. Allow social network(linkedin) block youtube -> name AllowSN

2. Allow youtube block social network(linkedin) -> name AllowYT

3 and so on

And I create for this URL filtering policies where specific users(by ldap) can access to specif sites.

Example:

1. AD group allow_yt -> url filtering AllowYT

2. AD group allow_sn -> url filtering AllowSN

And I have users who is in all of this groups(allow_yt,allow_sn). In this hierarchy they can access to YT but not social network but when I change policies order they can get to SN but not to YT 😞

Can someone provide information How can I improve my policies that users which are in both group can access to YT and social network?

Thanks for help.

Re: PA-500 6.1.4 Policy and URL filtering

reaper — Fri, 16 Oct 2015 08:47:01 GMT

the security policy will be processed from the top to bottom and once a positive match (source+destination+source user/group+application/port) is made, the security policy will be applied and any subsequent rules are not checked

so what you could try is to create a rule at the top that allows application youtube for the youtube group, then add the rule that allows youtube URL filtering below and then social networking

1. AD group allow_yt -> application YouTube, NO url filtering

2. AD group allow_yt -> url filtering AllowYT

3. AD group allow_sn -> url filtering AllowSN

regards

Tom

Re: PA-500 6.1.4 Policy and URL filtering

ITBT — Fri, 16 Oct 2015 09:48:39 GMT

Thanks for answer.

But how does it work? If security policy are processed from thr top to bottom then someone who is in the group allow_yt and allow_sn will be access to YT but not to SN.

Or am I wrong?

Re: PA-500 6.1.4 Policy and URL filtering

pankaku — Fri, 16 Oct 2015 10:23:12 GMT

Try chaning the order

1. AD group allow_yt -> application YouTube, NO url filtering

2. AD group allow_sn -> url filtering AllowSN

3. AD group allow_yt -> url filtering AllowYT

Re: PA-500 6.1.4 Policy and URL filtering

Raido_Rattameister — Fri, 16 Oct 2015 10:28:40 GMT

You can start with something like this and then tighten it down (allow only limited applications like youtube, web-browsing, ssl etc from www.youtube.com and permit only limited social-networking FQDN's etc).

And change User-Any to your AD group accordingly.

So first 2 rules source user is youtube group and third is social networkng group.

Re: PA-500 6.1.4 Policy and URL filtering

ITBT — Fri, 16 Oct 2015 11:37:31 GMT

Thanks for help.

reaper it doesn't work

pakumar it doesn't work

Raido but I use this type of configuration. So do you think I shoud change to URL Category?

Re: PA-500 6.1.4 Policy and URL filtering

Raido_Rattameister — Fri, 16 Oct 2015 11:49:46 GMT

Security profiles is always my first choice because it keeps security rules cleaner.

But with your requirement you should create security profile and AD group for every possible setup.

- permit youtube

- permit social

- permit youtube and social

Pao (and firewalls in general) evaluate rules from top to bottom.

First rule matches source and destination will be taken into account.

If in first rule you allow HR department to visit social networking sites with security profile but at the same time block streaming media in the same URL filtering profile then person in HR group can never go to youtube (even if same person is also in streaming media group and you allow streaming media with next rule below).

Rules are not mixed together - only one rule will be taken into account.

Re: PA-500 6.1.4 Policy and URL filtering

Raido_Rattameister — Fri, 16 Oct 2015 11:53:15 GMT

By the way "log at session start" should be used only for troubleshooting purpouses.

It generates a lot more log (every application shift) so your log will fill up faster and you can't go back as long as you could with less logging.

Re: PA-500 6.1.4 Policy and URL filtering

Brandon_Wertz — Fri, 16 Oct 2015 12:53:17 GMT

The firewall is a security tool. We should be first asking what's important...What's critical to have. It's annoying that everytime I'm on a TAC call I usually get the "you really shouldn't log on session start" comment.

The problem with not logging on session start is you're only notified when the session has ended (obvious.) The problem with saying "only use it for troubleshooting" is how do you troubleshoot something in the past?

Say for instance an FTP session, that session could be open for minutes, hours, or even days. You'd never be notified about that traffic until the session was closed.

Every one of my rules logs session start. Over 20k user network and we generate about 3 million logs a day. Our Panorama has 2TB of storage and we just shy of 2 months of on box retention.