04-07-2011 11:54 AM
Lets say I have rules set up like this...First rule uses a URL Filtering Profile on just port 80/443, and another rule below it that uses the Antivirus and Spyware profile also on just port 80/443. If the first rule allows traffic through, will that traffic be checked by the next rule down(Antivirus/Spyware profile)?? Or is it, once the rule allows traffic, it does not get checked by other rules?
04-07-2011 12:14 PM
Rules are parsed from the top down. 1st matched rule will take effect and skip all subsequent rules. You can have URL filtering, AV, vuln, spyware profiles all on the same rule. If the we site is blocked by URL filtering, then no scanning is needed. If the site is allowed, then all contents transferred will be inspected for virus, vulns, & spyware.
04-07-2011 12:14 PM
Rules are parsed from the top down. 1st matched rule will take effect and skip all subsequent rules. You can have URL filtering, AV, vuln, spyware profiles all on the same rule. If the we site is blocked by URL filtering, then no scanning is needed. If the site is allowed, then all contents transferred will be inspected for virus, vulns, & spyware.
04-08-2011 07:33 AM
The reason I need to seperate the profiles into two different rules is because we are forwarding the logs to our Central Log Manager(QRadar). I set the first rule for just URL Filtering Profile on 80/443, and to "Alert" on allowed sites(I set to "Alert" so I can keep a log in Palo Alto of all the allowed sites). On this rule, I do NOT forward logs to QRadar. If I do, all of the allowed sites show up as "offenses" because they are set to "Alert" in PaloAlto.
I then set up a second rule below this first to run the AV, Spyware, etc. profiles on 80/443. This rule does forward logs to QRadar. BUT, I've been noticing all traffic on 80/443 skips over this second rule after it hits the first rule. I'm not sure if there's any other way to do what I need...
04-08-2011 08:15 AM
URL & threat logs are stored together in the same log database. URL logs have the severity of 'Informational'. You can combine your rules into one rule and have the URL filtering, AV, vuln, spyware enabled. Then set up the log forwarding to forward all threats to QRadar except for informational threats, which contains the URL logs. Granted you also will not forward any informational threats and QRadar will receive all Low to Critical threats.
See screenshot.
04-08-2011 09:06 AM
Good to know that all URL traffic is set to "informational". QRadar not being able to receive "informational" threats is better than QRadar receiving Alerts for every single URL accessed. Thank you for your help!
04-11-2011 08:09 AM
Is there any way to change the "Severity" of threats? Looks like Brute Force Attempts are set to "Informational". Now QRadar doesn't receive any Brute Force Attempts. There's probably other threats defaulted to "Informational" that I may need to change.
04-14-2011 11:49 AM
It looks like you can not change the severity for Vulnerabilities in 3.1 but you can change the default action.
OBJECTS tab >> Security Profiles >> Vulnerability Protection
Click "New" to create a new profile.
Name the profile.
Describe the profile (Optional)
Set "Rule Type" = Custom
Steve Krall
04-14-2011 12:33 PM
Does not work. The vulnerabilities in question are already set to "Alert" as its default Action. BUT, it does not get forwarded because it has a non-configurable severity set to "Informational".
skrall wrote:
It looks like you can not change the severity for Vulnerabilities in 3.1 but you can change the default action.
OBJECTS tab >> Security Profiles >> Vulnerability Protection
Click "New" to create a new profile.
Name the profile.
Describe the profile (Optional)
Set "Rule Type" = Custom
Steve Krall
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!