IBM Support

Configuring a sensor to ignore or whitelist traffic from certain IP addresses

Technote (FAQ)


How can you configure a network or host-based sensor to ignore or whitelist traffic from certain internal hosts without creating firewall rules?


For ignoring and/or whitelisting specific traffic on GXs and XGS versions:

Users can use the* advanced tuning parameter to configure a sensor to ignore traffic or events from certain IP addresses. All traffic or events that meet the specified criteria are ignored. Users can add this parameter to the tuning parameters policy in the following contexts:

Filtering IPS events by IP Address (source or destination)

Example Scenario: We have a scanner that is located at that routinely generates many security events during audit scans. Because we know that these events are benign, we do not want our IPS using the extra system resources to process the events. We also do not want to use our SiteProtector database to store all of this unnecessary security event data. We can filter this traffic at the inspection engine level by using the following tuning parameter:

Value: ip addr

There are many different ways the Value field can be completed depending on your needs. Here are some examples of different ways to filter that uses the parameter:

To filter events by Value String example
Single IP (Source or Destination) ip addr
Single Source IP Address ip intruder addr
Single Destination IP Address ip victim addr
All events from/to a Subnet (Using CIDR notation) ip addr
All traffic from/to a range of Addresses ip addr
By defining both intruder and victim IP Addresses ip intruder addr victim addr
Note: To add multiple values, separate them using a comma (with no space).

Filtering IPS events by specific Event ID and IP Address (source or destination)

Example Scenario: We use the RDP_Login audit event to monitor remote access on our admin VLAN. The common management system is We do not want to see the RDP_Login events from this system. In order to filter IPS inspection for this signature that uses the IP address, we first need to find the issueid for RDP_Login. There are two ways that this can be done. You can right-click the event in the Analysis view of the SiteProtector Console and select Open Event Details... or you can look at the PAM help file and find the event there. Both of these sources are considered to be authoritative and provides the issueid for the event that you are looking for. The issueid for RDP_Login is 3113009. Based on this example, we use the following tuning parameter to ignore the traffic:

Value: ip addr

As with the filterall parameter, the filter parameter can use all of the Value variants listed in the previous table.

Using multiple filterall or filter Parameters

It is sometime necessary to add multiple instances of the aforementioned parameters depending on administrative need. For example, you might create one parameter to filter events generated by a vulnerability scanner and another to ignore events for a particular host.

You can add multiple instances of the parameter to filter more than one address entry by adding an index to the parameter name.

Example using multiple filterall parameters:

Value: ip addr

Value: ip addr

Example using multiple filter parameters:

Value: ip addr

Value: ip addr

For disabling PAM inspection for XGS versions and up:

A Do Not Inspect (DNI) option has been added to the Network Access Policy (NAP) to allow whitelisting of all traffic. See, XGS v5.3.2 release notes in technotes:

Cross reference information
Segment Product Component Platform Version Edition
Security IBM Security Network Intrusion Prevention System Protocol Analysis Module (PAM) Platform Independent Version Independent
Security Proventia Virtualized Network Security Platform Not Applicable Platform Independent Version Independent

Historical Number


Document information

More support for: IBM Security Network Protection
Protocol Analysis Module (PAM)

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1436125

Modified date: 07 October 2014

Translate this page: