How do I exclude traffic from firewall security services?
03/26/2020 81 10257
At times it's necessary to exclude traffic from security services. This can be necessary when certain applications don't interact well with threat scans, additional throughput is required, or traffic is simply going from trusted device to trusted device. This article will detail how to exclude traffic using a variety of methods, such as IP Address, Port, Signature, etc., from the various SonicWall Threat Engines.
Furthermore this article will describe the different methods of excluding traffic, both by the security services themselves as well as via App Rules.
For the purpose of this article security services will be Gateway Anti-Virus (GAV), Intrusion Prevention (IPS), Anti-Spyware (AS), and App Control. Similar setups will also work for the Botnet Filter and Geo-IP Filter features, although those will not be explicitly touched on.
Excluding Traffic via security service Features
TIP: Using the security service feature itself to exclude traffic is the simpler, although less granular, method that we will begin with. If you'd like more granular control over the type of traffic excluded from security services please use the App Rules method detailed below.
- Login to the SonicWall Management GUI and navigate to the Feature you'd like to exclude traffic for. For App Control navigate to Firewall | App Control, for all other Features navigate to Security Services and select the appropriate option.
- Each feature will have an option for Configure ______ Settings, select that and a pop-up window will appear. From this menu you may select a single Address Object or Address Group to Exclude from the Security Feature. Once you've made your selections, click OK.
TIP: If you have multiple IP Address to Exclude, add them to an Address Group.
NOTE: App Control can inherit Exclusions from IPS by using the Use IPS Exclusion List option.
Excluding Traffic via App Rules
TIP: Excluding Traffic via App Rules allows for more granular control over exemptions but also requires more configuration. If you'd like a quicker, less granular method please use the steps listed above.
- Login to the SonicWall Management GUI and navigate to Firewall | Match Objects.
NOTE: If you want to Exclude Traffic by IP Address or Port, skip to Step 5.
- Select Add New Match Object and a pop-up window will appear.
- Change the Match Object Type field to whatever you wish to use. Typically this will be Application Signature List but any of the available options are valid.
- Select any sub-categories, if necessary, and input any needed values. Click OK.
EXAMPLE: I'd like to Exclude Windows Updates from being subjected to security services. For my Match Object I select the following:
- Match Object Type Application Signature List
- Application Category: APP-UPDATE
- Application: APP-UPDATE Microsoft Windows Updates
- Application Signature: Select each entry, select Add, and repeat until all Signatures are included in the List field.
- Navigate to Firewall | App Rules and select Add New Policy. A pop-up window will appear.
- Set the following information for the App Rule Policy:
- Name - This will be a Friendly Name.
- Policy Type - Set to Custom Policy if you created a Match Object, otherwise set to App Control Content.
- Address | Service | Exclusion Address - Set these as needed. Service is required when going by Ports, Address when going by IP Address.
- Match Object - If you created a Match Object in the earlier steps, select it now. Otherwise leave this blank.
- Action Object - Select the security service you'd like to Bypass, such as IPS.
- Users/Group - Which Users and/or Groups will be included or excluded from this Policy.
- Schedule - You may optionally set a time during which this Policy is in effect.
CAUTION: Remember that if you're creating a Policy which Excludes Traffic from a security service Engine, Excluding an IP Address, User, or Port will effectively exclude them from the exclusion.
- Click OK. You should now see your new Policy in the App Rules Table.
EXAMPLE: In the image below you can see a sample App Rule which exempts all SIP Traffic from the IPS Engine.